- In Cursor
- Figma connection
- In the plugin
Skill not activating
Skill not activating
Symptom: You type a prompt but the skill doesn’t run.Solutions:
- Use the direct reference format:
@create-voiceinstead of typing keywords - Check that the Echo Specs project folder is open in Cursor (not a parent directory)
- Restart Cursor if skills don’t autocomplete
Poor output quality
Poor output quality
Symptom: The generated JSON is missing information or has incorrect values.Solutions:
- Add more context to your prompt: describe all states, variants, and behaviors
- Specify states explicitly (e.g., “enabled, hover, pressed, disabled”)
- Include a screenshot for complex components
- Mention any non-obvious interactions or behaviors
Skills don't autocomplete
Skills don't autocomplete
Symptom: Typing
@create- doesn’t show skill suggestions.Solutions:- Confirm the Echo Specs project folder is open in Cursor
- Check that
.cursor/skills/contains the skill folders - Restart Cursor after cloning the repository
Improving output quality
If the agent’s output is incomplete or doesn’t match your expectations, the issue is usually missing context rather than a technical problem.Output is incomplete or missing states
The agent can only document what it can see in Figma or what you describe. If states, variants, or behaviors are missing from the output:- Add them to your prompt: explicitly list all states (enabled, hover, pressed, disabled, selected, loading)
- Describe behavioral modes: fill vs. hug width, truncation rules, multi-select behavior
- Mention invisible constraints: tap target minimums, aspect ratios, focus order preferences
Output seems generic or empty
If the output has the right structure but lacks detail:- Check your MCP connection: type “Check Figma status” in Cursor. If the connection is down, the agent can’t read your component data
- Verify the Figma link: make sure the node-id points to the actual component, not a parent frame
- Re-run with more context: describe the component’s parts and their relationships
Re-prompting strategies
When the first output isn’t quite right:- Identify what’s missing: Is it a state? A variant? A specific part?
- Run the skill again with additional context about the missing elements
- Be specific: instead of “include all states,” say “include enabled, disabled, and loading states”
The agent validates JSON structure internally. If the JSON is malformed, the issue is likely a connection problem, not a prompt problem. Check your MCP connection first.
Get the project
The Echo Specs repository is private. If you don’t have access, request it from ian.guisard. Once you have access, clone the repository:This project is maintained by Ian Guisard. Reach out to Ian directly if you have questions or need help getting started.