Menu
Update bryllen to the latest version
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Start (or restart) the Bryllen dev server
Create a new design project and start designing
Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence.
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations.
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.
| name | bryllen-update |
| description | Update bryllen to the latest version |
Update everything in one shot — npm package, migrations, and Claude Code plugin.
Update the npm package (pulls latest from GitHub + runs migrations):
npx bryllen update
Get the new version number — read it from the installed package:
node -e "console.log(require('./node_modules/bryllen/package.json').version)"
Commit migration changes — migrations modify consumer files (App.tsx, CLAUDE.md, settings.json, etc.). Commit them so there's a rollback point:
git add -A && git diff --cached --quiet || git commit -m 'chore: bryllen update migrations'
(The diff --quiet check skips the commit if migrations made no changes.)
Update the plugin marketplace repo (git pull updates skills and CLAUDE.md):
cd ~/.claude/plugins/marketplaces/bryllen && git pull origin main 2>/dev/null; cd -
Tell the user:
git revert if needed)/bryllen-designclaude plugin update?claude plugin update cannot run inside a Claude Code session (nested sessions crash). The git pull in step 4 already updates all plugin files on disk — the restart picks them up.