@repo-phuocdt/prompt-engineer
ATransform rough prompts/ideas into production-ready LLM prompts. Use when crafting, refining, or optimizing prompts for any AI model (Claude, GPT, Llama, etc.) with advanced techniques like CoT, constitutional AI, RAG optimization.
Install
agr install @repo-phuocdt/prompt-engineer --target claudeWrites 6 files into .claude/skills/, pinned to git-8a66fd01.
- .claude/skills/prompt-engineer/.gitignore
- .claude/skills/prompt-engineer/LICENSE
- .claude/skills/prompt-engineer/README.md
- .claude/skills/prompt-engineer/SKILL.md
- .claude/skills/prompt-engineer/cli.js
- .claude/skills/prompt-engineer/package.json
Document
name: prompt-engineer description: Transform rough prompts/ideas into production-ready LLM prompts. Use when crafting, refining, or optimizing prompts for any AI model (Claude, GPT, Llama, etc.) with advanced techniques like CoT, constitutional AI, RAG optimization.
Prompt Engineer
Expert prompt engineering skill that transforms rough ideas into well-structured, production-ready prompts optimized for LLMs.
When to Activate
- User provides a rough prompt/idea and wants it refined
- User asks to create/design/optimize a prompt for any LLM
- User needs prompt architecture for agents, RAG, or multi-step workflows
- User asks about prompting techniques or best practices
Workflow
1. Analyze Input
Identify from user's request:
- Target model (Claude, GPT, Llama, etc.) — default: Claude
- Use case (agent system prompt, task prompt, RAG, chat, etc.)
- Domain (technical, creative, business, etc.)
- Constraints (token limits, output format, safety requirements)
2. Apply Techniques
Select appropriate techniques from references/techniques.md based on use case:
- Complex reasoning → Chain-of-Thought, Tree-of-Thoughts
- Safety-critical → Constitutional AI patterns
- Data extraction → Structured output, JSON mode
- Multi-step tasks → Prompt chaining, agent patterns
- Knowledge-heavy → RAG optimization
3. Craft the Prompt
Follow model-specific guidelines from references/model-optimization.md:
- Structure with clear sections (role, context, instructions, output format)
- Include examples where beneficial (few-shot)
- Add constraints and guardrails
- Optimize for token efficiency
4. Deliver Output
MANDATORY format — always include ALL sections:
The Prompt
Display complete prompt in a single copyable code block.
Implementation Notes
- Techniques used and rationale
- Model-specific optimizations
- Parameter recommendations (temperature, max_tokens)
- Expected behavior and output format
Testing & Evaluation
- 3-5 test cases to validate
- Edge cases and failure modes
- Optimization suggestions
Usage Guidelines
- When/how to use effectively
- Customization options
- Integration considerations
Key Principles
- Always show the complete prompt — never just describe it
- Token efficiency — concise but comprehensive
- Production-ready — reliable, safe, optimized
- Model-aware — tailor to target model's strengths
- Refer to
references/techniques.mdfor advanced technique details - Refer to
references/model-specific-optimization-guide.mdfor model-specific guidance - Refer to
references/production-patterns-and-enterprise-templates.mdfor enterprise patterns
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-8a66fd01d8192026-07-31