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 6529-Collections/6529seize-frontend --skill design-ui-uxgit clone --depth 1 https://github.com/6529-Collections/6529seize-frontendWrote 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/6529-collections/6529seize-frontend/design-ui-ux)<a href="https://agentmods.dev/skills/6529-collections/6529seize-frontend/design-ui-ux"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/design-ui-ux/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/6529-collections/6529seize-frontend/design-ui-ux"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/design-ui-ux.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.00896 |
| Opus 5 | $0.00041 | $0.00448 |
| Sonnet 5 | $0.00016 | $0.00179 |
| Haiku 4.5 | $0.00008 | $0.00090 |
Grade A, and why
design-ui-ux 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 11d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design UI/UX
Use this skill for user-facing design and UX work in this repository.
Workflow
- Read
ops/standards/frontend-design-ui-ux.md. - Inspect the nearest existing route, component, style module, and shared primitive before proposing or changing UI.
- Classify the touched surface as modern Tailwind, legacy CSS (plain-CSS modules or global CSS), or mixed. Treat legacy styling as compatibility evidence, not automatically as the target for new UI.
- Prefer prefixed Tailwind utilities,
tailwind-scope,tailwind.config.tstokens, and shared Tailwind-based components for new or migrated UI. Use existing CSS-module patterns only when maintaining a legacy surface or when a narrow exception is justified. Bootstrap, React Bootstrap, and Sass are removed from this repo and must not be reintroduced. - Check shape, color, and surface-token choices against the standard, especially the product radius hierarchy and local Tailwind token usage.
- Keep the change scoped to the touched surface. Reuse the existing visual language, icon set, spacing scale, palette, and nearby component patterns unless the user request clearly calls for a new pattern.
- Verify desktop and mobile rendering for visible UI changes. Check overflow, clipping, readable text, focus, hover/touch alternatives, media behavior, and loading/empty/error/disabled states that the change can affect.
- Use screenshot or pixel sanity evidence when the visual result matters. Do not rely only on DOM presence when a route can render blank or unreadable.
- In PR notes or closeout, summarize the UI pattern reused, migration judgment, evidence collected, unchecked states, and any documented exceptions.
Review Checklist
- The UI fits the local 6529 surface and does not read like a new product style.
- The result feels sleek, current, polished, and premium without becoming decorative or over-produced.
- The surface is content-led and native to 6529: art, media, identity, waves, profiles, badges, activity, and collector context create the richness.
- Social and art surfaces do not collapse into generic dashboard, admin, or template UI.
- New or migrated UI uses
tw-Tailwind classes and modern tokens unless the touched surface is intentionally still legacy. - Dark-first surfaces,
iron-*greys, typography, and compact spacing match current Tailwind patterns before older legacy-CSS patterns. - Cards, dialogs, controls, and framed surfaces use the product radius hierarchy:
tw-rounded-xlfor larger framed surfaces,tw-rounded-lgfor standard controls and rows,tw-rounded-mdonly for compact details, andtw-rounded-fullfor circular/pill UI. - Color choices use Tailwind tokens or established local custom colors tied to product meaning, media/art treatment, brand color, chart/domain state, or legacy compatibility.
- Product content remains primary, especially NFT/media/art imagery, avatars, wave names, badges, scores, and timestamps.
- Long text, translated text, counters, and labels do not overlap or clip on tested mobile and desktop widths.
- Loading, empty, error, disabled, selected, focus, hover, and touch states are designed or explicitly unaffected.
- Browser evidence includes both DOM/layout checks and visual confirmation when the rendered surface is part of the change.
What ships with it
1 file 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.
- 11d ago First seen · 78 lines · 82 tokens per session scan A bd84f32f1b1b
design-ui-ux is a skill published in the GitHub repository 6529-Collections/6529seize-frontend (10 stars, last pushed today), licensed Apache-2.0. It adds 82 tokens to every session and 896 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-31.
Other skills, from other repositories
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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
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.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
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
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.