Menu
Styling and design-system conventions — theme colors, MUI usage, typography. Use when styling components, adding colors, or making any visual/design change.
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
How the SAQ background worker is wired and how to add a new job type. Use when adding, changing, or debugging a background job, JobBatch, or worker task handler.
Step-by-step checklist for migrating a backend service to the DDD/hexagonal architecture. Use when porting an existing service, repository, or router to domain entities and repository protocols.
Use when the user provides a GitHub issue/ticket URL (e.g. github.com/Crossbill-Highlights/crossbill-web/issues/NNN) and asks to start working on it — fetches the ticket, moves it to In Progress on the project board, creates a branch, and begins implementation.
Backend testing policy — API-first tiering, assertion depth, and test-quality rules
| name | frontend-design |
| description | Styling and design-system conventions — theme colors, MUI usage, typography. Use when styling components, adding colors, or making any visual/design change. |
This app has an established design system; consistency with it beats novelty.
frontend/src/theme/theme.ts is the source of truth for
colors, typography, and component styling. Read it before styling anything.customColors section
first and reference it from there.sx prop. Use semantic components
(Button, IconButton) — never <Box component="button">; the semantic
components carry the accessibility and interaction behavior.