This skill is the authoritative clean code standard for this repository's shared skills. It defines stable rule IDs (CC-*), how to apply them in reviews, and how to extend them safely via language overlays and explicit exceptions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsoftware-clean-code-standardExecute the skills CLI command in your project's root directory to begin installation:
Fetches software-clean-code-standard from vasilyu1983/ai-agents-public and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate software-clean-code-standard. Access via /software-clean-code-standard in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
53
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
53
stars
This skill is the authoritative clean code standard for this repository's shared skills. It defines stable rule IDs (CC-*), how to apply them in reviews, and how to extend them safely via language overlays and explicit exceptions.
Modern Best Practices (January 2026): Prefer small, reviewable changes and durable change context. Use RFC 2119 normative language consistently. Treat security-by-design and secure defaults as baseline (OWASP Top 10, NIST SSDF). Build observable systems (OpenTelemetry). For durable links and current tool choices, consult data/sources.json.
| Task | Tool/Framework | Command | When to Use |
|---|---|---|---|
| Cite a standard | CC-* rule ID |
N/A | PR review comments, design discussions, postmortems |
| Categorize feedback | CC-NAM, CC-ERR, CC-SEC, etc. |
N/A | Keep feedback consistent without "style wars" |
| Add stack nuance | Language overlay | N/A | When the base rule is too generic for a language/framework |
| Allow an exception | Waiver record | N/A | When a rule must be violated with explicit risk |
| Reuse shared checklists | assets/checklists/ |
N/A | When you need product-agnostic review/release checklists |
| Reuse utility patterns | references/*-utilities.md |
N/A | When extracting shared auth/logging/errors/resilience/testing utilities |
CC-* IDs and avoid restating standards in reviews.CC-* IDs.CC-SEC-* baseline.Feedback needed: [What kind of guidance is this?]
├─ Universal, cross-language rule? → Add/modify `CC-*` in `references/clean-code-standard.md`
│
├─ Language/framework-specific nuance? → Add overlay entry referencing existing `CC-*`
│
└─ One-off constraint or temporary tradeoff?
├─ Timeboxed? → Add waiver with expiry + tracking issue
└─ Permanent? → Propose a new rule or revise scope/exception criteria
Resources
data/sources.jsonTemplates
Utility Patterns
Related Skills
CC-* IDsCC-SEC-*CC-* IDs (linters, SAST, dependency scanning) so humans can review impact, not tooling noise.IMPORTANT: When users ask recommendation questions about clean code standards, linters, or code quality tools, you MUST use a web search capability (if available) to check current trends before answering. If web search is unavailable, say so and answer using data/sources.json, clearly flagging that the recommendation may be stale.
"clean code best practices 2026""[specific linter] vs alternatives 2026""code quality tools trends 2026""[language] linter comparison 2026"After searching, provide:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
asyrafhussin/agent-skills
shadcn/improve
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
We added software-clean-code-standard from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
software-clean-code-standard reduced setup friction for our internal harness; good balance of opinion and flexibility.
software-clean-code-standard is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
software-clean-code-standard reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added software-clean-code-standard from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: software-clean-code-standard is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added software-clean-code-standard from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
software-clean-code-standard is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: software-clean-code-standard is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: software-clean-code-standard is focused, and the summary matches what you get after install.
showing 1-10 of 30