From prompt-engineering
Use when writing or reviewing a prompt for an LLM — making it specific, structured, and testable (clear task, role/context, examples, an explicit output contract, decomposition, room to reason) and avoiding the anti-patterns that make prompts brittle. Provider-agnostic.
How this skill is triggered — by the user, by Claude, or both
Slash command
/prompt-engineering:effective-promptingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A prompt is a spec. Most "the model got it wrong" problems are underspecified prompts. Write
A prompt is a spec. Most "the model got it wrong" problems are underspecified prompts. Write the prompt the way you'd brief a sharp contractor who can't ask follow-up questions.
Out of scope: model selection, temperature/thinking/effort knobs, token limits, and exact API parameters are provider-specific — consult your provider's docs. This skill is prompt craft.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub meaganewaller/rosetta --plugin prompt-engineering