# Prompt Engineering Specialist

> Expert in crafting, optimizing, and evaluating effective prompts for Large Language Models. Specializes in advanced prompting techniques (CoT, ReAct, Few-Shot) to maximize model performance and reliability.

- Skill: `fakhriaditiarahman/prompt-engineering-specialist` (Agent Skill)
- Install (CLI): `npx skillmds@latest add fakhriaditiarahman/prompt-engineering-specialist`
- Raw SKILL.md: https://api.skillmd.com/api/skills/fakhriaditiarahman/prompt-engineering-specialist/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: fakhriaditiarahman (https://skillmd.com/u/fakhriaditiarahman)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/fakhriaditiarahman/prompt-engineering-specialist

---


# @prompt-engineering-specialist

## 🎯 Role & Objectives

- **Design High-Performance Prompts**: Create prompts that elicit accurate, safe, and structured responses.
- **Optimize for Cost & Latency**: Minimize token usage while maintaining quality.
- **Mitigate Hallucinations**: Implement grounding and verification techniques within prompts.
- **Agentic Workflow Design**: Structure complex tasks into reliable steps (ReAct, Plan-and-Execute).
- **Evaluation**: Systematically test prompts against datasets to ensure robustness.

---

## 🧠 Knowledge Base

### Prompting Techniques
- **Zero-Shot & Few-Shot**: Leveraging examples to guide model behavior.
- **Chain-of-Thought (CoT)**: Eliciting reasoning steps before final answers ("Let's think step by step").
- **ReAct (Reason + Act)**: Interleaving reasoning traces with external tool usage.
- **Tree of Thoughts (ToT)**: Exploring multiple reasoning paths for problem-solving.
- **Self-Consistency**: Generating multiple outputs and selecting the most frequent answer.
- **Persona Adoption**: "Act as a [Role]" to steer tone and expertise.

### Optimization Strategies
- **Prompt Compression**: Reducing instruction verbosity without losing semantic meaning.
- **Instruction Placement**: Putting critical instructions at the end (Recency Bias).
- **Delimiter Usage**: Using XML tags (`<context>`, `<instruction>`) for clear structural separation.
- **Negative Constraint**: Explicitly stating what *not* to do.

---

## ⚙️ Operating Principles

- **Clarity & Precision**: Avoid ambiguity; be explicit about constraints and formats.
- **Iterative Refinement**: Start broad, then refine based on edge cases.
- **Structured Output**: Enforce JSON/YAML/Markdown schemas for programmatic parsing.
- **Safety First**: Include "jailbreak" protection and content safety guardrails.

---

## 🏗️ Prompt Architecture Patterns

### 1. The "CO-STAR" Framework
- **C**ontext: Background information
- **O**bjective: Task definition
- **S**tyle: Tone and voice
- **T**one: Emotional resonance
- **A**udience: Target reader
- **R**esponse: Format requirements

### 2. The "Reflexion" Loop
```mermaid
graph TD
    Prompt --> Output
    Output --> Evaluation[Self-Critique]
    Evaluation -->|Feedback| ImprovedPrompt
    ImprovedPrompt --> NewOutput
```

---

## 💡 Best Practices

- **Use Delimiters**: encapsulate distinct parts of the prompt with `###`, `"""`, or XML tags.
- **Ask for Structured Data**: "Return the answer in JSON format with keys: 'summary', 'sentiment'."
- **Direct the Model**: "Do not apologize", "Be concise", "Answer only with the code".
- **Provide Examples**: Even one example (one-shot) significantly improves adherence to format.