Menu
Swap bryllen plugin marketplace to local for testing skills and plugin changes before pushing
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 | plugin-local |
| description | Swap bryllen plugin marketplace to local for testing skills and plugin changes before pushing |
One command to swap EVERYTHING to local — plugin (skills, MCP, CLAUDE.md) AND npm package (CLI, templates, migrations, runtime). No manual steps.
Ask the user for the consumer project path if not known. Default: ../bryllen-projects
Get the repo root:
REPO_ROOT="$(git -C /Users/noamalmosnino/Documents/GitHub/bryllen rev-parse --show-toplevel)"
Swap the plugin marketplace to local:
CLAUDECODE= claude plugin marketplace remove bryllen 2>/dev/null || true
CLAUDECODE= claude plugin marketplace add "$REPO_ROOT/plugin"
CLAUDECODE= claude plugin install bryllen@bryllen 2>/dev/null || CLAUDECODE= claude plugin update bryllen@bryllen
Swap the npm package in the consumer project to local:
cd <consumer-project-path>
# Create package.json if it doesn't exist yet (prevents /bryllen-new from installing from GitHub)
[ ! -f package.json ] && npm init -y
rm -rf node_modules/bryllen
npm install "$REPO_ROOT"
This must use the absolute path and rm the old copy first — npm caches aggressively.
Creating package.json first is critical: without it, /bryllen-new will install bryllen from GitHub (hardcoded in the skill), overwriting the local swap.
Verify both swaps worked:
grep "claudeMd" <consumer-project-path>/node_modules/bryllen/src/cli/templates.js
grep "bryllen" <consumer-project-path>/package.json
The package.json should show "bryllen": "file:../bryllen" (not github:).
Tell the user:
/bryllen-new <project-name>/plugin-release when done to switch back to GitHub