Skip to content

code-yeongyu/oh-my-openagent / packages/shared-skills/skills/frontend

frontend

Flagged

Builds, styles, and polishes anything drawn with HTML, CSS, or SVG: web UI, pages, components, HTML reports rendered to PDF or print, figures, PNG/SVG diagrams, slides, and images for Notion or Slack. Use for any styling, layout, animation, or visual-quality task, or when asked to make something look or feel a certain way.

FileKindSize
.gitignoreother1.2 KB
.npmignoreother563 B
ATTRIBUTION.mdmarkdown20.0 KB
LICENSE-Apache-2.0.txtmarkdown11.0 KB
SKILL.mdskill md26.4 KB
references/design/README.mdmarkdown17.0 KB
references/design/_INDEX.mdmarkdown17.6 KB
references/design/ambience-skill.mdmarkdown18.0 KB
references/design/aside.mdmarkdown12.5 KB
references/design/clone-from-url.mdmarkdown5.3 KB
references/design/component-catalogs.mdmarkdown11.2 KB
references/design/design-system-architecture.mdmarkdown15.7 KB
references/design/grounding.mdmarkdown3.7 KB
references/design/interaction-skill.mdmarkdown16.1 KB
references/design/layout-skill.mdmarkdown8.3 KB
references/design/lazyweb.mdmarkdown3.8 KB
references/design/print-paged-media.mdmarkdown6.8 KB
references/design/react-dev-tooling-skill.mdmarkdown8.5 KB
references/design/stylegallery.mdmarkdown4.3 KB
references/designpowers/EVIDENCE.mdmarkdown3.7 KB
references/designpowers/README.mdmarkdown3.7 KB
references/designpowers/UPSTREAM.mdmarkdown2.2 KB
references/designpowers/lane-a-direction.mdmarkdown5.3 KB
references/designpowers/lane-b-execution.mdmarkdown5.6 KB
references/designpowers/lane-c-review.mdmarkdown5.4 KB
references/designpowers/lane-d-memory.mdmarkdown5.0 KB
references/designpowers/orchestration.mdmarkdown5.3 KB
references/designpowers/routing.mdmarkdown5.2 KB
references/perfection/README.mdmarkdown12.2 KB
references/perfection/craft-floor.mdmarkdown6.4 KB
references/perfection/detect.mdmarkdown3.9 KB
references/perfection/react-perf-tooling.mdmarkdown8.3 KB
scripts/detect/cli.tsscript3.0 KB
scripts/detect/config.test.tsscript1.4 KB
scripts/detect/config.tsscript3.0 KB
scripts/detect/core/characters.tsscript157 B
scripts/detect/core/color.test.tsscript1.1 KB
scripts/detect/core/color.tsscript7.1 KB
scripts/detect/core/page.tsscript3.7 KB
scripts/detect/core/shadow.tsscript1.5 KB
scripts/detect/core/source.tsscript1.4 KB
scripts/detect/detect.tsscript3.5 KB
scripts/detect/index.tsscript1.1 KB
scripts/detect/lint.test.tsscript1.2 KB
scripts/detect/lint.tsscript4.2 KB
scripts/detect/render/probe-placement.test.tsscript1.6 KB
scripts/detect/render/probe-placement.tsscript1.9 KB
scripts/detect/render/renderer.tsscript1.4 KB
scripts/detect/render/webview.tsscript3.4 KB
scripts/detect/report.tsscript1.0 KB
scripts/detect/rule.tsscript1.4 KB
scripts/detect/rules/color/ai-color-palette.test.tsscript5.2 KB
scripts/detect/rules/color/ai-color-palette.tsscript6.5 KB
scripts/detect/rules/color/cream-palette.test.tsscript1.5 KB
scripts/detect/rules/color/cream-palette.tsscript2.3 KB
scripts/detect/rules/color/dark-glow.test.tsscript3.2 KB
scripts/detect/rules/color/dark-glow.tsscript3.0 KB
scripts/detect/rules/color/design-system-color.test.tsscript1.6 KB
scripts/detect/rules/color/design-system-color.tsscript1.8 KB
scripts/detect/rules/color/gradient-text.test.tsscript2.6 KB
scripts/detect/rules/color/gradient-text.tsscript3.4 KB
scripts/detect/rules/color/gray-on-color.test.tsscript2.7 KB
scripts/detect/rules/color/gray-on-color.tsscript2.2 KB
scripts/detect/rules/color/index.tsscript685 B
scripts/detect/rules/color/low-contrast.test.tsscript17.0 KB
scripts/detect/rules/color/low-contrast.tsscript5.0 KB
scripts/detect/rules/color/placeholder-contrast.test.tsscript5.3 KB
scripts/detect/rules/color/radial-halo.test.tsscript2.5 KB
scripts/detect/rules/color/radial-halo.tsscript2.3 KB
scripts/detect/rules/color/radial-spotlight-glow.test.tsscript2.3 KB
scripts/detect/rules/color/radial-spotlight-glow.tsscript2.1 KB
scripts/detect/rules/color/support/animation-opacity.tsscript4.3 KB
scripts/detect/rules/color/support/color-path.tsscript869 B
scripts/detect/rules/color/support/contrast-pairs.tsscript3.1 KB
scripts/detect/rules/color/support/contrast-role.tsscript5.6 KB
scripts/detect/rules/color/support/glow-forms.tsscript3.8 KB
scripts/detect/rules/color/support/gradient-samples.tsscript6.5 KB
scripts/detect/rules/color/support/gradients.tsscript4.1 KB
scripts/detect/rules/color/support/mockup-roots.tsscript5.5 KB
scripts/detect/rules/color/support/page-ignore.tsscript457 B
scripts/detect/rules/color/support/painted-text.tsscript8.3 KB
scripts/detect/rules/color/support/palette-roles.tsscript3.6 KB
scripts/detect/rules/color/support/placeholder-contrast.tsscript2.0 KB
scripts/detect/rules/color/support/stock-accent.tsscript2.5 KB
scripts/detect/rules/color/support/text-colors.tsscript4.7 KB
scripts/detect/rules/copy/aphoristic-cadence.test.tsscript1.1 KB
scripts/detect/rules/copy/aphoristic-cadence.tsscript993 B
scripts/detect/rules/copy/broken-image.test.tsscript1.4 KB
scripts/detect/rules/copy/broken-image.tsscript902 B
scripts/detect/rules/copy/em-dash-overuse.test.tsscript2.4 KB
scripts/detect/rules/copy/em-dash-overuse.tsscript2.8 KB
scripts/detect/rules/copy/index.tsscript768 B
scripts/detect/rules/copy/marketing-buzzword.test.tsscript1.1 KB
scripts/detect/rules/copy/marketing-buzzword.tsscript1.6 KB
scripts/detect/rules/copy/numbered-section-labels.test.tsscript3.6 KB
scripts/detect/rules/copy/numbered-section-labels.tsscript2.4 KB
scripts/detect/rules/copy/repeated-container-text.test.tsscript2.5 KB
scripts/detect/rules/copy/repeated-container-text.tsscript3.6 KB
scripts/detect/rules/copy/script-error.test.tsscript3.3 KB
scripts/detect/rules/copy/script-error.tsscript1.7 KB
scripts/detect/rules/copy/skipped-heading.test.tsscript3.0 KB
scripts/detect/rules/copy/skipped-heading.tsscript8.3 KB
scripts/detect/rules/copy/support/numbered-label.tsscript5.4 KB
scripts/detect/rules/copy/support/page-text.tsscript1.8 KB
scripts/detect/rules/copy/theater-slop-phrase.test.tsscript1.1 KB
scripts/detect/rules/copy/theater-slop-phrase.tsscript1.2 KB
scripts/detect/rules/decoration/blinking-cursor.test.tsscript2.1 KB
scripts/detect/rules/decoration/blinking-cursor.tsscript2.3 KB
scripts/detect/rules/decoration/border-accent-on-rounded.test.tsscript1.3 KB
scripts/detect/rules/decoration/border-accent-on-rounded.tsscript556 B
scripts/detect/rules/decoration/bounce-easing.test.tsscript3.5 KB
scripts/detect/rules/decoration/bounce-easing.tsscript5.0 KB
scripts/detect/rules/decoration/buried-raster.test.tsscript5.1 KB
scripts/detect/rules/decoration/buried-raster.tsscript3.5 KB
scripts/detect/rules/decoration/codex-grid-background.test.tsscript1.1 KB
scripts/detect/rules/decoration/codex-grid-background.tsscript1.3 KB
scripts/detect/rules/decoration/design-system-radius.test.tsscript1.2 KB
scripts/detect/rules/decoration/design-system-radius.tsscript1.3 KB
scripts/detect/rules/decoration/gpt-thin-border-wide-shadow.test.tsscript2.4 KB
scripts/detect/rules/decoration/gpt-thin-border-wide-shadow.tsscript2.9 KB
scripts/detect/rules/decoration/hard-offset-shadow.test.tsscript2.2 KB
scripts/detect/rules/decoration/hard-offset-shadow.tsscript1.2 KB
scripts/detect/rules/decoration/hero-eyebrow-chip.test.tsscript2.6 KB
scripts/detect/rules/decoration/hero-eyebrow-chip.tsscript754 B
scripts/detect/rules/decoration/icon-tile-stack.test.tsscript2.8 KB
scripts/detect/rules/decoration/icon-tile-stack.tsscript3.5 KB
scripts/detect/rules/decoration/index.tsscript1.3 KB
scripts/detect/rules/decoration/kicker-above-heading.test.tsscript5.0 KB
scripts/detect/rules/decoration/kicker-above-heading.tsscript2.8 KB
scripts/detect/rules/decoration/marquee.test.tsscript2.9 KB
scripts/detect/rules/decoration/marquee.tsscript2.8 KB
scripts/detect/rules/decoration/organic-clip-path.test.tsscript2.7 KB
scripts/detect/rules/decoration/organic-clip-path.tsscript1.9 KB
scripts/detect/rules/decoration/pulsing-dot.test.tsscript3.2 KB
scripts/detect/rules/decoration/pulsing-dot.tsscript4.4 KB
scripts/detect/rules/decoration/repeating-stripes-gradient.test.tsscript1.1 KB
scripts/detect/rules/decoration/repeating-stripes-gradient.tsscript973 B
scripts/detect/rules/decoration/shape-assembled-illustration.test.tsscript2.5 KB
scripts/detect/rules/decoration/shape-assembled-illustration.tsscript3.0 KB
scripts/detect/rules/decoration/side-tab.test.tsscript4.4 KB
scripts/detect/rules/decoration/side-tab.tsscript747 B
scripts/detect/rules/decoration/support/appearance.tsscript3.9 KB
scripts/detect/rules/decoration/support/assert-cases.tsscript1.3 KB
scripts/detect/rules/decoration/support/borders.tsscript6.9 KB
scripts/detect/rules/decoration/support/clip-geometry.tsscript5.9 KB
scripts/detect/rules/decoration/support/css-candidates.tsscript2.7 KB
scripts/detect/rules/decoration/support/curve-samples.tsscript2.1 KB
scripts/detect/rules/decoration/support/gradient-pattern.tsscript1.7 KB
scripts/detect/rules/decoration/support/keyframes.tsscript5.8 KB
scripts/detect/rules/decoration/support/labels.tsscript4.2 KB
scripts/detect/rules/decoration/support/raster-state.tsscript3.4 KB
scripts/detect/rules/index.tsscript452 B
scripts/detect/rules/layout/body-text-viewport-edge.test.tsscript4.5 KB
scripts/detect/rules/layout/body-text-viewport-edge.tsscript4.4 KB
scripts/detect/rules/layout/clipped-overflow-container.test.tsscript2.7 KB
scripts/detect/rules/layout/clipped-overflow-container.tsscript945 B
scripts/detect/rules/layout/content-hidden-at-rest.test.tsscript4.1 KB
scripts/detect/rules/layout/content-hidden-at-rest.tsscript4.9 KB
scripts/detect/rules/layout/cramped-padding.test.tsscript4.9 KB
scripts/detect/rules/layout/cramped-padding.tsscript6.8 KB
scripts/detect/rules/layout/edge-flush-cards.test.tsscript2.5 KB
scripts/detect/rules/layout/edge-flush-cards.tsscript3.4 KB
scripts/detect/rules/layout/first-viewport-column-overflow.test.tsscript2.1 KB
scripts/detect/rules/layout/first-viewport-column-overflow.tsscript3.2 KB
scripts/detect/rules/layout/heading-rhythm.test.tsscript4.2 KB
scripts/detect/rules/layout/heading-rhythm.tsscript1.9 KB
scripts/detect/rules/layout/index.tsscript1.1 KB
scripts/detect/rules/layout/monotonous-spacing.test.tsscript1.3 KB
scripts/detect/rules/layout/monotonous-spacing.tsscript2.0 KB
scripts/detect/rules/layout/nested-cards.test.tsscript4.1 KB
scripts/detect/rules/layout/nested-cards.tsscript2.6 KB
scripts/detect/rules/layout/straggler.test.tsscript2.1 KB
scripts/detect/rules/layout/straggler.tsscript1.8 KB
scripts/detect/rules/layout/support/cards.tsscript7.2 KB
scripts/detect/rules/layout/support/clipping.tsscript4.8 KB
scripts/detect/rules/layout/support/declared-mockups.tsscript4.9 KB
scripts/detect/rules/layout/support/geometry.tsscript4.9 KB
scripts/detect/rules/layout/support/hidden-interface.tsscript2.5 KB
scripts/detect/rules/layout/support/layout-cases.tsscript1.3 KB
scripts/detect/rules/layout/support/line-breaks.tsscript1.7 KB
scripts/detect/rules/layout/support/motion.tsscript4.1 KB
scripts/detect/rules/layout/support/padding.tsscript5.1 KB
scripts/detect/rules/layout/support/rhythm.tsscript9.0 KB
scripts/detect/rules/layout/text-occlusion.test.tsscript2.9 KB
scripts/detect/rules/layout/text-occlusion.tsscript5.2 KB
scripts/detect/rules/layout/text-overflow.test.tsscript6.0 KB
scripts/detect/rules/layout/text-overflow.tsscript4.9 KB
scripts/detect/rules/layout/unbalanced-heading.test.tsscript1.3 KB
scripts/detect/rules/layout/unbalanced-heading.tsscript1.3 KB
scripts/detect/rules/layout/viewport-reflow.test.tsscript2.0 KB
scripts/detect/rules/layout/viewport-reflow.tsscript1.8 KB
scripts/detect/rules/source/ai-color-palette.test.tsscript564 B
scripts/detect/rules/source/ai-color-palette.tsscript888 B
scripts/detect/rules/source/aphoristic-cadence.test.tsscript622 B
scripts/detect/rules/source/aphoristic-cadence.tsscript984 B
scripts/detect/rules/source/border-accent-on-rounded.test.tsscript776 B
scripts/detect/rules/source/border-accent-on-rounded.tsscript1.5 KB
scripts/detect/rules/source/bounce-easing.test.tsscript1.1 KB
scripts/detect/rules/source/bounce-easing.tsscript1.8 KB
scripts/detect/rules/source/broken-image.test.tsscript1.2 KB

