project-context

To define project constraints for new software, you establish technical, development, quality, and compliance guardrails upfront. This ensures all subsequent architectural decisions align with predefined non-negotiable rules like specific runtime versions or accessibility standards.

Yes, you can extract project context from a brownfield codebase by scanning the existing project. The system automatically detects the existing codebase scenario and gathers information to map current technical and operational constraints.

The best way to enforce compliance and quality standards is to define project guardrails before development begins. Setting non-negotiable project-level constraints ensures every architectural decision adheres to required guidelines.

You manage project context by letting the system detect whether your scenario is greenfield or brownfield. For greenfield projects it interactively guides context creation, while for brownfield projects it extracts context from existing scans.

You do not need to manually specify all technical constraints, as the system interactively guides you through context creation. It helps establish necessary technical, development, and operational guidelines for your new application architecture.

You should define project guardrails before architectural decisions to establish foundational standards and requirements. This prevents inconsistency and ensures all development choices adhere to non-negotiable technical, compliance, and quality rules.