gh-architecture-docs

Generate backend architecture specifications by analyzing existing PRDs and database schemas to produce technical specs, implementation plans, and SQL migration skeletons for Supabase applications. This enforces a standardized design process before code is written.

The best way to design Supabase database schemas with RLS policies is using a backend design gate that validates new tables or user roles against established security patterns, automatically generating required schema definitions and migration scripts.

Convert product requirements into actionable engineering tasks through a structured, multi-phase approval workflow that transitions PRDs into technical specifications and implementation plans, eliminating ambiguity and technical debt.

Yes, you can automate SQL migration skeleton generation for new database tables by validating the database design against existing Supabase patterns, ensuring consistency and security across schema changes without manual scripting.

Yes, an existing PRD is required as input. The architecture documentation process operates by analyzing product requirements and current database schemas to output structured spec files and implementation plans.

Standardize backend design before writing code to eliminate the ambiguity and technical debt associated with new feature development, ensuring database changes are fully spec'd with RLS policies and schema definitions beforehand.