Updated 4mo ago
by coleam00
frontend-mix
Mixed-provider frontend workflow: Opus 4.8 plans, Gemini 3.5 Flash designs, Opus ships. Six skills + an Archon workflow.
40 GitHub stars (40)
+1 in 16 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | +1 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | 0 |
| Oct 15 | 0 |
| Oct 16 | 0 |
- 9 skills (9 skills found in its SKILL.md files)
- 14 forks (14 forks)
- 4mo ago last update (Last updated 4mo ago)
Install
Skills CLI
npx skills add coleam00/frontend-mix
Asks which skills and agents to install. Just one: npx skills add coleam00/frontend-mix --skill archon — add -g for every project.
Claude Code
git clone https://github.com/coleam00/frontend-mixcp -r "frontend-mix/.claude/skills/archon" ~/.claude/skills/
Copies the archon skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add coleam00/frontend-mix
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
archon
Use when: User wants to run Archon workflows, CREATE workflows or commands, set up Archon, or manage Archon configuration. Triggers (run): "use archon to", "run archon", "archon workflow", "use archon for", "have archon", "let archon", "ask archon to". Triggers (create): "create a workflow", "write a workflow", "make a command", "author a workflow", "new workflow", "new command", "archon workflow…
.claude/skills/archon/SKILL.md on GitHub (opens in a new tab) -
frontend-mix-deploy
Deploy a validated build per SECTION C of a planning document. Run this skill in a Claude Code session driving Opus - the deploy step is reasoning-light most of the time but needs judgment when the dry-run output looks off. Skill is generic: it does whatever SECTION C says (Vercel, Fly, Railway, clerk deploy, local-only). Refuses to deploy unless validation is confirmed clean.
.claude/skills/frontend-mix-deploy/SKILL.md on GitHub (opens in a new tab) -
frontend-mix-design
Design and scaffold a beautiful frontend from SECTION A of a planning document. Run this skill in a Pi session driving Gemini 3.5 Flash, because Gemini builds the most beautiful frontends right now. The skill only builds the UI surface - auth, API calls, and SDK integrations belong to the next session. Use when the user has a plan.md from the frontend-mix-plan skill and is ready to build the UI.
.claude/skills/frontend-mix-design/SKILL.md on GitHub (opens in a new tab) -
frontend-mix-explore
Gather context for a mixed-provider full-stack build before planning. Run this skill in a Claude Code session on Sonnet (cheap context gathering, no heavy reasoning needed). It inspects the repo, reads the spec if you point it at one, and writes a context.md handoff the plan step feeds off. Use this FIRST, before frontend-mix-plan. Triggers on "explore a frontend", "gather context for a mixed-pro…
.claude/skills/frontend-mix-explore/SKILL.md on GitHub (opens in a new tab) -
frontend-mix-fix-validation
Address validation failures recorded by the frontend-mix-validate session. Run this skill in a Claude Code session driving Opus - failures that survived two Sonnet repair attempts need real judgment, not more grinding. Reads validation-issues.md, fixes each failure at the source, re-runs the validation suite, writes resolution-summary.md. Use when frontend-mix-validate wrote validation-issues.md…
.claude/skills/frontend-mix-fix-validation/SKILL.md on GitHub (opens in a new tab) -
frontend-mix-integrate
Wire up auth, backend API, and third-party SDK integrations into a UI scaffold by executing SECTION B of a planning document. Run this skill in a Claude Code session driving Opus - integration is reasoning-heavy. The skill is plan-driven, not vendor-specific: it uses whatever auth/SDKs/APIs SECTION B says. Use when the design session has finished and `ui-summary.md` plus `plan.md` are ready.
.claude/skills/frontend-mix-integrate/SKILL.md on GitHub (opens in a new tab) -
frontend-mix-plan
Plan a full-stack web application by producing a three-section spec (UI / Integration / Deployment) that downstream provider-specific sessions can execute. Run this skill in a Claude Code session on Opus, AFTER frontend-mix-explore has produced a context.md. Pure planning - it reads the context handoff (and the spec it points to) and turns it into an actionable plan. Triggers on "plan a frontend"…
.claude/skills/frontend-mix-plan/SKILL.md on GitHub (opens in a new tab) -
frontend-mix-smoke
Runtime smoke-test a freshly validated mixed-provider build by driving the RUNNING app with agent-browser - load every route, exercise the primary interaction, check status codes and console errors. Run this skill in a Claude Code session driving Sonnet. Catches the class of bug static checks (typecheck/lint/build) miss: broken routes, dead buttons, soft-404s, runtime errors, and the page that lo…
.claude/skills/frontend-mix-smoke/SKILL.md on GitHub (opens in a new tab) -
frontend-mix-validate
Run the full validation suite (install, type-check, lint, build, tests) on a freshly integrated app and fix anything broken. Run this skill in a Claude Code session driving Sonnet - validation is grind work, Sonnet is the right tool. Two-attempt cap per step; failures are recorded for the fix-validation escalation step, not papered over. Use after the frontend-mix-integrate session finishes.
.claude/skills/frontend-mix-validate/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.