Przejdź do treści
Biblioteka skilli
Projektowanie i UX · Budowanie i kod

strict-theme-dispatch

/strict-theme-dispatch

Buduje serwis informacyjny i sportowy w motywie Dispatch dla shadcn, z mocnymi nagłówkami i wynikami na żywo.

Repozytorium
strictthemes ↗
Licencja
MIT
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
8
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Buduje serwis informacyjny i sportowy w motywie Dispatch dla shadcn, z mocnymi nagłówkami i wynikami na żywo.

Oryginalny opis (EN)

Build UI in the Dispatch theme from strictthemes.com. A loud, fast theme for news and sport. Newsprint, black rules, condensed headlines and a breaking-news red. Use it when the project's DESIGN.md is Dispatch, or when the user asks for the Dispatch theme. It installs the theme into a shadcn project, gives its layout rules and its page briefs (front page, news story, live blog, sports results and section index), and checks the result with Strict Check.

Jak działa

  1. Before you start
  2. The theme in short
  3. Rules
  4. Page briefs
  5. Check before you finish
Sekcje z nagłówków SKILL.md, w oryginale · 133 linii, 5 804 słów
Podgląd SKILL.md
---
name: strict-theme-dispatch
description: "Build UI in the Dispatch theme from strictthemes.com. A loud, fast theme for news and sport. Newsprint, black rules, condensed headlines and a breaking-news red. Use it when the project's DESIGN.md is Dispatch, or when the user asks for the Dispatch theme. It installs the theme into a shadcn project, gives its layout rules and its page briefs (front page, news story, live blog, sports results and section index), and checks the result with Strict Check."
---

# Dispatch

A loud, fast theme for news and sport. Newsprint, black rules, condensed headlines and a breaking-news red.

This skill is for building UI in the Dispatch theme: a page, a section or a component. `DESIGN.md` decides the tokens: colors, type, spacing steps and corners. The notes below say how the theme lays a page out and which token goes where.

## Before you start

1. **Check the theme is installed.** The project should have `DESIGN.md` in its root and the Dispatch variables in its global CSS. If not, run `npx shadcn@latest add https://strictthemes.com/r/dispatch.json` and save https://strictthemes.com/themes/dispatch/DESIGN.md as `DESIGN.md` in the project root. In a project without shadcn, use https://strictthemes.com/themes/dispatch/tailwind.css instead. If the global CSS still imports a font the theme does not use (a new shadcn project imports Geist), remove that import, and uninstall its package if nothing else uses it. Keep every font import the theme's install added, also one for a style no page uses yet.
2. **Read `DESIGN.md` from start to finish.** It is the source of truth for every visual decision.
3. **Look at the project before writing code.** Use its framework, router and file layout. For controls (buttons, inputs, tabs, menus, dialogs, accordions, data tables) use the components in `components/ui`, and add a missing one with `npx shadcn@latest add <name>` rather than writing your own, unless the page brief names a plain element. Layout is plain elements with theme classes: sections, panels, figures and lists need no component.
4. **Teach `cn()` the theme's type classes.** shadcn's class merger does not know `text-display` or `text-h1`. It takes them for colors, so `cn("text-label text-muted-foreground")` silently drops one of the two, and a type class passed to a stock component does not replace its size. In a new shadcn project, `lib/utils.ts` only passes `cn` on from the `cn` package. Unless the file already holds the lines below, change it to:

   ```ts
   import { createCn } from "cn/config"

   // The theme's type classes are font sizes, not colors.
   export const cn = createCn({
     extend: {
       classGroups: {
         "font-size": [{ text: ["display", "h1", "h2", "body", "label"] }],
       },
     },
   })
   ```

   Then make every file in `components/ui` use it: where one has `import { cn } from "cn"`, change that line to import `cn` from the project's utils file (`@/lib/utils` in a default setup). Do the same for each component you add later. If the project uses `tailwind-merge` instead of the `cn` package, its components already import from the utils file: pass the same object to `extendTailwindMerge` and keep `clsx`.

## The theme in short

