vibex

Featured

Generate 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

API & Backend 392 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
86
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# vibeX *You vibed it into existence. vibeX shows you what you actually built.* Output is always two files: `<name>.<type>.json` (the spec, the source of truth) and `<name>.<type>.html` (self-contained viewer: pan/zoom, search, click-for-details, dark/light, SVG/PNG export). Not fancy. Correct and readable. Skill root: the directory containing this file. Every command below is `node <skill-root>/bin/vibex.mjs …`. ## Steps 1. **Pick the type** from the ask. One diagram per type per question; do not mix. | Ask | Type | Spec file | |---|---|---| | tables, models, schema, relations, FKs, data model | `erd` | `schemas/erd.schema.json` | | context, containers, components, who talks to what, system boundary | `c4` | `schemas/c4.schema.json` | | endpoints, routes, API surface, GraphQL operations, events/topics | `endpoints` | `schemas/endpoints.schema.json` | | statuses, state machine, lifecycle, what happens after X, allowed transitions | `lifecycle` | `schemas/lifecycle.schema.json` | 2. **Find a machine-readable source first.** Search the repo before reading code: - `endpoints`: `openapi.*`, `swagger.*`, `*.graphql`, `schema.gql`, or a generated schema endpoint dump. Run `import openapi` or `import graphql`. - `erd`: `schema.prisma` → `import prisma`. A GraphQL SDL can also seed an ERD with `import graphql <file> out.json --erd`. - `c4`: never importable. Author it (step 3). ```bash node bin/vibex.mjs import openapi path/to/openapi.yaml o...

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

Data & Documents Listed

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".

0 Updated 3 months ago
yash0208
AI & Automation Listed

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.

0 Updated 2 months ago
muchandresh
Code & Development Listed

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

8 Updated 2 weeks ago
aakashdhar