aurora-engineering-protocols

Contract-first development requires a contracts.ts (Elysian) file to exist before implementation begins. This skill enforces that requirement and provides centralized architectural governance to ensure compliance with established engineering standards.

The Certum blueprint is a centralized reference for engineering blueprints, contracts, and architectural standards. It guides architectural governance to ensure projects meet required compliance protocols during frontend and backend integration.

To access engineering blueprints for Mad Lab Aurora projects, request the Certum master blueprint and Elysian contracts-first guidelines. This provides the technical references needed to begin project alignment and compliance.

Yes, a contracts.ts file is required before starting implementation. This skill enforces contract-first requirements by ensuring the Elysian contracts file exists before any frontend or backend development proceeds.

Yes, this skill supports frontend and backend integration by providing quick reference guidance based on established standards. It ensures integration aligns with Certum master blueprints and Elysian contract-first development protocols.

This skill provides centralized access to standards rather than automated code refactoring. Limitations include the need for manual alignment of existing projects to meet Elysian contract-first and Certum architectural governance requirements.