// Performance patterns and anti-patterns for ethereum.org covering TTFB, LCP, INP, CLS, bundle size, build memory, and RSC payload. Use when diagnosing a perf regression or reviewing proposed code changes for perf landmines.
| name | performance |
| description | Performance patterns and anti-patterns for ethereum.org covering TTFB, LCP, INP, CLS, bundle size, build memory, and RSC payload. Use when diagnosing a perf regression or reviewing proposed code changes for perf landmines. |
| user-invocable | false |
Knowledge base. No runtime actions; authoring conventions for maintainers below. Read the relevant references/*.md files directly via the Read tool.
references/diagnose-table.md (symptom → bucket).references/review-checklist.md (diff pattern → rules to load).Both flows always also load references/anti-patterns.md.
| Topic | File |
|---|---|
| Symptom → bucket routing | references/diagnose-table.md |
| Diff pattern → rules routing | references/review-checklist.md |
| TTFB, edge caching, CDN | references/edge-caching.md |
| Bundle size, code splitting | references/bundle.md |
| Build OOM, ENOSPC, file tracing | references/build.md |
| RSC payload, HTML size | references/rsc.md |
| INP, main-thread work | references/inp.md |
| LCP, images | references/images.md |
| Cross-cutting anti-patterns | references/anti-patterns.md |
For data-fetching patterns (Trigger.dev tasks, Netlify Blobs, src/lib/data caching, internal /api/* routes, fetcher retries), use the data-layer skill instead.
PR #N) when a rule comes from a specific shipped change. Add a SHA only when no PR exists.review-checklist.md AND the matching bucket file. Don't restate the rule inline.Use when building, refactoring, or styling any UI in the ethereum.org Next.js site (`src/components/`, `app/`, `src/styles/`, `public/content/`, or any `.tsx`/`.mdx`/`.css` change that affects the rendered UI). Provides canonical component choices, design tokens, RTL/i18n rules, server/client guidance, and the "use a variant, not a new component" pattern for the project's Tailwind v4 + Radix + shadcn-style design system.
Use when working on the translation pipeline (`src/scripts/intl-pipeline/`), the post-import sanitizer (`intl-sanitizer.ts`), the `intl/pending-*` branches, the `intl-pipeline.yml` GitHub Actions workflow, ETHGlossary integration, or any translation-related issue (broken translations, missing locales, manifest drift, sanitizer false positives, ETHGlossary term lookups, language-group transliteration questions). Provides the manifest-driven incremental pipeline mental model, the "don't hand-propagate" rule, recovery procedures, the ETHGlossary-as-canonical-source policy, and the `intl/pending-{base}` orchestration contract.
Use when reviewing translation imports/PRs (especially against `intl/pending-*` branches), evaluating translation quality across any of the 24 target languages, triaging issues in `.claude/translation-review/`, scoring a locale's translation, running the `/review-translations` slash command, debugging brand-name mistranslations or glossary deviations, or working with the per-language findings tracking files. Covers the scoring rubric, ETHGlossary-as-authority policy, language-group rules, agent-role split (structural / terminology / semantic), the concept-tag-vs-brand-tag distinction in frontmatter, and the critical-vs-warning severity policy.
Playwright + Chromatic full-page visual tests for ethereum.org. Trigger on "add a page to the visual suite", "the snapshot keeps changing", "chromatic pages", "chromatic playwright", or edits to `tests/visual/`, `playwright.visual.config.ts`, or `.github/workflows/chromatic-pages.yml`. Skip for Storybook Chromatic (`chromatic.yml`), e2e (`tests/e2e/`), unit (`tests/unit/`).
This skill provides patterns for working with the data-layer module. Use when creating/editing files in src/data-layer/, src/lib/data/, or adding new data sources.