メニュー
Use when the user asks to deploy this app to production, push to GitHub Pages, ship the current build to `app.quorummessenger.com`, or update the live site. Triggers on "deploy", "deploy to prod", "publish", "ship it", "push to gh-pages", "update production".
Use when the user asks to update the component audit, categorize a component as shared/platform/complex, or refresh `src/dev/components-audit/audit.json` after working on a component. Triggers on "update audit", "audit this component", "categorize component", "refresh audit stats".
Use when the user asks to convert a CSS or SCSS file to use the project's `_variables.scss` tokens, replace `@apply` with raw CSS, or align a stylesheet with the styling guidelines. Triggers on "convert this CSS", "use variables in this stylesheet", "remove @apply", "align with styling guidelines".
Use when the user asks to refresh or sync a documentation file in `.agents/docs/` against the current codebase. Triggers on "update this doc", "refresh the modals doc", "sync the docs with the code", "the doc is out of date", "verify the references in <doc>".
Use when the user asks to rebuild or refresh `.agents/INDEX.md` after adding, removing, or renaming files in `.agents/`. Triggers on "update the INDEX", "rebuild the agents index", "sync INDEX.md", "regenerate the docs index".
Use when the user asks to inspect, verify, or run something against the sibling `quorum-mobile` (React Native) or `quorum-shared` repos. Triggers on "check on mobile", "look at quorum-mobile", "verify in shared", "does this exist in shared", "check the mobile side".
Use when the user asks to convert a component to use the primitives architecture, replace raw HTML/Tailwind with primitive props, or make a component cross-platform-friendly. Triggers on "use primitives in this component", "convert to primitives", "primitives-ify", "make this primitive-based".
| name | deploy |
| description | Use when the user asks to deploy this app to production, push to GitHub Pages, ship the current build to `app.quorummessenger.com`, or update the live site. Triggers on "deploy", "deploy to prod", "publish", "ship it", "push to gh-pages", "update production". |
Deploy the current main branch of quorum-desktop to the gh-pages branch of the production repo (quorum-app-prod). That branch serves the live site at app.quorummessenger.com.
The production repo is a separate repository at ../quorum-app-prod (sibling directory of this repo).
Pause and ask for user confirmation before any destructive or irreversible action: before building, before deleting old assets, before committing, and before pushing. Never proceed silently through these gates.
main. If not, stop and tell the user.git status. If there are uncommitted changes, stop and tell the user — the working tree must be clean before deploying.main for reference (the entire app is built, not just these commits).main to production.yarn build and show the output.dist/web/ exists and show its size.../quorum-app-prod directory exists. If not, stop and tell the user they need to clone git@github.com:QuilibriumNetwork/quorum-app-prod.git as a sibling directory.cd ../quorum-app-prodgit fetch origin, git checkout gh-pages, git pull origin gh-pages.CNAME, 404.html, redirect.js, handleredirect.js, apple/) and replaces them with the new build.CNAME):
rm -rf assets twitter channelwasm_bg.wasm wasm_exec.js *.ttf *.svg *.png *.ico index.html manifest.webmanifest browserconfig.xml yandex-browser-manifest.json
dist/web/:
cp -r ../quorum-desktop/dist/web/* .
git add -A, then git status to show what changed.git commit -m "<their message>".git log -1 --oneline).git push origin gh-pages.After a successful push, switch back to the quorum-desktop repo and apply a production tag to the current HEAD of main. Use the prod-tag skill for the full workflow (date-based naming, suffix increment, annotated tag, push, confirmation gates).
End by reporting: tag name, commit hash, and live URL (https://app.quorummessenger.com).