- **Fonts:** Big Shoulders for headings, Newsreader for body text, Chivo Mono for labels and code.
- **Type scale** (size/weight; each class also sets line height and tracking): `text-display` 88px/800, `text-h1` 56px/800, `text-h2` 32px/700, `text-body` 18px/400, `text-label` 12px/500.
- **Font per size:** a type class does not set the font family. Headings (`<h1>` to `<h6>`) get the heading font on their own; on any other element add the font class: `font-heading` with `text-display`, `text-h1`, `text-h2`; `font-mono` with `text-label`.
- **Spacing scale**, with the Tailwind step in brackets: 4px (`1`), 8px (`2`), 16px (`4`), 24px (`6`), 48px (`12`), 96px (`24`).
- **Corners:** `rounded-none` 0px, `rounded-sm` 1px, `rounded-md` 2px.
- **Colors (light mode):** primary #BF0D2A, on-primary #FFFFFF, secondary #111111, on-secondary #FFFFFF, tertiary #FFE14D, on-tertiary #111111, neutral #5C5850, background #F4F1EA, surface #FFFFFF, foreground #111111, border #1C1C1C, error #9E0019.

The layout notes below are written around a sample organisation and its pages. If the user gave you their own product, its name, pages and content replace the sample's, and the layout, the colors and the classes stay as the notes give them.

### How Dispatch pages are laid out

