code-principles-skill
Skill7 starsChanged 56 days agoApache-2.0View on GitHub
Code principles router — one entry point for clean code, code smells and refactoring, SOLID, design patterns, object design (responsibility-driven), complexity tradeoffs (KISS/YAGNI/DRY), and clean architecture. Routes each design or review question to the right principle route.
In this repository85 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-a11y-skillSkill
- agent-introspection-debugging-skillSkill
- amplify-nextjs-deployment-skillSkill
- architecture-review-skillSkill
- authentication-authorization-skillSkill
- autoresearch-skillSkill
- aws-iac-safety-skillSkill
- blast-radius-skillSkill
- browser-fallback-skillSkill
- cad-dxf-skillSkill
- cad-generation-skillSkill
- cad-implicit-skillSkill
- cad-redraw-skillSkill
- cad-specialist-skillSkill
- cad-viewer-skillSkill
- changelog-python-cliff-skillSkill
- civiltekk-api-spec-skillSkill
- civiltekk-coding-harness-setup-skillSkill
- civiltekk-context-optimization-skillSkill
- civiltekk-diagram-skillSkill
- civiltekk-documentation-inline-skillSkill
- civiltekk-documentation-sync-skillSkill
- civiltekk-git-commits-skillSkill
- civiltekk-nextjs-skillSkill
- referencesSkill
- civiltekk-opencode-creation-skillSkill
- civiltekk-opentofu-skillSkill
- civiltekk-ponytail-audit-skillSkill
- civiltekk-pr-workflow-skillSkill
- civiltekk-python-backend-skillSkill
- civiltekk-react-quality-skillSkill
- civiltekk-startup-docs-skillSkill
- civiltekk-test-generation-skillSkill
- civiltekk-zai-media-skillSkill
- code-review-inline-skillSkill
- construction-bd-skillSkill
- continuous-learning-skillSkill
- coverage-readme-workflow-skillSkill
- database-migration-skillSkill
- deprecated-code-cleanup-skillSkill
- docker-containerization-skillSkill
- domain-modeling-skillSkill
- email-drafter-skillSkill
- error-resolver-workflow-skillSkill
- eval-harness-skillSkill
- frontend-design-skillSkill
- gh-cli-setup-skillSkill
- grilling-skillSkill
- gsap-skillSkill
- horseshoe-paper-writing-skillSkill
- install-assistant-skillSkill
- language-linting-skillSkill
- language-review-checklists-skillSkill
- linting-inline-skillSkill
- linting-workflow-skillSkill
- logging-observability-skillSkill
- monorepo-management-skillSkill
- office-document-router-skillSkill
- opencode-repo-setup-skillSkill
- The first 60 shown.
The file
Files
Code Principles Router
One entry point for code-quality principle questions. Identify the question type, run only the matched route's file, and follow it.
Provenance: routes consolidated from the seven former principle skills (#690). Three routes (clean-code, code-smells, solid-principles) carry opt-in autoresearch iteration-protocol sections — engage them only when the task is an autonomous loop.
Routes (load exactly one)
| Question | Route | Read | Skip-when |
| Readability, naming, small functions | clean-code | references/routes/clean-code.md | smell hunt → code-smells |
| Detect/fix smells + refactoring guidance | code-smells | references/routes/code-smells.md | readability → clean-code |
| SOLID application/review | solid-principles | references/routes/solid-principles.md | concrete smells → code-smells |
| GoF pattern selection/review | design-patterns | references/routes/design-patterns.md | principle questions → solid-principles |
| Responsibility-driven object design | object-design | references/routes/object-design.md | SOLID mechanics → solid-principles |
| KISS/YAGNI/DRY tradeoffs | complexity-management | references/routes/complexity-management.md | smell-level → code-smells |
| Layering, dependency rule, slicing | clean-architecture | references/routes/clean-architecture.md | class-level → object-design |
Route files open with their own Load when / Skip when lines.
Hard rules
- One route per question; if a task spans two (e.g. "refactor this class" = smells + SOLID), run them sequentially — never preload both.
- The three retrofitted routes' iteration-protocol sections are OPT-IN:
engage only for autonomous keep/revert loop tasks (protocol source:
autoresearch-skill). - Each route file owns its detail; this router never restates it.
Gates
- Zero-preload: only the matched route file enters context.
- Findings cite the route file's rules (file:line), not generalities.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

