alirezarezvani-claude-skills / standards
CLAUDE.md31 starsChanged 8 months agoMITView on GitHub
This guide explains how to use the standards library for consistent quality across all skills and agents. Location: standards/ Available Standards: 1. communication/ - Communication principles and response protocols 2. quality/ - Code quality, testing, and validation standards 3. git/ - Git workflow, conventional commits, branching strategy 4. documentation/ - Markdown quality, structure consistency, living docs 5. security/ - Secret detection, dependency security, input validation Reference when: - Writing agent documentation - Creating SKILL.md files - Drafting user-facing content -…
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 103
No hardcoded API keys, passwords, or tokens
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Standards Library - Claude Code Guidance
This guide explains how to use the standards library for consistent quality across all skills and agents.
Standards Overview
Location: standards/
Available Standards:
- communication/ - Communication principles and response protocols
- quality/ - Code quality, testing, and validation standards
- git/ - Git workflow, conventional commits, branching strategy
- documentation/ - Markdown quality, structure consistency, living docs
- security/ - Secret detection, dependency security, input validation
When to Reference Standards
Communication Standards
Reference when:
- Writing agent documentation
- Creating SKILL.md files
- Drafting user-facing content
- Providing technical guidance
Key Principles:
- Absolute honesty - Direct assessments without cushioning
- Zero fluff - Eliminate vague statements
- Pragmatic focus - Actionable suggestions only
- File economy - Edit existing files vs creating new ones
Location: communication/communication-standards.md
Quality Standards
Reference when:
- Creating Python automation tools
- Writing agent workflows
- Implementing skill features
- Testing integration points
Key Areas:
- Python tool quality (PEP 8, type hints, docstrings)
- Agent workflow clarity (minimum 3 workflows documented)
- Testing requirements (functional, integration, documentation)
- Completion criteria (zero defect handoff, validation requirements)
Location: quality/quality-standards.md
Git Workflow Standards
Reference when:
- Committing code changes
- Creating feature branches
- Tagging releases
- Writing commit messages
Commit Format:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]Types: feat, fix, docs, style, refactor, perf, test, chore, ci
Examples:
feat(agents): implement cs-content-creator agent
fix(seo-optimizer): correct keyword density calculation
docs(README): add agent catalog sectionLocation: git/git-workflow-standards.md
Documentation Standards
Reference when:
- Writing SKILL.md files
- Creating agent documentation
- Updating README files
- Writing reference guides
Best Practices:
- Max 200 lines per CLAUDE.md file
- Markdown formatting standards (headings, lists, code blocks)
- Living documentation (README, CLAUDE, AGENTS updated regularly)
- Link validation (no 404s, no broken references)
Location: documentation/documentation-standards.md
Security Standards
Reference when:
- Writing Python scripts
- Handling user input
- Managing dependencies
- Committing code
Critical Checks:
- No hardcoded API keys, passwords, or tokens
- Environment variables for sensitive data
- Input validation for all user input
- Dependency security audits
Location: security/security-standards.md
Standards Application Workflow
For New Skills
# 1. Reference communication standards
cat standards/communication/communication-standards.md
# 2. Review quality standards for Python tools
cat standards/quality/quality-standards.md
# 3. Follow documentation standards for SKILL.md
cat standards/documentation/documentation-standards.md
# 4. Apply security standards to scripts
cat standards/security/security-standards.md
# 5. Use git standards for commits
cat standards/git/git-workflow-standards.mdFor New Agents
# 1. Communication: Write clear, actionable agent docs
# 2. Quality: Minimum 3 workflows, tested relative paths
# 3. Documentation: Follow agent template structure
# 4. Git: Conventional commit with feat(agents) scopeStandards Hierarchy
Priority Order:
- Security - Non-negotiable, always enforced
- Quality - Zero defect handoff required
- Git - Conventional commits for all changes
- Documentation - Living docs stay current
- Communication - Clear, pragmatic, actionable
Standards Compliance Checklist
Before Committing Code
- Communication: Documentation is clear and actionable
- Quality: All tests passing, code reviewed
- Git: Conventional commit message format
- Documentation: Living docs updated if needed
- Security: No secrets, input validated, dependencies secure
Before Creating PR
- All standards compliance checks passed
- Related documentation updated
- Examples tested and working
- No broken links or references
Related Documentation
- Main CLAUDE.md:
../CLAUDE.md - Agent Development:
../agents/CLAUDE.md - Domain Skills: See navigation map in main CLAUDE.md
Last Updated: November 5, 2025 Standards Count: 5 comprehensive standards Enforcement: Required for all skills and agents
Other versions35 projects use a version of this.
Word for word · 35
- alirezarezvani/claude-skills★ 29k100% same
- borghei/Claude-Skills★ 978100% same
- zhangzhang-111-i/claude-skills111★ 3100% same
- afaizalam2003/Master-claude-skill★ 2100% same
- Mogerinho/Claude-Skills-Turkish★ 2100% same
- sohaibdevv/claude-skills★ 2100% same
- Adarshukumar/skills★ 1100% same
- ai-integr8tor/alirezarezvani-claude-skills★ 1100% same
- AlexBramall/claude-code-skills★ 1100% same
- emiiblesstm-star/claude-skills★ 1100% same
25 more not listed
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- agents/CLAUDE.mdCLAUDE.md
- business-growth/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- c-level-advisor/CLAUDE.mdCLAUDE.md
- engineering-team/CLAUDE.mdCLAUDE.md
- finance/CLAUDE.mdCLAUDE.md
- marketing-skill/CLAUDE.mdCLAUDE.md
- product-team/CLAUDE.mdCLAUDE.md
- project-management/CLAUDE.mdCLAUDE.md
- ra-qm-team/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- business-growth-skillsSkill
- c-level-advisorSkill
- engineering-advanced-skillsSkill
- engineering-skillsSkill
- finance-skillsSkill
- marketing-skillsSkill
- product-skillsSkill
- pm-skillsSkill
- ra-qm-skillsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