references/perfection/README.md

View on GitHub

# Frontend Perfectionist

You are a senior frontend engineer with one binding standard: **every page hits 100 in EVERY Lighthouse category, measured on a REAL browser, without sacrificing a single drop of UX quality.**

## TENETS. NON-NEGOTIABLE.

### 1. AUDIT THROUGH A REAL BROWSER. NEVER THROUGH THE CLI.

The `lighthouse` CLI runs `chrome-headless-shell` with default settings. That is **NOT** what your users see, and the number it produces will lie to you. **REJECT** any report based on the CLI, even if the CI shows green.

The correct path:

1. Build the app in production mode (`next build && next start`, `vite build && vite preview`, `astro build && astro preview`, `bun run build && bun run start`). **NEVER** measure a dev server.
2. Launch Playwright with `channel: "chrome"` (real Chrome stable, not the headless-shell binary).
3. Run Lighthouse against the Playwright-controlled page via `playwright-lighthouse` OR via `chrome-launcher` + the `lighthouse` Node API, attaching to the Playwright CDP endpoint so cookies, auth state, and warmed caches mirror what a real returning user sees.
4. Use the **mobile** preset (4x CPU throttle, Fast 3G) for the primary number, AND the **desktop** preset for the secondary number. Report both.

If no browser-automation skill is loaded in this session, load the `browser` skill now (read its `SKILL.md`).

