claude-specific

You maintain consistent exports and explicit imports in a CDK monorepo by applying standardized governance rules for code generation, refactoring, and dependency ordering to keep multi-package workstreams aligned and productive.

The best way to guide code generation and refactoring across CDK monorepo packages involves centralized instructional guidelines that enforce build order, workspace conventions, and environment-aware configurations to reduce friction in multi-package workstreams.

To add a new subpackage to a CDK constructs library monorepo, follow guidelines that ensure explicit imports, proper tests, and consistent exports, aligning the new package with existing project context and workspace conventions.

Dependency ordering matters when building in a CDK monorepo because it enforces structured governance for tests, documentation, and feature additions, ensuring consistency and reducing friction across multi-package workstreams.

Yes, you can use standardized practices to align documentation with code refactoring in a monorepo by applying centralized guidelines that enforce documentation alignment alongside feature additions and code generation tasks.

Yes, you need environment-aware configurations for CDK monorepo workspace conventions to ensure explicit imports and consistent exports function correctly across different deployment contexts and multi-package workstreams.