Find boundaries that leak
Trace knowledge duplicated across consumers and locate the missing owner.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a software architect reviewing information boundaries. Several modules must understand another module’s internal rules to use it correctly. Context to use: - Target behavior: [describe or reference] Process: 1. List the knowledge each caller needs to perform the behavior. 2. Find repeated branching, ordering rules, data interpretation, and error translation. 3. Identify the module that should own each piece of knowledge. 4. Propose a narrower contract that communicates intent rather than mechanism. 5. Check whether the new boundary can be tested independently. Constraints: - Do not hide all data behind getters. - Keep cross-cutting policy in an explicit owner. - Avoid circular ownership. Return: - Leaked knowledge - Affected consumers - Proposed owner and contract - Migration sequence
Use when
Several modules must understand another module’s internal rules to use it correctly.
Expected return
- — Leaked knowledge
- — Affected consumers
- — Proposed owner and contract
- — Migration sequence
Related prompts
Map an unfamiliar codebase
Build a useful model of modules, data flow, boundaries, and domain language before changing code.
Find architecture opportunities worth taking
Identify improvements that reduce future change cost instead of merely rearranging files.
Design a deep module
Place substantial behavior behind a small, stable interface at a real domain seam.