readme-constitution-reader

Parse React Native constitution documents into constitution.config.json for Spec-Kit skills.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Saurav-snapwork/NewAppTemplate --skill readme-constitution-reader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: readme-constitution-reader
Source: https://github.com/Saurav-snapwork/NewAppTemplate/tree/main/.github/skills/readme-constitution-reader
Command: npx skills add https://github.com/Saurav-snapwork/NewAppTemplate --skill readme-constitution-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parse, validate, and normalize constitution documents (readmes) into a single machine-readable config used by downstream Spec-Kit skills to bootstrap architecture and tooling.

Core Features & Use Cases

  • Extracts architecture pattern, folder structure, layer definitions, dependency rules, tech stack, and API endpoints from constitutions.
  • Validates presence of required sections and emits warnings or fatal errors to ensure a reliable config.
  • Produces constitution.config.json that downstream skills consume to orchestrate feature code generation and validation.

Quick Start

Run the Constitution Reader to ingest your constitution files and produce a ready-to-consume configuration for downstream skills.

Frequently Asked Questions about readme-constitution-reader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a React Native README constitution into a machine-readable config file?

This Skill parses and validates React Native constitution documents to produce a single machine-readable constitution.config.json. It extracts architecture patterns, layer definitions, dependency rules, tech stack, folder structure, and API endpoints while emitting fatal or warning violations for missing or malformed sections to ensure reliable downstream consumption.

What is a README constitution document and when do I need to parse it?

A README constitution defines repository-level architecture rules, layer definitions, dependency constraints, and folder structures for React Native projects. You need to parse it to automate architecture validation and bootstrap feature code generation using downstream Spec-Kit skills that require a deterministic, machine-readable configuration.

How do I validate required sections in a repository constitution and enforce architecture dependency rules?

You validate required sections in a repository constitution by running this Skill, which checks for architecture patterns, layer definitions, dependency rules, tech stack, folder structure, and API endpoints. It enforces deterministic extraction and emits fatal errors or warnings when required sections are missing or malformed.

Does the constitution parser work with module-level READMEs or only repository root constitutions?

The constitution parser works with both repository root constitutions and module-level READMEs. It applies deterministic extraction to both document types, normalizing architecture patterns, dependency rules, and folder structures into a single unified constitution.config.json for downstream Spec-Kit skills.

What happens when required sections are missing from a constitution document during parsing?

When required sections are missing or malformed during parsing, the Skill emits fatal or warning violations. This ensures the generated constitution.config.json reliably captures all necessary architecture patterns, dependency rules, and tech stack details before downstream skills consume it.

What is the best way to extract architecture patterns and API endpoints from a React Native constitution?

The best way to extract architecture patterns and API endpoints is to use this Skill, which parses and normalizes the constitution while preserving verbatim rule descriptions. It deterministically assembles extracted layer definitions, tech stack, and folder structure into a ready-to-consume constitution.config.json file.