repo-orientation

Create a repo orientation playbook that captures build commands, CI workflows, and required checks to reduce onboarding time. It documents conventions, run/debug steps, and architecture boundaries into a concise project-specific guide shared as REPO_PLAYBOOK.md.

A repo playbook is a concise document capturing conventions, commands, and guardrails for a new or refactored project. You need one when starting work in a new repo or after a major refactor to map architecture boundaries and ensure consistent governance across teams.

Define guardrails and security tooling checks by documenting required CI workflows and conventions in a repo playbook. The playbook captures build, test, lint, and run/debug checks to ensure consistent governance across backend and frontend projects during refactoring.

Yes, a repo orientation playbook is applicable across both backend and frontend projects. It provides coverage for key projects, API contracts, migrations, CI workflows, and architecture boundaries, ensuring conventions and guardrails are consistently documented regardless of stack.

No, a repo orientation playbook does not implement features or write code. It only produces a concise playbook that maps conventions, commands, and guardrails, designed to be followed reliably by other skills working on the project.

The best way to capture API contracts and migration steps is generating a repo orientation playbook. It provides coverage for key projects, API contracts, migrations, and CI workflows, documenting architecture boundaries and conventions in a single REPO_PLAYBOOK.md file.