Build
Stop Claude from winging it — 7 workflow skills that route every task through two thinking modes (Philosopher = absorb / Engineer = ship). Works in Claude Code + Codex.
npx -y skills add Lemonaderrrrr/flow-kit --skill buildAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Turn an idea into a working product or project (side projects, repos, technical designs). Default Engineer mode (define needs -> design -> MVP -> iterate); Philosopher mode for thinking through "should this exist, what is it really, what's the differentiation" before building. Saves to outputs/build/. Use when the user says "I want to build X", "design this project", or invokes the skill.
SKILL.md
2.3 KB, as published. Nobody here has run it
Build Workflow
Turn an idea into something that runs and ships.
Start
- Route-confirm (see
CONVENTIONS.md): one line stating this is the build workflow and the suggested mode; wait for the go-ahead. - Confirm mode: default ⚙️ Engineer; the user may switch to 🧠 Philosopher.
- (Optional) Align with the user's broader product/strategy goals if they have one.
⚙️ Engineer mode (default)
Goal: make it and get it running — validate in small steps, not all at once.
- Define needs — What problem? For whom? Measurable success criterion? Cut nice-to-haves first.
- Design — Break into modules / pick architecture / make tech choices; write down the key trade-offs (why A not B).
- MVP — Build the smallest version that validates the core assumption; get the main path working before optimizing.
- Iterate — Compare results to the success criterion → find the bottleneck → change one thing at a time.
- Capture — Save to
outputs/build/build_<english-slug>.md(needs + design + trade-offs + current progress + next step).
🧠 Philosopher mode
For thinking before building (should it exist, what is it): avoid building a pretty solution to a fake problem.
- Dig for the real need — The genuine pain point? Real need or vanity feature?
- Interrogate from first principles — Why this solution? Where's the real differentiation?
- Set direction — Once it's clear, switch to Engineer mode and build.
- Capture — Same location.
Wrap-up conventions
- Keep design docs separate from code (docs in
outputs/build/). - Maintain a "current progress + next step" line per project so work resumes cleanly across sessions.
- Promote: if it's directional/reusable, offer to save it to long-term memory; one-off outputs stay put.
- Filenames use English slugs.