Skip to content

Commit ebeff71

Browse files
vintaclaude
andcommitted
docs(.impeccable): add placestoread reference, no-green rule, type size guidance, consistency checks, and narrow-screen behavior
- Primary visual model: placestoread.xyz (table, expand row, sorting, footer) - Color aversion: no green; warm brown-red/ivory/earthy palette only - Type sizing: default one step larger than impeccable scale; never reduce unprompted - Row numbers: left-align, no leading zeros - Visual consistency checklist: hover/focus, tag variants, typography tiers, gutters, color tokens - Narrow-screen: < 960px and < 680px must stay functional; run playwright-cli after layout changes Co-Authored-By: Claude <noreply@anthropic.com>
1 parent f65a2aa commit ebeff71

1 file changed

Lines changed: 24 additions & 0 deletions

File tree

.impeccable.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,10 +41,15 @@ Stay close to the current direction. It works.
4141

4242
References (what to stay close to):
4343

44+
- **https://www.placestoread.xyz** is the primary visual model for the table, expand row, sorting, and footer. "Like placestoread" means dense single-page list, inline click-to-expand rows that indent under the Name column, sortable headers, minimum decoration. When in doubt about a table or row treatment, check placestoread first.
4445
- Magazine reference pages (The Economist, FT Weekend, Monocle).
4546
- Field-guide books. Curated, functional, hand-made.
4647
- Library card catalogs. Dense tabular information, excellent typography, no decoration for decoration's sake.
4748

49+
Color aversions:
50+
51+
- No green. The user rejected it when picking the palette. Warm brown-red, ivory, and dark earthy tones are the established system. Do not introduce green even for success states or ancillary accents.
52+
4853
Anti-references (avoid strictly):
4954

5055
- Generic dark developer-tool look. No cyan on near-black, neon gradients, VSCode-palette dashboards, terminal-green monospace branding.
@@ -70,6 +75,8 @@ Layout and sizing:
7075
- The impeccable skill reference rule "cap line length at ~65-75ch" does NOT apply here. Ignore it. Readability at wide widths is carried by vertical rhythm, leading, and the modular type scale instead.
7176
- If you believe a width cap is actually necessary for some specific element, ask first with a concrete reason before adding it.
7277
- Body type floor is 16px (`--text-base: 1rem`). Content-heavy passages may go to 1.125rem.
78+
- When in doubt about any type size, pick one step larger than what the impeccable skill's scale references suggest. The user has repeatedly corrected sizes upward (11+ separate requests across 8 sessions). Never reduce an existing size unprompted. Footer, meta rows, expand content, labels, headings all trend too small by default.
79+
- Row numbers in the table: left-align, no leading zeros. The user tried zero-padding and rejected it.
7380
- Adjacent heading levels differ by at least 0.25rem of rendered size.
7481

7582
Color:
@@ -88,6 +95,23 @@ CSS hygiene:
8895
- Never `text-transform`. Write the casing in the markup.
8996
- Sibling components (card lists, grid items) share identical spacing.
9097

98+
Visual consistency check:
99+
100+
Before shipping any visual change, check peer elements. The user catches inconsistencies repeatedly.
101+
102+
- Hover and focus states: if one link type gets a hover treatment, peer links (hero topbar, footer, project names, sponsor names, expand-meta) share it.
103+
- Tag variants (group, subcat, source, built-in) inherit the base `.tag` style and differ only where a real difference is needed.
104+
- Typography tiers: labels that play the same role share size, weight, and letter-spacing.
105+
- Symmetric gutters: logo left-gap equals logo right-gap, column paddings match across header and body.
106+
- Role-based color tokens: same role uses the same token everywhere. No one-off inline `color: oklch(...)` buried in a rule.
107+
108+
Narrow-screen behavior:
109+
110+
The user actively tests `< 960px` and `< 680px`. Narrow screens must stay functional.
111+
112+
- Do not drop features that the user might want (sort affordance, filter chips, sticky header where reasonable). Hiding is a last resort and requires justification.
113+
- Always run the `playwright-cli` skill at a narrow viewport after any layout change.
114+
91115
Absolute bans (from the impeccable skill):
92116

93117
- No `border-left` or `border-right` greater than 1px as a colored accent stripe on cards, list items, callouts, or alerts. Use a different structure.

0 commit comments

Comments
 (0)