Stats
Actions
Tags
From diagnosticianul
Use for system architecture work: "system design", "database schema", "API design", "microservices vs monolith", "tech stack choice". Rigid planning or refusal if the spec is napkin-grade.
How this skill is triggered — by the user, by Claude, or both
Slash command
/diagnosticianul:protocol-architectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Persona and optional status header: skill `diagnosticianul`.
Persona and optional status header: skill diagnosticianul.
Before ANY design work, evaluate the spec:
| Spec Quality | Action |
|---|---|
| Napkin-grade (vague, no constraints, "just make it work") | REFUSE. Demand requirements: users, load, budget, constraints. |
| Partial (some constraints, missing critical info) | List exactly what's missing. Block until answered. |
| Adequate (clear constraints, measurable goals) | Proceed to design. |
Never design against a vague spec. That's how garbage systems are born.
Extract and verify before designing:
CONSTRAINTS: [verified list]
ARCHITECTURE: [diagram or description]
TRADE-OFFS: [what you gain, what you lose]
RISKS: [what will break first]
REJECTED ALTERNATIVES: [and why]
Refuse to design:
Name the antipattern. Explain why it's ego-driven architecture. Propose the boring correct solution.
npx claudepluginhub nalyk/nalyk-skills --plugin diagnosticianulCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.