### 2. 100 IN EVERY CATEGORY IS THE FLOOR.

A 99 is a regression. A 95 is a fire. You do NOT report "performance 93, accessibility 100, SEO 100, best-practices 100" as a pass. You diagnose what cost the 7 points, fix the root cause, re-run, and only report when all four panels show 100. On mobile AND desktop.

### 3. WIN THE SCORE IN THE ARCHITECTURE.

Performance is decided at architecture and code-quality level. Bundle size, render path, hydration strategy, asset pipeline, image format and dimensions, font loading, third-party scripts, critical CSS, deferred JS, route-level code splitting. These are the LEVERS that move the score. Slapping `loading="lazy"` on a hero image is not optimization. It is panic.

For EVERY failing audit, trace it back to a SPECIFIC line of code or a SPECIFIC build-config choice. Fix it at the source. No band-aids.

### 4. NEVER WEAKEN UX TO BUY POINTS.

If your fix removes a hover state, drops a CSS transition, replaces an animated mount with an abrupt one, swaps a smooth scroll-into-view for an instant jump, degrades a 60fps interaction to 30fps, or hides content you would normally render, **REJECT THE FIX**. The animation language, motion design, and tactile feel of the product are load-bearing.

Find another way:

- Split the bundle further (route-level, then component-level, then feature-flag-level).
- Defer non-critical paint work to `requestIdleCallback`.
- Move expensive work off the main thread via Web Workers (use Comlink for ergonomics).
- Use the `View Transitions API` for cross-route transitions.
- Use `content-visibility: auto` plus `contain-intrinsic-size` for offscreen sections.
- Use `will-change` precisely, ONLY on the property actually animating, ONLY for the duration of the animation.
- Preload the LCP image: `<link rel="preload" as="image" fetchpriority="high" imagesrcset="...">`.
- HTTP/2 server-push or `<link rel="modulepreload">` for the critical chunk.
- GPU-composited animations only (`transform`, `opacity`, `filter`). NEVER animate `width`, `height`, `top`, `left`, `margin`, `padding`.

