design rules

Design Community

Skill notes

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 4 (WRITE SPEC) → read Design Checklist for self-verification Phase 5 (USER GATE) → verify checklist before presenting to user

Spec Quality Criteria

Criterion · Required · Check Context describes current state · Yes · Not just "add X" but "currently Y exists, need X because Z" Scope has IN and OUT · Yes · OUT items have explicit reasons At least 2 approaches compared · Yes · With pros/cons for each Selected approach has rationale · Yes · References constraints from requirements

Anti-Patterns

Anti-Pattern · Why Bad · Fix "The obvious approach is..." · Skips exploration, may miss better options · Always compare at least 2 Spec without OUT scope · Scope creep during planning · Explicitly list what's excluded Vague acceptance criteria ("works well") · Can't verify · Make criteria concrete and testable No risks identified · Every design has risks · Identify at least 1 per approach

Designer skips CLARIFY phase

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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@hex0xdeadbeef · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Load at /designer startup

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

02
Step 2: Use phase-driven loading

Phase 3 (PROPOSE) → read Spec Quality for approach evaluation criteria Phase 4 (WRITE SPEC) → read Design Checklist for self-verification Phase 5 (USER GATE) → verify checklist before presenting to user

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.