BetterMech PUBLIC · REV 0.1
Библиотека · EN

Library for Claude

BGENES · FR · DE — скоро

v0.1 · 2026-10-19 · от Better Mechanics · ниво: общност (текст, без протокол от проверка)

1 · Read before work

  • Project CLAUDE.md and parent ones: the owner's rules override my habits.
  • Matching skills (SKILL.md). For web: 04_Shabloni/01_AGENTS_web.md of the web prompt library.
  • The brand book: tokens, fonts, bans. No brand book, no colour choices.

2 · My design failure modes and the guard in the recipe

Failure Symptom Guard
Generic "AI look" centred hero + three cards, purple gradient, Inter everywhere, emoji headings negative prompt with explicit bans + layout sketch before code
Invented content "10,000+ happy clients", faceless testimonials, fake stats only supplied content; gaps become a visible "missing" note
Cyrillic with Russian forms Inter, Playfair, JetBrains Mono lack Bulgarian forms lang="bg" + font with locl BGR, verified on the file with fontTools
Phone overflow wide tables, long words, fixed widths minmax(min(Xpx,100%),1fr); measure at 360 px as a number
Contrast in the second theme light theme checked, dark not run axe in both themes (emulate_media)
Declaring "done" unseen code, then report take a screenshot and look at it before saying done
Invented versions and URLs @latest, non-existent CDN exact version, self-hosted, URL checked live
Rewriting whole files others' work lost small exact edits; full rewrite only for new files
Too much motion parallax, particles, everything animates motion only with meaning + prefers-reduced-motion
Unstructured long pages everything on one page one function per screen, steps 1→2→3

3 · Prompt patterns that work with me

  • Role and audience → constraints → output: "for whom · what not · how it will be checked".
  • References with a reason ("I like it because…"), never "make it beautiful".
  • Explicit "verify and show proof": screenshot, axe, overflow, weight.
  • Separate thinking from building: a text layout sketch first, then code.

4 · My tools

Claude Code (files, shell, browser), skills, MCP (Figma, browser), Playwright on the owner's machine for screenshots and checks, artifacts for sharing.

5 · First 10 recipes

  1. Negative prompt against the generic look (bans + sketch)
  2. Cyrillic with Bulgarian forms: choose, verify with fontTools, subset with --layout-features=*
  3. The loop "code → screenshot → look → fix" with proof
  4. Page check: axe in light and dark, 360 px, weight, console errors
  5. Tokens first: :root colours, fonts, spacing before the first component
  6. Self-hosting: fonts, three.js, no external CDN
  7. Light 3D hero: load after content, pause off-screen, static on reduced motion
  8. Missing content as a visible note, never invented
  9. Small edits in someone else's file: read, exact replace, verify
  10. The recipe plate: reporting what was measured and what was not