Borrowing it
Nothing to install: this file belongs to sparq-org/sparq. 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/sparq-org/sparq/main/.claude/skills/frontend-design/SKILL.mdgit clone --depth 1 https://github.com/sparq-org/sparqWrote 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/sparq-org/sparq/frontend-design)<a href="https://agentmods.dev/skills/sparq-org/sparq/frontend-design"><img src="https://agentmods.dev/badge/skills/sparq-org/sparq/frontend-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/sparq-org/sparq/frontend-design"><img src="https://agentmods.dev/badge/skills/sparq-org/sparq/frontend-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.00185 | $0.04911 |
| Opus 5 | $0.00093 | $0.02455 |
| Sonnet 5 | $0.00037 | $0.00982 |
| Haiku 4.5 | $0.00018 | $0.00491 |
Grade A, and why
frontend-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 10d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend design (sparq)
sparq ships two frontends that are deliberately different products, not two skins of one app. Conflating them is the single biggest design failure to avoid — and the one the maintainer flagged: "the website has too much text; it is overwhelming." The fix is not "trim words"; it is to keep each frontend doing only its own job.
Website (site/) |
GUI (gui/) |
|
|---|---|---|
| Audience | the RDF/SPARQL-curious dev evaluating "is this real, should I care?" | the dev who already decided and wants to do work |
| Job | persuade + route + prove with a few live demos; link out for depth | operate the engine as a real tool over persistent local data |
| Stack | Next.js output: "export", React 19, Tailwind v4, radix/shadcn; GitHub Pages |
Tauri 2 webview + direct native-Rust engine link; desktop bundle |
| Shape | a small set of pages you read top-to-bottom | a workbench shell: rails + tabs + command palette, no marketing pages |
| Content | marketing-docs: one-liner → demo → link to repo/SKILL.md/papers | operational: import → query → inspect → operate surfaces as tools |
| Depth lives | crates/*/README.md, skills/*/SKILL.md, research/, /papers |
the engine itself + a Help → opens the website in the system browser |
Litmus test for any new frontend work: "Does this help someone DECIDE (website) or DO (GUI)?" If a change makes the website more of a workbench, or the GUI more of a brochure, it is going the wrong way. The GUI must never just wrap the marketing site (today
gui/is asrc-tauriscaffold whosefrontendDistpoints atsite/out— that is a placeholder, not the design).
Design records (read these for the full spec — this skill is the reusable method):
research/website-redesign.md and research/gui-design.md.
1. Information architecture + content reduction (fight "too much text")
The overwhelm is structural, not verbal. Audited, the same ~16 surfaces appear in up
to three places at once (site/src/components/layout/app-shell.tsx): a persistent
w-64 sidebar rendering the full 6-group/16-surface tree (sidebar-nav.tsx) and a
top-tab bar (Showcase/Benchmarks/About) and the landing page re-renders all surfaces as
cards. Cutting prose does not fix a tripled nav. Cut structure first.
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.
- 10d ago First seen · 288 lines · 185 tokens per session scan A d6099f7d62fc
frontend-design is a skill published in the GitHub repository sparq-org/sparq (12 stars, last pushed today), licensed MIT. It adds 185 tokens to every session and 4,911 once invoked, about $0.0009 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-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.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…