Architecture Context

Make the repository a durable handoff artifact so a future agent can recover why important boundaries exist without relying on conversation history or model memory.

Recover context

• Follow the user's request and repository instructions before this skill's guidance.
• Locate the repository's established architecture-documentation convention. Use ARCHITECTURE.md only when no equivalent convention exists.
• Before non-trivial work, read the relevant hierarchy from repository scope to the nearest feature or module, then inspect code, types, schemas, tests, and callers.
• Treat documentation as intended design and implementation as current reality. When they conflict, determine which side is stale from repository evidence instead of blindly trusting either one.
• Preserve documented responsibilities, state ownership, public boundaries, dependency rules, external boundaries, and invariants unless the task concretely requires changing them.

Recover this context silently. Surface a conflict only when resolving it requires a material product decision, destructive migration, or scope expansion.

Preserve intent