### 5. LOAD THE DESIGN RULESET IN LOCKSTEP.

You **MUST** read the design ruleset (`../design/README.md`) alongside this one for any visual or layout work. That skill carries the brand-grade taste references (Apple, Stripe, Linear, Vercel, Claude, Notion, Airbnb, Figma, etc.) and the anti-AI-SaaS-slop posture.

A page that scores 100 but looks like AI SaaS slop has failed. Speed serves design; design rides on speed. **Both win or neither does.**

Use the design ruleset:

- BEFORE writing JSX/CSS: pull a relevant brand reference to ground the visual direction.
- DURING implementation: cross-check against the anti-slop guardrails.
- BEFORE declaring done: verify the page passes the design taste bar, not just the Lighthouse bar.

### 6. DESIGN SYSTEM COMPLIANCE IS NOT OPTIONAL.

The design ruleset (`../design/README.md`) enforces a **Phase 0 Design System Gate** — every project must have a `DESIGN.md` before any UI work begins. This skill enforces the other side: **every audit must verify compliance.**

During the audit loop, after Lighthouse scores pass, run a Design System Compliance check:

- **Colors**: grep the codebase for raw hex/rgb values not declared in `DESIGN.md`. Each is a violation.
- **Typography**: every font-size in CSS/Tailwind must map to the type scale in `DESIGN.md`. No arbitrary sizes.
- **Spacing**: every margin/padding/gap value must be a multiple of the base unit (4px) and ideally use a declared token.
- **Components**: any component used 2+ times must be documented in `DESIGN.md` Section 5. If it isn't, add it.
- **Depth**: if `DESIGN.md` says "borders-only", there must be zero `box-shadow` declarations. If "tonal-shift", zero borders for surface separation.
- **Draft guard**: run `bun ../../scripts/perfection/check-draft-guard.ts <src dirs>`. Besides promotional filler copy, emoji icons, hype badges, and hard-coded vanity stats, it flags a coloured one-side border (including a gradient `border-image`), a coloured `::before`/`::after` bar, an inset `box-shadow` stripe, or a hard-stop gradient band along one edge of any box, rounded or square, and a 2px-or-wider accent outline (border or inset ring) on a rounded card, in CSS, Tailwind, inline styles, and styled-components, whether the stripe is decorative or marks selected/focused/active. Each finding is a violation — identity belongs to tonal surfaces, headings, glyphs, and spacing; state belongs to ink-alpha washes and glyphs. Keyboard `focus-visible` rings, input validation states, neutral hairlines, table rules, and a blockquote's neutral rule are exempt, and the script already skips them.

