code-nest-project-spec

To identify affected modules for multi-module Code-Nest development, analyze the repository structure and SKILL.md files to automatically determine frontend-backend boundaries and enforce naming conventions, ensuring clear change ownership and minimal rollback costs.

Coordinating API and SQL migrations across Code-Nest modules involves analyzing SKILL.md and repository structures to locate impacted modules, then outputting minimal actionable steps that align with existing conventions to reduce integration friction.

YAML frontmatter enforces module boundaries in Code-Nest workflows by validating module naming conventions and metadata presence, ensuring that changes are routed to the correct modules and that controlled activations utilize SKILL.md with optional resources like scripts or references.

Yes, you can use this approach for refactoring tasks across frontend and backend Code-Nest modules. The workflow identifies the appropriate modules, enforces YAML frontmatter presence, and provides minimal runnable paths for compilation and joint debugging.

You do not need to manually configure scripts and references when activating a Code-Nest module change. The workflow provides guidance on using SKILL.md with optional resources like scripts, references, and assets to support controlled activations and minimal deployment paths.

Cross-module Code-Nest changes fail during joint debugging when module boundaries and naming conventions are not properly aligned. Enforcing YAML frontmatter and following the minimal runnable path for compilation and verification ensures successful frontend-backend integration.