Borrowing it
Nothing to install: this file belongs to nerds-odd-e/doughnut. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nerds-odd-e/doughnut/main/.agents/skills/frontend/SKILL.mdgit clone --depth 1 https://github.com/nerds-odd-e/doughnutWrote 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/nerds-odd-e/doughnut/frontend)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/frontend"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/frontend/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/frontend"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/frontend.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00038 | $0.01009 |
| Opus 5.5 | $0.00015 | $0.00404 |
| Sonnet 5.5 | $0.00008 | $0.00202 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
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 19d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend
Vue 3 + TypeScript in frontend/src/. Tests in frontend/tests/. Import the backend client from @generated/donut-backend-api/sdk.gen.
Matching frontend-component, frontend-testing, frontend-api, and frontend-storybook skills attach via paths when those files are in context — do not fetch them up front. Lint: linting_formating skill.
Commands
CURSOR_DEV=true nix develop -c pnpm frontend:test
Spec paths are relative to frontend/. Do not pass -- before the path (Vitest skips file filtering). Prefer the full frontend unit suite; a single file only while iterating on that file.
Always run frontend unit tests headlessly. The shared Vitest config keeps Chromium
headless and disables automatic browser opening for regular, direct, UI, and watch
runs. Agents must not override this with --browser.headless=false or --open
unless the user explicitly requests a visible browser.
Frontend proof
frontend:test runs Vitest only; frontend/vitest.config.ts disables
typechecking there for speed. Passing behavioral tests alone is incomplete
frontend proof: before accepting a frontend change, also require these
typechecks to pass against the same working-tree content, including generated
API types:
CURSOR_DEV=true nix develop -c pnpm -C frontend exec vue-tsc --noEmit
CURSOR_DEV=true nix develop -c pnpm -C frontend exec tsc --noEmit
The build that CI runs (pnpm -C frontend build) checks with both. Plain
tsc types every *.vue import through frontend/tests/shims-vue.d.ts, so
it sees no exposed component members: a test reaches an exposed method
through a helper that casts wrapper.vm structurally, never through
wrapper.vm.<method> or InstanceType<typeof Component>.
Reuse existing typecheck evidence from a lint or build run on
identical content instead of repeating it. This requirement applies at proof
acceptance, not to every focused Vitest run while iterating on one file.
Components
<script setup lang="ts">. PascalCase.vuefiles; testsComponentName.spec.ts.- DaisyUI uses the
daisy-prefix (daisy-btn,daisy-card). Unprefixed Tailwind utilities. No Bootstrap. Scoped SCSS. Lucide via@lucide/vue(currentColor,:sizeor Tailwindsize-*). - Derived state:
computed, not arefthat mirrors props/store.refonly for owned mutable state (input, toggles). - Modals:
Modalfrom@/components/commons/Modal.vue. In tests, querydocument.querySelector("dialog"). - Tracked
frontend/components.d.tsis regenerated by the Vite build, not by tests. After adding or deleting a component, runCURSOR_DEV=true nix develop -c pnpm -C frontend exec vite build --emptyOutDirand commit its change. - Routing: name and params (helpers such as
noteShowLocation); href only vianoteShowHref(compiled from the named location). ADR 0005.
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.
- 19d ago Changed · +7 lines 3e9c761ec847
- 1mo ago Changed · +6 lines 089d92698899
- 1mo ago Changed 678b748279d1
- 1mo ago Changed · +16 lines 0b63a1441605
- 1mo ago First seen · 40 lines · 38 tokens per session scan A 57c9a4ee7ede
frontend is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,009 once invoked, about $0.0002 per session on Opus 5.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-09-17.
Other skills, from other repositories
shadcn-svelte
Pre-built shadcn-svelte components for json-render Svelte apps. Use when working with @json-render/shadcn-svelte, adding standard UI components to a Svelte catalog, or building Svelte web UIs with shadcn-svelte + Tailwind CSS components.
add-localization
Adds or extends multilingual localization in a Power Pages code-site SPA. Use whenever the user asks to translate, localize, internationalize, support multiple languages, add a language selector, add locale routes, repair an i18n setup, or add languages to an existing React, Vue, Angular, or Astro Power Pages site.
vue-router-best-practices
Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
moai-domain-frontend
Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.
frontend-conventions
Frontend convention reference (SvelteKit / Svelte 5). Auto-injected into frontend-aware agents - not user-invocable.