Menú
When the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Best practices and guidelines for optimizing the performance of Tauri applications. Use this skill when the user asks to improve the performance, reduce the bundle size, or optimize the Rust/Frontend code of a Tauri app.
Keep the Vesta Launcher architecture atlas current while changing code or docs. Use when working in /Users/eatham/Vesta/launcher on refactors, feature changes, bug fixes that reveal Module ownership, docs/tests cleanup, architecture review follow-ups, questions like "where does this area live?", or any change that creates, removes, renames, deepens, splits, or connects Modules, Interfaces, seams, Adapters, events, task flows, persisted models, resource flows, runtime preparation, launch lifecycle, or frontend state.
When multiple tests fail, assign each failing test file to a separate subagent that fixes it independently in parallel.
Perform a thorough code review focused on correctness, maintainability, performance, and best practices.
Analyze existing code and write comprehensive unit and integration tests for it. Detects the test framework, identifies untested code paths, and generates tests with proper mocking, edge cases, and assertions. Use when the user asks to add tests, improve coverage, or test a specific module.
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
| name | suggesting-cursor-rules |
| description | When the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently. |
| user-invocable | false |
Watch for repeated corrections and frustration. When the user keeps telling you the same thing, suggest a .cursor/rules/ file so they never have to say it again.
Suggest a rule when you notice:
When you detect a trigger, offer it naturally:
I notice you've corrected me on [pattern] a couple times. Want me to
create a Cursor rule so I always follow this convention?
If they say yes, create the rule:
.cursor/rules/<name>.mdc
---
description: <what this rule enforces>
globs: <file pattern this applies to>
---
- <the convention, stated clearly>
User keeps saying "use relative imports":
---
description: Import conventions
globs: **/*.{ts,tsx}
---
- Use relative imports, not @ aliases
- Import from the same package with relative paths (e.g. "../../queries/..." not "src/queries/...")
User keeps saying "no comments on obvious code":
---
description: Comment style
globs: **/*.{ts,tsx,js,jsx}
---
- Do not add comments that narrate what the code does
- Only comment non-obvious intent, tradeoffs, or constraints
User frustrated about test file locations:
---
description: Test file conventions
globs: **/*.test.{ts,tsx}
---
- Co-locate test files next to the source file they test
- Name test files <source>.test.ts, not __tests__/<source>.ts
.cursor/rules/ first so you don't duplicate an existing rule