Does it help with AI context management?

It specifically maintains the CLAUDE.MD file, which provides essential high-level context for AI tools to understand project architecture and standards.

Does this skill support multi-file documentation updates?

Yes, a single code change or feature addition can trigger simultaneous updates across multiple files, including API docs, architecture diagrams, and the project README.

How does it handle database schema changes?

It identifies new tables or RPC functions and maps them to the correct sections in your technical documentation, ensuring schema references stay current.

Is it optimized for Supabase projects?

Yes, it includes specific patterns for documenting Supabase Edge Functions, database tables, and Row Level Security (RLS) policies.

Can it generate documentation directly from source code?

Absolutely. The skill can analyze TypeScript files, Edge Functions, and database schemas to generate structured Markdown documentation with usage examples.

Documentation Sync Assistant

Name: Documentation Sync Assistant
Author: Spectaculous-Code

bySpectaculous-Code

Learning & Documentation

Maintains and synchronizes project documentation with code changes to ensure architectural and API records remain accurate.

About

The Docs Updater skill acts as a specialized assistant for the KR92 Bible Voice project, automating the critical task of keeping technical documentation in sync with evolving code. It intelligently monitors changes to database schemas, RPC functions, and Edge Functions to provide real-time updates for API contracts, architecture diagrams, and project READMEs. By ensuring that context files like CLAUDE.MD and developer guides are always current, it prevents documentation rot and maintains a high-fidelity source of truth for both human developers and AI assistants.

Key Features

Real-time synchronization of README files with new feature deployments
Structured management of AI context files to improve model performance
Automated API documentation updates triggered by schema changes
Maintenance of architecture diagrams and system flow visualizations
Direct generation of Markdown documentation from JSDoc and source code
0 GitHub stars

Use Cases

Syncing the project README to reflect user-facing changes like new audio playback controls
Updating API documentation and database schemas after adding new Supabase tables or RLS policies
Documenting new Edge Functions, including detailed request/response examples and authentication requirements

About

Key Features

Real-time synchronization of README files with new feature deployments
Structured management of AI context files to improve model performance
Automated API documentation updates triggered by schema changes
Maintenance of architecture diagrams and system flow visualizations
Direct generation of Markdown documentation from JSDoc and source code
0 GitHub stars

Use Cases

Syncing the project README to reflect user-facing changes like new audio playback controls
Updating API documentation and database schemas after adding new Supabase tables or RLS policies
Documenting new Edge Functions, including detailed request/response examples and authentication requirements