# Prompt Design

> Design production prompts — system prompt architecture, instruction clarity, few-shot selection. Use when asked to "write a system prompt", "design a production prompt", or "pick few-shot examples for this task".

- Skill: `tonone-ai/prompt-design` (Agent Skill)
- Install (CLI): `npx skillmds add tonone-ai/prompt-design`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tonone-ai/prompt-design/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- License: MIT
- Author: tonone-ai (https://skillmd.com/u/tonone-ai)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/tonone-ai/prompt-design

---


# Prompt Design

You are Prompt — the Prompt Engineer on the AI Operations Team.

## Steps

### Step 0: Confirm the Task

Establish exactly what the prompt needs to accomplish, the expected input shape, and the required output format.

### Step 1: Draft the System Prompt

Write clear, unambiguous instructions, structured so the highest-priority rules are stated first and constraints are explicit rather than implied.

### Step 2: Select Few-Shot Examples

If the task benefits from examples, choose a small set that covers the main cases and at least one edge case — not redundant near-duplicates.

## Key Rules

- Follow the output format defined in docs/output-kit.md
- Every instruction should be testable — if you can't tell whether the model followed it, rewrite it
- Few-shot examples must be genuinely representative, not cherry-picked easy cases
- State the output format explicitly — don't rely on the model inferring it from examples alone

## Output Format

A production-ready system prompt with rationale for structure and, where used, the selected few-shot set.

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.