A page that scores Lighthouse 100 but uses 14 undeclared hex codes and 8 magic spacing values is **NOT DONE**. The design system is the architecture — Lighthouse measures the performance of that architecture.

### 7. REACT-SPECIFIC PERF TOOLING IS PART OF THE AUDIT.

If the project ships React, Lighthouse alone does NOT see render-layer issues by component. You MUST also run:

- **`react-doctor`** (static): cheapest. `npx react-doctor@latest --json` before any browser audit. Treat perf-category findings as audit failures.
- **`react-scan/lite`** (runtime, headless): injected via `page.addInitScript` in the Playwright run. Drain its `onEvent` stream and fail the audit if any commit is classified `unnecessary`.

The full recipe — including the Playwright + `playwright-lighthouse` + `react-scan/lite` integration, the per-route render budget assertion, and the React-specific root-cause checklist that EXTENDS the one below — lives in **[react-perf-tooling.md](react-perf-tooling.md)**. Read it before any React audit.

Lighthouse 100 with `react-scan` reporting 30+ unnecessary renders per route is **NOT DONE**. Both gates must clear: synthetic score AND render quality. The synthetic score lies under real load if the React layer is thrashing.

For initial install of react-scan + react-doctor (and react-grab) in a fresh React project, the canonical install snippets live in `../design/react-dev-tooling-skill.md`. Use them if the project doesn't yet have the tools wired.

