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 skills add dyeoman2/tanstack-start-template --skill designgit clone --depth 1 https://github.com/dyeoman2/tanstack-start-templateWrote 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/dyeoman2/tanstack-start-template/design)<a href="https://agentmods.dev/skills/dyeoman2/tanstack-start-template/design"><img src="https://agentmods.dev/badge/skills/dyeoman2/tanstack-start-template/design/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/dyeoman2/tanstack-start-template/design"><img src="https://agentmods.dev/badge/skills/dyeoman2/tanstack-start-template/design.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.00088 | $0.00953 |
| Opus 5.5 | $0.00035 | $0.00381 |
| Sonnet 5.5 | $0.00018 | $0.00191 |
| Haiku 4.5 | $0.00009 | $0.00095 |
Grade A, and why
design 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design
Use this skill to turn vague frontend requests into repo-compatible design decisions. Apply the article's emphasis on clear art direction, explicit constraints, strong hierarchy, and browser verification without replacing the repo's existing routing, token, shadcn, or copy patterns.
Workflow
- Read references/repo-ui-patterns.md before changing page-level layout, tokens, or visual tone.
- Classify the surface before coding:
- marketing or auth
- authenticated app, admin, or operational workspace
- Write a compact internal brief with:
- visual thesis
- content plan
- interaction thesis
- hard constraints
- Keep the first viewport organized around one clear composition. Do not default to a generic grid of disconnected cards unless the surface is truly data-dense.
- Implement with existing route, feature, and UI primitive boundaries.
- Verify in the browser and refine spacing, hierarchy, responsive behavior, and states after the first pass.
Surface Rules
Marketing and Auth
- Allow more visual expressiveness than the app shell.
- Prefer one strong composition above the fold: headline, supporting proof, and one primary action.
- Use real product copy, not design commentary.
- Add imagery only when it clarifies the offer. Decorative texture alone is not a visual anchor.
- Preserve the repo's existing public-route pattern when creating or reshaping top-level marketing pages.
App, Admin, and Operations
- Default to utility copy over marketing copy.
- Start with the working surface itself: KPIs, filters, tables, status, tasks, or current context.
- Do not add a hero section unless the user explicitly asks for one.
- Give each section one job: orient, explain status, show data, or enable action.
- Keep motion sparse and purposeful. Orientation and clarity come before flourish.
Repo Guardrails
- Preserve the existing shadcn and Tailwind variable approach. Extend the system before inventing a new one.
- Prefer composing from
~/components/ui/*before creating new primitives. - Reuse
cn()and existing variant patterns for class composition. - Keep global token work in
src/styles/app.css. Prefer adjusting CSS variables or section-level styling over hard-coded one-off palettes. - Avoid global font swaps, dramatic visual rebrands, or wholesale restyling unless the user explicitly asks for them.
- Preserve TanStack Start route boundaries, pending states, and error boundaries.
- Keep UI components pure. Put business logic in hooks, Convex hooks, or server modules.
- Use
~/aliases and static imports.
What ships with it
2 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.
- 1mo ago First seen · 82 lines · 88 tokens per session scan A 536289a026f7
design is a skill published in the GitHub repository dyeoman2/tanstack-start-template (26 stars, last pushed 5mo ago), licensed MIT. It adds 88 tokens to every session and 953 once invoked, about $0.0004 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-01.
Other skills, from other repositories
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
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…
antigravity-design-expert
Core UI/UX engineering skill for building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS.
tamagui-v6-config
Tamagui v6 theme system: the light/dark/accent/brand/inverse/level/active theme family, the background-active one-off key, and recipe-tree authoring with createV6Config. Use when choosing a theme for a surface, building a selected/emphasis state, or authoring a custom v6 colors pack.
tamagui-theme-generator
Generate custom Tamagui themes, color palettes, and preview URLs. Use when creating or refining a color scheme, authoring light/dark palettes with brand accents, or previewing generated themes in the browser.
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.