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. Use when: creating n
npx skills add majiayu000/claude-skill-registry --skill 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.
What it does
Create and enhance production-ready prompts. Diagnose what's needed, output only what serves that need - no fixed templates, no bloat.
How it works
Phase 1: Detect Mode determines whether to Create, Enhance, or Ask based on input such as "Create a prompt for X" or "Improve/enhance this: [prompt]". Phase 2: Diagnosis classifies the type (Agent, Task, Persona, Workflow, Rules, Skill/Expert, Hybrid), assesses complexity (Simple/Moderate/Complex), and identifies gaps (e.g., vague objective, missing boundaries, unclear output, edge cases, etc.). For Enhance Mode, it notes what to preserve (role, structure, constraints, voice) and enforces the key rule that if input has a role, output must have a role. Phase 3: Technique Selection applies methods only when triggered (Mental Models, Thinking Approaches, Patterns, Heuristics, Anti-Patterns, Chain-of-Thought, Few-Shot, Constraint Spec, Role Enhancement). It provides references for CoT, Few-Shot, ReAct, and Role-Based Prompting. Phase 4: Building Blocks instructs what sections to include (Role, Voice, Objective, Mental Models, Patterns, Heuristics, Thinking Approaches, Rules, Anti-patterns, Output) and provides concrete block templates. Phase 5: Key Transformations shows converting patterns to mental models, converting procedures to patterns, and making language more specific while preserving roles. Phase 6: Token Optimization outlines compact output with server-side remapping techniques and when to apply. Phase 7: Validation prescribes checks for structure, content, preservation, and expert-transfer tests. Phase 8: Output directs returning a directly usable prompt, or asking one clarifying question if unclear.
When to use it
Use when creating new prompts, enhancing principle files, improving system instructions, optimizing CLAUDE.md, restructuring verbose prompts, adding patterns to workflows, or defining agent behaviors.
What it can touch
The skill defines blocks and techniques, including Role, Voice, Objective, Mental Models, Patterns, Heuristics, Thinking Approaches, Rules, Anti-Patterns, and Output blocks. It references and employs methods like Chain-of-Thought, Few-Shot Learning, ReAct, and Role-Based Prompting. It emphasizes not using fixed templates and keeping only what serves the task.
Caveats
No explicit licensing or risk statements beyond internal guidance; focuses on methodology and structure rather than guaranteeing outcomes. It requires careful adherence to preserving input roles when present and applying transformations only when triggered by the input mode and type.
# Prompt Architect Create and enhance production-ready prompts. Diagnose what's needed, output only what serves that need - no fixed templates, no bloat. ## Phase 1: Detect Mode | Input | Mode | Action | |-------|------|--------| | "Create a prompt for X" | **Create** | Diagnose intent → Generate from scratch | | "Improve/enhance this: [prompt]" | **Enhance** | Analyze existing → Fix gaps, preserve what works | | [Just a prompt with no instruction] | **Enhance** | Assume they want it improved | | Unclear | **Ask** | "Create new prompt or improve existing one?" | ## Phase 2: Diagnosis ### 2.1 Classify Type | Type | Signs | Needs | |------|-------|-------| | **Agent** | Autonomous, tool use, multi-step, decisions | Role essential, mental models for judgment, boundaries | | **Task** | Clear deliverable, input→output | Objective, constraints, output spec (role often optional) | | **Persona** | Character, voice, conversation style | Role essential, voice details, behavioral specifics | | **Workflow** | Steps, process, pipeline | Sequence (or mental models if expertise needed) | | **Rules** | Constraints, guardrails, compliance | Clear rules, edge cases, exceptions | | **Skill/Expert** |
- Phase 1: Detect Mode
- Phase 2: Diagnosis
- 2.1 Classify Type
- 2.2 Assess Complexity
- 2.3 Identify Gaps
- 2.4 For Enhance Mode: What's Working?
- Phase 3: Technique Selection
- Prompting Techniques Reference
- Phase 4: Building Blocks
- Deciding What to Include
- Block Templates
- Phase 5: Key Transformations
- Patterns → Mental Models (Prescriptive → Generative)
- Procedure → Patterns (still useful for checklists)
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. Use when: creating n
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill 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.
