with one click
bryllen-share
Build the canvas and deploy to GitHub Pages for sharing
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.
Menu
Build the canvas and deploy to GitHub Pages for sharing
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
| name | bryllen-share |
| description | Build the canvas and deploy to GitHub Pages for sharing |
Build the current canvas project and deploy it to GitHub Pages so you can share a live link with others.
project-name (optional) — only include this project in the build. If omitted and multiple projects exist, ask the designer.--dest subpath (optional) — deploy to a subdirectory of the GitHub Pages site instead of root. Useful when the root is reserved for something else (e.g. a landing page). Example: --dest explore deploys to /<repo>/explore/.Check prerequisites:
gh repo view --json nameWithOwner -q .nameWithOwner
Determine which project to share.
src/projects/, ask: "Share all projects or just one?"Parse arguments. Check if --dest <subpath> was provided. This determines:
--base path for vite--dest flag for gh-pagesBuild with the correct base path:
# Without --dest (deploys to root):
BRYLLEN_PROJECT=<project-name> npx vite build --base=/<repo-name>/
# With --dest explore (deploys to subpath):
BRYLLEN_PROJECT=<project-name> npx vite build --base=/<repo-name>/explore/
The BRYLLEN_PROJECT env var tells the vite plugin to only include that project's manifest.
Deploy to GitHub Pages:
# Without --dest (replaces root):
npx gh-pages -d dist
# With --dest explore (deploys to subpath, preserves everything else):
npx gh-pages -d dist --dest explore
Enable GitHub Pages if not already enabled:
gh api repos/<owner>/<repo>/pages -X POST -f source.branch=gh-pages -f source.path=/ 2>/dev/null || true
Save the share URL to the manifest.
Open src/projects/<project-name>/manifest.ts and set shareUrl on the manifest object:
const manifest: ProjectManifest = {
project: '<project-name>',
shareUrl: 'https://<owner>.github.io/<repo>/', // ← add or update this
iterations: [ ... ],
}
If shareUrl already exists, update it. If it doesn't, add it after the project field.
Return the URL:
# Without --dest:
Deployed! View at: https://<owner>.github.io/<repo>/
# With --dest:
Deployed! View at: https://<owner>.github.io/<repo>/explore/
/bryllen-share → all projects, deployed to root
/bryllen-share bryllen-ui → single project, deployed to root
/bryllen-share bryllen-ui --dest explore → single project at /explore/ subpath
--base flag is critical — without it, asset paths break on GitHub PagesBRYLLEN_PROJECT filters the build to only include the specified project--dest uses gh-pages' subdirectory support — it won't overwrite other content on the gh-pages branchStart (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.