@esthernandez/vibe-cartographer 1.0.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,21 @@
+{
+  "name": "vibe-cartographer",
+  "owner": {
+    "name": "626Labs LLC"
+  },
+  "metadata": {
+    "description": "Vibe Cartographer — plot your course from idea to shipped app. Spec-driven development, delivered as eight slash commands."
+  },
+  "plugins": [
+    {
+      "name": "vibe-cartographer",
+      "source": "./plugins/vibe-cartographer",
+      "description": "Vibe Cartographer — plot your course from idea to shipped app through spec-driven development, delivered as eight slash commands.",
+      "author": {
+        "name": "626Labs LLC"
+      },
+      "keywords": ["vibe-cartographer", "spec-driven", "app-readiness", "project-planning", "claude-code-plugin"],
+      "category": "education"
+    }
+  ]
+}

package/CHANGELOG.md

@@ -0,0 +1,122 @@
+<!-- markdownlint-disable MD024 -->
+<!-- Keep-a-Changelog uses duplicate "Added / Changed / Fixed" headings per version by design. -->
+
+# Changelog
+
+All notable changes to this project are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+- Nothing yet.
+
+## [1.0.0] — 2026-04-15 — Rebrand to Vibe Cartographer
+
+The plugin formerly known as `@esthernandez/app-project-readiness` is now **Vibe Cartographer**. Same 8-command spec-driven workflow, same personas, same session memory — new name that actually says what the plugin does: *plot your course from idea to shipped app*.
+
+### Changed
+
+- **Package rename.** `@esthernandez/app-project-readiness` → `@esthernandez/vibe-cartographer`. The old package is deprecated on npm with a pointer to the new one; existing installs keep working but get a deprecation warning on next install.
+- **Plugin directory rename.** `plugins/app-project-readiness/` → `plugins/vibe-cartographer/`. Update any local pointers in Claude Desktop's Personal Plugins panel after upgrading.
+- **Unified profile namespace.** `plugins.app-project-readiness` → `plugins.vibe-cartographer` in `~/.claude/profiles/builder.json`. `/onboard` auto-migrates on first v1.0.0+ run; the old key is kept side-by-side for one release as a safety net.
+- **Session log path.** `~/.claude/plugins/data/app-project-readiness/sessions/` → `~/.claude/plugins/data/vibe-cartographer/sessions/`. Legacy logs are preserved untouched (append-only history doesn't migrate).
+- **ASCII banner.** Replaced the 626Labs FIGlet banner with a cleaner 5-line neural-network mesh + side-by-side text — cleaner alignment, more reproducible under the LLM's rendering.
+- **GitHub repository renamed.** `estevanhernandez-stack-ed/app-readinessplugin` → `estevanhernandez-stack-ed/vibe-cartographer`. GitHub auto-redirects the old URL, so existing clones keep working until you update the remote.
+
+### Migration
+
+On first `/onboard` with v1.0.0+, the plugin:
+
+1. Checks `~/.claude/profiles/builder.json` for a legacy `plugins.app-project-readiness` block
+2. Copies it to `plugins.vibe-cartographer`, leaving the old key in place for one release as a safety net
+3. Logs the migration in `process-notes.md`
+
+The deep-legacy markdown profile at `~/.claude/plugins/data/app-project-readiness/user-profile.md` (v0.4.x and earlier) still migrates the way it did in v0.5.0, just now into `plugins.vibe-cartographer` instead.
+
+### Why the rename
+
+"App Project Readiness" described what the plugin *technically* was but said nothing about the vibe. "Vibe Cartographer" captures the whole point: vibe coding with purpose and direction. Cartographers produce maps before expeditions — this plugin produces scope, PRD, spec, and checklist docs before you write any code. Pairs with [Vibe Doc](https://www.npmjs.com/package/@esthernandez/vibe-doc) in the 626Labs ecosystem: Doc writes the documentation you need, Cartographer plots the route you'll take.
+
+This is the "plugin has graduated from beta" moment. No new features — just the rename, the migration machinery, and a new banner.
+
+## [0.5.0] — 2026-04-15
+
+### Added
+
+- **Persona selection** during `/onboard` (new step 9). Five named personas — **Professor**, **Cohort**, **Superdev**, **Architect**, **Coach** — plus a **System default** that preserves base behavior. Persona controls voice (relational stance, explanation depth, checkpoint style) and coexists with the Learner / Builder mode which controls pacing. Stored in `shared.preferences.persona` on the unified profile so all 626Labs plugins respect it.
+- **Session-logger skill** (`skills/session-logger/SKILL.md`). Every command appends a one-line JSON entry to `~/.claude/plugins/data/app-project-readiness/sessions/<date>.jsonl` at completion — command name, outcome, user pushback flag, friction notes, key decisions. Local-first, append-only, no PII. This is the Level 2 increment of the Self-Evolving Plugin Framework: passive memory that a future `/app-readiness-evolve` step will read to propose plugin improvements.
+- **Self-Evolving Plugin Framework doc** at [docs/self-evolving-plugins-framework.md](docs/self-evolving-plugins-framework.md). Thesis, 12-pattern catalog, and applied playbook (maturity ladder, retrofit/scaffold playbooks, anti-patterns, shipping cadence). The architectural north star for this plugin and all future 626Labs plugins.
+- **Persona Adaptation reference table** in the guide SKILL, mapping each persona to voice / explanations / checkpoints / feedback style so every command renders a consistent voice from start to handoff.
+- **Learning Hackathon credit** in the README — this plugin extends the foundational spec-driven-dev workflow from the Hackathon, rebuilt as a builder-focused tool with persistent memory and a reflective retro.
+
+### Changed
+
+- **Unified builder profile** moved from plugin-scoped markdown (`~/.claude/plugins/data/app-project-readiness/user-profile.md`) to a cross-plugin JSON file at `~/.claude/profiles/builder.json`. Schema has a top-level `shared` block (identity, experience, preferences, creative sensibility) and `plugins.<plugin-name>` blocks (plugin-scoped state). Strict ownership: each plugin writes its own `plugins.<name>` block and never stomps other plugins' namespaces. `/onboard` auto-migrates the legacy file to the new location on first run; old file preserved as `.bak`.
+- **README install instructions** rewritten. Removed the stale `/install-plugin` references (that command doesn't exist in current Claude Code versions) and documented three real install paths: npm, Claude Desktop Personal Plugins UI, and local clone.
+- **README table formatting and code block language hints** cleaned up (markdown lint fixes).
+
+### Fixed
+
+- **`/reflect` no longer feels like a classroom wrap-up.** Rewrote the reflect SKILL, the reflection template, and the eval-rubric to read like a peer retro. "What landed / What to tighten" replaces "strength / growth area", "quiz" becomes "check-in", and the defensive disclaimers ("not to grade you", "no wrong answers") are gone. The final artifact reads like feedback from a senior engineer doing a post-ship retro, not a teacher wrapping up a student project.
+
+## [0.4.0] — 2026-04-15
+
+### Added
+
+- **Persistent global builder profile.** `/onboard` now detects returning builders, skips the background interview if a profile exists, and jumps straight to project-specific questions. The profile is written during `/onboard` and updated at the end of each full run during `/reflect`. Per-project `docs/builder-profile.md` is still created — the global profile captures the *person*, the per-project profile captures the *project*.
+
+## [0.3.0] — 2026-04-15
+
+### Changed
+
+- **Rebranded from Marcus Corporation to 626Labs LLC** across the plugin manifest, marketplace entry, README, plugin CLAUDE.md, and the onboard welcome banner.
+- **Welcome banner** replaced with a clean FIGlet-style `626Labs` ASCII logo. The previous asterisk-and-dash art rendered as a scrambled wall of characters because it was too fragile for the LLM to reproduce character-perfect.
+
+## [0.2.0] and earlier
+
+Foundational work, pre-dating the first npm publish:
+
+- Initial plugin structure with the 8-command workflow: `/onboard` → `/scope` → `/prd` → `/spec` → `/checklist` → `/build` → `/iterate` → `/reflect`.
+- Learner / Builder mode split for pacing.
+- Architecture docs support — the builder can point at their own stack preferences during `/onboard` and downstream commands calibrate against them.
+- Per-project `docs/builder-profile.md` artifact that every command reads.
+- Extensive builder-focused language cleanup after a LADDER stress-test surfaced too much "learner" framing in early drafts.
+
+---
+
+## Contributing
+
+This plugin is maintained by [626Labs LLC](https://626labs.dev) (solo maintainer at the moment — expect slower turnaround than a team-backed project).
+
+### How to contribute
+
+1. **Fork** the repo on GitHub: [estevanhernandez-stack-ed/vibe-cartographer](https://github.com/estevanhernandez-stack-ed/vibe-cartographer).
+2. **Branch** from `main` with a short, focused name (`fix/reflect-wording`, `feat/new-persona`, etc.).
+3. **Make the change** — most of this plugin is markdown (SKILL files and templates). No build step.
+4. **Test it locally** by installing from your fork (`git clone && point Claude Code at it`) or by pointing the plugin directory in your Claude Desktop Personal Plugins panel at your working copy.
+5. **Open a PR** against `main` with a clear description of what's changing and why.
+
+### Development setup
+
+There's no build, no package manager install, no test suite yet — just markdown:
+
+```bash
+git clone https://github.com/estevanhernandez-stack-ed/vibe-cartographer
+cd vibe-cartographer
+# edit plugins/vibe-cartographer/skills/**/SKILL.md directly
+```
+
+Point Claude Desktop's Personal plugins at `plugins/vibe-cartographer/` and iterate. Every change takes effect the next time you run a slash command.
+
+### Proposing a change
+
+- **Small fixes and language tweaks** — open a PR directly, reference the specific SKILL file and section you're changing.
+- **New personas, new commands, structural changes** — open an issue first to discuss scope. The plugin has a specific tone (builder-focused, peer-to-peer) and structural changes to the 8-command flow deserve a conversation.
+- **Bug fixes** — include a short "before / after" in the PR description showing what was wrong and how the fix changes the behavior.
+
+### Review process
+
+Reviews are handled by the maintainer (Estevan). Expect feedback within a few days. There's no formal approval process — if the change is sound and fits the plugin's voice, it merges.
+
+### Code of conduct
+
+Be direct, be kind, don't waste each other's time. Disagreements about technical direction are welcome; personal attacks, gatekeeping, and "this is bad because I say so" are not.

package/INSTALL.md

@@ -0,0 +1,132 @@
+# Installation Guide — Vibe Cartographer
+
+## Prerequisites
+
+- **Claude Code** — any form of it: CLI, Desktop app, VS Code extension, or JetBrains plugin. Vibe Cartographer defines slash commands that Claude Code executes. Without Claude Code, there's nothing to run.
+- **Node.js 18 or later** — only required if you plan to install via npm. Installing from a local clone doesn't need Node at all.
+- **A fresh, empty project folder** — the plugin creates artifacts in `docs/` of your working directory. Running `/onboard` in a directory that already has code and docs mixed together will get messy fast. Make a new folder for your project before you start.
+
+## Install paths
+
+You only need one of these. Pick whichever matches how you're already running Claude Code.
+
+### Option 1: npm (recommended)
+
+```bash
+npm install -g @esthernandez/vibe-cartographer
+```
+
+This drops the plugin files on your disk at your npm global root — typically `~/.npm-global/lib/node_modules/@esthernandez/vibe-cartographer/` on macOS/Linux or `%APPDATA%\npm\node_modules\@esthernandez\vibe-cartographer\` on Windows. You then need to tell Claude Code about them — see [Connecting to Claude Code](#connecting-to-claude-code) below.
+
+### Option 2: Claude Desktop — Personal plugin
+
+If you're on the Claude Desktop app and don't want an npm install:
+
+1. Open **Personal plugins** in Claude Desktop (the panel in the left sidebar).
+2. Click the **+** button → **Create plugin**.
+3. Point it at a local clone of this repo (see Option 3 for the clone step).
+4. The plugin's slash commands become available immediately — no restart required.
+
+### Option 3: Clone and reference locally
+
+```bash
+git clone https://github.com/estevanhernandez-stack-ed/vibe-cartographer ~/vibe-cartographer
+```
+
+Then point Claude Code at `~/vibe-cartographer/plugins/vibe-cartographer/` as the plugin root. This is the same as Option 2 minus the Claude Desktop UI step — useful if you're on the Claude Code CLI directly.
+
+## Connecting to Claude Code
+
+After installing, Claude Code needs to know where the plugin lives. The exact steps depend on your client:
+
+- **Claude Desktop** — use the **Personal plugins** panel (**+** button → **Create plugin** → point at the folder). Same flow for Option 1 (point at the npm install path) and Option 3 (point at your local clone).
+- **Claude Code CLI** — if your version has a plugin-add command, point it at the install path. Otherwise clone the repo and rely on Claude Code's plugin discovery for folders in its known marketplace list.
+- **VS Code / JetBrains** — Claude Code in your IDE reads from the same global plugin config as Claude Desktop. Install via Option 2 on Claude Desktop first and the IDE will pick it up on next launch.
+
+**Pointing at the right folder matters.** The plugin root is the folder that contains `.claude-plugin/plugin.json` — in this repo that's `plugins/vibe-cartographer/`, not the repo root. Pointing at the repo root will not work.
+
+## Verification
+
+Open Claude Code in a **fresh, empty folder** for a project you want to build, then run:
+
+```text
+/onboard
+```
+
+You should see the Vibe Cartographer neural-network welcome banner and the first onboarding question. If you instead see `Unknown skill: onboard`, the plugin isn't wired in yet — double-check your Claude Code plugin list and confirm the path points at the folder containing `.claude-plugin/plugin.json`.
+
+You can also check the installed version from a shell:
+
+```bash
+npm list -g @esthernandez/vibe-cartographer
+```
+
+## Configuration
+
+No required configuration. On first `/onboard`, the plugin creates a **unified builder profile** at `~/.claude/profiles/builder.json` that captures your identity, experience level, and preferences (tone, pacing, persona). This profile is shared across all 626Labs plugins — install another 626Labs plugin later (like Vibe Doc) and it reads the same file, so you don't re-onboard.
+
+You can inspect the profile any time:
+
+```bash
+cat ~/.claude/profiles/builder.json
+```
+
+It's plain JSON, lives in your home directory, and never leaves your machine.
+
+## Migrating from `@esthernandez/app-project-readiness`
+
+Vibe Cartographer is the rename of what used to be `@esthernandez/app-project-readiness` (v0.5.0 and earlier). v1.0.0 handles the migration automatically:
+
+1. **Install the new package:** `npm install -g @esthernandez/vibe-cartographer`
+2. **Uninstall the old one** when you're ready: `npm uninstall -g @esthernandez/app-project-readiness`
+3. **Run `/onboard`** in a project. The plugin will:
+   - Check `~/.claude/profiles/builder.json` for a legacy `plugins.app-project-readiness` block
+   - Copy that block to `plugins.vibe-cartographer` (leaving the old key in place for one release as a safety net)
+   - Note the migration in `process-notes.md`
+4. **Legacy session logs** at `~/.claude/plugins/data/app-project-readiness/sessions/` are preserved untouched — append-only history isn't migrated, it just stays where it was written.
+5. **Your per-project `docs/*.md` artifacts are untouched.** Nothing in your existing project folders needs to change.
+
+## Troubleshooting
+
+**`Unknown skill: onboard` when running `/onboard`.**
+Claude Code isn't loading the plugin. Confirm the plugin folder is registered in your client's plugin list, and that you're pointing at the folder that contains `.claude-plugin/plugin.json` (the plugin root — `plugins/vibe-cartographer/` in this repo), not the repo root or a parent directory.
+
+**The welcome banner renders as a scrambled wall of characters.**
+You're on an ancient install (0.2.x or earlier) that still ships the fragile asterisk-and-dash ASCII art. Upgrade:
+
+```bash
+npm install -g @esthernandez/vibe-cartographer@latest
+```
+
+**`/reflect` feels like a classroom quiz instead of a peer retro.**
+Your Claude Code is loading a 0.4.x or earlier copy. Upgrade to 1.0.0+ (Vibe Cartographer) or 0.5.0+ (final app-project-readiness).
+
+**My builder profile still has `plugins.app-project-readiness` and not `plugins.vibe-cartographer`.**
+Run `/onboard` once on v1.0.0+ and the plugin will copy the old block to the new location automatically. Both keys will exist side-by-side for one release as a safety net; the next major bump will drop the old key.
+
+**I picked the wrong persona or mode and want to switch.**
+Tell the agent directly mid-session: "switch to Superdev persona" or "switch to Builder mode". The override sticks for the rest of the session. To change it permanently for future runs, edit `~/.claude/profiles/builder.json` directly (it's plain JSON — `shared.preferences.persona` and `plugins.vibe-cartographer.mode`).
+
+## Uninstalling
+
+```bash
+npm uninstall -g @esthernandez/vibe-cartographer
+# and if you still have the old package installed:
+npm uninstall -g @esthernandez/app-project-readiness
+```
+
+If you want to wipe the builder profile and session logs too:
+
+```bash
+# macOS/Linux
+rm -f ~/.claude/profiles/builder.json
+rm -rf ~/.claude/plugins/data/vibe-cartographer/
+rm -rf ~/.claude/plugins/data/app-project-readiness/
+
+# Windows (PowerShell)
+Remove-Item -Path "$HOME\.claude\profiles\builder.json" -Force
+Remove-Item -Path "$HOME\.claude\plugins\data\vibe-cartographer" -Recurse -Force
+Remove-Item -Path "$HOME\.claude\plugins\data\app-project-readiness" -Recurse -Force
+```
+
+Both are safe to delete — the plugin recreates them on next use, and nothing else on your system depends on them.

package/README.md

@@ -0,0 +1,148 @@
+# Vibe Cartographer
+
+**Plot your course from idea to shipped app.**
+
+```text
+   ◯───◯───◯
+   │ ╲ │ ╱ │
+   ◯───◯───◯       V I B E   C A R T O G R A P H E R
+   │ ╱ │ ╲ │        plot your course
+   ◯───◯───◯
+```
+
+A spec-driven development plugin for [Claude Code](https://claude.ai/code) and Claude Desktop. Vibe coding with purpose and direction — takes you from idea spark to shipped app through eight structured commands, with documentation and security verification baked into the process.
+
+> **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.
+
+## What It Does
+
+Vibe Cartographer delivers a guided spec-driven development workflow as eight slash commands. Each command produces artifacts (scope doc, PRD, technical spec, build checklist, reflection) that downstream commands consume. The agent acts as a sharp, encouraging collaborator — interviewing you through each phase rather than waiting for prompts, adapting its voice to the persona you pick.
+
+**Command chain:** `/onboard` → `/scope` → `/prd` → `/spec` → `/checklist` → `/build` → `/iterate` → `/reflect`
+
+| Command      | What It Does                                                     |
+| ------------ | ---------------------------------------------------------------- |
+| `/onboard`   | Welcome, builder profiling, persona selection, architecture docs |
+| `/scope`     | Brainstorm and refine your idea into a focused project scope     |
+| `/prd`       | Turn scope into detailed product requirements                    |
+| `/spec`      | Translate PRD into a technical blueprint using your architecture |
+| `/checklist` | Break the spec into a sequenced, dependency-aware build plan     |
+| `/build`     | Build the app — autonomous or step-by-step mode                  |
+| `/iterate`   | Optional polish pass after the core build                        |
+| `/reflect`   | Retro, peer-style feedback, and qualitative review               |
+
+The final checklist step is always **Documentation & Security Verification** — README, docs cleanup, secrets scan, dependency audit, and deployment security posture.
+
+## Personas
+
+Pick 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**.
+
+- **Professor** — *"Let me explain the why."* Patient, explanatory, frequent checkpoints.
+- **Cohort** — *"Let's think through this together."* Peer, collaborative, brainstormy.
+- **Superdev** — *"You know what you're doing. Let's move."* Terse, direct, minimal handholding.
+- **Architect** — *"Let's design for the long game."* Strategic, tradeoff-focused.
+- **Coach** — *"Keep moving. Ship it."* Momentum-focused, anti-paralysis.
+- **System default** — No override. Base Claude Code behavior calibrated only by your experience level and mode.
+
+The persona lives in `~/.claude/profiles/builder.json` under `shared.preferences.persona` and is respected cross-plugin — other 626Labs plugins (like [Vibe Doc](https://www.npmjs.com/package/@esthernandez/vibe-doc)) pick up the same voice.
+
+## Architecture Docs
+
+Vibe Cartographer supports custom architecture docs so technical decisions are guided by your preferred stack, patterns, and conventions. During `/onboard`, the builder points to their architecture docs (or skips to use sensible defaults).
+
+See [`plugins/vibe-cartographer/architecture/`](plugins/vibe-cartographer/architecture/) for the included defaults and an example.
+
+## Install
+
+Requires [Claude Code](https://claude.ai/code) or Claude Desktop with plugin support.
+
+### Option 1: npm (recommended)
+
+```bash
+npm install -g @esthernandez/vibe-cartographer
+```
+
+Then in Claude Code / Claude Desktop, point your personal plugins at the installed path:
+
+- macOS/Linux: `~/.npm-global/lib/node_modules/@esthernandez/vibe-cartographer/plugins/vibe-cartographer`
+- Windows: `%APPDATA%\npm\node_modules\@esthernandez\vibe-cartographer\plugins\vibe-cartographer`
+
+### Option 2: Claude Desktop personal plugin
+
+1. Open Claude Desktop's **Personal plugins** panel.
+2. Click **+ Create a plugin**.
+3. Point it to the `plugins/vibe-cartographer` folder from this repo (cloned or downloaded).
+4. The slash commands (`/onboard`, `/scope`, `/prd`, etc.) become available.
+
+### Option 3: Clone and reference locally
+
+```bash
+git clone https://github.com/estevanhernandez-stack-ed/vibe-cartographer ~/vibe-cartographer
+```
+
+Then point your Claude Code / Claude Desktop at `~/vibe-cartographer/plugins/vibe-cartographer`.
+
+### Migrating from `@esthernandez/app-project-readiness`
+
+Vibe Cartographer is the rename of what was previously `@esthernandez/app-project-readiness` (v0.5.0 and earlier). The migration is automatic:
+
+- Your unified builder profile at `~/.claude/profiles/builder.json` gets its `plugins.app-project-readiness` block copied to `plugins.vibe-cartographer` on first v1.0.0+ run.
+- The old `@esthernandez/app-project-readiness` npm package is deprecated. Run `npm install -g @esthernandez/vibe-cartographer` and uninstall the old one when you're ready.
+- Legacy session logs at `~/.claude/plugins/data/app-project-readiness/sessions/` are left in place — append-only history isn't touched.
+
+### Start the workflow
+
+Navigate to a **fresh, empty folder** for your project and run:
+
+```text
+/onboard
+```
+
+All project artifacts get created in your project folder under `docs/`.
+
+## Project Structure
+
+```text
+plugins/vibe-cartographer/
+├── .claude-plugin/plugin.json    # Plugin metadata
+├── CLAUDE.md                     # Root agent behavior config
+├── architecture/                 # Architecture docs (customizable)
+│   ├── README.md
+│   ├── default-patterns.md       # Fallback stack patterns
+│   └── example-architecture.md   # Example: React + Supabase
+└── skills/                       # One folder per slash command
+    ├── onboard/SKILL.md
+    ├── scope/SKILL.md
+    ├── prd/SKILL.md
+    ├── spec/SKILL.md
+    ├── checklist/SKILL.md
+    ├── build/SKILL.md
+    ├── iterate/SKILL.md
+    ├── reflect/SKILL.md
+    ├── session-logger/SKILL.md   # Append-only session memory (L2)
+    └── guide/                    # Shared references and templates
+        ├── SKILL.md              # Core agent behavior (loaded by all commands)
+        ├── references/           # eval-rubric, prd-guide, spec-patterns
+        └── templates/            # Output templates for each artifact
+```
+
+## Works Independently or Together
+
+Vibe Cartographer is part of the **626Labs plugin ecosystem**. It runs standalone or alongside other 626Labs plugins like [`@esthernandez/vibe-doc`](https://www.npmjs.com/package/@esthernandez/vibe-doc) — when both are installed, they share a **unified builder profile** at `~/.claude/profiles/builder.json` so you only onboard once across all 626Labs plugins. Persona, tone, experience, and preferences carry across.
+
+The unified profile is part of the [Self-Evolving Plugin Framework](docs/self-evolving-plugins-framework.md) — see that doc for the thesis, 12-pattern catalog, and the maturity ladder the plugin is working through. Vibe Cartographer is currently at **Level 2** (session memory + passive feedback capture); Level 3 (reflective evolution — the plugin proposes changes to itself based on observed usage) is on the roadmap.
+
+## Documentation
+
+- [INSTALL.md](INSTALL.md) — detailed install, verification, configuration, troubleshooting, and uninstall steps
+- [CHANGELOG.md](CHANGELOG.md) — release history and contributing guide
+- [docs/self-evolving-plugins-framework.md](docs/self-evolving-plugins-framework.md) — thesis and pattern catalog driving the plugin's architecture
+
+## Credits
+
+- **Based on the Learning Hackathon spec-driven development plugin.** The 8-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.
+- Built by [626Labs LLC](https://626labs.dev) — Fort Worth, TX.
+
+## License
+
+MIT