Menu
Instructions on how to design high quality typography
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, sets up a worktree, and begins implementation.
Guidelines on makign git commits
Guidelines on writing tests for the backend
Instructions on how to add new colors for CSS rules
Instructions on how to write database queries with SQLAlchemy.
Instructions on how to design high quality frontend aesthetics
| name | typography |
| description | Instructions on how to design high quality typography |
Typography instantly signals quality. Avoid using boring, generic fonts.
Never use: Inter, Roboto, Open Sans, Lato, default system fonts
Here are some examples of good, impactful choices:
Pairing principle: High contrast = interesting. Display + monospace, serif + geometric sans, variable font across weights.
Use extremes: 100/200 weight vs 800/900, not 400 vs 600. Size jumps of 3x+, not 1.5x.
Pick one distinctive font, use it decisively. Load from Google Fonts.