constitution-reader
Read and summarize constitution principles for the AI-Native Robotics Textbook project. Use when checking project rules, validating compliance, or understanding constraints.
When & Why to Use This Skill
The Constitution Reader is a specialized Claude skill designed to streamline project governance and compliance for the AI-Native Robotics Textbook project. It acts as an intelligent interface for the project's 'constitution,' allowing contributors to instantly retrieve, summarize, and validate technical constraints, pedagogical standards, and architectural requirements. By automating the cross-referencing of project rules, it ensures high-quality, consistent output while reducing the manual effort required for compliance checks.
Use Cases
- Technical Stack Validation: Quickly verify if specific frameworks or libraries (e.g., FastAPI, Qdrant) are permitted for backend development according to the project's strict technical guidelines.
- Pedagogical Alignment: Ensure that educational content adheres to the defined L1-L5 pedagogical layers and includes mandatory structural elements like the 'Try With AI' section.
- Compliance Auditing: Check whether software-building or content agents meet the specific quality and verification requirements outlined in the project's core documentation.
- Contributor Onboarding: Provide new team members with instant answers regarding project constraints and rules without requiring them to manually search through lengthy documentation files.
| name | constitution-reader |
|---|---|
| description | Read and summarize constitution principles for the AI-Native Robotics Textbook project. Use when checking project rules, validating compliance, or understanding constraints. |
| allowed-tools | Read, Grep |
Constitution Reader
Instructions
When this skill is invoked, help the user understand the project constitution:
- Read the constitution file at
.specify/memory/constitution.md - Summarize the relevant principles based on the user's query
- Highlight any constraints or requirements that apply
- Reference specific sections when providing guidance
Key Sections to Reference
- Section III: Strict Technical Stack (allowed frameworks and libraries)
- Section IV: Pedagogical Layers (L1-L5 definitions)
- Section VII: Content Agents Specification
- Section VIII: Software-Building Agents Specification
- Section IX: Quality & Verification requirements
Examples
User asks: "What tech stack is allowed for the backend?" Response: Reference Section III - Only FastAPI, Qdrant, BetterAuth are permitted.
User asks: "How should content be structured?" Response: Reference Section VII - Content must include "Try With AI" final section.
Reference
For the full constitution, see reference.md.