When to use this workflow
Use this resource to package a repeated workflow for the supported Cursor environment. Begin with a task you can already perform and review. A skill should make a known process reusable; it should not hide unresolved product decisions inside a broad instruction to improve the interface.
A worked example
For a spacing-audit example, provide a target component, the token source, and an accepted findings format. Write the trigger so the host can distinguish auditing existing spacing from designing a new layout. Include the source-inspection steps, how to report uncertainty, and the boundary between proposing and applying changes.
Decisions and common mistakes
Test a normal request, missing inputs, and a nearby request that should not activate the skill. If the description is too broad, the skill can interrupt unrelated work. If it is too narrow, contributors may never discover it. Keep the procedure aligned with the host’s actual supported format and location.
What to hand off
Share a reviewed example and record the version used. When the team changes its token structure or workflow, update the references and rerun the examples. A skill that points to stale project paths can be less useful than a short, current manual checklist.
Set up and try the skill
1. Start with one concrete task
Bring: A repeatable Cursor workflow, sample inputs, and an example of an acceptable result.
First task: Write the trigger and boundaries, then package the sequence into a skill with concrete examples.
Choose a small task for “create a cursor skill.” Provide the relevant file, screen, or brief and define what a useful result should contain. Keep the original version available for comparison.
2. Install and verify the instructions
Run this command from the project where you want the skill available. Follow the installer’s host selection, then confirm the skill appears in that host. The command is the installation method documented by the TDP repository.
npx skills add thedesignproject/agent-skills -s create-skillRead the full skill instructions for prerequisites and supported tools. Installing a skill does not automatically connect Figma or grant access to external tools.
3. Apply it with your project context
Use the starter request below with the relevant inputs attached or referenced. Confirm that the host loaded the intended skill; a matching name alone is not evidence that its instructions were applied.
4. Review the result
Try both an intended request and a nearby request that should not activate the skill.
Compare the output with the task’s acceptance criteria. Check factual claims, unsupported assumptions, and any changes to the interface. For code or design changes, review real states and behavior before treating the result as finished.
5. Keep what works
Save approved outputs with their source and ownership. Note which instructions helped, where the result needed correction, and what must be checked next time. Use the workflow below to connect this task to its next step.
A starter request
Adapt this example to your files, audience, and requirements.
Package this repeated Cursor workflow as a skill with a clear trigger, inputs, steps, expected output, and examples of when it should not run.
Completion checklist
- The inputs and intended result are explicit.
- Required files and tools are available in the chosen host.
- The result has been reviewed against the actual task.
- Limitations and follow-up checks are recorded.