tech-stack-constraints

Technology stack validation compares your proposed libraries, frameworks, and tools against an approved list defined in your constitution. This Skill checks backend code, platform selections, and framework choices to ensure compliance, flagging non-approved technologies and recommending approved alternatives with migration guidance.

When a technology isn't approved, this Skill identifies compliant alternatives from your allowed-tech directives and provides a migration path to transition your code. It delivers actionable recommendations for conformance without breaking your current implementation.

Yes, stack validation applies across backend, frontend, robotics (including ROS2), and infrastructure layers. The Skill enforces allowed technologies and validation rules uniformly, ensuring your entire codebase—from platform code to library selections—aligns with your constitution.

Migration guidance compares your current stack against approved alternatives, suggests compliant replacements, and outlines the steps to transition your code. This reduces technical debt and ensures new selections align with your long-term stack strategy.

The allowed-tech.md document serves as the definitive reference for approved technologies and constraints. This Skill links to that constitution to enforce rules consistently and provide transparent reasoning for compliance decisions.