agentsclimarketplace

Design rules

Skill hex0xdeadbeef/claude-kit/.claude/skills/design-rules

Design phase rules for /designer command. Load at /designer startup (step 0). Covers spec quality, design checklist, approach evaluation criteria.From its SKILL.md

Install
npx -y skills add hex0xdeadbeef/claude-kit --skill design-rules

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

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

2.7 KB, as published. Nobody here has run it

Design Rules

Purpose

Guidelines for the /designer command to produce high-quality design specs that reduce plan-review iterations.

Instructions

Step 1: Load at /designer startup

Read this SKILL.md for overview. Supporting files loaded on-demand per phase.

Step 2: Use phase-driven loading

  • Phase 3 (PROPOSE) → read Spec Quality for approach evaluation criteria
  • Phase 3.5 (CRITIQUE) → read Critique Lenses for the adversarial lens set + disposition forcing-function
  • Phase 4 (WRITE SPEC) → read Design Checklist for self-verification
  • Phase 5 (USER GATE) → verify checklist before presenting to user

Spec Quality Criteria

CriterionRequiredCheck
Context describes current stateYesNot just "add X" but "currently Y exists, need X because Z"
Scope has IN and OUTYesOUT items have explicit reasons
At least 2 approaches comparedYesWith pros/cons for each
Selected approach has rationaleYesReferences constraints from requirements
Key decisions are numberedYesEach has rationale and impact
Risks have severity and mitigationYesHIGH risks must have concrete mitigation
Acceptance criteria are verifiableYesEach can be checked as pass/fail

Anti-Patterns

Anti-PatternWhy BadFix
"The obvious approach is..."Skips exploration, may miss better optionsAlways compare at least 2
Spec without OUT scopeScope creep during planningExplicitly list what's excluded
Vague acceptance criteria ("works well")Can't verifyMake criteria concrete and testable
No risks identifiedEvery design has risksIdentify at least 1 per approach
Copying task description as contextNo analysisDescribe current state, not just goal

Common Issues

Designer skips CLARIFY phase

Cause: Task seems clear. Fix: Even "clear" tasks benefit from scope IN/OUT confirmation. At minimum, confirm scope.

User rejects all approaches

Cause: Missing constraint not captured. Fix: Ask: "What constraint am I missing?" — don't generate more approaches without new information.

References

Keep looking

Skills are one crate of 614,496. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.