vibex
FeaturedGenerate ERD (entity-relationship), C4 (context/container/component), API endpoint catalogue, and lifecycle/state-machine diagrams as a validated JSON spec plus a standalone interactive HTML viewer. Imports OpenAPI, GraphQL SDL, and Prisma schemas directly; when no spec file exists, reads the code (NestJS controllers/resolvers, TypeORM/Prisma entities) and authors the JSON by hand. Use when the user asks for a database diagram, ERD, data model, table relationships, C4 diagram, system context, container or component diagram, API map, endpoint list, route overview, GraphQL operation overview, "show me the endpoints", status flow, state machine, lifecycle, allowed transitions, or "what happens after X is approved". Also writes the system's documentation as a checkable fact graph — every statement carries its source and a computed confidence, and a drift check fails CI when the code moves underneath it. Use when the user asks to document a system, write architecture docs, produce an onboarding or handover documen
Install
Quality Score: 93/100
Skill Content
Details
- Author
- Raja0sama
- Repository
- Raja0sama/vibex
- Created
- 2 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
visual-vibes
Analyze any repository (or a proposed system) and create, update, and explain evidence-backed architecture diagrams and docs. Use for creating or updating C4, UML, ERD, DFD, sequence, state, deployment, CI/CD, and security diagrams; generating HLD/LLD/ADRs; answering questions about how a codebase is structured; and producing animated diagram READMEs. Triggers on requests like "diagram this repo", "how is X wired up", "update the architecture diagram", "map the data flow", or "explain the system design".
vibe-map
Codebase cartographer and architecture explainer tailored for vibe coders and builders. Deeply scans directories, builds visual component maps, user journeys, function-by-function breakdowns, and impact blast-radius analysis.
vibe-graph
Dual-layer dependency graph for vibe-* projects. No external packages. DEPENDENCY_GRAPH.json maps file-level relationships with confidence tagging: EXTRACTED (verified from source, confidence 1.0), INFERRED (derived from specs/patterns, 0.6–0.95), AMBIGUOUS (flagged for review). Rationale nodes capture WHY, HACK, DECISION comments from source files — surfaced during bug diagnosis and review to prevent intent drift. God nodes identify highest-coupling files — read first in review, flagged in bug diagnosis, blocked from simultaneous parallel writes. CONCEPT_GRAPH.json maps semantic relationships (features, agents, models, components). graph.html is an interactive visual. Auto-updated via git diff. Queried by vibe-fix-bug, vibe-test, vibe-review, vibe-parallel. Primary value is semantic navigation: accurate blast-radius, intent-drift detection via rationale nodes, and safe parallel dispatch via god nodes — not raw token savings (current models have large context windows + prompt caching, so the graph is a precis