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 wahidyankf/ose-public --skill developing-frontend-uigit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/developing-frontend-ui)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/developing-frontend-ui"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/developing-frontend-ui/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/wahidyankf/ose-public/developing-frontend-ui"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/developing-frontend-ui.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.00060 | $0.00906 |
| Opus 5.5 | $0.00024 | $0.00362 |
| Sonnet 5.5 | $0.00012 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
developing-frontend-ui 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 2d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend UI Development Skill
This skill provides repo-specific guidance for building UI components in the open-sharia-enterprise monorepo. It covers design tokens, component patterns, accessibility, anti-patterns, and per-app brand context.
When This Skill Triggers
- Editing
.tsxcomponent files inapps/*/src/components/ - Editing
globals.cssor Tailwind configuration - Creating or modifying shared UI components in
libs/web-ui/ - Working on design tokens in
libs/web-ui-token/
Reference Modules
Consult these reference docs for detailed guidance on specific topics:
- Design Tokens Reference — Token architecture, current values, Tailwind mapping
- Design Tokens — Spacing and Format Reference — Spacing scale, token format differences across apps
- Component Patterns Reference — Standard template, complete Button example
- Component Patterns — Key Patterns and Testing — CVA/Radix key patterns, Storybook, unit tests, checklist
- Anti-Patterns Catalog — 13 repo-specific anti-patterns with before/after examples
- Accessibility Reference — Per-component ARIA checklists, keyboard navigation
- Brand Context Reference — Per-app audience, personality, palette guidance
- Top Rules Reference — Quick-reference Do/Do-Not checklist
Test-Driven Development for UI
TDD applies to UI component and page work. Write the failing check before writing the component:
- Vitest unit test (
component-name.test.tsx): failing assertion on render, variant output, ortoHaveNoViolations()(vitest-axe) — write this first. - Visual snapshot (Playwright visual diff): failing screenshot comparison — write before finalizing visual styles.
- Accessibility check (axe): failing
toHaveNoViolations()in unit test or Playwright — write before adding interactive states or ARIA markup. - E2E Playwright spec: failing user-flow assertion — write before implementing flows that cross component boundaries.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- README.md 495 B
- reference/accessibility.md 3.9 KB
- reference/anti-patterns.md 1.4 KB
- reference/brand-context.md 1.7 KB
- reference/component-patterns-key-patterns-and-testing.md 3.5 KB
- reference/component-patterns.md 2.5 KB
- reference/design-tokens-spacing-and-format.md 1.7 KB
- reference/design-tokens.md 2.7 KB
- reference/README.md 857 B
- reference/top-rules.md 1.6 KB
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.
- 2d ago First seen · 69 lines · 60 tokens per session scan A fed2d31717d5
developing-frontend-ui is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 906 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-10-14.
Other skills, from other repositories
styling-sidebar-products
How products and pages appear in the PostHog sidebar: which category they sit in, which icon and color they get, and which groups share a color gradient. Use when adding a product or data management page to the sidebar (treeItemsProducts or treeItemsMetadata in a products//manifest.tsx), giving an entry a new icon or…
quill-code
Edit the @posthog/quill design system locally and consume the change in products/desktop before it is published to npm. Use when changing quill components/primitives/tokens, when a quill change must be tested inside the Code app, or when the user mentions quill, the design system, the .local-quill tarball, or the…
design-iterator
Iteratively refines UI design through N screenshot-analyze-improve cycles. Use PROACTIVELY when design changes aren't coming together after 1-2 attempts, or when user requests iterative refinement.
design
Design workflow that creates design systems, DESIGN.md, and design tokens with anti-pattern enforcement and accessibility checks.
figma-design-sync
Detects and fixes visual differences between a web implementation and its Figma design. Use iteratively when syncing implementation to match Figma specs.
design-implementation-reviewer
Visually compares live UI implementation against Figma designs and provides detailed feedback on discrepancies. Use after writing or modifying HTML/CSS/React components to verify design fidelity.