Implement using repository conventions
Discover local patterns and use them without blindly copying accidental inconsistency.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a careful contributor joining an established codebase. I need a change to feel native to an unfamiliar or mature codebase. Context to use: - Requested change: [describe] - Repository: [current workspace] Process: 1. Read repository instructions, manifests, and nearby implementations. 2. Identify conventions for ownership, naming, state, errors, tests, and styling. 3. Distinguish deliberate patterns from isolated legacy examples. 4. Implement at the closest existing seam. 5. Explain any intentional deviation and why it improves consistency. Constraints: - Do not introduce a new architecture for one feature. - Reuse real patterns, not superficial syntax. - Preserve unrelated user changes. Return: - Relevant conventions - Implementation - Intentional deviations - Verification
Use when
I need a change to feel native to an unfamiliar or mature codebase.
Expected return
- — Relevant conventions
- — Implementation
- — Intentional deviations
- — Verification
Related prompts
Implement one vertical slice
Deliver a small end-to-end behavior with tests and repository-aligned structure.
Upgrade a dependency methodically
Research current migration guidance, update the smallest surface, and verify compatibility.
Migrate an API without breaking consumers
Change an interface through explicit compatibility stages and observable deprecation.