What problem does it solve? Technical documentation in growing projects becomes scattered, duplicated, and outdated. This Skill provides a canonical methodology to create, refactor, and maintain documentation for the ibarra-app project (Peajes module), ensuring each topic has a single canonical location with proper indexes and cross-references. ## Core Features & Use Cases - Canonical documentation structure: Organizes docs by domain and artifact type (modules, components, tables, backend/RPC, tests) with a defined folder taxonomy and INDEX.md chain. - Refactor methodology: Inventories existing docs, detects duplicates, designates canonical documents, and updates parent indexes and cross-links. - Ready-to-use templates: Provides Markdown templates for tests, components, tables, SQL/RPC, and index pages, plus a minimal-update rule mapping each code change to exactly which docs to touch. - Use Case: After implementing a new Supabase RPC for the Peajes module, ask the agent to document it; it will place the doc under docs/backend/, update the module and table references, and refresh the index chain without rewriting unrelated docs. ## Quick Start Ask the agent to document the Peajes wizard component following the project documentation methodology and place it in the correct docs folder with updated indexes.
