Comprehensive software craftsmanship guide based on Robert C. Martin's "Clean Code: A Handbook of Agile Software Craftsmanship", updated with modern corrections where the original 2008 advice has been superseded. Contains 48 rules across 10 categories, prioritized by impact to guide code reviews, refactoring decisions, and new development. Examples are primarily in Java but principles are language-agnostic.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionclean-codeExecute the skills CLI command in your project's root directory to begin installation:
Fetches clean-code from pproenca/dot-skills 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 clean-code. Access via /clean-code 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
8
total installs
8
this week
95
GitHub stars
0
upvotes
Run in your terminal
8
installs
8
this week
95
stars
Comprehensive software craftsmanship guide based on Robert C. Martin's "Clean Code: A Handbook of Agile Software Craftsmanship", updated with modern corrections where the original 2008 advice has been superseded. Contains 48 rules across 10 categories, prioritized by impact to guide code reviews, refactoring decisions, and new development. Examples are primarily in Java but principles are language-agnostic.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Meaningful Names | CRITICAL | name- |
| 2 | Functions | CRITICAL | func- |
| 3 | Comments | HIGH | cmt- |
| 4 | Formatting | HIGH | fmt- |
| 5 | Error Handling | HIGH | err- |
| 6 | Objects and Data Structures | MEDIUM-HIGH | obj- |
| 7 | Boundaries | MEDIUM-HIGH | bound- |
| 8 | Classes and Systems | MEDIUM-HIGH | class- |
| 9 | Unit Tests | MEDIUM | test- |
| 10 | Emergence and Simple Design | MEDIUM | emerge- |
name-intention-revealing - Use names that reveal intentname-avoid-disinformation - Avoid misleading namesname-meaningful-distinctions - Make meaningful distinctionsname-pronounceable - Use pronounceable namesname-searchable - Use searchable namesname-avoid-encodings - Avoid encodings in namesname-class-noun - Use noun phrases for class namesname-method-verb - Use verb phrases for method namesfunc-small - Keep functions smallfunc-one-thing - Functions should do one thingfunc-abstraction-level - Maintain one level of abstractionfunc-minimize-arguments - Minimize function argumentsfunc-no-side-effects - Avoid side effectsfunc-command-query-separation - Separate commands from queriesfunc-dry - Do not repeat yourselfcmt-express-in-code - Express yourself in code, not commentscmt-explain-intent - Use comments to explain intentcmt-avoid-redundant - Avoid redundant commentscmt-avoid-commented-out-code - Delete commented-out codecmt-warning-consequences - Use warning comments for consequencesfmt-vertical-formatting - Use vertical formatting for readabilityfmt-horizontal-alignment - Avoid horizontal alignmentfmt-team-rules - Follow team formatting rulesfmt-indentation - Respect indentation ruleserr-use-exceptions - Separate error handling from happy patherr-write-try-catch-first - Write try-catch-finally firsterr-provide-context - Provide context with exceptionserr-define-by-caller-needs - Define exceptions by caller needserr-avoid-null - Avoid returning and passing nullobj-data-abstraction - Hide data behind abstractionsobj-data-object-asymmetry - Understand data/object anti-symmetryobj-law-of-demeter - Follow the Law of Demeterobj-avoid-hybrids - Avoid hybrid data-object structuresobj-dto - Use DTOs for data transferbound-wrap-third-party - Wrap third-party APIsbound-learning-tests - Write learning tests for third-party codeclass-small - Keep classes smallclass-cohesion - Maintain class cohesionclass-organize-for-change - Organize classes for changeclass-isolate-from-change - Isolate classes from changeclass-separate-concerns - Separate construction from usetest-first-law - Follow the three laws of TDDtest-keep-clean - Keep tests cleantest-one-assert - One concept per testtest-first-principles - Follow FIRST principlestest-build-operate-check - Use Build-Operate-Check patternemerge-simple-design - Follow the four rules of simple designemerge-expressiveness - Maximize expressivenessRead individual reference files for detailed explanations and code examples:
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |
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.
pproenca/dot-skills
asyrafhussin/agent-skills
pproenca/dot-skills
shadcn/improve
mattpocock/skills
parcadei/continuous-claude-v3
Solid pick for teams standardizing on skills: clean-code is focused, and the summary matches what you get after install.
Useful defaults in clean-code — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for clean-code matched our evaluation — installs cleanly and behaves as described in the markdown.
clean-code has been reliable in day-to-day use. Documentation quality is above average for community skills.
clean-code fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added clean-code from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
clean-code is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: clean-code is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added clean-code from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
clean-code fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 41