Neko Master is a dashboard that collects and visualizes network traffic from local gateway environments. It is for monitoring, auditing, and analyzing traffic across multiple gateways, with the catalogue entries providing instructions and skills for working with the dashboard.
Borrowing it
Nothing to install: this file belongs to foru17/neko-master. 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/foru17/neko-master/main/.claude/skills/ui-conventions/SKILL.mdgit clone --depth 1 https://github.com/foru17/neko-masterWrote 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/foru17/neko-master/ui-conventions)<a href="https://agentmods.dev/skills/foru17/neko-master/ui-conventions"><img src="https://agentmods.dev/badge/skills/foru17/neko-master/ui-conventions.svg" alt="Measured on agentmods" 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.00048 | $0.00798 |
| Opus 5 | $0.00024 | $0.00399 |
| Sonnet 5 | $0.00010 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
ui-conventions 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 8d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
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.
- 8d ago First seen · 45 lines · 48 tokens per session scan A 2fbab5f3d56f
ui-conventions is a skill published in the GitHub repository foru17/neko-master (3,924 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 798 once invoked, about $0.0002 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-30.
Other skills, from other repositories
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
experience-lwc-rtl-validate
Use this skill to review a Lightning Web Component (.html, .js, .css files) for right-to-left (RTL) internationalization correctness, producing a finding list with code-level fixes covering CSS logical properties, bidirectional text handling, keyboard semantics, and RTL-aware SLDS class usage. TRIGGER when the user…
rtl-internationalization
Right-to-left (RTL) layout and bidirectional text support for Hebrew, Arabic, Persian, and Urdu interfaces. Use when building UI that must support RTL languages, converting physical CSS/Tailwind properties to logical ones, handling mixed-direction (bidi) text, mirroring directional icons, or testing an app with…
styling
PyWry provides CSS variables that adapt to dark/light themes. Use these instead of hardcoded colors!
css_selectors
The most reliable way to target elements is by componentid.
hebrew-rtl-best-practices
Implement right-to-left (RTL) layouts for Hebrew web applications. Use when user asks about RTL layout, Hebrew text direction, bidirectional (bidi) text, Hebrew CSS, "right to left", or needs to build a Hebrew web UI. Covers CSS logical properties, the :dir() pseudo-class, Tailwind RTL, React/Next.js RTL setup, icon…