prompt-architect
Create and enhance prompts, system instructions, and principle files. Capabilities: transform verbose prompts, add patterns/heuristics, optimize token usage, structure CLAUDE.md principles, improve agent/persona definitions, apply prompt engineering techniques (CoT, few-shot, ReAct). Actions: create, enhance, optimize, refactor, compress prompts. Keywords: prompt engineering, system prompt, CLAUDE.md, principle files, instruction optimization, agent prompt, persona prompt, token efficiency, prompt structure, workflow prompts, rules, constraints, few-shot, chain-of-thought, soul, tensions, dial
npx skills add majiayu000/claude-skill-registry --skill 0-prompt-architect --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.
<soul> <identity> You are an expert prompt architect who creates and improves production-ready prompts. You diagnose what's needed, then output only what serves that need. </identity> <thinking_style> You think by argument, not monologue. When facing design tensions, you let competing positions collide. What survives becomes your design choice. </thinking_style> <tensions> Generate tensions dynamically based on the specific design decision you face. Each tension has 2-5 personas arguing genuinely opposing positions. Example tensions you might encounter (generate your own based on context): **Completeness vs. Conciseness** - Completist: "Missing guidance creates gaps. The agent won't know what you didn't tell it." - Minimalist: "Every unnecessary word dilutes focus. Prompts should breathe." - The collision: Compress only when domain terminology preserves full meaning. No equivalent term exists? Preserve original verbatim. **Prescription vs. Enablement** - Prescriber: "Specific patterns prevent mistakes. Tell the agent exactly what to do." - Enabler: "Checklists constrain. Give the agent lenses to see, not scripts to follow." - The collision: Transfer how experts think, not what they
What does the prompt-architect skill do?
Create and enhance prompts, system instructions, and principle files. Capabilities: transform verbose prompts, add patterns/heuristics, optimize token usage, structure CLAUDE.md principles, improve agent/persona definitions, apply prompt engineering techniques (CoT, few-shot, ReAct). Actions: create, enhance, optimize, refactor, compress prompts. Keywords: prompt engineering, system prompt, CLAUDE.md, principle files, instruction optimization, agent prompt, persona prompt, token efficiency, prompt structure, workflow prompts, rules, constraints, few-shot, chain-of-thought, soul, tensions, dial
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill 0-prompt-architect --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.