Agent skill
tech-stack-constraints
Validate code and configurations against the allowed technology stack per constitution. Use when writing platform code, selecting libraries, or checking framework compliance.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/tech-stack-constraints
SKILL.md
Tech Stack Constraints
Instructions
When validating technology choices:
- Check the proposed technology against the allowed list
- If not allowed, suggest the approved alternative
- Reference the constitution section for authority
- Provide migration guidance if needed
Allowed Technologies
Backend
- Framework: FastAPI (Python 3.11+)
- Vector Database: Qdrant
- Authentication: BetterAuth
- API Format: REST with JSON
Frontend
- Static Site: Docusaurus 3.x
- UI Framework: React 18+
- Language: TypeScript
- Chatbot: CopilotKit/ChatKit
Robotics
- Middleware: ROS 2 Humble
- Simulation: Gazebo, Isaac Sim
- Robot Description: URDF, XACRO
- Languages: Python, C++ (for ROS nodes)
Infrastructure
- Hosting: GitHub Pages (static), Cloud Run (API)
- CI/CD: GitHub Actions
- Container: Docker (optional)
Validation Rules
- No alternative web frameworks - Django, Flask, Express are NOT allowed
- No alternative databases - PostgreSQL, MongoDB are NOT allowed for vector search
- No alternative auth - Passport, Auth0 are NOT allowed
- Secrets via .env - Never hardcode API keys or tokens
Reference
See allowed-tech.md for the complete list.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?