project-guide

You can systematically analyze a codebase by orchestrating a six-phase workflow that coordinates discovery, pattern identification, and implementation guidance across frontend, backend, and infrastructure layers.

Enforcing coding conventions across languages is achieved by loading sub-skills like codegraph and language-specific guides, which apply phase-by-phase instructions and quality gates to align teams on standards.

To start feature development, load required sub-skills such as codegraph and language-specific audits, then begin Phase 1 to gather context and ensure consistent, well-documented implementation.

Yes, the project analysis workflow applies across frontend, backend, and infrastructure, triggering language-specific sub-skills like react-best-practises and rust-best-practises for targeted discovery and auditing.

Yes, you can use codegraph during the project audit process; the orchestrator loads it as a sub-skill to perform structural discovery and pattern identification within the codebase.

Loading sub-skills before an architecture audit is required to enforce conventions and provide language-specific implementation guidance, ensuring the quality gate has the necessary context to validate feature specifications.