project-guardrails

You enforce development standards for a backend monorepo by applying strict architectural rules that dictate backend authority, package boundaries, and app structure. This prevents dependency violations and maintains code integrity across the project.

Before feature development, you must check architectural rules covering backend authority, monorepo boundaries, offline functionality, data handling, media storage, API contract generation, and scope control to ensure implementation alignment.

You manage dependencies between apps and packages in a monorepo by following strict boundary rules that define what applications can depend on which packages. This prevents structural violations and maintains clear separation of concerns.

Yes, this approach supports offline functionality and data handling by defining specific requirements for offline operations and data/media storage. These rules ensure your implementation meets the project's core architectural principles.

You need to review architectural guardrails before starting any code refactoring or new feature development. Loading these rules beforehand ensures your implementation aligns with core principles and prevents costly rework later.

The best way to generate API contracts in a structured monorepo is by following documented architectural rules that enforce backend authority and scope control. This ensures contracts align with the project's non-negotiable guidelines.