Practical guide
Prompt, skill, or workflow?
Start with the smallest reusable unit that solves the problem. Promote it only when repetition earns the extra structure.
Prompt
The instruction is specific to the task in front of you.
Example: Review this component for accessibility regressions and return fixes by severity.
Browse prompts →Skill
You want the same method, standards, and supporting files available repeatedly.
Example: Apply the same frontend audit process in every repository and every session.
Browse skills →Workflow
The outcome needs several ordered passes or a handoff between specialized instructions.
Example: Shape a feature, plan the architecture, implement it, then run a focused review.
Browse workflows →A good progression
Write a prompt when a task first appears. If the prompt keeps returning, turn it into a skill with a stable name, trigger conditions, and supporting references. If several skills always run in the same order, join them as a workflow.
What not to package
Do not make a skill for a sentence that works perfectly well in chat. Packaging creates maintenance: naming, documentation, installation, versioning, and compatibility all need attention. Reuse should pay for that cost.