codex

minimal-vibe-coding-kit

Reusable vibe coding skills and workflows for Codex-compatible repositories.

26 on GitHubby Minimal Vibe Coding Kitv0.5.15MITupdated 1 month ago

Ships a Codex manifest but no marketplace file, so Codex can't add it by name yet. Add it to a local marketplace (.agents/plugins/marketplace.json).

Plugin minimal-vibe-coding-kit in giang6283623/minimal-vibe-coding-kit. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (26)

  • agent-control-center

    Coordinate complex coding work through one verified controller and bounded native or cross-provider workers. Use when a user wants an active Codex, Claude, Cursor, OpenCode, Grok, Kimi, or other capable host to coordinate work through a native, automatically selected, or explicitly selected provider

  • agentshield-security-review

    repository-native security review workflow for Claude Code, Cursor, Codex, OpenCode, Grok, and Kimi projects using the AgentShield concept. Use when auditing or hardening agent configuration, skills, prompts, hooks, MCP servers, permissions, commands, plugin files, AGENTS.md, CLAUDE.md, or repositor

  • autoresearch-coding

    Run a metric-driven coding experiment loop. Use when improving a repo through repeated hypotheses, benchmark-guided changes, validation, keep/discard decisions, or safe workflow enhancement. Requires a goal, metric command, direction, editable paths, protected paths, and budget.

  • claim

    Vet a request to bring something new into the repo - validate every URL and reference against official sources, check fit with existing rules, conventions, and skills, confirm anything unclear with the user, then integrate it and document how to use it.

  • clean-delivery

    Deliver one observable behavior slice through Specify, Code, Clean, Architect, Harden, and Verify gates with proportional rigor and reproducible proof. Use when the user asks for extreme craftsmanship, clean-code delivery, TDD, architecture boundaries, or a high-confidence implementation workflow.

  • clearthought

    Structured reasoning for complex coding work. Use when requirements are ambiguous, a design/debugging decision has multiple valid paths, or a large request needs to be split into safe implementable tasks.

  • clone-website

    Plan, build, and verify an authorized website clone or migration through one front-loaded requirements session and an optional autonomous A-to-Z run. Use for small marketing or content sites, corporate sites, web applications, and small, medium, or large ecommerce projects from local screenshots, mo

  • coding-level

    Set the coding-explanation register. /coding-level N (0=ELI5, 1=Junior, 2=Mid, 3=Senior, 4=Tech Lead, 5=God); active until reinvoked. A project default may be recorded in backbone.yml conventions.custom_rules.

  • daily-workflow-curator

    Propose daily improvements to project AI rules, skills, workflows, prompts, AgentShield posture, and backbone.yml. Use when the user asks to auto-enhance, update workflow, improve rules, or keep the vibe coding kit current. Propose diffs only; do not silently write.

  • graph-engineering-verified-orchestration

    Design and run bounded dependency graphs for complex engineering work, with explicit artifacts, isolation, objective verification, resource budgets, retries, rollback, merge ownership, and human gates. Use when a task has at least three bounded work items, two or more genuinely independent branches,

  • memento

    Leave yourself a note before closing a multi-day task, then read it back at the start of the next session - it's the only memory that survives the gap.

  • mermaid

    Generate styled Mermaid diagrams (31 types) from requirements - flowcharts, sequence, class, ER, state, Gantt, kanban, timeline, XY charts, architecture, and more. Also use when writing documentation (offer to include diagrams), when debugging or explaining a workflow (offer a visual flow map with r

  • model-provider-settings

    Safely inspect, plan, and update model, provider, reasoning, context, and compaction settings for Codex, Claude Code, Cursor, OpenCode, Grok Build, and Kimi Code from current official documentation. Use when setting up, comparing, migrating, or repairing provider configuration. Do not use for contro

  • parallel-analysis

    Fan out 2-5 independent read-only analysis lanes across the repo using provider-ready native subagents or configured adapters, then merge the lane reports and verify them with a refutation pass. Use for repo-wide questions, large uncommitted-diff reviews, multi-doc reading, impact analysis, or consi

  • path-sensitive-shell-safety

    Guardrail workflow for shell changes that use path variables, remote base directories, repo folders, checkout repair, or destructive filesystem commands such as rm, mv, cp, rsync, find -delete, git clean, or git reset.

  • prompt-sharpener

    Sharpen a rough prompt into a precise one - same intent, sharper not longer - then execute the sharpened version immediately in the same turn.

  • proofline-orchestration

    Govern complex agent work with an original four-role contract, independent challenge, explicit escalation signals, evidence-bound handbacks, and optional provider adapters. Use when the user asks for Proofline, role-separated orchestration, an empowered dissenting reviewer, multi-agent governance, o

  • reviewing-4p-priorities

    P0-P4 issue and task triage for vibe coding. Use when reviewing bugs, risks, feature requests, agent-surface changes, or deciding which work must happen first.

  • sequential-thinking

    Evidence-led step-by-step reasoning for complex coding tasks. Use to decompose work, revise assumptions, compare alternatives, verify hypotheses, and choose the next safe action without exposing private chain-of-thought.

  • swap-control-center

    Select verified controller and worker routes with independent provider, model, reasoning effort, and transport choices, then bind a compatible relay mode for work initiated from Cursor, Codex, Claude, OpenCode, Grok, Kimi, or another capable host. Use when the user wants the active host to relay bou

  • the-creator

    Create original but workable art, designs, interfaces, methods, processes, systems, or other solutions through ten cumulative creativity levels. Use only when the user explicitly invokes the-creator, names a creator level from 1 to 10, or directly asks to use the ten-level Creator framework for logi

  • threat-model-security-review

    Run a dependency-free, threat-model-led application security review of a repository, scoped component, code diff, or supplied vulnerability claim. Use when auditing source code, authentication, authorization, input handling, filesystem or network access, sensitive data paths, trust boundaries, or se

  • tutien

    Run a private, persistent xianxia coding-reflection mode with evidence-backed classification and an open-ended, repository-specific living chronicle. Use only when the user invokes /tutien; once enabled, carry its cultivation-novel voice across every reply until /tutien off or an explicit request en

  • vibekit-init

    Initialize or repair Minimal Vibe Coding Kit in an existing project. Use for first prompt, backbone.yml setup, CLAUDE.md merge, AGENTS.md merge, Cursor rules setup, Codex skill setup, OpenCode setup, Grok setup, or Kimi setup. Always show requirements and a diff before writing.

  • visual-design-loop

    Run an iterative visual design improvement loop for UI/product polish tasks. Use when a request involves screenshots, rendering, visual review, frontend polish, layout/typography/color refinement, design QA, or a Claude/Codex loop goal that touches a visible product surface. Score the visual gate fi

  • wait-what

    The last message did not land - stop and re-pitch it in plain language, in the user's language, until it lands.

View source on GitHub

Maintain minimal-vibe-coding-kit?

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