ce-prototype

Build throwaway web prototypes to settle product design questions before implementation.

24.7k|2.0k|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/EveryInc/compound-engineering-plugin --skill ce-prototype
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-prototype
Source: https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-prototype
Command: npx skills add https://github.com/EveryInc/compound-engineering-plugin --skill ce-prototype

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Committing to a product behavior or visual direction without seeing it risks expensive rework later. This Skill builds a disposable prototype at the fidelity needed to answer how something should work, feel, or read, so decisions are made against a real artifact instead of guesswork.

Core Features & Use Cases

  • Question scoping: Classifies questions as narrow comparisons or wide explorations, sizes the build to the uncertainty, and gets a go-ahead before building.
  • Local preview server: Ships a lightweight Node.js web server that serves prototype screens with live reload, safe path containment, and idle shutdown.
  • Decision capture and write-back: Records settled decisions in a run capsule and writes them back into a related brainstorm or plan's Product Contract when the user applies.
  • Use Case: Before committing to a new onboarding flow, prototype two or three navigation mechanisms, let the user drive each one in a browser, then write the winning decision back into the plan.

Quick Start

Ask the agent to prototype how the new settings page layout should feel before we commit to an implementation approach.

Frequently Asked Questions about ce-prototype

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

FAQPage Schema
How do I prototype a product flow before building the real feature?

Describe the question you need settled, and the Skill scopes it, builds a throwaway web prototype at the right fidelity, and serves it locally for you to drive. Decisions are captured in a capsule and can be written back into your plan.

When should I use a throwaway prototype instead of a sketch?

Use a prototype when the question is about behavior, such as a flow or state model that must be driven, or a visual direction that must be seen at real finish. A cheap sketch is enough for questions it can settle; the prototype exists for questions it cannot.

Does the prototype preview work in Codex or remote sessions?

Yes. The bundled Node.js server supports detached or foreground modes per platform, and can bind to 0.0.0.0 for remote or containerized sessions where localhost is unreachable, with a warning to use a trusted network.

Can I use this skill in an unattended or automated pipeline run?

No. The Skill requires a human to experience and judge the prototype. In unattended modes it stops and reports that a person is needed rather than inventing how the product should feel.

What happens to prototype code after the decision is made?

Prototypes live under .context/compound-engineering/ce-prototype/ or a temp fallback and are never committed or shipped. Overlay edits to the real app are reverted when the try ends, and kept prototypes are never deleted.