From dev-skills
Use as a one-time design setup for UI, product, landing-page, or brand-heavy work. Scans the project for design context, asks only the UX questions that cannot be inferred, then writes persistent design guidelines to .design-context.md. Does not implement features or review code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-skills:dev-design-contextThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gather design context for this project, then persist it so future UI work starts with the same visual and product direction.
Gather design context for this project, then persist it so future UI work starts with the same visual and product direction.
This skill is for one-time setup or major design-direction resets. It does not write application code, generate mockups, or review implementation diffs.
Use this skill when the user wants Codex / Claude Code to learn a project's design direction before building UI.
Trigger phrases include:
dev-design-contextsetup design context设计上下文设计规范先建立设计方向gather design contextpersistent design guidelinesOutput goes to .design-context.md in the project root.
执行前先加载 references/dev-baseline.md。以下行为准则在本 skill 全程生效:不假设、最小代码、外科手术式改动、可验证成功标准。
baseline 与本 skill 的关联点:
.design-context.md 的设计上下文,不要顺手改组件、CSS 或产品文案。.design-context.md 已存在,只更新 ## Design Context 相关内容。Before asking questions, scan the project to discover what can be inferred:
Summarize what you learned and what remains unclear before asking the user anything.
Ask the user directly to clarify only what cannot be inferred from the codebase. Keep questions focused and avoid long questionnaires.
Skip questions where the answer is already clear from the codebase exploration.
Synthesize the codebase findings and the user's answers into this section:
## Design Context
### Users
[Who they are, their context, and the job to be done]
### Brand Personality
[Voice, tone, 3-word personality, and emotional goals]
### Aesthetic Direction
[Visual tone, references, anti-references, theme, color, and motion direction]
### Design Principles
[3-5 principles derived from the codebase and conversation that should guide all design decisions]
Write this section to .design-context.md in the project root. If the file already exists, update the ## Design Context section in place instead of duplicating it.
Then ask the user whether they also want the same Design Context appended to .github/copilot-instructions.md. If yes, append or update that section there as well.
Confirm completion and summarize the key design principles that will guide future UI work.
Recommended agent_type: explorer
Use when:
Do:
../../docs/multi-agent-policy.md.Do not:
.design-context.md.Output:
npx claudepluginhub jason-chen-coder/dev-skills --plugin dev-skillsProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.