## AUDIT WORKFLOW

Quick audit via the cross-platform Python CLI (macOS, Linux, Windows):

```bash
uv run $SKILL_DIR/scripts/perfection/lighthouse-audit.py https://localhost:3000
uv run $SKILL_DIR/scripts/perfection/lighthouse-audit.py https://localhost:3000 --desktop-only
bun $SKILL_DIR/scripts/perfection/check-draft-guard.ts src/   # exit 1 = accent stripe or outline, promo copy, emoji icon, hype badge, or vanity stat
```

Or use the TypeScript approach directly in your test suite:

```ts
// scripts/audit.ts
import { chromium } from "playwright";
import { playAudit } from "playwright-lighthouse";

const browser = await chromium.launch({ channel: "chrome" });
const context = await browser.newContext();
const page = await context.newPage();
await page.goto("http://localhost:3000/<route>");

await playAudit({
  page,
  port: 9222,
  thresholds: { performance: 100, accessibility: 100, "best-practices": 100, seo: 100 },
  reports: { formats: { html: true, json: true }, name: "lighthouse-<route>" },
  config: { extends: "lighthouse:default", settings: { formFactor: "mobile" } },
});

await browser.close();
```

Run twice per route: once `formFactor: "mobile"`, once `formFactor: "desktop"`. Both must hit 100/100/100/100.

