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 n-n-code/n-n-code-skills --skill ui-guidancegit clone --depth 1 https://github.com/n-n-code/n-n-code-skillsWrote 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/n-n-code/n-n-code-skills/ui-guidance)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/ui-guidance"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/ui-guidance/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/n-n-code/n-n-code-skills/ui-guidance"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/ui-guidance.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.00054 | $0.00868 |
| Opus 5.5 | $0.00022 | $0.00347 |
| Sonnet 5.5 | $0.00011 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
ui-guidance 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 1mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/Frontend Guidance
This is a composable overlay, not a standalone workflow.
Use alongside the matching principle skill (for example,
coding-guidance-cpp) when the change touches UI or frontend code. Add
project-core-dev only when repository-specific completion checks still need
to be discovered or reported.
Choose the activity before applying the rules below:
- for implementation, make only the requested UI changes and validate them
- for review, inspect and report prioritized findings with evidence; do not edit files or require findings to be fixed unless the user also asks for remediation
Use this as the thin default overlay for ordinary UI work.
If the task is redesign-heavy, frontend-polish heavy, or needs a stronger UX
review checklist, prefer ui-design-guidance.
Routing examples:
- add a small control that matches nearby components -> use this skill
- fix spacing, labels, or responsive behavior within the existing visual language -> use this skill
- redesign a page, introduce a new visual direction, or perform a UX-heavy
release review -> use
ui-design-guidance - product-security or permission-sensitive UI flows -> use
securityfirst when the main risk is trust, identity, or authorization rather than presentation; addsecurity-identity-accesswhen the security scope centers on identity, sessions, recovery, or tenant authorization
When to use
The repo includes graphical UI or web frontend code — web views, desktop UI, embedded panels, or rendering layers.
Not for
Terminal UIs belong to their framework's guidance, including
coding-guidance-go-tui for Bubble Tea. Pure data visualization or plotting
without product-interface work is also out of scope.
Rules
- Preserve the existing design language unless the task explicitly calls for redesign. Do not introduce new color palettes, spacing systems, or component patterns without justification.
- Accessibility, layout stability, and responsive behavior are part of done — not follow-up work.
- UI changes must not bypass the repo's test and build hygiene.
- Verify visual output manually or with snapshot tests if the repo supports them.
- If the repo does not document breakpoints, design tokens, or visual test tooling, derive them from nearby UI code and record the fallback evidence in any implementation or review note you produce.
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.
- 1mo ago Changed b27f587246df
- 1mo ago First seen · 94 lines · 54 tokens per session scan A 281127e388da
ui-guidance is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 868 once invoked, about $0.0002 per session on Opus 5.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
logo-design
Professional logo and brand-mark design, from brief to production files. Guides discovery and the design brief, concept generation, choosing a mark type (wordmark, monogram, letterform, pictorial, abstract, emblem, mascot, combination), building clean geometric SVG logos, optical refinement, colour and typography…
review-a11y
Internal accessibility review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks the changed user-facing surface for accessibility: semantics, keyboard, focus, contrast, and ARIA correctness — applies only to user-facing surfaces. Findings only…
review-design
Internal UI/UX design review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks the changed UI against the project's design doc: consistency, states, responsiveness, and reuse — applies only when the project has a UI and the change touches it.…
mermaid-diagrams
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes…
web-frontend-designer
Scaffold frontend architecture, components, routing, and UI dependencies from project config and wireframes.
web-ux-architect
Generate sitemap and wireframe specifications from project-config.json and produce UX planning artifacts.