strict-theme-ember
/strict-theme-ember
Buduje strony gier, e-sportu i sportu w motywie Ember dla shadcn, ciemnym i z bursztynowym akcentem.
- Autor
- strictthemes ↗
- Repozytorium
- strictthemes ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 8
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Buduje strony gier, e-sportu i sportu w motywie Ember dla shadcn, ciemnym i z bursztynowym akcentem.
Oryginalny opis (EN)
Build UI in the Ember theme from strictthemes.com. A hot, dark-first theme for games, esports and sport. Blue-black, ember red, and an amber signal from the same fire. Use it when the project's DESIGN.md is Ember, or when the user asks for the Ember theme. It installs the theme into a shadcn project, gives its layout rules and its page briefs (game home page, patch notes page, leaderboard, item shop and player profile), and checks the result with Strict Check.
Jak działa
- Before you start
- The theme in short
- Rules
- Page briefs
- Check before you finish
Podgląd SKILL.md
---
name: strict-theme-ember
description: "Build UI in the Ember theme from strictthemes.com. A hot, dark-first theme for games, esports and sport. Blue-black, ember red, and an amber signal from the same fire. Use it when the project's DESIGN.md is Ember, or when the user asks for the Ember theme. It installs the theme into a shadcn project, gives its layout rules and its page briefs (game home page, patch notes page, leaderboard, item shop and player profile), and checks the result with Strict Check."
---
# Ember
A hot, dark-first theme for games, esports and sport. Blue-black, ember red, and an amber signal from the same fire.
This skill is for building UI in the Ember 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 Ember variables in its global CSS. If not, run `npx shadcn@latest add https://strictthemes.com/r/ember.json` and save https://strictthemes.com/themes/ember/DESIGN.md as `DESIGN.md` in the project root. In a project without shadcn, use https://strictthemes.com/themes/ember/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:** Oxanium for headings, Sofia Sans for body text, Martian Mono for labels and code.
- **Type scale** (size/weight; each class also sets line height and tracking): `text-display` 72px/800, `text-h1` 44px/700, `text-h2` 24px/700, `text-body` 16px/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`), 12px (`3`), 24px (`6`), 48px (`12`), 80px (`20`).
- **Corners:** `rounded-sm` 1px, `rounded-md` 3px, `rounded-xl` 6px (the `lg` corner in `DESIGN.md`). `rounded-lg` is 3px as well: it is shadcn's name for the base corner, the one its stock buttons and inputs use.
- **Colors (light mode):** primary #9D0208, on-primary #FFFFFF, secondary #03071E, on-secondary #FFF5E9, tertiary #FFBA08, on-tertiary #03071E, neutral #6A4B52, background #FFF5E9, surface #FFFFFF, foreground #03071E, border #E5CBAE, error #D00000, heat-low #DC2F02, heat-mid #F48C06, heat-high #FFBA08.
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 Ember pages are laid out
- **Page:** one `<div>` wraps the whole page: `min-h-screen bg-background text-body text-foreground`. Inside it sit the `<header>`, the `<main>` holding everything between the two, and the `<footer>`. Ember lives in dark mode: build and look at every part in dark mode first, then in light mode, and keep both right.
- **Container:** `mx-auto max-w-[1280px] px-3 md:px-6`. This width is the one arbitrary value allowed. The `<main>` element is itself a container and also carries `pt-12`. The header and the footer run the full width of the window, with their lines; the container is a `<div>` inside each. Every other line stays inside the container.
- **Grid:** where the page brief gives columns, the element is `grid grid-cols-1 md:grid-cols-12 md:gap-x-6` (24px gutters) and each item says its span, such as `md:col-span-7`. The grid sets columns only, never vertical space. Below `md` items stack in source order.
- **Vertical rhythm:** written as a top margin on the later element, never as `space-y-*` and never as a gap on a column of mixed content. A heading under a label has `mt-2`. A paragraph under a heading, and a paragraph under a paragraph, has `mt-3`. A block under text (a row of buttons, a list, a table, a meter, a row of cards) has `mt-6`. A new group inside a section has `mt-12`. A `<section>` inside `<main>` has `mt-20` (80px), except the first, which has none: the `pt-12` on `<main>` is the space above it. Where two grid items share a row from `md` up and stack below it, the second gets `mt-6 md:mt-0` when it follows on from the first (a picture beside its text) and `mt-12 md:mt-0` when it is a separate group (a card, a column with its own heading); each brief writes which. Gaps are only for items side by side in a row (`flex`, `flex-wrap`, a grid of cards), where the page brief or these notes name one. Inside a list of rows, a row has its own top border and padding and no margin. Where a part of a brief gives a margin that differs from this note, the brief's part wins.
- **Headings:** headings are Oxanium, which `<h1>` to `<h6>` get on their own; no full stop. Every heading set at `text-h1` or `text-display`, at any width, is `uppercase`: the page's big title and every section `<h2>`. Write their text in sentence case in the code; the class sets the capitals. A heading in `text-h2` alone (in a card, a row, a tile) stays in sentence case. The page's big title is `text-h1 md:text-display`, the only `text-display` text on the page unless a brief gives a big figure that size. A section's `<h2>` is `text-h2 md:text-h1 uppercase`. Keep every word of an uppercase heading to nine letters or fewer, so nothing runs out of the screen at 375px. Titles wrap; never truncate one.
- **Labels:** versions, dates, times, ranks, regions, prices, eyebrows, captions, nav links, table headers and button and badge text are labels: `font-mono text-label uppercase`. Write their text in sentence case ("Patch 4.2 · Tue 10 Nov"); the `uppercase` class sets the capitals. `text-label` already carries the tracking; add no `tracking-*` class. A label is a short fragment; anything that is a sentence is body text. A table's body cells are not labels: they are `text-body`, with the Figures classes where they hold a number, unless a brief gives a column label classes. Parts of a label line are joined with ` · `. A label on its own line is a block element such as a `<p>`. Martian Mono is wide: a label of more than about 30 characters will not fit a phone's line, so keep them short.
- **Figures:** every number that stands on its own (a rank, a rating, a score, a price, a count, a version, a date or a time in a label, a table cell or a big figure) gets `font-mono tabular-nums`. A **big figure** is a number set large: `font-mono text-h1 tabular-nums`, or `font-mono text-h2 tabular-nums` where a brief says so; it is never uppercased and has no label classes. Where a big figure and a label share one `<p>` (`61 days left`), the `<p>` has no classes but its margin, the figure is a `<span>` with the big figure classes, and the label is a `<span>` with `ml-2`. A heading that holds a number (`Patch 4.2`) stays in Oxanium and adds only `tabular-nums`. Thousands take a comma (`2,418`), a change takes a sign (`+21`, and `−17` with the minus sign `−`, not a hyphen), a rate takes one decimal (`55.4%`). A number inside a sentence is plain text. A label that holds any digit (a date, a time, a count, a price, a year, `5v5`, `Season 4`) adds `tabular-nums` to its label classes, on the label's own element, even where a brief lists only `font-mono text-label uppercase`.
- **Dates:** "today" is always the sample date, Thursday 12 November 2026, never the clock; nothing on these pages reads the time. In a label a date is short, `Tue 10 Nov`, with the year only where a brief writes one (`Tue 10 Nov 2026`); in a sentence it is written in full, `Tuesday 10 November`. Times are 24-hour (`09:40`). A date or a time that stands on its own is a `<time>` with a `dateTime` (`2026-11-10`, or `2026-11-12T09:40` with a time). A date range in a label (`6 Oct – 12 Jan 2027`) is two `<time>` elements joined by an en dash in plain text.
- **Text color:** headings, body text, nav links, table body cells, big figures and labels that name a thing (a player, an item) are `text-foreground`. Other labels, captions and helper text are `text-muted-foreground`, and muted text sits only on `bg-background` or `bg-card`. Running text (the sentences under a heading, a summary, a description) is never muted. A one-line note that a brief or the Footer note gives in `text-muted-foreground` (the footer's line, a note under a table) is a caption, not running text, and stays muted. A button's text color comes from its variant. `text-primary` is never used: red is not a text color in this theme.
- **Red:** `bg-primary` is ember red, brighter in dark mode, for the screen's one main action: a default `Button` or a link styled as one. Each brief names it or says the page has none, and there is never a second. It is never a text color, a border, a band or the fill of anything else. The focus outline from the rules (`outline-ring`) is red too, and stays.
- **Amber:** `bg-tertiary` is for one badge on a page, always with `text-tertiary-foreground` (blue-black in both modes). It is never a text color, a border or a fill of anything else.
- **Heat:** `bg-heat-low` (deep red), `bg-heat-mid` (orange) and `bg-heat-high` (amber) are the theme's own three-step scale, the same in both modes. They are fills only: for meters, rank marks, the viewer's row in a table, chart bars and the shapes in a drawn picture. Never a text color, a border, a button, or a fill with text on it. `bg-heat-low` sits close to the page in dark mode and `bg-heat-high` close to it in light mode, so a heat fill never carries meaning alone: the value or the step is always written next to it in words or figures.
- **Meters:** a meter is a `<div>` with `role="meter"`, `aria-valuemin`, `aria-valuemax`, `aria-valuenow`, an `aria-valuetext` in words and an `aria-labelledby` that points to its label. Its track is `h-3 w-full border border-border bg-muted`, with square corners, and holds one fill, `h-full` with one heat class and its width as an inline `style` (`style={{ width: "61%" }}`). A meter always has its value written beside or above it as a label or a big figure. Each brief says which value takes which of the three steps.
- **Rank marks:** a small square, `size-3 shrink-0 rounded-sm` with one heat class and `aria-hidden="true"`, always followed by the step's name in words in a row `flex items-center gap-2`. The tiers of Ranked Clash are Inferno (rating 2,800 and up, `bg-heat-high`), Blaze (2,600 to 2,799, `bg-heat-mid`) and Cinder (under 2,600, `bg-heat-low`).
- **Measure:** a paragraph of running text is at most `max-w-xl` wide.
- **Links:** a text link is `text-foreground underline decoration-1 underline-offset-4 hover:decoration-2`: it is the text color, underlined, and its line thickens under the pointer. A link that holds a title (inside a heading, and the game's name in the header) is `text-foreground decoration-1 underline-offset-4 hover:underline`. A nav link is a label in `text-foreground` with `underline-offset-4 hover:underline`; the link for the current page has `aria-current="page"` and `underline decoration-2`. Links get `transition-colors duration-150`.
- **Link destinations:** the five pages are `/` (Game), `/patch`, `/leaderboard`, `/store` and `/player`; where the project has another router layout, use its paths. A link whose destination the page brief does not name points to `#`.
- **Header:** a `<header>` with `border-b border-border`. Its container `<div>` is also the row: `flex items-center justify-between gap-6 py-3`. On the left the game's name, "Ashfall", a link to `/` in `font-heading text-h2 uppercase`, never marked as the current page. On the right, a `<nav>` with the `aria-label` "Main" and `hidden md:block`, holding a `<ul>` with `flex gap-6` of five label links, in this order: Game (`/`), Patch notes (`/patch`), Leaderboard (`/leaderboard`), Store (`/store`), Profile (`/player`). The brief names the current one.
- **Menu on small screens:** below `md` the `<nav>` is hidden and a "Menu" button (`variant="outline"`, with the button classes below) stands at the right end of the row, with `aria-expanded` and `aria-controls`. It shows the links as a list inside the `<header>`, under its row: a second `<nav>` with the same `aria-label` and `md:hidden`, which carries the `id` that `aria-controls` names and has the `hidden` attribute while closed. It has a 1px top border across the full width (`border-t border-border`, on the `<nav>` itself, with the container `<div>` inside it) and, inside the container, `py-2`; each link is a block with `py-2`. It closes on Escape, pressed while focus is on the Menu button or in the menu (one `onKeyDown` handler on the `<header>`, acting only while the menu is open), and focus then goes to the Menu button; it also closes when a link in it is chosen. Do not use a `Sheet` or a `Dialog`.
- **Footer:** a `<footer>` with `mt-20`, `border-t border-border` and `py-12`. Inside it, the container `<div>` holds a grid (`md:grid-cols-12`): columns 1–6 hold the game's name as plain text in `font-heading text-h2 uppercase` and, with `mt-2`, a `<p>` in `text-body text-muted-foreground`: "A team arena game by Lowlight Games."; columns 7–12 hold a `<ul>` (not a `<nav>`) of the same five links as the header, as text links in `text-body`, with `flex flex-wrap gap-x-6 gap-y-2`, and `mt-6 md:mt-0`. These links take no `aria-current`: only the header marks the current page. Under the grid, with `mt-12`, a label line in `text-muted-foreground`: `© 2026 Lowlight Games`.
- **Buttons:** the shadcn `Button` with `className="h-auto px-6 py-2 font-mono text-label uppercase"`. It keeps its stock `rounded-lg` corner (3px). The default variant (red) is the screen's one main action, as the Red note says. Every other action is `variant="secondary"` (blue-black, warm white in dark mode), or `variant="outline"` for quiet ones. The `secondary` variant's stock hover is the same color as its fill: in `components/ui/button.tsx`, replace its `hover:bg-[color-mix(in_oklch,var(--secondary),var(--foreground)_5%)]` with `hover:bg-secondary/80`, once, on every page, whether or not the page has a secondary button, and add no hover class where you use it. A button that sends a form needs `type="submit"`: this `Button` is `type="button"` unless told otherwise. A link that looks like a button (to another page, or to a part of this one) is an `<a>` with the same classes: write `cn(buttonVariants({ variant }), "…")`, because `buttonVariants` alone does not merge classes. Such a link is `inline-flex`, so a top margin on it works: it needs no wrapper. 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 (a region, a class) is a `role="group"` with an `aria-label` and `flex flex-wrap gap-2`. The chosen button has `aria-pressed="true"` and `variant="secondary"`; the others have `aria-pressed="false"` and `variant="outline"`. Every button in it has the Buttons classes. Pressing the chosen button again changes nothing. Not `Tabs`: there are no tab panels.
- **Badges:** the shadcn `Badge` (add it with `npx shadcn@latest add badge`) with `variant="secondary"` and `className="h-auto rounded-sm border-transparent bg-tertiary px-2 py-1 font-mono text-label uppercase text-tertiary-foreground"`: the variant is named only because its classes hold no red, and these classes replace its fill and text color. One or two words, and at most one badge on a page.
- **Status dots:** the only full round in this theme: `size-2 shrink-0 rounded-full bg-foreground`, `aria-hidden="true"`, always beside a word that says the state. It does not pulse or blink. Only where a brief names one.
- **Announcements:** a message that tells a screen reader what changed goes into an element that is on the page from the start, empty or with its first text: one that arrives together with its text is often not announced. It is never hidden with `hidden` or `empty:hidden`. Each brief says whether it is a visible line with `aria-live="polite"` or a `<p>` with `role="status"` and `sr-only`.
- **Cards:** a card is a plain element with `rounded-xl border border-border bg-card p-6` (6px corners, 24px padding, a 1px border). Inside it, a label comes first where it has one, and the rest follows the rhythm above. Never put a card inside a card, and never a box with a border on all four sides inside a card: divide a card's parts with `border-t border-border` and `pt-3`. Do not use the shadcn `Card`.
- **Pictures:** there are no image files. A picture is a plain element in a fixed aspect ratio, `bg-muted`, with `role="img"` and an `aria-label` that says what it shows, and the shapes in it are plain `<div>`s with heat fills or `bg-foreground`, square corners, no border and no text, placed with `flex` or with `absolute` and fraction classes (`left-1/4`, `bottom-1/3`, `w-1/12`, `h-1/2`) as each brief gives them. A picture that stands on the page has `relative overflow-hidden rounded-xl border border-border`. A picture at the top of a tile has no corners of its own and only a bottom border (`border-b border-border`): the tile is `overflow-hidden` and clips it, so it never reads as a card inside a card. Nothing glows: no gradient, no blur, no shadow, no opacity trick.
- **Lists of rows:** a list of news or entries is an `<ol>` or `<ul>` with no markers and no padding. Each row has `border-t border-border py-6`, and the list has `border-b border-border` so the last row closes.
- **Tables:** the shadcn `Table` (add it with `npx shadcn@latest add table`) with `text-body`. Edit `components/ui/table.tsx`: its scroll box, the `<div>` around the `<table>`, gets `tabIndex={0}`, `role="region"`, an `aria-label` from a new required `label` prop, and the focus outline. Header cells are labels in `text-muted-foreground` with `px-3`; they keep the stock `h-10`. Body cells have `px-3 py-2`. Add `first:pl-0 last:pr-0` to every cell, unless a brief says otherwise. Numbers are `font-mono tabular-nums` and right-aligned (`text-right`), and so is their column header. Rows are divided by 1px borders, with no zebra stripes. The stock `TableBody` drops its last row's border: take `[&_tr:last-child]:border-0` out of it. The rows do nothing, so take `hover:bg-muted/50` out of the stock `TableRow`. Every cell keeps the stock `whitespace-nowrap`. The table's name is the heading above it and the `label`; it has no `<caption>`. The `Table`'s `className` reaches the `<table>` inside the scroll box, so a margin a brief gives the table goes on a plain `<div>` around it (`<div className="mt-6">`). Where the table sits in a grid column, that column gets `min-w-0`; a table straight in a `<section>` needs none. A table that a brief says scrolls on a phone gets the `min-w-*` class the brief gives, so it scrolls in its box and the page does not.
- **Icons:** from `lucide-react`, with `size-4`, `strokeWidth={1.5}` and `aria-hidden="true"`, and only where a brief names one. An icon takes the color of the text beside it (`text-foreground`): never red, even beside an issue or an error. Never emoji.
- **Corners:** hard. `rounded-sm` (1px) for badges and rank marks, `rounded-lg` (3px, the stock corner) for buttons, `rounded-md` (3px as well) for a player's mark, `rounded-xl` (6px) for cards, tiles and pictures. Meter tracks and the shapes in a picture are square. `rounded-full` is for the status dot only, 8px across. No pills, no circles around a person: a player's mark is a square.
- **Surfaces:** flat and dark: no shadow, glow, blur or gradient in the code you write. A card is `bg-card`, one step lighter than the page. A stock component that floats keeps its one short shadow.
- **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`, `3`, `6`, `12`, `20`) plus 0, 1px and 2px. No arbitrary values such as `p-[18px]`, and no other steps such as `p-5` or `gap-10`. `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 design the dark mode first: it is where this theme lives.
- Do keep red to one action per screen and amber to one badge.
- Do let numbers be large: a score or a rank can be the biggest thing on a page.
- Don't add glows, neon, gradients or blurred glass.
- Don't use a heat color for text or for a button.
- Don't introduce a color, size or radius that is not a token above.
## Page briefs
Ember 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.
- **Game:** the home page of a team arena game, with an opening that fills the first screen with the title and one action, the four classes, the current season, the latest news and the system requirements in a table. https://strictthemes.com/themes/ember/prompts/game.md
- **Patch notes:** the patch notes of one version of a team arena game, with its version and date, a summary, the new features, a table of balance changes with before and after figures and a filter by class, the fixes and the known issues. https://strictthemes.com/themes/ember/prompts/patch.md
- **Leaderboard:** the season's ranking of a team arena game, with the viewer's place, a filter by region, a table of players with rank, tier, rating, wins and win rate in which the viewer's own row is marked with a heat bar, and a key to the tiers. https://strictthemes.com/themes/ember/prompts/leaderboard.md
- **Store:** the item shop of a team arena game, with the viewer's balance in the game's currency, this week's featured bundle, and a grid of items with drawn pictures and prices that can be bought until the balance runs out. https://strictthemes.com/themes/ember/prompts/store.md
- **Player:** a player's profile in a team arena game, with a square mark with their initials, their rank and rating set large, the season's figures, meters for the classes they play and the season pass, their recent matches in a table and a few achievements. https://strictthemes.com/themes/ember/prompts/player.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-ember.
Migawka bazy z 13.11.2026 · wersja paczki fd9e2d481228 (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-dispatch
Buduje serwis informacyjny i sportowy w motywie Dispatch dla shadcn, z mocnymi nagłówkami i wynikami na żywo. - 95ember
Pomaga budować aplikacje Ember.js z użyciem Ember CLI i Ember Data, w stylu Octane: komponenty, trasy i usługi. - 100ember
Pomaga budować aplikacje w Ember.js: komponenty Glimmer, tracked state, zagnieżdżony routing, serwisy, Ember Data i ember-cli, a także aktualizować Ember i konwertować szablony do .gjs lub .gts. - 90ember-evaluator
Konfiguruje, sprawdza, uruchamia i raportuje eksperyment benchmarkowy ember-evaluator oraz tworzy wtyczkę ewaluatora Cordis. - 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.