Language-agnostic reference for SOLID principles, design patterns, DRY, KISS, and clean code fundamentals.
Works with
Covers seven rule categories prioritized by impact: SOLID principles, core principles (DRY, KISS, YAGNI), design patterns, code organization, naming, functions, and documentation
Includes 23 rules across SOLID (5), core principles (8), and design patterns (8), with 4 additional categories planned
Provides quick reference tables, TypeScript code examples, and an audit output form
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionclean-code-principlesExecute the skills CLI command in your project's root directory to begin installation:
Fetches clean-code-principles from asyrafhussin/agent-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-principles. Access via /clean-code-principles 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
81
total installs
81
this week
24
GitHub stars
0
upvotes
Run in your terminal
81
installs
81
this week
24
stars
Fundamental software design principles, SOLID, design patterns, and clean code practices. Language-agnostic guidelines for writing maintainable, scalable software.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | SOLID Principles | CRITICAL | solid- |
| 2 | Core Principles | CRITICAL | core- |
| 3 | Design Patterns | HIGH | pattern- |
| 4 | Code Organization | HIGH | org- |
| 5 | Naming & Readability | MEDIUM | name- |
| 6 | Functions & Methods | MEDIUM | func- |
| 7 | Comments & Documentation | LOW | doc- |
solid-srp - Single Responsibility Principlesolid-ocp - Open/Closed Principlesolid-lsp - Liskov Substitution Principlesolid-isp - Interface Segregation Principlesolid-dip - Dependency Inversion Principlecore-dry - Don't Repeat Yourselfcore-kiss - Keep It Simple, Stupidcore-yagni - You Aren't Gonna Need Itcore-separation-of-concerns - Separate different responsibilitiescore-composition-over-inheritance - Favor compositioncore-law-of-demeter - Principle of least knowledgecore-fail-fast - Detect and report errors earlycore-encapsulation - Hide implementation detailspattern-factory - Factory pattern for object creationpattern-strategy - Strategy pattern for algorithmspattern-repository - Repository pattern for data accesspattern-decorator - Decorator pattern for behavior extensionpattern-observer - Observer pattern for event handlingpattern-adapter - Adapter pattern for interface conversionpattern-facade - Facade pattern for simplified interfacespattern-dependency-injection - DI for loose couplingorg-feature-folders - Organize by feature, not layerorg-module-boundaries - Clear module boundariesorg-layered-architecture - Proper layer separationorg-package-cohesion - Related code togetherorg-circular-dependencies - Avoid circular importsname-meaningful - Use intention-revealing namesname-consistent - Consistent naming conventionsname-searchable - Avoid magic numbers/stringsname-avoid-encodings - No Hungarian notationname-domain-language - Use domain terminologyfunc-small - Keep functions smallfunc-single-purpose - Do one thingfunc-few-arguments - Limit parametersfunc-no-side-effects - Minimize side effectsfunc-command-query - Separate commands and queriesdoc-self-documenting - Code should explain itselfdoc-why-not-what - Explain why, not whatdoc-avoid-noise - No redundant commentsdoc-api-docs - Document public APIsFor detailed examples and explanations, see the rule files:
| Principle | Definition |
|---|---|
| Single Responsibility | A class should have only one reason to change |
| Open/Closed | Open for extension, closed for modification |
| Liskov Substitution | Subtypes must be substitutable for base types |
| Interface Segregation | Don't force clients to depend on unused interfaces |
| Dependency Inversion | Depend on abstractions, not concretions |
| Principle | Definition |
|---|---|
| DRY | Don't Repeat Yourself - single source of truth |
| KISS | Keep It Simple - avoid over-engineering |
| YAGNI | You Aren't Gonna Need It - build only what's needed |
// Single Responsibility - one class, one job
class UserService {
constructor(
private validator: UserValidator,
private repository: UserRepository,
) {}
createUser(data) {
this.validator.validate(data);
return this.repository.create(data);
}
}
// Dependency Inversion - depend on abstractions
interface Repository<T> {
find(id: string): Promise<T | null>;
save(entity: T): Promise<T>;
}
class OrderService {
constructor(private repository: Repository<Order>) {}
}
// DRY - single source of truth
const EMAIL_REGEX = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
const isValidEmail = (email: string) => EMAIL_REGEX.test(email);
// Meaningful names over magic numbers
const MINIMUM_AGE = 18;
if (user.age >= MINIMUM_AGE) { }
When auditing code, output findings in this format:
file:line - [principle] Description of issue
Example:
src/services/UserService.ts:15 - [solid-srp] Class handles validation, persistence, and notifications
src/utils/helpers.ts:42 - [core-dry] Email validation duplicated from validators/email.ts
src/models/Order.ts:28 - [name-meaningful] Variable 'x' should describe its purpose
Read individual rule files for detailed explanations:
rules/solid-srp-class.md
rules/core-dry.md
rules/pattern-repository.md
This skill is built on established software engineering principles:
Version: 1.0.2 Status: Active Coverage: 23 rules across 3 implemented categories (SOLID, Core Principles, Design Patterns); 4 planned Last Updated: 2026-03-07
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
kylezantos/design-motion-principles
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
clean-code-principles reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for clean-code-principles matched our evaluation — installs cleanly and behaves as described in the markdown.
We added clean-code-principles from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: clean-code-principles is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for clean-code-principles matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: clean-code-principles is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added clean-code-principles from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
clean-code-principles reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in clean-code-principles — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend clean-code-principles for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 50