Agent Skills: ce-prototype
Build a throwaway prototype to answer how something should work, feel, or read. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle it. Not a rough visual probe during brainstorming, not for deciding what to build, not polishing a feature that already works, not implementing the real thing.
ID: everyinc/compound-engineering-plugin/ce-prototype
25,9702,057
Install this agent skill to your local
Skill Files
The files that make up ce-prototype.
Loading file tree…
More agent skills
- ce-code-reviewReview a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.
- ce-explainExplain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judgment or recommendation.
- ce-workExecute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.
- ce-compoundCapture a solved problem's lesson in its cheapest durable form, a test or lint rule, a coding standard, or a repo learning, or refresh existing learnings against the codebase. Use when verified work produced non-obvious reasoning absent from its final code, tests, or existing docs, or when auditing stale, overlapping, or drifted learnings. Avoid routine fixes whose artifacts already explain the lesson.
- ce-strategyCreate or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.
- ce-polishPolish a working feature through user-directed live browser feedback. Use when a functional feature needs focused UX refinement before shipping.