Finds and assesses existing solutions across the whole product before an implementation responsibility is added or relocated. Use for PFE, Proudly Found Elsewhere, or when deciding whether to reuse, change, modularize, or replace an existing product solution.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Given an implementation responsibility, find a domain-correct way to use what this product already knows before adding another representation of the same solution.
Use the selected story or plan, current product behavior, and this project's domain language and applicable decisions to state the responsibility, its purpose, and genuine constraints. Resolve this project's navigation and product boundaries. If the responsibility or the domain meaning needed to assess it is missing, stop the affected work and ask the developer for that specific context.
Project decisions remain authoritative. This skill does not grant permission to override an architectural decision, expand the assignment, or alter unrelated behavior.
Search broadly enough to find conceptual solutions, not just matching names. Follow domain concepts, behavior, callers, tests, documentation, data flow, and ownership across the whole product. Include other components, services, tools, and process boundaries when the responsibility can meaningfully cross them.
Judge a candidate by its domain meaning: the responsibility it owns, the purpose it serves, its rules and invariants, and its lifecycle. Different structure or names do not rule out a fit; similar-looking code does not establish one. Stop searching once the evidence is sufficient to make or rule out a suitable choice.
Use the smallest justified outcome:
Explain the candidate evidence and why the choice preserves one coherent representation of the responsibility. Do not force unrelated responsibilities together to remove superficial duplication, and do not add machinery for hypothetical future reuse.
If domain meaning remains unresolved, or the choice has consequential product or architectural effects that are not already authorized, stop that path. Give the developer the competing interpretations, decisive evidence, and the choice needed to continue.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Backend Java — Spring Boot controllers/services, JUnit controller tests, MakeMe. Read this first for any backend work. Use when working on the Java Spring backend.
The English summary is being prepared. Showing the original description.
Backend Java production code, Spring Boot controllers/services/repositories, controller return values, imports, schema ERD pointer. Use when editing backend production Java.
The English summary is being prepared. Showing the original description.
Backend Java tests, controller-level stable-boundary tests, JUnit, @Nested, MakeMe builders, @Transactional, parameterized tests. Use when writing or changing backend JUnit tests.
The English summary is being prepared. Showing the original description.
related to donut CLI. Use when working on donut-cli.
The English summary is being prepared. Showing the original description.
Set up and run the Donut dev environment on Cursor Cloud VM (no Nix). Use when working on Cloud VM, running tests on Cloud VM, or encountering command errors related to missing nix. Triggers on: cloud VM, cloud agent, no nix available, /workspace path.
The English summary is being prepared. Showing the original description.
Regenerate docs/database-erd.md from MySQL information_schema (Mermaid ERD: foreign keys and key columns). Use after Flyway schema changes, new migrations, or when the diagram is stale. Triggers on: database ERD, database-erd.md, export_database_erd, schema diagram, ER diagram after migration.
The English summary is being prepared. Showing the original description.