constitution-reader_skill

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

1

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

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

  • reference.md1.5 KB
  • SKILL.md1.3 KB

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

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).

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational