interactive-plugin-builder

Orchestrates a five-stage pipeline to build, verify, and package installable Claude Code and Codex plugins.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill interactive-plugin-builder-lygolang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interactive-plugin-builder
Source: https://github.com/LYGOLANG/fufan-cc-flow/tree/main/bundled-plugins/plugin-builder/skills/interactive-plugin-builder
Command: npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill interactive-plugin-builder-lygolang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, jsonschema, playwright-core, and includes scripts (resource) and references (resource) components.

What problem does it solve? Building an installable interactive plugin for Claude Code or Codex involves requirements gathering, interaction design, planning, development, and real host verification, and skipping any stage produces a plain web app instead of a shippable plugin. This Skill acts as the master router that detects project state and drives each stage in order until every required host target is verified. ## Core Features & Use Cases - Stage Routing: Detects existing artifacts (Plugin-Spec.md, Plugin-Design.md, PLUGIN-DEV-PLAN.md, Plugin-Project-State.md) and routes to the correct stage Skill: spec builder, interaction/runtime designer, dev planner, builder, checker, or installer. - Deterministic Toolchain: Ships scripts for project initialization, harness and plugin validation, scaffolding, packaging, style linting, one-click installation, skill-trigger evaluation, and Playwright-based UI audits. - Evidence-Gated Delivery: Only declares SHIPPABLE when all required host targets are HOST_VERIFIED with machine-readable evidence conforming to the bundled evidence JSON schema. - Use Case: A developer wants to turn an idea into an installable Claude Code plugin with a companion web UI and MCP server; the Skill interviews for requirements, produces design contracts, executes the dev plan, and verifies installation in the real host before delivery. ## Quick Start Ask the assistant to help you build an installable Claude Code or Codex plugin from your idea, and it will detect the project state and route you through specification, design, planning, development, and verification.

Frequently Asked Questions about interactive-plugin-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an installable Claude Code plugin with a UI?▼

Start from an idea and let the router run five stages: spec interview, interaction and runtime design, dev planning, task-by-task development, and independent checking. The final artifact is a plugin package installed via a personal marketplace using claude plugin marketplace add and claude plugin install.

What is the difference between companion-web-app and mcp-app plugin forms?▼

companion-web-app opens a full web interface in the host browser or system browser, while mcp-app embeds a lightweight UI in the conversation via MCP Apps ui:// resources. The form is decided during the spec interview and recorded in plugin.yaml; hybrid combines both.

Does this workflow support Codex plugins as well as Claude Code?▼

Yes, it defines host profiles for both Claude Code and Codex, including codex-plugin installation via codex plugin add and cache paths under ~/.codex/plugins/cache. Each host target is verified independently, and one host's verification never substitutes for the other.

What dependencies do the validation and packaging scripts need?▼

The Python scripts require python3 with PyYAML and jsonschema installed via pip. Generated plugins need Node.js 22 or later, mcp-app forms additionally fetch @modelcontextprotocol/ext-apps and vite, and UI audits need playwright-core with a local Chrome or a full playwright install.

When is a plugin considered finished and shippable?▼

A plugin is SHIPPABLE only when every required host target reaches HOST_VERIFIED status backed by real evidence in evidence/check/evidence.json. Build success or localhost previews alone never count as delivery, and the checker report must show no unresolved required failures.