system-prompt-structure
Anatomy of effective system prompts — role, context, constraints, format.
- Installs
- 456
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/ai-design-skills --skill system-prompt-structure- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads system-prompt-structure automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
System Prompt Structure
A system prompt is the most important piece of design in an AI product. It defines who the AI is, what it knows, how it behaves, and what it produces. It's the equivalent of a brand guide, interaction spec, and behavioral contract rolled into one document.
Anatomy of a System Prompt
A well-structured system prompt has distinct sections, each serving a specific purpose: 1. Identity and Role Who is the AI? What's its purpose? This anchors everything that follows.
- "You are a senior UX researcher helping design teams..."
- Keep it specific. "You are a helpful assistant" is too vague to produce consistent behavior. 2. Context and Knowledge What does the AI know? What's its domain? What information is it working with?
- Domain boundaries: what it's an expert in and what's outside its scope
- Background information relevant to the task
- User context: who it's talking to and what they need 3. Behavioral Rules How should the AI behave? What are the do's and don'ts?
- Tone and voice specifications
- Response format preferences
- Guardrails and prohibited behaviors
- Interaction style (ask clarifying questions, be concise, think step by step) 4. Output Specifications What should the AI produce? In what format?
- Expected output structure
- Length guidelines
- Format requirements (markdown, JSON, plain text)
- Quality criteria 5. Examples (optional but powerful) Concrete demonstrations of expected behavior.
- Input-output pairs showing ideal responses
- Edge cases showing how to handle tricky situations
Structure Principles
- Order matters: Models pay more attention to content at the beginning and end of the prompt. Put the most important instructions first.
- Specificity beats length: A short, specific prompt outperforms a long, vague one.
- Positive instructions beat negative: "Do X" is clearer than "Don't do Y" — though both have their place.
- Separation of concerns: Keep identity, rules, and output specs in distinct sections.
- Testability: Every instruction in the prompt should be testable. If you can't tell whether the AI followed it, rewrite it.
Common Structural Mistakes
- Kitchen sink prompts: Cramming every possible instruction in. The model can't prioritise.
- Contradictory instructions: Rules that conflict with each other, forcing the model to guess which to follow.
- Implicit expectations: Assuming the model knows what you want without saying it.
- Scattered instructions: The same topic addressed in multiple places, creating inconsistency.
- Static prompts: Never updating the prompt based on what actually works.
Design Artefacts
- System prompt document with labelled sections
- Prompt requirement specifications (what the prompt must achieve)
- Prompt review checklists
- Version history with change rationale
FAQ
What does the system-prompt-structure skill do?
Anatomy of effective system prompts — role, context, constraints, format.
How do I install system-prompt-structure?
Run npx skills add https://github.com/owl-listener/ai-design-skills --skill system-prompt-structure in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/system-prompt-structure/ (personal) or .claude/skills/system-prompt-structure/ (project).
Which AI agents can use system-prompt-structure?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is system-prompt-structure safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains system-prompt-structure?
It is published by owl-listener in owl-listener/ai-design-skills. It has 456 recorded installs.
More from owl-listener/ai-design-skills
guardrail-design
owl-listener/ai-design-skills
Open the skill to read its SKILL.md instructions.
constraint-specification
owl-listener/ai-design-skills
Defining output format, length, tone, and content boundaries within prompts.
generative-ui
owl-listener/ai-design-skills
Designing interfaces where AI generates UI components dynamically.
conversation-patterns
owl-listener/ai-design-skills
Turn-taking, repair sequences, grounding, and dialogue structure for human-AI interaction.
progressive-disclosure
owl-listener/ai-design-skills
Open the skill to read its SKILL.md instructions.
persona-architecture
owl-listener/ai-design-skills
Open the skill to read its SKILL.md instructions.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available