{ "markdown": "

\n \"vibe-cartographer\n \"Vibe\n

\n\n# Vibe Cartographer\n\n**Plot your course from idea to shipped app — vibe coding with purpose and direction.**\n\n[![stable](https://img.shields.io/github/v/tag/estevanhernandez-stack-ed/vibe-cartographer?label=stable&color=17d4fa)](https://github.com/estevanhernandez-stack-ed/vibe-cartographer/tags)\n\n## What it does\n\nVibe Cartographer takes you from idea spark to shipped app through a structured chain of slash commands, with documentation and security verification baked into the process. Each command produces an artifact — scope doc, PRD, technical spec, build checklist, reflection — that the next command consumes. The agent acts as a sharp, encouraging collaborator: it interviews you through each phase instead of waiting for prompts, and adapts its voice to the persona you pick.\n\n> **Based on the Learning Hackathon spec-driven dev plugin.** Vibe Cartographer extends and productionizes the spec-driven development approach introduced in the Learning Hackathon — rebuilt from the ground up as a builder-focused tool with persistent memory, cross-plugin profiles, selectable personas, and a reflective retro in place of the original classroom quiz. Credit to the Hackathon authors for the foundational workflow pattern.\n\n## How it works\n\n**The eight-command chain** runs idea → ship in order. Each step reads the prior artifacts and writes its own:\n\n`/onboard` → `/scope` → `/prd` → `/spec` → `/checklist` → `/build` → `/iterate` → `/reflect`\n\n| Command | What it does |\n| ------------ | -------------------------------------------------------------------- |\n| `/onboard` | Welcome, builder profiling, persona selection, architecture docs |\n| `/scope` | Brainstorm and refine your idea into a focused project scope |\n| `/prd` | Turn scope into detailed product requirements |\n| `/spec` | Translate the PRD into a technical blueprint using your architecture |\n| `/checklist` | Break the spec into a sequenced, dependency-aware build plan |\n| `/build` | Build the app — autonomous or step-by-step mode |\n| `/iterate` | Optional polish pass after the core build |\n| `/reflect` | Retro, peer-style feedback, and qualitative review |\n\nThe final checklist step is always **Documentation & Security Verification** — README, docs cleanup, secrets scan, dependency audit, and deployment security posture.\n\n**The self-evolution commands** sit on top of the chain. They're how the plugin reads its own runs and keeps itself honest:\n\n| Command | What it does |\n| -------------- | ----------------------------------------------------------------------------- |\n| `/evolve-cart` | **L3** — the plugin reads its own session logs and proposes self-improvements |\n| `/vitals` | **L3.5** — self-diagnostic health check across profile, logs, and complements |\n| `/friction` | **L3.5** — capture real-time friction signal with calibration for future evolve |\n| `/tend` | Read-only drift sweep on the app you built — entropy and spec deviation, writes nothing |\n\nNothing auto-applies. Every proposed change from `/evolve-cart` is one-at-a-time, with your consent.\n\n### Personas\n\nPick a voice during `/onboard` that shapes how the agent talks to you through the whole process. Personas coexist with the Learner / Builder pacing mode — persona controls **voice**, mode controls **pacing**.\n\n- **Professor** — *\"Let me explain the why.\"* Patient, explanatory, frequent checkpoints.\n- **Cohort** — *\"Let's think through this together.\"* Peer, collaborative, brainstormy.\n- **Superdev** — *\"You know what you're doing. Let's move.\"* Terse, direct, minimal handholding.\n- **Architect** — *\"Let's design for the long game.\"* Strategic, tradeoff-focused.\n- **Coach** — *\"Keep moving. Ship it.\"* Momentum-focused, anti-paralysis.\n- **System default** — No override. Base Claude Code behavior calibrated only by your experience level and mode.\n\nThe persona lives in `~/.claude/profiles/builder.json` under `shared.preferences.persona` and is respected cross-plugin — other Vibe plugins (like Vibe Doc) pick up the same voice, so you only onboard once.\n\n### Architecture docs\n\nVibe Cartographer guides technical decisions by your preferred stack, patterns, and conventions. During `/onboard`, you point it at your architecture docs — or skip to use sensible defaults. See [`plugins/vibe-cartographer/architecture/`](plugins/vibe-cartographer/architecture/) for the included defaults and an example (React + Supabase).\n\nThe unified profile and self-evolution loop are part of the [Self-Evolving Plugin Framework](docs/self-evolving-plugins-framework.md) — see that doc for the thesis, the 12-pattern catalog, and the maturity ladder the plugin is working through.\n\n## Validated on\n\nDogfooded across build cycles — Vibe Cartographer builds the other Vibe plugins. The eight-command chain is proven by the work it ships, run after run, on real apps.\n\n## Install\n\n**Stable (recommended) — as a Claude Code plugin via the marketplace:**\n\n```text\n/plugin marketplace add estevanhernandez-stack-ed/vibe-plugins\n/plugin install vibe-cartographer@vibe-plugins\n```\n\n**Canary — track this repo's `main`:**\n\n```text\n/plugin install vibe-cartographer@estevanhernandez-stack-ed/vibe-cartographer\n```\n\nThen navigate to a **fresh, empty folder** for your project and run `/onboard`. All project artifacts get created in your project folder under `docs/`.\n\n## Migration\n\nVibe Cartographer is the rename of what was previously `@esthernandez/app-project-readiness` (v0.5.0 and earlier). **Migration is automatic on your first `/onboard` run** — no manual steps:\n\n- Your unified builder profile at `~/.claude/profiles/builder.json` gets its `plugins.app-project-readiness` block copied to `plugins.vibe-cartographer` (old key preserved for one release as a safety net).\n- Deep-legacy markdown profiles at `~/.claude/plugins/data/app-project-readiness/user-profile.md` also migrate.\n- Legacy session logs at `~/.claude/plugins/data/app-project-readiness/sessions/` are left in place — append-only history isn't touched.\n- The old `@esthernandez/app-project-readiness` npm package is deprecated with a pointer. Install Vibe Cartographer via the marketplace above and uninstall the old one when you're ready.\n\n## More\n\n- [INSTALL.md](INSTALL.md) — detailed install, verification, configuration, troubleshooting, and uninstall steps\n- [CHANGELOG.md](CHANGELOG.md) — release history and contributing guide\n- [docs/self-evolving-plugins-framework.md](docs/self-evolving-plugins-framework.md) — thesis and pattern catalog driving the plugin's architecture\n\n## Part of the Vibe ecosystem\n\nPart of the **[Vibe Plugins](https://github.com/estevanhernandez-stack-ed/vibe-plugins)** marketplace from [626 Labs](https://626labs.dev) — foundations and process pillars for AI-assisted creation.\n\n```text\n/plugin marketplace add estevanhernandez-stack-ed/vibe-plugins\n```\n\n## Credits\n\n- **Based on the Learning Hackathon spec-driven development plugin.** The eight-command workflow (onboard → scope → PRD → spec → checklist → build → iterate → reflect) is adapted from the Hackathon's original spec-driven dev pattern. Vibe Cartographer productionizes that workflow with builder-focused language, persistent cross-plugin memory, selectable personas, and a reflective retro in place of the original quiz.\n- Built by [626Labs LLC](https://626labs.dev) — Fort Worth, TX.\n\n## License\n\nMIT — *Imagine Something Else.*\n", "bytes": 7909, "sha": "b47729219152ebb4924826cceeae86d762f4be993725b913007054dc8ae44215", "repo_slug": "estevanhernandez-stack-ed/vibe-cartographer", "fonte": "repo", "truncated": false, "api": "https://agentalog.com/api/listings/plg_estevanhernandez_stack_ed_vibe_cartograp_7e15e3b4/readme" }