- **Container:** the `<header>`, the `<main>` and the `<footer>` each hold one `<div>` that is the container: `mx-auto max-w-[1280px]`, with `px-4`, and `px-6` from `md` up. The three landmarks carry no classes of their own; every class these notes give the header, main or footer goes on its container `<div>`. This width is the one arbitrary value allowed. Put `text-body` on the element that wraps the whole page.
- **Fonts:** headings (`<h1>` to `<h6>`) get Big Shoulders, the headline font, on their own. `font-sans` is Newsreader, the body font: in this project it is a serif, and it is the only serif. Do not write `font-serif`. `font-mono` is Chivo Mono, for labels and figures. The theme declares the weights 400, 500, 700 and 800: use only `font-normal`, `font-medium`, `font-bold` and `font-extrabold`.
- **Headlines:** every piece of text in the headline font is `uppercase`: headlines, the masthead name, a pull quote set in it. Never sentence case. A headline is at most two lines at 1280px (three are fine between `md` and `lg` in a row of three), with no word over ten letters so nothing overflows at 375px. Do not rely on word-breaking utilities.
- **Headline sizes:** the page's one main headline is the largest text on the screen, and nothing else comes near it. It is `text-h1` below `md` and `text-display` from `md` up; the page brief names which headline that is. Other story headlines are `text-h2`. A short headline in a dense list (a side column, "Most read", the "Live" strip, a related story) is a **small headline**: `font-heading text-body font-bold uppercase`. A headline that is a link holds an `<a>` in `text-foreground hover:underline decoration-2 underline-offset-4`.
- **Masthead:** the paper's name is a link to `/` in `font-heading uppercase text-foreground hover:underline decoration-2 underline-offset-4 transition-colors duration-150`, in the header and the footer, never a heading element. It is `text-h1` from `md` up on the front page, and `text-h2` on every other page and below `md` everywhere, so that it never competes with the page's headline.
- **Header:** a `<header>` whose container holds three rows. The top row is `flex items-center justify-between gap-4 py-2`: the date as a label in `text-muted-foreground` at the left (`Wednesday 11 November 2026`, a `<time>` with `dateTime="2026-11-11"`), and at the right the "Subscribe" link to `#` styled as a default button. The second row is `flex items-center justify-between gap-4 border-t-2 border-b py-4 md:border-b-0`, holding the masthead name; on the front page from `md` up it is `md:justify-center` instead, with the name alone in it. Its `border-b` closes the header below `md`, where the third row is hidden; from `md` up the third row's top border does it. Below `md` the name may wrap to two lines beside the "Menu" button; that is fine. The third row is a `<nav>` with the `aria-label` "Sections" and `hidden border-y py-2 md:block`, holding a `<ul>` with `flex flex-wrap gap-x-6 gap-y-2` of the section links as labels. The section links, in this order, each to `#`: News, Politics, City, Sport, Results, Business, Culture, Opinion. Each brief names the current one. The link for the current page is `text-foreground` with `aria-current="page"` and `underline decoration-2 underline-offset-4`; the others are `text-foreground hover:underline`.
- **Menus on small screens:** below `md` the third row is hidden, and a "Menu" button (`variant="outline"`, with the Buttons note's classes) with `aria-expanded` and `aria-controls` sits at the right end of the second row. It shows the section links inside the `<header>`, under the second row: a second `<nav>`, placed in the source between the second row and the third, with the same `aria-label` "Sections", shown only below `md`, which carries the `id` that `aria-controls` names and has the `hidden` attribute while closed. It has a 1px bottom border and `py-2`, and holds a `<ul>` with no classes; each link is a block with `py-2`. It closes on Escape and gives focus back to the button. Do not use a `Sheet` or a `Dialog`.
- **Footer:** a `<footer>` whose container is `flex flex-col gap-4 border-t-2 py-6`: the masthead name, a link to `/` in `font-heading text-h2 uppercase` with `self-start` so it is only as wide as its text, then a `<nav>` with the `aria-label` "Footer" holding a `<ul>` with `flex flex-wrap gap-x-6 gap-y-2` of the section links as label links, none of them current: no `aria-current` and no underline at rest. Then a `<p>` label line in `text-muted-foreground` with the copyright year, the paper's name and the city: `© 2026 The Port Avery Ledger · Port Avery`.
- **Vertical rhythm:** written as gaps on stacks (`flex flex-col gap-*`), never as `space-y-*`, and never as a margin on an element inside a stack unless the page brief names one. The container `<div>` inside `<main>` is a stack, `flex flex-col gap-12 pt-6 pb-12`: its items are the page's blocks (the page head, the lead row, each section). Inside a block: `gap-4` between a section head and what follows, between paragraphs and between stories in a list; `gap-2` inside a story unit and between a label and its value; `gap-1` between a line and a label line directly under it that belongs to it (a headline and its time, two lines of one byline) where the page brief says so.
- **Grid:** a row of columns is `grid grid-cols-1` with `lg:grid-cols-12`, and a column spans what the page brief gives it (`lg:col-span-8`, `lg:col-span-4`). Below `lg` the columns stack in source order.
- **Rules between columns:** columns of stories are divided by a 1px rule, not by space. The grid is `gap-4 lg:gap-0`: a row gap while the columns are stacked, and no column gap. The column after a rule has `lg:border-l lg:pl-6`, and the column before it `lg:pr-6`, so there is 24px of space on each side of the rule. Below `lg`, where the columns stack, the rule turns into a 1px top border on each column after the first, with `pt-4`, and the grid's `gap-4` above it; from `lg` up that is `lg:border-t-0 lg:pt-0`. A stacked column that opens with a section head takes no top border and no `pt-4`: the head's 2px rule divides it. Use the same construction for three stories in a row at `md`: a `<div>` with `grid grid-cols-1 md:grid-cols-3`, not a list, holding three `<article>`s that carry these classes. Each story after the first has `border-t pt-4 md:border-t-0 md:pt-0 md:border-l md:pl-6`, each story before the last `md:pr-6`, and the grid has `gap-4 md:gap-0`.
- **Rules between stories:** a list of stories stacked in a column is a `<ul>` (or `<ol>`) with `flex flex-col gap-4`, no markers and no padding. Each item after the first has a 1px top border and `pt-4`. Every line is `border-border` (nearly black on purpose), which the base styles set, so `border` alone draws it. Never use a pale line or `border-muted`.
- **Section head:** a section opens with a row `flex items-baseline justify-between gap-4 border-t-2 pt-2`: the section's name as an `<h2>` label in `font-mono text-label uppercase text-foreground` (it needs `font-mono`, since a heading gets the headline font on its own), and at the right end, where the page brief gives one, a label link such as "All politics". Where it gives none, the row keeps its classes and holds the name alone.
- **Story unit:** a story in a list is an `<article>`, a stack with `gap-2`: an optional kicker (a `<p>` label in `text-foreground`), the headline, an optional standfirst in `text-body`, and the label line. A story with a picture puts the figure first, except a page's lead story, whose headline comes before its picture (the brief says so). A story's headline is an `<h3>` inside a section and an `<h2>` where it stands under the `<h1>` with no section head between.
- **Labels:** section names, kickers, bylines, times, captions, table headers, nav links, and button and badge text are labels: `font-mono text-label uppercase`, a short fragment and never a sentence; only a caption may be a short sentence. A label line joins its parts with ` · ` (`By Hana Lindqvist · 09:40`). Names in a byline are set in capitals by `uppercase` like the rest of it, as `DESIGN.md` asks.
- **Text color:** headlines, body text, kickers and section names are `text-foreground`. Bylines, times, captions and helper text are `text-muted-foreground`. Paragraphs are never muted.
- **Red:** `text-primary` and `bg-primary` mean live, new or the main action, and nothing else: the "Live" marker, the "New" label (a `<span>` label `New` in `text-primary`, with no dot or badge, beside the time where the brief puts it), links in running text and the default button. Never a headline, a rule or a fill for decoration. The one other red is the focus outline from the rules: `outline-ring` is red in this theme, and stays so. Red text is fine on `bg-background` and `bg-card` in both modes.
- **Live marker:** `inline-flex items-center gap-2 font-mono text-label uppercase text-primary`, holding a dot (`size-2 shrink-0 rounded-full bg-primary`, `aria-hidden="true"`) and the word "Live". The word is always there: the dot never stands alone. The dot does not pulse or blink.
- **Yellow:** `bg-tertiary` is a fill only, always with `text-tertiary-foreground` on it, which is black in both modes. It marks one phrase (a `<mark>` with `bg-tertiary px-0.5 text-tertiary-foreground`) or the "Exclusive" badge. Never red text on yellow, and never yellow as text.
- **Badges:** the shadcn `Badge` with `className="h-auto rounded-none border-transparent bg-tertiary px-2 py-1 font-mono text-label uppercase text-tertiary-foreground"`, for "Exclusive" only. At most one on a page.
- **Dates:** "today" is always the sample date, Wednesday 11 November 2026, never the clock. Nothing on these pages reads the time. Dates and times take three forms: a time today is `09:40`; another day is `Tue 10 Nov`, with no time; the long form, in the header and a page head, is `Wednesday 11 November 2026`. Every date and time in a label, in a byline or alone, is a `<time>` that wraps only the date or time (`Updated <time>09:40</time>`), with `dateTime="2026-11-11T09:40"` for a time and `dateTime="2026-11-10"` for a day or a long date. A time inside a headline or a sentence (`Council meets at 18:00`) is plain text, and so is the copyright year in the footer.
- **Numbers:** every `<time>`, the long date included, and every score, position and count outside a sentence is `font-mono tabular-nums`, labels or not. In a table, numbers are right-aligned, and so is their column header. A **big figure** (a score in a score box, a number in a fact box, a rank in a numbered list) is `font-mono text-h2 tabular-nums`: this is the one use of a mono font at a heading size, because `DESIGN.md` sets scores in Chivo Mono with tabular figures.
- **Measure:** a paragraph of body text is at most `max-w-xl` wide (576px, about 65 to 70 characters a line in Newsreader at 18px), whatever column it sits in. A standfirst in `font-sans text-h2 font-normal` is capped at `max-w-3xl` instead.
- **Emphasis:** `<em>` is a real italic. Newsreader italic is also used for a pull quote. No bold inside paragraphs.
- **Links:** a link in running text is `text-primary underline underline-offset-4 hover:text-foreground` and inherits its size. A label link (in the nav, the footer, a section head) is `font-mono text-label uppercase text-foreground hover:underline underline-offset-4`. Links get `transition-colors duration-150`. The masthead name points to `/`; every other link, the current page's own nav link and every story link included, points to `#`, unless the page brief gives another `href`.
- **Buttons:** the shadcn `Button` with `className="h-auto px-4 py-2 font-mono text-label uppercase"`. It keeps its stock corners (`rounded-lg`, 2px here). The default variant (red) is the one main action, and "Subscribe" in the header is it on every page: any other button is `variant="secondary"` (black, cream in dark mode), except the "Menu" button and the unchosen buttons of a button group, which are `variant="outline"`. Its stock hover cannot be told from its resting color: in `components/ui/button.tsx`, replace the `secondary` variant's `hover:bg-[color-mix(in_oklch,var(--secondary),var(--foreground)_5%)]` with `hover:bg-secondary/80`, once, on every page (each has the "Menu" button), and add no hover class on the page. A call to action that goes to another page is an `<a>` with the same classes: write `cn(buttonVariants({ variant }), "…")`, because `buttonVariants` alone does not merge classes. A button that its own click disables, while focus stays on it, gets `focusableWhenDisabled`; on these pages that is only the live blog's "Show new update". Base UI then sets `aria-disabled="true"` and `data-disabled` instead of the `disabled` attribute, so the stock `disabled:` classes do nothing: on a page that uses the prop, and only there, add `data-disabled:pointer-events-none data-disabled:opacity-50` beside them in `components/ui/button.tsx`. A button whose click moves focus elsewhere or removes it does not get the prop. If the project has no `Button` yet, add it with `npx shadcn@latest add button`.
- **Button groups:** a set of buttons where one is chosen (an order, a filter) is a `role="group"` with an `aria-label` and `flex flex-wrap gap-1`. The chosen button has `aria-pressed="true"` and `variant="secondary"`; the rest have `aria-pressed="false"` and `variant="outline"`. Every button in it has the Buttons classes. Pressing the chosen button again changes nothing, and a status element keeps its text.
- **Announcements:** a message that tells a screen reader what changed goes into an element with `role="status"` that is on the page from the start, empty: one that arrives together with its text is often not announced. It is never hidden with `hidden` or `empty:hidden`; where its text is for screen readers only, it is `sr-only`. Each status element here is a `<p>` whose only class is `sr-only`: it adds no gap and has no margin.
- **Pictures:** there are no image files. A picture is a `<figure>`, a stack with `gap-2`: a plain `<div>` with an aspect ratio (`aspect-3/2` unless the page brief says otherwise), `w-full bg-muted` (the flat muted block `DESIGN.md` names, used only for this fill), `role="img"` and an `aria-label` that describes the scene; then a `<figcaption>` label in `text-muted-foreground` that says what it shows and ends with the credit after ` · ` (`The Kessel Street Bridge on Tuesday · Photograph: Odile Marsh`). Nothing is written on the fill. Pictures have square corners and no border.
- **Boxes:** a box (a fact box, a score box, the "Live" strip) is a plain element with `border bg-card p-6`, `p-4` below `md`, and square corners. Do not use the shadcn `Card`. Never put a box inside a box.
- **Tables:** the shadcn `Table` with `text-body`. Header cells are labels in `text-muted-foreground`; they keep their stock `h-10` and padding, and so do body cells. Rows keep their stock borders and hover color. A table that is wider than a phone scrolls sideways in its own box, reachable with the keyboard: `tabIndex={0}`, `role="region"` and an `aria-label`. Edit `components/ui/table.tsx`: put these on its scroll box, with the focus outline from the rules, and add a required `label` prop for the name. The grid column or flex item that holds the scroll box gets `min-w-0`, or `min-w-lg` widens the column and the page instead of scrolling. Name the table with a visible `<h2>` or `<h3>` above it, not a `<caption>`, which would scroll with the table. Give the `Table` `min-w-lg` where the page brief says it scrolls on a phone.
- **Icons:** from `lucide-react`, with `size-4`, `strokeWidth={1.5}` and `aria-hidden="true"`, only where the page brief names one. Never emoji.
- **Corners:** square. `rounded-none` for boxes, pictures and badges (boxes and pictures need no class at all). Buttons and the stock `Input` keep `rounded-lg`, which is 2px. `rounded-full` only for the "Live" dot.
- **Surfaces:** flat: ink on paper. No shadows, no blur and no gradients in the code you write. The page is `bg-background`; a box is `bg-card`. A stock component that floats over the page (a menu, a dialog) keeps its border and the one short shadow it ships with.
- **Motion:** in the code you write, the only transition is color. Nothing moves on scroll, and nothing animates in when it is added to the page. The stock `Button` keeps its `transition-all` and its 1px press nudge, as the rules say.

## Rules

- **Colors:** only the theme's colors, through the semantic classes (`bg-background`, `text-foreground`, `bg-card`, `bg-primary`, `text-primary-foreground`, `text-muted-foreground`, `border-border` and so on). No hex, rgb or named colors in components, and no Tailwind palette classes such as `bg-blue-500` or `text-gray-600`.
- **Spacing:** padding, margin and gap use only the scale's steps (`1`, `2`, `4`, `6`, `12`, `24`) plus 0, 1px and 2px. No arbitrary values such as `p-[18px]`, and no other steps such as `p-3` or `gap-5`. `auto` margins are fine. Widths and heights such as `w-64` or `size-4` are sizes, not spacing. This applies to the code you write: a stock component keeps the spacing inside it, unless the page brief changes it. That includes the stock `gap-1.5` between a `Button`'s icon and its words: leave it, and add no gap class to the button.
- **Type:** every piece of text you write gets its size from one of `text-display`, `text-h1`, `text-h2`, `text-body`, `text-label`, set on the element or on a parent it inherits from. Put `text-body` on the outermost element of the page you write. No other sizes. A stock shadcn component keeps the size it ships with, unless `DESIGN.md` or the page brief gives that component its own style. A type class does not replace a weight class: where a stock component ships `font-medium` and the text should be regular, add `font-normal`. Text that `uppercase` sets in capitals is written in normal case in the code, also where the page brief shows it in capitals, so a screen reader does not spell it out.
- **Fonts:** only the theme's fonts, through `font-sans`, `font-heading` and `font-mono`. Do not add a font.
- **Corners:** only the `rounded-*` classes, which the theme already sets. No arbitrary radius in the code you write; a stock component's own corner classes stay. `rounded-full` only where `DESIGN.md` or the page brief names a full round, such as an avatar or a status dot. The theme allows a full round on a box up to 12px across, not larger, and a pill counts by its height.
- **Contrast:** all text meets WCAG AA against its background.
- **Stock components:** a component from `components/ui`, and an `<a>` styled with `buttonVariants`, keeps the hover, pressed and disabled colors and the motion it ships with, unless the page brief changes them, also where the layout notes give links a transition. They are the theme's colors under other names. The same holds for every other stock class that neither the notes nor the page brief name, also in a file you edit: it stays. Examples are `TableHead`'s `h-10`, `font-medium` and `whitespace-nowrap`, a `Badge`'s `gap-1` and `whitespace-nowrap`, and the `group-has-[:focus-visible]/field-label:` classes, which only act inside a shadcn `Field`. A `Button` that a stock component renders inside itself, such as the `CalendarDayButton`'s `size="icon"`, keeps its variant and size: what the notes say about button sizes is for buttons you write. Classes the notes give a stock component go in its `className` where you use it, unless they say to change its file. `TableCell`'s stock `p-2` then stays beside the `px-*` and `py-*` you pass, which is fine: those win.
- **Link transitions:** where the layout notes give every link a transition, that includes a link whose color does not change on hover, such as the name in the header: there the class does nothing, which is fine.
- **Forms:** a typed value is trimmed at both ends before it is checked and before the page shows it back (in a confirmation, a list or a summary), so a field of spaces is empty. The field itself keeps what was typed. A field's error line comes after its helper text, and its `aria-describedby` names the helper text first. A group of choices with an error (radios, checkboxes, toggle buttons) names its error line in its own `aria-describedby`, unless the page brief ties the error line to each control in it. A group that only holds fields does not: each field names its own. A radio group takes `aria-invalid` on its `RadioGroup` and a set of checkboxes on each `Checkbox`. A `<fieldset>` and a `role="group"` do not take it, so a group of toggle buttons has none.
- **Long words:** every email address and URL, the page's own included, and any name the visitor typed that the page shows back, gets `wrap-break-word` on its element or on the paragraph that holds it. One long word can run out of its box or push it wider, also in a narrow column on a wide screen. A flex item, and an item of a grid with no `grid-cols-*` class at that width, is never narrower than its longest word or its widest scroll box, so neither the class nor a scroll box keeps it in: give such an item `min-w-0`, or give the grid `grid-cols-1` below its breakpoint (`grid grid-cols-1 md:grid-cols-12`).
- **Grid columns:** an item placed in "columns 9–12" gets a span and a start at the grid's breakpoint (`md:col-span-4 md:col-start-9` where it is `md`). Write the start whenever the item does not begin right after the one before it.
- **Lists:** a list "with no markers and no padding" needs no class for it: Tailwind's base styles already remove both.
- **Dates and figures:** where the layout notes and the page brief leave a case open, a `<time>` wraps only the date or the time, not the words around it. A date or a time inside a sentence then gets no `<time>`, and nor does a copyright year. That is about the element only: whether the figure takes `tabular-nums` is a separate question. Where they leave open whether a figure in a label line, a row or a table cell takes `tabular-nums`, add it: it changes only the width of digits. Figures in running text need none. Where they ask for it but not on which element, put it on the element that holds the whole figure or label line, so that it covers every figure in it; a `<time>` inside inherits it. For a time inside a sentence, that is the `<time>` itself, not the paragraph.
- **Menus on small screens:** where the layout notes put the nav links behind a "Menu" button that opens a second `<nav>` in the header, the button is hidden from the notes' breakpoint up (`md:hidden` for `md`). Escape closes the menu while focus is on the button or in the menu, through one `onKeyDown` on the `<header>` that acts only while the menu is open, and focus then goes to the button. The second `<nav>` marks the current page's link the way the row does. It shares the row's `aria-label`, which is right, because one of the two is always hidden.
- **Counts:** a number with a noun reads right at one: "1 set", not "1 sets". Where the page brief gives the words for only one of the two, write the other the same way.
- **Sizes from data:** a height or a width that comes from data (a chart bar, a meter) is set with an inline `style`. That is the one use for an inline style.
- **Focus:** every link and control shows a 2px outline on keyboard focus: `focus-visible:outline-solid focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring`. Where a class list that the layout notes or the page brief spell out for a link, a nav link or a table's scroll box lacks them, add them to it. Keep `focus-visible:outline-solid` in it: in Tailwind 4 an `outline-none` on the same element, which stock components carry, otherwise hides the outline. An element that only gets focus from code (a heading or a message with `tabIndex={-1}`) gets the same outline written with `focus:` in place of `focus-visible:` (`focus:outline-solid focus:outline-2 focus:outline-offset-2 focus:outline-ring`): after a mouse click, a browser does not match `:focus-visible` on an element that code focuses. A link, a button or a field that code focuses keeps the `focus-visible:` classes it has: after a mouse click it shows no outline, which is how a browser treats every control, and is right. A stock component that ships its own focus ring (`Button`, `buttonVariants`, `Input`, `Textarea`, `Checkbox`, `Switch`, `RadioGroupItem`, `SelectTrigger`, the day buttons of a `Calendar`, `AccordionTrigger`, the close button of a `Sheet`) must lose that ring. Do it once, in the component's file in `components/ui`, which is yours to change: replace its `focus-visible:ring-*` classes with the outline classes, and in a field (an `Input`, a `Textarea`, a `SelectTrigger`, a `Checkbox`, a `Switch` or a `RadioGroupItem`) replace its `aria-invalid:ring-*` classes, the `dark:` ones included, with `aria-invalid:ring-0`, or a field with an error shows a tinted ring. `Button` has two more sets. Its base classes also carry `aria-invalid:ring-*` classes, the `dark:` one included: replace them with one `aria-invalid:ring-0`, as in a field. Its `aria-invalid:border-destructive` and `dark:aria-invalid:border-destructive/50` are borders and stay: what the notes say about a field's border classes is for fields. Its `destructive` variant carries `focus-visible:ring-*` classes of its own, the `dark:` one included: delete them and put nothing in their place, because the base classes already give every variant the outline. That variant's `focus-visible:border-destructive/40` is a border and stays. Wherever this rule says replace, change the classes in the file and do not add `ring-0` beside them: an added class only wins where it comes later and passes through `cn`. The stock `focus-visible:border-ring` can stay. These ring changes go only into the files of components that this page uses and that can take focus on it: a `Badge` that is not a link keeps its ring classes. So does `button.tsx` on a page with no `Button` and no `buttonVariants` link. Its other edits still follow the notes: a hover change they make "on every page" is made here too, and the `cn` import from the setup steps goes into every file. A box that scrolls sideways (a code block, a wide table) gets `tabIndex={0}`, `role="region"`, an `aria-label` and the same outline, also at widths where it happens to fit. Where a focusable box touches the edges of a parent that has `overflow-hidden`, draw its outline inside it: `focus-visible:-outline-offset-2` in place of `focus-visible:outline-offset-2`.
- **Controls:** no control keeps the browser's own look, at rest or open. A choice from a list is the project's `Select`, never a native `<select>`, whose arrow and open list the browser draws. A date is picked from the project's `Calendar` in a `Popover`, never an `<input type="date">`. A checkbox, a radio button and a switch are the project's `Checkbox`, `RadioGroup` and `Switch`, never a bare `<input>`. Add a missing one with `npx shadcn@latest add <name>`. The theme's layout notes say how it styles each one. For one they do not cover, make it match the theme's `Input`: the same height, corner, border, fill, text size and focus outline, with its icon as far from the right edge as the text is from the left, and a popup on the theme's surface with a 1px `border-border`, the theme's corner and text in the type scale. Leave no stock text size, glow ring or translucent ring on it. Every `Textarea` gets `resize-none` as well as the classes the notes give it, so the browser draws no grip in its corner. The stock one grows with its text (`field-sizing-content`), and one the page brief sizes (`field-sizing-fixed` with `rows`) keeps that size. A field that searches or filters is an `Input` with `type="search"`, which tells a screen reader it is a search box. It also gets `[&::-webkit-search-cancel-button]:appearance-none`, which hides the clear button a browser draws in it. A `Select` takes its name from its visible label in two ways: the `<label>` has the `SelectTrigger`'s `id` as its `htmlFor` (the trigger is a `<button>`, so a click on the label reaches it), and the trigger has `aria-labelledby` with the label's `id`. Base UI links only its own `Select.Label`, which `select.tsx` does not wrap (its `SelectLabel` heads a group in the open list). A date field you write as a component takes a `ref` and passes it to its trigger, so code can focus it. The stock `CalendarDayButton` makes a `ref` and never attaches it, so add `ref={ref}` to its `<Button>`, or the arrow keys move nothing. End its classes with a `dark:data-[selected-single=true]:hover:` copy of the chosen day's fill and text classes (`dark:data-[selected-single=true]:hover:bg-primary dark:data-[selected-single=true]:hover:text-primary-foreground` for the stock ones): a `hover:` class loses to the chosen day's stock `data-[selected-single=true]:` classes, but a `dark:hover:` one beats them.
- **Not allowed:** purple or multi-color gradients; emoji used as icons or bullets; glows and colored shadows.
- **Avoid:** a card inside a card.
- **Dark mode:** the page must work with the `dark` class on `<html>`. Because every color comes from a semantic class, this needs no extra code; do not write `dark:` color overrides. A new shadcn project follows the system's mode and switches on the `d` key: leave that as it is, and add no mode switch of your own.

From the theme's own do's and don'ts:

- Do make one headline much larger than everything else on the screen.
- Do divide with rules and keep the columns tight.
- Do keep red for what is live, new or the main action. The focus outline is red as well: it marks where the reader is, and it is the one other use.
- Don't soften it: no rounded cards, no shadows, no pale grey borders.
- Don't set body copy in the headline font, or headlines in sentence case.
- Don't introduce a color, size or radius that is not a token above.

## Page briefs

Dispatch has a full brief for each of these pages: sections, layout, sample content and checks. When the user asks for one of them, fetch its brief and follow it. Where a brief and the notes above differ, the brief wins.

- **Front page:** a city newspaper's front page, with a masthead, one lead story, a column of other stories, a live strip and three sections of three stories each. https://strictthemes.com/themes/dispatch/prompts/front.md
- **Story:** one news story, with its section and time, a large headline, a standfirst, a byline, a captioned picture, the body with a pull quote and a fact box, and related stories. https://strictthemes.com/themes/dispatch/prompts/story.md
- **Live blog:** live coverage of one event, with a summary of key points, timed updates of several kinds, a control for their order and a new update that arrives and is announced. https://strictthemes.com/themes/dispatch/prompts/live.md
- **Results:** a sports results page, with today's scores, a league table, fixtures to come and a filter by competition. https://strictthemes.com/themes/dispatch/prompts/scores.md
- **Section:** one section's index page, with its lead story, a list of stories with their times, a numbered most-read list and a button that loads more stories. https://strictthemes.com/themes/dispatch/prompts/section.md

## Check before you finish

Build the project, then measure it against the theme with Strict Check:

```bash
npx @strictthemes/check --dist dist
```

`dist` is the folder the build wrote. Add `--path /pricing` for each page you touched other than `/`. Fix every error it lists by using a value the theme allows, and run it again until the last line starts with `Passed`. Do not mark code `strict-ignore` to get there.

Then tell the user what you built, what the check reported, and anything you could not verify.

Wersje

W bazie nie ma innych skilli o nazwie strict-theme-dispatch.

Migawka bazy z 13.11.2026 · wersja paczki 2fb7bfe7dd2c (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100strict-theme-strict-one
    Buduje strony w motywie Strict One dla shadcn, w stylu szwajcarskiej siatki, z jednym akcentem i pulpitem.
  • 100strict-theme-relay
    Buduje strony klubów sportowych i lig w motywie Relay dla shadcn, z terminarzem, tabelą ligową i wynikami.
  • 10021st-design-sync
    Publikuje bieżący design projektu, na przykład zmienne shadcn i Tailwind, jako udostępniony motyw w społeczności 21st.dev.
  • 100shadcn-add
    Dodaje komponent lub blok shadcn/ui do aplikacji web w systemie projektowym Masumi, kopiując kod z ui.shadcn.com.
  • 100pikku-theme
    Nadaje aplikacji Pikku z Tailwind i shadcn/ui wygląd: motywy poleceniem pikku ui theme, kolory marki, fonty, warianty komponentów cva, tryb jasny i ciemny oraz reguły kontrastu WCAG.
  • 100od-shadcn-ui
    Buduje komponenty interfejsu z biblioteką shadcn/ui.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.