claude

CoFounder

Guardrails + VibeSpec/FlowSpec feature flow + 16 skills, 4 commands, 3 agents, 3 hooks, and a built-in MCP server.

0 on GitHubv0.2.0MITupdated 24 days agodevelopment
/

Plugin cofounder from marketplace waymaker-ai in waymaker-ai/ranavibe. Commands read from the repo's manifest — 23 days ago.

What it installs

Skills (16)

  • cofounder-check

    Use this skill when the user asks to validate their repo against CoFounder guardrails — "run cofounder check", "verify the changes are safe", "is this PR-ready?", "check for guardrail violations". Runs typecheck, lint, tests, and CoFounder-specific rules (no secrets, no mock data in prod, no scope c

  • cofounder-commit

    Use this skill when the user asks to commit their staged changes, or asks "what's a good commit message for this". Writes a Conventional Commits-style message from the ACTUAL staged diff. Will NEVER commit without explicit user confirmation.

  • cofounder-compliance-frame

    Use this skill BEFORE implementing a feature that may touch regulated data (health records, payments, EU users, financial advice, minors). Reframes the feature spec against HIPAA, GDPR/CCPA, SEC, PCI DSS, FERPA, or SOX requirements and surfaces what changes in scope, data handling, audit logging, an

  • cofounder-context-fit

    Use this skill when the agent is hitting context limits, the prompt is too long, or "this conversation is getting expensive". Distills long inputs (long files, long histories, huge diffs, large RAG returns) into the minimum context that preserves the answer. Wraps `@waymakerai/aicofounder-context-op

  • cofounder-cost-route

    Use this skill when the user asks "which model should I use?", "how much will this cost?", or "make this cheaper". Recommends the cheapest model that's still good enough for the task, based on task class and the project's budget envelope. Wraps the cost tracking and routing in `@waymakerai/aicofound

  • cofounder-diagram

    Use this skill when the user asks for an architecture diagram, sequence diagram, ER diagram, dependency graph, flowchart, or "show me how this works visually". Generates Mermaid (default) or PlantUML diagrams from REAL code — actual imports, actual call graph, actual schema — never invented relation

  • cofounder-feature-implement

    Use this skill when the user points to a CoFounder feature spec and asks to implement it — "implement specs/X.yml", "build this spec", "let's ship this". Creates a branch, proposes a scoped changeset, implements under VibeSpec constraints, adds tests, and runs guardrail checks before handing off for

  • cofounder-feature-new

    Use this skill when the user wants to start a new feature — "add X feature", "let's build a Y page", "I want to add Z to the app". Guides idea → clarifying questions → VibeSpec-compliant feature spec written to `specs/<slug>.spec.yml`. DOES NOT write implementation code.

  • cofounder-pattern-scout

    Use this skill BEFORE writing new code, when the user asks to "add", "build", "create", or "extract" something — to find existing patterns in the repo so the agent extends them instead of reinventing. Searches for similar functions, components, hooks, models, routes, and styling. Returns the closest

  • cofounder-pr-summary

    Use this skill before opening a PR, when the user asks "write the PR description" or "summarize these changes". Generates a PR description from the ACTUAL diff — what changed, why, blast radius, test coverage — framed as a mental model the reviewer can hold in their head, not a list of file names.

  • cofounder-readme

    Use this skill when the user asks for a README, "documentation for this package", or "explain this project to a new dev". Generates a README from REAL exports, REAL scripts, REAL config — never from imagined APIs. Writes to README.md (or asks before overwriting an existing one).

  • cofounder-sandbox-preview

    Use this skill BEFORE running anything destructive — migrations, data backfills, mass renames, deletions, scripts that touch external services. Runs the operation in `@waymakerai/aicofounder-sandbox` and reports what would happen, without touching the real environment. Required for any skill marked

  • cofounder-second-opinion

    Use this skill when the user asks "is this right?", "double-check this", "get another perspective", or before merging anything high-stakes. Routes the same prompt through a *different* model (or even a different provider) via `@waymakerai/aicofounder-core`'s router and diffs the answers. Surfaces di

  • cofounder-spec-review

    Use this skill when the user has a CoFounder spec file (under specs/) and asks to review it — "review this spec", "is this spec good?", "anything missing?". Returns a structured critique covering completeness, testability, scope clarity, and VibeSpec compliance. Does NOT modify the spec.

  • cofounder-test-plan

    Use this skill when the user asks "what tests should I write?", "test plan for this feature", or after a feature is implemented but tests are missing. Reads a spec or a diff and proposes a tiered test plan — what to assert, at what layer (unit / integration / e2e), and what's NOT worth testing. Writ

  • cofounder-vibespec-author

    Use this skill when the user asks to "set up CoFounder", "create a VibeSpec", or "what rules should this project follow?". Reads the repo to infer existing conventions (design system, file layout, test framework, branching style, security posture) and proposes a VibeSpec that codifies them. Writes t

Slash commands (4)

  • /cofounder:check

    Run CoFounder safety gates on the current changeset (secrets, mock data, scope, design system, missing tests). Usage — /check or /check --diff <range>

  • /cofounder:cofounder

    CoFounder root command — route to feature-new, feature-implement, check, or spec-review. Usage — /cofounder <subcommand> [args]

  • /cofounder:explain-changes

    Explain the current branch's changes as a mental model — what changed, why, blast radius — not a file list. Usage — /explain-changes [--diff <range>]

  • /cofounder:spec

    Turn a feature idea into a VibeSpec-compliant spec file. Usage — /spec <one-line idea> or /spec (interactive)

Subagents (3)

  • cofounder-reviewer

    Use this agent to review a diff or PR against the repo's CoFounder VibeSpecs. Checks for secrets, mock data in prod, scope violations, design-system breaches, missing tests, and deviations from referenced specs. Returns a structured review with confidence-filtered findings — reports only high-priori

  • cofounder-scout

    Spawnable sub-agent variant of the pattern-scout skill. Delegate to this agent when you want a separate, isolated context to find existing patterns in the repo before writing new code — searches for similar functions, components, hooks, models, and routes, then returns ranked matches with extend-vs-

  • cofounder-spec-writer

    Use this agent when the user describes a feature idea but the scope, acceptance criteria, or data sources aren't clear. Asks 3–5 clarifying questions, searches the repo for prior art, and writes a VibeSpec-compliant feature spec to `specs/<slug>.spec.yml`. Use proactively before any non-trivial feat

View source on GitHub rana.cx

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Use Alibaba Open Code Review from local Codex.

2 skills

alibaba/open-code-review 50,068

slidev

claude

Claude Code skill for creating and presenting Slidev slidedecks

1 skill

slidevjs/slidev 49,452

Maintain CoFounder?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted