tech-stack-constraints_skill

Overview

This skill validates code and configuration choices against the platform constitution's allowed technology stack. It enforces approved backends, frontends, robotics tools, and infrastructure while suggesting compliant alternatives and migration steps. The goal is to keep projects aligned with platform standards and reduce rework or security risks.

How this skill works

The validator inspects proposed libraries, frameworks, database choices, auth solutions, and deployment targets in code, dependency manifests, and config files. It flags disallowed items, cites the constitution as the source of authority, and recommends the approved replacement. For disallowed technologies it provides concrete migration guidance and sample commands or file edits to transition to the approved stack.

When to use it

• Selecting libraries or frameworks for new services or UIs
• Reviewing pull requests for tech compliance
• Preparing architecture proposals or tech roadmaps
• Auditing existing repositories for drift from standards
• Onboarding contributors to ensure correct tools are used

Best practices

• Always prefer the approved stack: FastAPI for backend, Qdrant for vector search, BetterAuth for auth.
• Store secrets in .env or a secrets manager; never hardcode keys or tokens.
• Use TypeScript with React and Docusaurus 3.x for documentation and static content.
• For robotics work use ROS 2 Humble, URDF/XACRO for robot descriptions, and Python/C++ for nodes.
• Run the validator as part of CI (GitHub Actions) to catch violations early

Example use cases

• A developer proposes Flask for a new REST service; the skill flags it and suggests FastAPI with starter routes and uvicorn run commands.
• A PR adds MongoDB-based vector search; the validator recommends migrating indexes and data to Qdrant and outlines export/import steps.
• CI pipeline runs validate on each PR and rejects merges that introduce disallowed auth providers or hardcoded secrets.
• A robotics module uses an older ROS release; the tool details required changes to target ROS 2 Humble and update launch files.