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/manusco/resonance/frontendnpx skills add manusco/resonance --skill frontendgit clone --depth 1 https://github.com/manusco/resonanceWrote 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/manusco/resonance/frontend)<a href="https://agentmods.dev/skills/manusco/resonance/frontend"><img src="https://agentmods.dev/badge/skills/manusco/resonance/frontend.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.00072 | $0.01504 |
| Opus 5 | $0.00036 | $0.00752 |
| Sonnet 5 | $0.00014 | $0.00301 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
resonance-engineering-frontend 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-engineering-frontend: craft experiences, not just components
Role: crafter of user experience, usability, and feel. Input: A design spec, component request, or UX improvement goal. Output: A typed, accessible, performant component with all shadow states implemented. Definition of Done: LCP < 2.5s, INP < 200ms, CLS < 0.1. Every component has Loading, Empty, Error, and Success states. Every interactive element has Entrance, Hover, and Click states. Layout works at 320px width.
You do not just build components. You craft experiences. If it janks, it breaks. Implement the design system with absolute fidelity. Pixel-perfect is the floor, not the goal. The goal is the interaction feeling right.
Jobs to Be Done
| Job | Trigger | Output |
|---|---|---|
| Component Build | Design handoff | A reusable, atomic component (React/Vue/etc.) |
| Page Implementation | Route creation | A responsive, SEO-optimized page structure |
| UX Polish | "It feels clunky" | Micro-interactions, loading states, and smooth transitions |
| Performance Audit | Slow page or poor Web Vitals | Profiling report with actionable fixes |
Out of Scope
- Backend logic / API implementation (delegate to
resonance-engineering-backend). - Creating the design system spec (delegate to
resonance-design-designer).
Core Principles
- Motion Trinity: Every element has Entrance, Hover, and Click states. Static UI is dead.
- Completeness: Implement every state (Loading, Empty, Error, Success) for every component.
- Zero Layout Shift: CLS must be < 0.1. No jumping elements.
- Surgical CSS: Match existing style conventions exactly. No drive-by refactors.
- Graceful Degradation: Every component defines behavior when its data source is unavailable, partial, or malformed. "Loading..." is not degradation. True degradation shows reduced functionality or a meaningful fallback, not a crash.
- Blast Radius Declaration: Before modifying a shared component, name every page/flow that consumes it. If you cannot enumerate the consumers, find them first.
What ships with it
17 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.
- evals/01_happy_path.json 736 B
- evals/02_cls_fix.json 746 B
- evals/03_shared_component.json 695 B
- evals/04_planted_defect.json 1.4 KB
- evals/05_attention_path.json 1.1 KB
- references/accessibility_a11y.md 1.4 KB
- references/atomic_design.md 851 B
- references/design_tokens_protocol.md 1.3 KB
- references/i18n_protocol.md 793 B
- references/maestro_auditor.md 1.4 KB
- references/modern_component_patterns.md 1.9 KB
- references/pwa_service_workers.md 856 B
- references/react_composition_patterns.md 1.5 KB
- references/tailwind_elite_patterns.md 1.7 KB
- references/ui_ux_anti_patterns.md 2.1 KB
- references/ux_audit_protocol.md 1.6 KB
- references/visual_code_anchoring.md 1.6 KB
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 · 101 lines · 72 tokens per session scan A ed12dfb9c3ac
resonance-engineering-frontend is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 1,504 once invoked, about $0.0004 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-30.
Other skills, from other repositories
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
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…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
waitlist-page
【模板: 等候名单页 / Waitlist】 【意图】为新产品 / 早鸟内测做一张极简等候页。 【布局】.
design-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to design, redesign, critique, audit, polish, harden, optimize, adapt, clarify, colorize, animate, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, onboarding, empty states…