funkstyr

Bring up infra and run the tix end-to-end suites — `@tix/api-e2e` (cross-service integration over docker compose) and/or `@tix/web-e2e` (Playwright browser flows over testcontainers). Handles infra startup, picks the right suite, and surfaces results + the Playwright report. Use when the user asks to run e2e tests, "run the integration suite", "run the browser tests", or invokes `/run-e2e`.

Run the tix pre-PR merge-ready gate on the current branch. Verifies zero must-fix review findings, green `pnpm check`, and a clean rebase on `origin/main`. Pass / fail — if all three gates pass, the branch is ready for `gh pr create`. Use when the user wants to confirm a branch is merge-ready before opening a PR, asks "is this ready?", "ready to ship?", "ready for PR?", or invokes `/pr-ready`.

Review an open GitHub PR against tix's house style, TypeScript conventions, test discipline, and security baselines. Fetches the diff via `gh pr diff`, runs the review locally, then optionally posts the report as a single PR review (approve / request-changes / comment). Use when reviewing someone else's PR, asked to "review PR

Review the current branch's diff (or the latest commit on main) against tix's house style, TypeScript conventions, test discipline, and security baselines. Use when the user is about to push, open a PR, or asks "review my branch", "review before push", or "code review this".

Code conventions for tix — duck/feature layout, file-size limits, blank-line groups, strict TypeScript, fast tests. Use when writing or refactoring code in this repo, splitting large files, planning a package refactor, or whenever code structure decisions come up.

Run the bun-mono pre-PR merge-ready gate on the current branch. Verifies zero must-fix review findings, green `bun check`, and a clean rebase on `origin/main`. Pass / fail — if all three gates pass, the branch is ready for `gh pr create`. Use when the user wants to confirm a branch is merge-ready before opening a PR, asks "is this ready?", "ready to ship?", "ready for PR?", or invokes `/pr-ready`.

Review an open GitHub PR against bun-mono's house style, TypeScript conventions, test discipline, and security baselines. Fetches the diff via `gh pr diff`, runs the review locally, then optionally posts the report as a single PR review (approve / request-changes / comment). Use when reviewing someone else's PR, asked to "review PR

Review the current branch's diff (or the latest commit on main) against bun-mono's house style, TypeScript conventions, test discipline, and security baselines. Use when the user is about to push, open a PR, or asks "review my branch", "review before push", or "code review this".

Code conventions for bun-mono — duck/feature layout, file-size limits, blank-line groups, strict TypeScript, fast tests. Use when writing or refactoring code in this repo, splitting large files, planning a package refactor, or whenever code structure decisions come up.

Conventions for editing this GitHub profile README. Use when adding/removing tech badges, restructuring sections, or proposing copy changes to README.md. The README is live on the GitHub profile page, so changes are user-facing.

Code conventions for this Astro site — component patterns (polymorphic, spread props, named slots), strict TypeScript, Tailwind v4 with cn(), file-based routing, image globs, content collections. Use when writing or refactoring code in this repo, adding components/pages/posts, or whenever code structure decisions come up.