Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/tienenwu/fables/frontend-webnpx skills add tienenwu/fables --skill frontend-webgit clone --depth 1 https://github.com/tienenwu/fablesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tienenwu/fables/frontend-web)<a href="https://agentmods.dev/skills/tienenwu/fables/frontend-web"><img src="https://agentmods.dev/badge/skills/tienenwu/fables/frontend-web.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00095 | $0.01379 |
| Opus 5 | $0.00048 | $0.00690 |
| Sonnet 5 | $0.00019 | $0.00276 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
frontend-web-playbook scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🌐 繁體中文（canonical） · English mirror
React / Next.js Frontend Judgment Handbook
Core Principles
- A green dev server proves nothing: hydration, env-var injection, bundle size, SEO metadata, and minification only show their true behavior under
next build && next start— any change on the production path must be verified with a production build. - Remote data and UI state are two different things: server state (from an API/DB — it goes stale, needs caching, needs refetching) belongs to React Query/SWR; client state (pure view toggles, input fields) uses useState/zustand. Mixing the two is the root of most "data out of sync" bugs.
- Put state at the lowest layer that uses it: default to local, lift only when it hurts, go global last. Reaching for a global store too early is entropy, not architecture.
- A re-render is a symptom, not the disease: first use the Profiler to measure which component re-renders and why, then decide whether to memo; scattering useMemo/useCallback on gut feel is just noise.
- Anything that enters the client bundle is visible to the user:
NEXT_PUBLIC_-prefixed variables, strings hardcoded into components, whole libraries imported into a Client Component — assume it is public first, then prove it deserves to be public.
Task Triage
| Situation | Path | Read first |
|---|---|---|
| New screen/feature | First decide where data comes from, who owns state, what needs "use client", then write the UI | references/architecture-state.md |
| Write/change a component, extract a component, styling | First settle the semantic boundary and props contract, then act | references/components-styling.md |
| Janky screen, too many re-renders, oversized bundle | Do not scatter memo first — measure first | references/rendering-performance.md |
| Fetch remote data, caching, loading/error states | Separate server state from client state | references/architecture-state.md §1 |
| Ship to production / deploy / diagnose "fine in dev, blows up in prod" | Run the mandatory checklist line by line | references/release-checklist.md |
| hydration mismatch, env vars, SEO | Assume a build-time difference first, do not thrash | references/release-checklist.md |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 56 lines · 95 tokens per session scan A ffd76224851d
frontend-web-playbook is a skill published in the GitHub repository tienenwu/fables (4 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 1,379 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
uniwind
Uniwind — Tailwind CSS v4 styling for React Native. Use when adding, building, or debugging components in a React Native project that uses Uniwind classNames. Covers setup, Metro config, global.css, theming, className props, accent- color props, platform/data/state/responsive variants, CSS variables, custom utilities…
cometchat-theming
Customize CometChat UI to match the user's app design system. Covers the CSS variable cascade, preset themes, brand color overrides, design system extraction, dark mode, and framework-specific override locations.
framework-shadcn-tailwind-ui
Use with beautiful-ui and platform-web-ui when the target web app uses shadcn/ui components, Tailwind CSS utilities, or a React component system built from copied component source.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
ui-checkstyle
Run the exact ESLint + Prettier + organize-imports sequence that CI's UI Checkstyle workflow runs — on just the files the PR changed — and fail the task if any file ends up with a diff. Invoke after authoring or modifying any .ts, .tsx, .js, .jsx, or .json file under openmetadata-ui/src/main/resources/ui/src/…
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.