Design principles

Skill jagreehal/jagreehal-claude-skills/skills/design-principles

Applies software design rules beyond syntax (fail-fast, explicit over implicit, composition, illegal states unrepresentable) and runs structured design analysis. Use this skill when reviewing or refactoring for design quality, naming, coupling, or type safety. Do not use when/for UI visual design (use ui-design-principles) or enforcing only fn(args, deps) syntax (use fn-args-deps).From its SKILL.md

Install

npx -y skills add jagreehal/jagreehal-claude-skills --skill design-principles

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, as published. Nobody here has run it

Design Principles

Critical rules

Make the safe thing explicit and the wrong thing unrepresentable.
Fail fast with context — no ?? chains hiding missing data.
No any / as without approval; prefer guards, unions, Zod.
Explicit deps (fn(args, deps)); domain names; immutability by default; no clarifying comments.
For structured review: run all 8 analysis dimensions after code-flow-analysis.
Before applying rules or running analysis, read references/principles.md and references/design-analysis.md.

Workflow

If reviewing a module: invoke code-flow-analysis until structure and behavior are clear.
Apply critical principles (fail-fast, types, naming, immutability, YAGNI, calisthenics) — detail in references/principles.md.
For formal review, evaluate all 8 dimensions in references/design-analysis.md.
Report findings with severity, file:line, snippets, and concrete fixes only.
Do not suggest speculative abstractions or unmeasured performance tweaks.

Resources

references/principles.md — fail-fast, unions, naming, immutability, YAGNI, rationalizations. Read when refactoring.
references/design-analysis.md — 8-dimension protocol and report format. Read for design reviews.

Validation

Code understood via code-flow-analysis before findings
All 8 dimensions covered when doing formal analysis
Every finding has file:line and a real snippet
No unflagged any/as/@ts-ignore; no ?? fallback chains
Illegal states modeled as unions where applicable; domain names used

Constraints

Not for prose/article quality (spine-framework, structured-writing) or large multi-module architecture (system-architecture).
Related: fn-args-deps, result-types, strict-typescript, code-flow-analysis, critical-peer.