design-research
Conduct research and create design documents before implementation. Use when analyzing requirements, exploring solutions, creating architecture designs, or investigating codebase patterns. Invoked by: "research", "design", "analyze", "investigate", "explore codebase".
npx skills add majiayu000/claude-skill-registry --skill design-research --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.
# Research and Design Process SOP **Version**: 1.0.0 **Last Updated**: 2026-01-11 **Status**: Active --- ## Overview ### Purpose This process is the critical first phase before creating a design document. It ensures the user request is fully understood, the codebase is thoroughly analyzed, multiple solutions are considered, and the best approach is selected with solid foundation for design. ### When to Use **ALWAYS**: New features, complex refactorings, architectural changes, breaking changes **SKIP**: Simple bug fixes, trivial changes, explicit implementation instructions --- ## Process Workflow ### Flow Diagram ``` [User Request] --> [Request Understanding] --> [Repository Analysis] | v [Solution Exploration] --> [Recommendation & Decision] | v [Design Document] ``` ### Phase Summary | Phase | Duration | Focus | |-------|----------|-------| | 1. Request Understanding | 10-20 min | Clarify requirements | | 2. Repository Analysis | 20-40 min | Understand codebase | | 3. Solution Exploration | 15-30 min | Generate alternatives | | 4. Recommendation | 5-10 min | Document & approve | **Total Duration**: 50-90 minutes --- ## Key Principles 1. **Conversation First** - Collaborative, not
- Overview
- Purpose
- When to Use
- Process Workflow
- Flow Diagram
- Phase Summary
- Key Principles
- Research Agent Responsibilities
- Must Do
- Must NOT Do
- Phase 1: Request Understanding
- Quick Checklist
- Questions to Ask
- Phase 2: Repository Analysis
Find components Find pages/screens/views Find state management Find routing/navigation Find tests
What does the design-research skill do?
Conduct research and create design documents before implementation. Use when analyzing requirements, exploring solutions, creating architecture designs, or investigating codebase patterns. Invoked by: "research", "design", "analyze", "investigate", "explore codebase".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill design-research --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.