VedKathe
- 10 skills
- 0 followers
- 1 day ago last updated
- ▌ Database Design Doc · vedkathe bundleGenerate a professional Database Design document as a formatted Word (.docx) file — database overview, ER diagram placeholder, table/collection definitions, relationships, indexing, migrations, retention, and PII handling. Use this whenever someone asks for a "database design doc," "schema documentation," "data model doc," or wants a standalone document describing how a system's data is structured and managed (as distinct from the system's overall architecture or API contract, which have their own companion skills). Part of an enterprise handover documentation suite (see also: project-overview-doc, architecture-document, high-level-design, operations-deployment-guide, support-runbook, api-documentation, release-maintenance-guide) but fully usable standalone.
- ▌ Support Runbook · vedkathe bundleGenerate a professional Support Runbook as a formatted Word (.docx) file — monitoring, logging, health checks, scheduled jobs, troubleshooting guide, routine operational checklist, and support process/escalation. Use this whenever someone asks for a "runbook," "support handbook," "on-call guide," "incident response doc," or wants day-to-day operational reference material for a support or on-call team (as distinct from how a system gets deployed, which lives in the companion operations-deployment-guide skill). Part of an enterprise handover documentation suite (see also: project-overview-doc, architecture-document, high-level-design, operations-deployment-guide, api-documentation, database-design, release-maintenance-guide) but fully usable standalone.
- ▌ General Document Generator · vedkathe bundleGenerate any Word (.docx) or Markdown document that doesn't fit one of the other specific documents in this suite (project overview, architecture document, HLD, ops & deployment guide, runbook, API docs, database design, release & maintenance guide). Use this for memos, proposals, reports, whitepapers, meeting notes, policy documents, one-pagers, letters, or any other ad hoc document request — anything where the person wants "a document," "a report," "a Word doc," "a memo," a write-up of something, or a document type not covered by the more specific skills. Follows the same underlying engine as the rest of the suite (the docx library, and Mermaid + mmdc for any diagrams) but without a fixed section schema — the structure is decided per document rather than hardcoded.
- ▌ Project Overview Doc · vedkathe bundleGenerate a professional Project Overview document as a formatted Word (.docx) file — business context, objectives, scope, stakeholders, and business workflow, written for a non-technical audience (product owners, management, new joiners). Use this whenever someone asks for a "project overview," "project charter," "business context document," or wants a one-stop document explaining what a project is and why it exists, separate from its technical architecture. Part of an enterprise handover documentation suite (see also: architecture-document, high-level-design, operations-deployment-guide, support-runbook, api-documentation, database-design, release-maintenance-guide) but fully usable standalone.
- ▌ API Documentation Doc · vedkathe bundleGenerate professional API Documentation as a formatted Word (.docx) file — API overview, authentication, endpoint catalog, request/response schemas, error handling, rate limiting, versioning, and example requests. Use this whenever someone asks for "API docs," "API reference," "endpoint documentation," or wants a standalone document describing a system's API contract (as distinct from the system's overall architecture or database schema, which have their own companion skills). Part of an enterprise handover documentation suite (see also: project-overview-doc, architecture-document, high-level-design, operations-deployment-guide, support-runbook, database-design, release-maintenance-guide) but fully usable standalone.
- ▌ High Level Design Doc · vedkathe bundleGenerate a professional High-Level Design (HLD) document as a formatted Word (.docx) file — design principles, key design decisions and trade-offs, module-level design, major user journeys, non-functional requirements, performance considerations, and risks. Use this whenever someone asks for an "HLD," "high-level design document," "design rationale doc," or wants to document *why* a system was designed the way it was (as distinct from the structural component view, which lives in the companion architecture-document skill). Part of an enterprise handover documentation suite (see also: project-overview-doc, architecture-document, operations-deployment-guide, support-runbook, api-documentation, database-design, release-maintenance-guide) but fully usable standalone.
- ▌ Application Summary Generator · vedkathe bundleGenerate a 5-6 page business-facing summary of an existing application or codebase — what it does, who it's for, key capabilities, and its business value — written for non-technical stakeholders (executives, sales, new hires, partners), not developers. Use this when someone wants to understand "what does this app/product do" without wading through code, wants a business overview of an existing system, or asks to "summarize this codebase/application for business use," "explain what this app does," or similar. Discovers the app's purpose by checking any user-provided documentation first, then the codebase itself (README, package manifests, routes, models, config) — never invents business claims that aren't evidenced. Distinct from project-overview-doc (which documents a project via interview, for a handover) — this one reverse-engineers an existing, possibly-undocumented app. Part of the enterprise handover documentation suite but fully usable standalone.
- ▌ Architecture Document · vedkathe bundleGenerate a professional Architecture Document as a formatted Word (.docx) file — solution overview, system architecture, technology stack, repository/module structure, data flow, integrations, caching, and messaging design. Use this whenever someone asks for an "architecture document," "system design doc," "solution architecture," or wants to document how a system's components fit together (as distinct from business context or database/API detail, which have their own companion skills). Part of an enterprise handover documentation suite (see also: project-overview-doc, high-level-design, operations-deployment-guide, support-runbook, api-documentation, database-design, release-maintenance-guide) but fully usable standalone.
- ▌ Release Maintenance Guide · vedkathe bundleGenerate a professional Release & Maintenance Guide as a formatted Word (.docx) file — release/branch strategy, coding standards, documentation index, external/vendor dependencies, team contacts, known issues, technical debt, pending enhancements, and an ownership transfer checklist with sign-off. Use this whenever someone asks for a "release guide," "maintenance guide," "ongoing ownership doc," "handover sign-off," or wants a standalone document covering how a project continues to be maintained and by whom after a transition. Part of an enterprise handover documentation suite (see also: project-overview-doc, architecture-document, high-level-design, operations-deployment-guide, support-runbook, api-documentation, database-design) but fully usable standalone.
- ▌ Operations Deployment Guide · vedkathe bundleGenerate a professional Operations & Deployment Guide as a formatted Word (.docx) file — environments, infrastructure, deployment architecture, CI/CD pipeline, deployment/rollback procedures, configuration and secrets management, backups, and disaster recovery. Use this whenever someone asks for a "deployment guide," "infra runbook," "release process document," or wants to document how a system is deployed and kept resilient (as distinct from day-to-day incident troubleshooting, which lives in the companion support-runbook skill). Part of an enterprise handover documentation suite (see also: project-overview-doc, architecture-document, high-level-design, support-runbook, api-documentation, database-design, release-maintenance-guide) but fully usable standalone.