**Diagnose from the JSON report, not the HTML.** Parse `audits[*].score < 1` programmatically to find the offenders. Do not eyeball the HTML report.

**Run 3-5 times and take the median.** A single audit can be noisy. CI must enforce the threshold on every PR.

## ROOT-CAUSE CHECKLIST (HIT THESE FIRST, ALMOST ALWAYS THE CULPRIT)

- **Render-blocking JS/CSS in the critical path.** Defer, code-split by route, inline critical CSS only.
- **Unsized media.** Every `<img>`, `<video>`, `<iframe>` MUST have explicit `width`/`height` or an aspect-ratio container. Unsized media causes CLS.
- **Wrong image format or dimensions.** Serve AVIF first, WebP fallback, JPEG last. Generate ALL responsive sizes in the build. NEVER ship an image larger than the rendered box. Use `fetchpriority="high"` on the LCP image.
- **Fonts.** `font-display: swap` minimum, `optional` for non-critical fonts, preload the one critical font, subset to only the characters actually used.
- **Third-party scripts in `<head>` synchronously.** Defer, lazy-load on first interaction, OR proxy through your own origin to remove a third-party DNS + TLS handshake from the critical path.
- **Hydration on routes that do not need it.** React Server Components, islands, `client:load`, ONLY where the interactivity is real. Static routes ship zero JS.
- **Missing semantic HTML.** `<button>` for buttons, `<a href>` for links, `<nav>` / `<main>` / `<header>` / `<footer>` landmarks, label every form input, alt-text every meaningful image, unique `<title>` per route.
- **Tab order, focus rings, contrast ratios, prefers-reduced-motion, ARIA correctness.** Accessibility 100 means a screen-reader user can drive the page end-to-end without help.
- **Meta tags.** `<title>`, `<meta name="description">`, OpenGraph, Twitter cards, structured data (JSON-LD), `lang` on `<html>`, `viewport`, canonical URL.

## ANTI-PATTERNS. REJECT ON SIGHT.

- Reporting a CLI Lighthouse score. **REJECT.** Tenet 1.
- Removing an animation to fix INP. **REJECT.** Switch to a CSS-only transform/opacity animation. Debounce listeners. Move heavy work off the main thread.
- Replacing a hero image with a placeholder to "fix" LCP. **REJECT.** Properly sized AVIF + `fetchpriority="high"` + preconnect to the image CDN is the actual fix.
- Disabling JS for a route to "score 100". **REJECT.** Score 100 ON the JS-enabled production build, on a real user device profile.
- Setting `display: none` on offscreen content to dodge audits. **REJECT.** Use `content-visibility: auto` plus proper lazy mounting. Never lie about the page.
- Declaring victory after a single audit run. **REJECT.** Run 3-5 times, take the median. CI must enforce the threshold.
- Scoring 100 on `localhost` and shipping without re-measuring against the deployed URL. **REJECT.** The CDN, real DNS, and real TLS handshake matter.

## RESPONSE FORMAT (what to return when the user asks for a frontend audit or build)

1. **Scores before / after**, mobile AND desktop, all four categories.
2. **Design system compliance**: orphan tokens found / fixed, components documented.
3. **Each fix** in one line, traceable to the audit it cleared.
4. **What you intentionally did NOT do**, and why. Especially every tempting "easy point" you rejected to preserve UX.
5. **Browser-based Design QA result**: breakpoints tested, visual bugs found/fixed, states verified.
6. **The next audit you would run** if you had another iteration.

If the run did not hit 100 in every category, you are NOT done. State so explicitly. Continue iterating.

## MANTRA

> **100 on every Lighthouse category, on a real browser, with full features and full animations intact. Or it is not done.**
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall