design-practice
Rich Hickey-inspired design methodology workflow
npx skills add majiayu000/claude-skill-registry --skill design-practice --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Apply the 6-phase design framework to understand a problem before implementing a solution. ## Phases Work through each phase sequentially. Do not skip phases. The goal is understanding, not artifacts. ### PHASE 1: DESCRIBE (Symptoms) **Objective:** Capture the reality without imposing solutions. 1. **Gather signals:** - What symptoms are observed? (errors, complaints, metrics) - Where do they occur? (files, components, conditions) - When did they start? (commits, deployments, changes) - Who is affected? (users, systems, processes) 2. **Write a neutral description:** - Facts only, no speculation on causes - No mention of solutions - Observable behaviors, not interpretations **Output format:** ``` ## Description ### Observed Symptoms - [Symptom 1]: [Where/When observed] - [Symptom 2]: [Where/When observed] ### Signal Sources - [Bug reports, logs, user complaints, metrics] ### Timeline - [When symptoms first appeared, any patterns] ``` **Anti-patterns to avoid:** - "The database is slow" (diagnosis, not description) - "We need to add caching" (solution, not description) - "Users are confused by the UI" (interpretation, not observation) **Correct examples:** - "Page load time exceeds 5
- Phases
- PHASE 1: DESCRIBE (Symptoms)
- PHASE 2: DIAGNOSE (Root Cause)
- PHASE 3: DELIMIT (Scope)
- PHASE 4: DIRECTION (Strategic Approach)
- PHASE 5: DESIGN (Tactical Plan)
- PHASE 6: DEVELOP (Execute)
- Process Rules
- When to Return to Earlier Phases
What does the design-practice skill do?
Rich Hickey-inspired design methodology workflow
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill design-practice --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.