frontend-design-system
Skill1 starsChanged 7 months agoMITView on GitHub
Dashboard conventions — single static HTML file, vanilla DOM APIs, strict XSS hygiene
9 other projects use a version of this.
Adopted by
Most recently taken up by
- polyant-ai/polyanttheir own version, first seen Nov 3, 2026
- AntonioMellies/claude-code-skillstheir own version, first seen Nov 1, 2026
- hushh-labs/hushh-researchtheir own version, first seen Nov 1, 2026
- ChainChase/agent-toolboxtheir own version, first seen Oct 15, 2026
- gongyijie85/dsh-ecctheir own version, first seen Oct 13, 2026
- wangge-ai/wangge-skillstheir own version, first seen Oct 8, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- oikon48/cc-frontend-skills★ 69same name
- hushh-labs/hushh-research★ 40same name
- polyant-ai/polyant★ 10same name
- gongyijie85/dsh-ecc★ 8same name
- mnzralee/claude-multi-agent-architecture★ 8same name
- sefaertunc/Worclaude★ 4same name
- wangge-ai/wangge-skills★ 4same name
- AntonioMellies/claude-code-skills★ 2same name
- ChainChase/agent-toolbox★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-routingSkill
- backend-conventionsSkill
- claude-md-maintenanceSkill
- coding-principlesSkill
- context-managementSkill
- coordinator-modeSkill
- git-conventionsSkill
- memory-architectureSkill
- planning-with-filesSkill
- project-patternsSkill
- prompt-engineeringSkill
- review-and-handoffSkill
- security-checklistSkill
- subagent-usageSkill
- testingSkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
URLs must be validated before use: Use the safeUrl() helper (rejects anything that isn't http:// or https://) before setting href on any …
- Very specific: line 31
If a feature needs per-source items, fetch feeds/{source-key}.json separately.
- Distinctive: line 39
Keep styles surgical: don't restyle unrelated sections when editing.
- Distinctive: line 43
No explicit WCAG level targeted — it's a developer tool.
- Very specific: line 53
Run the pipeline locally (npm start) to populate public/feeds/.
- Distinctive: line 58
If browser tests ever become necessary, introducing them is a separate project decision — don't add a test framework as part of an …
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Frontend Design System — anthropic-watch
The "frontend" is one file: public/index.html. It is a static dashboard that fetches run-report.json and all.json from GitHub Pages and renders them with vanilla DOM APIs.
There is no framework (no React/Vue/Svelte), no build step (no bundler, no transpiler, no PostCSS), and no component library. These are intentional choices — the dashboard must be viewable by cloning the repo and opening the file, and deployable by copying the file to Pages.
Rendering Rules
- Never use
innerHTMLfor anything that includes data. Build the DOM withdocument.createElement(...)and assign text viatextContent. The v1.0.1 release replaced allinnerHTMLstring templates specifically because they allowedjavascript:URL XSS throughitem.url. - URLs must be validated before use. Use the
safeUrl()helper (rejects anything that isn'thttp://orhttps://) before settinghrefon any element. This applies toitem.url,sourceNamelinks, anything that comes from the feed. - External item links use
rel="noopener noreferrer"andtarget="_blank". textContentoverinnerTextfor consistency and performance.- Dates: format with
toLocaleString()or equivalent at render time; never trust pre-formatted date strings from the feed (they are ISO 8601, not display-ready). - Null handling:
item.datemay benull; render a sensible placeholder (blank or dash), never "null" or "undefined".
Data Sources
The dashboard fetches two files from the same origin (GitHub Pages):
feeds/run-report.json— for source status, health, timingfeeds/all.json— for the recent-items list
If a feature needs per-source items, fetch feeds/{source-key}.json separately. Never combine: the schemas are intentionally distinct (see docs/FEED-SCHEMA.md).
Handle fetch failures gracefully — GitHub Pages can have brief outages. Showing a stale-but-cached view is better than a blank page.
Styling
Inline <style> block at the top of public/index.html. No external stylesheets, no Tailwind, no CSS frameworks. Design tokens (colors, spacing) are defined as CSS custom properties in :root if present, or inlined where used.
Keep styles surgical: don't restyle unrelated sections when editing. The dashboard is utilitarian by design — dense info, no animations, no marketing polish.
Accessibility
No explicit WCAG level targeted — it's a developer tool. Keep basics sane:
- Semantic HTML (
<table>for tabular data,<button>for actions,<a>for links) - Visible focus states
- Color contrast sufficient for status dots (green/amber/red must be distinguishable by more than color alone — use shape, label, or hatching)
Testing
No automated browser tests. Verification is manual:
- Run the pipeline locally (
npm start) to populatepublic/feeds/. - Open
public/index.htmlin a browser. - Visually confirm the changed surface renders correctly.
- For security-sensitive edits (anything touching URL handling, DOM rendering, or user-controlled content), add an explicit note to the PR describing what was checked.
If browser tests ever become necessary, introducing them is a separate project decision — don't add a test framework as part of an unrelated change.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

