Create comprehensive ontological documentation for Grey Haven systems - extract domain concepts from TanStack Start and FastAPI codebases, model semantic relationships, generate visual representations of system architecture, and document business domains. Use when onboarding, documenting architecture, or analyzing legacy systems.
View on GitHubgreyhaven-ai/claude-code-config
developer-experience
grey-haven-plugins/developer-experience/skills/ontological-documentation/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/greyhaven-ai/claude-code-config/blob/main/grey-haven-plugins/developer-experience/skills/ontological-documentation/SKILL.md -a claude-code --skill grey-haven-ontological-documentationInstallation paths:
.claude/skills/grey-haven-ontological-documentation/# Grey Haven Ontological Documentation Create comprehensive ontological documentation that captures fundamental concepts, relationships, and classification systems within Grey Haven codebases and systems. ## When to Use This Skill Use this skill when you need to: - Document the conceptual structure and domain model of Grey Haven applications - Extract and organize business concepts from TanStack Start or FastAPI codebases - Create visual representations of multi-tenant system architectures - Build semantic maps of entities, services, and their tenant-isolated interactions - Design or document domain models for new Grey Haven features - Analyze and communicate complex architectures to stakeholders - Create knowledge graphs for Grey Haven development teams - Onboard new developers to Grey Haven project structure ## Core Capabilities ### 1. Concept Extraction from Grey Haven Codebases **TanStack Start (Frontend) Extraction:** - Drizzle schema tables and relationships - React components and their hierarchies - TanStack Router route structure - Better-auth session and user models - Server functions and their dependencies - Multi-tenant data patterns (tenant_id isolation) **FastAPI (Backend) Extraction:** - SQLModel entities and relationships - Repository pattern implementations - Service layer business logic - API endpoint hierarchies - Multi-tenant repository filters - Pydantic schemas and validation models ### 2. Grey Haven Architecture Patterns **Identify and Document:** - **Multi-Tenant Patterns**: tenant_id isolation, RLS roles (admin/authenticated/anon) - **Repository Pattern**: BaseRepository with automatic tenant filtering - **Service Layer**: Business logic separation from endpoints - **Database Conventions**: snake_case fields, UUID primary keys, timestamps - **Authentication**: Better-auth integration with session management - **Deployment**: Cloudflare Workers architecture ### 3. Visual Documentation Formats **Mermaid Diagrams** (for README files):
Issues Found: