Authoring prompts

---
name: prompt-engineering
description: Write, review, or fix a prompt. Use when the user asks for a prompt, wants better output from a model, says the model is ignoring instructions, or is building a system prompt for an app or agent.
---

# Prompt Engineering

There is no perfect prompt, only a perfect process. The highest-leverage mo

---
name: [skill-name-in-kebab-case]
description: >
  [What the skill does in third person, then WHEN to use it, including the
  exact words users type. E.g.: "Generates release notes from merged PRs.
  Use when the user asks for release notes, a changelog, or 'what shipped',
  or before tagging a release."]
---

# [Skill Name]

[2-3 sent

---
name: writing-great-skills
description: Reference for writing and editing skills well, the vocabulary and principles that make a skill predictable.
disable-model-invocation: true
---

A skill exists to wrangle determinism out of a stochastic system. **Predictability**: the agent taking the same _process_ every run, not producing the s

---
name: writing-skills
description: Use when creating new skills, editing existing skills, or verifying skills work before deployment
---

# Writing Skills

## Overview

**Writing skills IS Test-Driven Development applied to process documentation.**

**Personal skills live in your runtime's skills directory** (`~/.claude/skills/` on Cla