auracle-spec

You can verify backend implementation by reviewing the architecture and backend specifications in the `docs/` directory to ensure your codebase strictly adheres to defined requirements. This prevents architectural drift and maintains technical alignment across all development phases.

Checking code compliance involves validating implemented code against documented design system requirements. This ensures the frontend and design implementations align with the project's defined principles before and during the development process.

Yes, documentation specs can guide feature planning and code review by providing a framework to verify technical alignment. Reviewing the relevant requirements in `docs/` before implementing a new feature ensures your plan matches data models and CI/CD guidelines.

Specification validation applies to data models and CI/CD pipelines by ensuring technical alignment with their respective documentation. It checks implemented code against all architecture, backend, frontend, and infrastructure requirements defined in the `docs/` folder.

Codebase architecture drifts from documented specifications when implementation occurs without continuous validation against the `docs/` directory. Applying specification verification during feature planning and code review prevents this drift and maintains architectural integrity.

You need to validate codebase adherence during all development phases, including feature planning, implementation, and code review. This ensures your technical implementation continuously aligns with the architecture, backend, frontend, and data model documentation.