Project Interaction & Architecture Rules

This skill enforces a strict rule: read all the code first, then write the handbook. It lists and reads the project's entire routing, pages, components, state management, APIs, backend logic, database models, validators, scheduled jobs, and docs in one pass. Anything the code doesn't reveal is marked unknown in the handbook — never inferred to fill gaps.

The output is a structured, queryable project handbook that maps out business rules, UI interaction details, architectural wiring (MCP/database/APIs), the rationale behind non-standard designs, and project-specific conventions — for both operators and maintainers to query.

Use it when you want to fully absorb a repo or set of related projects, map out an existing codebase's architecture, build a whole-project rulebook, understand why technical details are the way they are, or identify project-specific conventions.

The repository can hold multiple skills; this one lives in the project-interaction-architecture-rules/ subdirectory. Clone the repo and add that subdirectory to your AI IDE's skills folder to use it.