vibe-cartographer
Developer not provided
Vibe Cartographer turns the vibe-coding hype into a structured workflow. Eight commands walk you from idea spark to shipped app: a flipped-interaction onboarding (/onboard), a scope brainstorm (/sc...
From the developer
Works with
Claude Code
Description
From the marketplace listing
Vibe Cartographer turns the vibe-coding hype into a structured workflow. Eight commands walk you from idea spark to shipped app: a flipped-interaction onboarding (/onboard), a scope brainstorm (/scope), a PRD interview (/prd), a tech spec grounded in your architecture (/spec), a dependency-aware build checklist (/checklist), an autonomous-or-step-by-step build loop (/build), an optional polish pass (/iterate), and a real retrospective (/reflect). The agent picks up a unified builder profile at ~/.claude/profiles/builder.json so persona, pacing, and stack preferences carry across projects and across other 626Labs plugins. Three Level-3.5 self-evolution commands round it out: /evolve (the plugin reads its own logs and proposes improvements), /vitals (self-diagnostic health check), /friction (real-time friction capture for future evolve cycles).
What changed
No changes recorded yet. Follow this plugin to keep track of future changes.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Vibe coding helper tool. Visual editor for Claude Code. Create commands, agents, pipelines, and prompts with handy GUI.
Shared terms: vibe, coding, command, agent
-
Hyperflow turns a Claude Code session into a structured engineering workflow through eight chained slash commands. /hyperflow:spec runs a...
Shared terms: eight, structured, command, scope
-
A TDD-driven iterative feedback loop for software development. 16 cohesive Claude Code skills walk an idea from brainstorm → plan → execu...
Shared terms: idea, walk, brainstorm, iterate
-
Onboard a Code-with-Claude Makers Cardputer with one /maker-setup command — clones the build-with-claude repo, flashes UIFlow firmware, a...
Shared terms: onboarding, command, onboard
-
Prodscope adds a structured Builder-Breaker loop to your AI coding assistant so every change is challenged for production risks before it...
Shared terms: coding, structured, builder, loop
Files & skills
vibe-cartographer · catalog manifest
Saved declaration
{}
vibe-cartographer · catalog manifest
Saved declaration
{
"name": "vibe-cartographer",
"source": {
"sha": "e9a8f3a82d9b94f964b5072a10d4c7f3baab9700",
"url": "https://github.com/estevanhernandez-stack-ed/vibe-cartographer.git",
"source": "url"
},
"homepage": "https://github.com/estevanhernandez-stack-ed/vibe-cartographer#readme",
"description": "Vibe Cartographer turns the vibe-coding hype into a structured workflow. Eight commands walk you from idea spark to shipped app: a flipped-interaction onboarding (/onboard), a scope brainstorm (/scope), a PRD interview (/prd), a tech spec grounded in your architecture (/spec), a dependency-aware build checklist (/checklist), an autonomous-or-step-by-step build loop (/build), an optional polish pass (/iterate), and a real retrospective (/reflect). The agent picks up a unified builder profile at ~/.claude/profiles/builder.json so persona, pacing, and stack preferences carry across projects and across other 626Labs plugins. Three Level-3.5 self-evolution commands round it out: /evolve (the plugin reads its own logs and proposes improvements), /vitals (self-diagnostic health check), /friction (real-time friction capture for future evolve cycles)."
}
Catalog declarations and available plugin.json metadata are saved. Referenced skills and executable source files are not downloaded or tested. Missing components in a manifest do not prove that the plugin has none.
Installation instructions
Community
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vibe-cartographer@claude-communityTechnical details
- Sources
- Community
- First seen
- Oct 3, 2026 · 22:13 UTC
- Last seen
- Nov 7, 2026 · 12:00 UTC
- Latest observed change
- Oct 3, 2026 · 22:13 UTC
- Collection status
- Listed
- Reported installs
- Not provided
Installation counts are source-reported, not independently verified active users. Observation dates are not release dates.
Download plugin data (JSON)Plugin history: freshly prepared. Prepared . Refreshed when catalog data changes or after 6 hours. Your account and Follow status are live.