ui-conventions
Skill4.2k starsChanged 37 days agoMITView on GitHub
Frontend change conventions for apps/web — i18n (bilingual keys), dark mode (the highest-frequency rework source), theming inline SVG/chart colors, loading/empty/error states. Use for any UI change.
5 other projects use a version of this.
Trending
Quiet since August.thin dataabout the whole repository
Most recently taken up by
- ericwood8/skillstheir own version, first seen Nov 1, 2026
- willdady/platypustheir own version, first seen Oct 13, 2026
- Autonoma-AI/autonomatheir own version, first seen Oct 9, 2026
- foru17/clash-masterword for word, first seen Oct 8, 2026
- beydemirfurkan/todoxtheir own version, first seen Sep 19, 2026
Who's talking about foru17/neko-master
- @camilleroux.com“Neko Master : un dashboard self-hosted pour visualiser et auditer le trafic réseau en temps réel, avec …”Bluesky · Aug 3, 2026 · 4 likes
- @github-trending-js.bsky.social“🚀 Skyrocketing! 🚀 (200+ new stars) 📦 foru17 / neko-master ⭐ 3,679 (+231) 🗒 TypeScript A modern and …”Bluesky · Aug 21, 2026 · 1 likes
- @chrisshort.net“foru17/neko-master: A modern and elegant dashboard for network traffic visualization and analysis. …”Bluesky · Jul 24, 2026 · 1 likes
- @github-trending-js.bsky.social“🔥 Hot Repo! 🔥 (100+ new stars) 📦 foru17 / neko-master ⭐ 2,741 (+186) 🗒 TypeScript A modern and elegant …”Bluesky · Jul 17, 2026 · 1 likes
- ruanyf/weekly“【开源自荐】Neko Master:现代化网络流量分析面板”GitHub · Feb 11, 2026
The biggest 5 of 5 mentions linking to the repository that our crawl found. Each line is their own headline.
Other versions5 projects use a version of this.
Word for word · 1
- foru17/clash-master★ 4.2k100% same
Edited · 0
None found.
Wrote their own version · 4
- Autonoma-AI/autonoma★ 242same name
- willdady/platypus★ 130same name
- beydemirfurkan/todox★ 2same name
- ericwood8/skills★ 1same 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- add-stats-dimensionSkill
- agent-probe-devSkill
- db-conventionsSkill
- releaseSkill
- verify-changesSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Never a lone light class: Every bg-*-50/100, text-*-500/600, border-*-200 needs a dark: counterpart.
“Common” is measured: kept by at least 6 in 10 of the 4 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
UI Conventions (apps/web)
i18n — every user-facing string, both locales
- Framework:
next-intl, localeszh(default) anden. Message files:apps/web/messages/{zh,en}.json— a key added to one file MUST be added to the other in the same commit. - Components use
useTranslations('namespace'). Never hardcode user-facing strings — including chart tooltips,titleattributes, and aria-labels (historically the most-missed spots). - Utility functions that produce display text (
formatDurationstyle) must not embed English words; return structured data and translate in the component.
Dark mode — check on every visual change
This is the project's highest-frequency rework source. Rules:
- Never a lone light class. Every
bg-*-50/100,text-*-500/600,border-*-200needs adark:counterpart. Grep your diff forbg-white|bg-.*-50|text-gray-before committing. - Prefer theme tokens over palette classes where one exists:
bg-background,bg-popover,text-muted-foreground,border-border(defined inapp/globals.cssfor both themes). - Inline SVG / chart colors can't use Tailwind — define both palettes and switch on
resolvedTheme:
const { resolvedTheme } = useTheme(); // next-themes
const palette = resolvedTheme === "dark" ? DARK_COLORS : LIGHT_COLORS;Precedents: components/features/countries/world-traffic-map.tsx (MAP_THEME), components/features/rules/rule-chain-flow.tsx. Recharts axis ticks should use fill: "currentColor" or CSS variables, not hex grays.
- Badge/status color sets: copy an existing complete set (e.g. the health badge classes in
app/[locale]/dashboard/components/header/index.tsx) rather than writing light-only classes.
Three states, always
Every data view needs loading (skeleton), empty, and error states. Error must be visible and actionable (retry button) — return null on error is a known anti-pattern here (see the chain-flow retry card in rule-chain-flow.tsx for the reference implementation). Route-level failures are caught by app/[locale]/error.tsx / app/global-error.tsx; heavy visualizations should still fail locally, not blank the page.
Data layer
- Server state via React Query; query keys are centralized in
lib/stats-query-keys.ts— never inline ad-hoc keys. - The stats WebSocket (
lib/websocket.ts) tags pushes withbackendIdand the hook drops mismatched messages — preserve this when touching the message path (prevents cross-backend cache bleed on backend switch). - Custom
memocomparators must compare every prop the component renders from (a missed prop froze the Active Policy whitelist once — include new props in the comparator when you add them).
Components
- shadcn/ui (
new-york) + Tailwind v4 + lucide-react. Base primitives incomponents/ui/— reuse before creating; use the RadixDialogfor modals (no hand-rolled fixed overlays — they lose Esc/focus-trap behavior). - Aesthetic bar: modern SaaS quality; avoid flat "admin panel" layouts. Search and other high-frequency entries should be prominent (icon inside input, clear affordances).
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.

