optimize-prompt
Prompt Drafting Assistant
The user wants to craft an effective prompt. Their intent: $ARGUMENTS
Your Process
Step 1: Understand the Goal
Based on the user's description, determine:
- What type of prompt is needed (system prompt, task/user prompt, agentic/tool-use prompt)
- What the prompt needs to accomplish
- What context or constraints exist
If the description is too vague to draft a good prompt, ask 2-3 focused clarifying questions before proceeding. Keep questions specific — do not ask open-ended "tell me more."
Step 2: Draft the Prompt
Write a complete, ready-to-use prompt based on the user's intent. Follow these principles:
More from zackbart/skills
kysely
>
7second-opinion
>
5update-docs
>
5design-system-patterns
>
5ethos
Conduct a structured interview and write a project's ethos.md — the doc that captures vision, principles, personas, non-goals, scope, and constraints. Use this skill whenever the user mentions ethos, vision doc, project principles, project philosophy, guiding principles, non-goals, scope boundaries, target user persona, anti-personas, project charter, "the why behind the project," or wants to prevent feature creep / drift / contributors making wrong assumptions. Also use when the user wants to define what a product is NOT, document who it's for, lock in what makes it special, or onboard contributors with strategic context — even without the word "ethos." Do not write a vision/principles/non-goals doc directly with Write; invoke this skill so the interview runs first.
4bird
>
4