Borrowing it
Nothing to install: this file belongs to Synerise/synerise-design. 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/Synerise/synerise-design/master/.claude/skills/overview-mdx/SKILL.mdgit clone --depth 1 https://github.com/Synerise/synerise-designWrote 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/synerise/synerise-design/overview-mdx)<a href="https://agentmods.dev/skills/synerise/synerise-design/overview-mdx"><img src="https://agentmods.dev/badge/skills/synerise/synerise-design/overview-mdx/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/synerise/synerise-design/overview-mdx"><img src="https://agentmods.dev/badge/skills/synerise/synerise-design/overview-mdx.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.01876 |
| Opus 5 | $0.00015 | $0.00938 |
| Sonnet 5 | $0.00006 | $0.00375 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
overview-mdx 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 6d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Create or update a component's MDX overview page in Storybook (packages/storybook/stories/components/<PascalName>/<PascalName>.mdx). This page appears as the "Overview" tab (configured via docs.defaultName: 'Overview' in .storybook/main.ts) and serves as the primary developer-facing documentation for consuming the component.
Arguments
The user must provide:
- Package name — e.g.,
modal,button,progress-bar(kebab-case directory name underpackages/components/)
The user may optionally provide:
- Specific sections or topics to emphasise
- Known usage caveats to document
If the package name was not provided, ask: "Which package would you like to create an overview page for? (e.g. modal, button, popover)"
Workflow
Step 1 — Read all source material
Read the component source and existing documentation to understand the full API surface:
packages/components/<package-name>/src/ ← component source (all .tsx/.ts files)
packages/components/<package-name>/CLAUDE.md ← AI reference doc (rich context)
packages/components/<package-name>/README.md ← existing docs (if present)
packages/storybook/stories/components/<PascalName>/ ← all story files
From the source, extract:
- All exported components and their props (from
index.tsand*.types.ts) - Sub-components and compound patterns
- Custom hooks exposed to consumers
- Context/Provider requirements
- Key dependencies that affect usage (e.g., requires
DSProviderwrapper)
From the stories, extract:
- All named story exports (these become
Canvasexamples) - Which stories best illustrate key use cases
- The meta export (needed for
<Meta>tag)
Step 2 — Check for existing MDX
Look for an existing file at:
packages/storybook/stories/components/<PascalName>/<PascalName>.mdx
Also check for alternate names: <PascalName>.overview.mdx, <PascalName>.docs.mdx.
- If found → read it, preserve accurate content, update outdated sections.
- If not found → create a new file.
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.
- 6d ago First seen · 215 lines · 31 tokens per session scan A ed4785c6526a
overview-mdx is a skill published in the GitHub repository Synerise/synerise-design (96 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 1,876 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-09-04.
Other skills, from other repositories
suanfish-design-system
A Chinese design system for creating and reviewing web interfaces, with multiple design perspectives working together. It focuses on React and Tailwind-based projects.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
compiler-orchestrator
Orchestrate the Rust compiler port end-to-end. Discovers the current frontier, fixes failing passes, ports new passes, reviews, and commits in a loop.
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
plan-update
Use when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.