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-component/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-component)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/frontend-component"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/frontend-component/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-component"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/frontend-component.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.00041 | $0.00947 |
| Opus 5.5 | $0.00016 | $0.00379 |
| Sonnet 5.5 | $0.00008 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
frontend-component 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 1mo 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Component Rules
File Organization
- Frontend code lives in
frontend/src/. - Test code lives in
frontend/tests/. - Generated backend API code is in
frontend/src/generated/backend.
Core Technologies
- Vue 3 with TypeScript.
- DaisyUI + Tailwind for styling: unprefixed Tailwind utilities (
flex,text-primary, …) anddaisy--prefixed DaisyUI component classes (daisy-btn,daisy-card, …). - Vitest for testing with Playwright browser mode.
- Biome for linting and formatting.
Icons
- Prefer Lucide for normal UI icons via
@lucide/vue(import { IconName } from "@lucide/vue"). Import only the icons each file needs; rely oncurrentColorso icons follow text/theme color. @lucide/vuedefaults to 24x24 via thesizeprop. Use:size="..."and/or Tailwindw-*,h-*, orsize-*on icons.
Naming Conventions
- Component files should use PascalCase, for example
NoteShow.vueorGlobalBar.vue. - Test files should match component names with a
.spec.tssuffix. - Use
.vuefor components and.tsfor TypeScript files.
Component Structure
<script setup lang="ts">
import { computed, onMounted, ref } from "vue"
const props = defineProps<{
value: string
}>()
const emit = defineEmits<{
(e: "update:value", value: string): void
}>()
const loading = ref(false)
const displayValue = computed(() => props.value.toUpperCase())
const handleClick = () => {
emit("update:value", "new value")
}
onMounted(() => {
// ...
})
</script>
<template>
<div class="daisy-component">
<!-- template content -->
</div>
</template>
<style scoped lang="scss">
// scoped styles
</style>
Modals And Dialogs
- Use
Modalfrom@/components/commons/Modal.vuefor modal overlays. It wraps a native<dialog>teleported tobodyand centralizes stacking, ESC, backdrop click, and route-change close. The dim background is the native::backdroppseudo-element. - Put panel content in
#body, optionally#header. Listen for@close_requestto hide the modal, such as parentv-ifor clearing model state. The overlay X is optional viashowCloseButtononModal. - Use
v-ifonModalwhen the dialog opens, or keepModalmounted and drive visibility from props; wireclose_requestand cancel buttons to the same close handler. - Layout variants:
alignToppins the panel to the top of the viewport,sidebar="left" | "right"renders a full-height side panel. UseisPopupfor nested popups viausePopupsso they do not participate in the ESC modal stack. - In tests, the dialog renders inside
document.body. Query the DOM viadocument.querySelector("dialog"),.close-button,.modal-container,.modal-sidebar, or.modal-mask, not the dialog's internal layout wrapper.
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.
- 1mo ago First seen · 92 lines · 41 tokens per session scan A ac15315a9ca9
frontend-component is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 947 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.
shadcn-svelte
Manages shadcn-svelte components and projects — adding, updating, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn-svelte, the CLI, design-system presets, or any project with a components.json file. Also triggers for…
nuxt-ui
Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.
league-akari-ui-components
Use when implementing or reviewing League Akari renderer UI components, especially consistency across related components, i18n component interpolation, multiple independent pluralized counts, Tailwind utility usage in templates or SFC style blocks, or native semantic HTML elements in the Naive UI renderer.
vue-base-skill
A parent guide for building Vue interface components with shared rules for cards, buttons, labels, and tables. It requires these components to sit inside a base card and use shared CSS design values.
frontend-upgrade-ops
Upgrade a server-rendered Craft CMS/Twig front end: Laravel Mix or Webpack to Vite via craft-vite (manifest, DDEV dev server, HMR, Tailwind v3, legacy builds, Twig asset URLs) and Vue 2 to Vue 3 (@vue/compat, Vuex to Pinia, plugin swaps, Vue islands in Twig). Use when a site still has webpack.mix.js, mix-manifest.json…