home / skills / zeeshan080 / ai-native-robotics / constitution-reader

constitution-reader skill

safe

This skill helps you understand project constitution rules by summarizing sections and highlighting constraints for compliant development.

npx playbooks add skill zeeshan080/ai-native-robotics --skill constitution-reader

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.3 KB

---
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:

1. Read the constitution file at `.specify/memory/constitution.md`
2. Summarize the relevant principles based on the user's query
3. Highlight any constraints or requirements that apply
4. 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](reference.md).

Overview

This skill reads the project constitution and summarizes applicable principles for the AI-Native Robotics Textbook project. It helps you check rules, validate compliance, and understand constraints that affect design and content. Use it to get section-specific guidance and to locate rules for agents, pedagogy, and technical choices.

How this skill works

The skill loads the constitution from .specify/memory/constitution.md and extracts the sections relevant to your query. It summarizes applicable principles, highlights constraints and requirements, and references the exact sections to support decisions. When asked, it will call out precise lines or section names so you can verify compliance quickly.

When to use it

Checking which libraries and frameworks are permitted for a service or component
Validating that a content agent or software-building agent meets project rules
Understanding pedagogical layer definitions (L1-L5) for curriculum alignment
Confirming quality, verification, and testing requirements before release
Preparing or reviewing contributions to ensure they follow the constitution

Best practices

Always reference the specific section number cited in guidance (III, IV, VII, VIII, IX).
Highlight any hard constraints first (e.g., allowed tech stack or mandatory content sections).
Summarize relevant paragraphs, then list concrete actions to comply.
When rules are ambiguous, flag uncertainties and recommend a clarification request.
Keep compliance summaries short and include the file path to the constitution for follow-up (.specify/memory/constitution.md).

Example use cases

Ask which backend frameworks are permitted; response references Section III and lists allowed tools.
Request how to structure a lesson; response cites Section VII and notes required elements like a 'Try With AI' final section.
Validate a content agent design against agent specs in Section VII and software-building rules in Section VIII.
Check verification steps and quality gates before publishing, referencing Section IX requirements.
Determine which pedagogical layer a module belongs to by matching it to Section IV L1-L5 definitions.

FAQ

Where does the skill read the constitution from?

It reads the file at .specify/memory/constitution.md and summarizes the relevant sections.

Which sections are most commonly referenced?

Sections III (Technical Stack), IV (Pedagogy), VII (Content Agents), VIII (Software-Building Agents), and IX (Quality & Verification).