What problem does it solve? Keeping backend documentation accurate and organized is hard when RPC functions, Edge Functions, tables, triggers, and RLS policies live scattered across migrations and source code. This Skill produces structured, canonical backend docs under docs/backend so teams stop duplicating or losing technical knowledge. ## Core Features & Use Cases - Structured backend docs: Generates documentation for Supabase RPC functions, Edge Functions, tables, triggers, RLS policies, validations, and business logic, organized by module (pedidos, ordenes-compra, productos, proveedores, api, supabase). - Code-grounded writing: Inspects migrations, Edge Function sources, RLS SQL files, Angular services, and database types before writing, so docs reflect real behavior. - Bilingual convention: Skill instructions are in English while all docs/backend output is written in technical Spanish, with fixed English section slugs for consistency. - Use Case: After adding a new Postgres RPC for order approval, ask the Skill to document it; it updates functions/index.md, creates the module detail page from the template, updates indexes, and hands off the Testing section to backend-tester. ## Quick Start Document the new aprobar-pedido-item RPC function under docs/backend following the project template and update the relevant indexes.
