Stop re-explaining yourself to AI. Turn your finished sessions into reusable agents.
opencode-maker-kit is a toolkit for opencode that does two things:
- Maker — reviews any of your past sessions (shared links or local history), finds the repeatable workflow inside, and distills it into a reusable skill or agent — so you never run the same manual process twice.
- A curated starter set of battle-tested workflows, distilled from real-world use:
- biz-planner — turns a raw idea into a decision-locked, approval-gated execution plan (scoping → decision questions → criteria-driven tech stack → final plan)
- designer — generates a
DESIGN.mddesign system for any project, no design knowledge needed (powered by ui-ux-pro-max or awesome-design-md) - safe-build — makes every code/UI change reversible by design (baseline commit → Goal/Steps/Rollback plan → isolated atomic commits), and follows your DESIGN.md automatically
- router — forget what you have installed? Drop an idea, get matched to the right agent/skill/command you already own
Every AI coding session, you repeat yourself: how I like plans structured, how decisions should be framed, how changes must stay revertible. Your history already contains your best workflow — it's just locked in transcripts.
Maker unlocks it:
you: /maker https://your-opencode-share-url
ai: [analyzes session] ... Proposed automation:
Name: release-checklist | Type: skill | Confidence: high
Generate this? [y/n]
you: y
✓ Skill generated. Restart opencode and it's yours forever.
Requirements: opencode installed.
Windows (PowerShell):
git clone https://github.com/Tariq-himself/opencode-maker-kit.git
cd opencode-maker-kit
.\install.ps1macOS / Linux:
git clone https://github.com/Tariq-himself/opencode-maker-kit.git
cd opencode-maker-kit
./install.shThe installer copies files into your global opencode config (~/.config/opencode/) and asks before overwriting anything that already exists. Then restart opencode.
Uninstall anytime with uninstall.ps1 / uninstall.sh.
| Try this | What happens |
|---|---|
/biz-planner meal-prep SaaS for busy parents |
Full ideation flow: mindmap → recommended-option questions → tech-stack criteria table → Final Plan with approval gate |
/designer landing page for my coffee shop |
3 plain-language questions → DESIGN.md design system written to your project (any product type) |
"restyle my landing page hero, but make it reversible" |
safe-build auto-triggers: auto-labeled checkpoints, before/after screenshots, journal — then just say "undo it", "nah", or "compare" |
"try without committing" |
Sandbox mode: changes applied as uncommitted edits → keep or discard |
/maker --last |
Analyzes your most recent session, proposes a skill/agent from it |
/maker scan |
Sweeps ALL your past sessions, ranks automation candidates |
/router I need to debug a flaky test suite |
Recommends which of YOUR installed tools fit, with exact launch syntax |
Tab |
maker & router appear in your agent switcher |
OpenCode share pages are single-page apps — but the full transcript is embedded inline in the HTML as SolidStart hydration data. Maker fetches the page, parses the embedded $R[...] payload, extracts the conversation, then analyzes it for: repeated document templates, formulaic decision framing, approval gates, and artifact structures. Local sessions work too — opencode stores everything under ~/.local/share/opencode/storage/.
See docs/how-it-works.md for details, docs/design-phase.md for the design workflow, docs/checkpoints.md for the undo system, or docs/create-your-own.md to distill your own workflow into a skill by hand.
This kit runs 100% locally on your machine:
- No telemetry, no network calls beyond fetching share URLs you explicitly provide
- Session content never leaves your machine unless YOU share the URL
- The repo ships zero personal data — a built-in privacy scanner (
scripts/check-privacy.*) blocks commits containing personal paths, emails, or project names
Distilled your own workflow into a skill? PRs welcome! Start with CONTRIBUTING.md and the templates in templates/. Every contribution needs: a SKILL.md with clear trigger description + the workflow as executable steps + an example invocation.
Built with opencode. If this saved you time, a star ⭐ helps others find it.