Borrowing it
Nothing to install: this file belongs to aziontech/webkit. 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/aziontech/webkit/main/.claude/skills/structure-decide/SKILL.mdgit clone --depth 1 https://github.com/aziontech/webkitWrote 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/aziontech/webkit/structure-decide)<a href="https://agentmods.dev/skills/aziontech/webkit/structure-decide"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/structure-decide/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/aziontech/webkit/structure-decide"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/structure-decide.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.00030 | $0.00635 |
| Opus 5.5 | $0.00012 | $0.00254 |
| Sonnet 5.5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
structure-decide 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 2mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: structure-decide
Purpose
Apply the shadcn-vue rule consistently:
Use Composition Pattern only when the consumer needs to reorder or omit parts the root exposes. Otherwise, monolithic with props + slots.
When in doubt, choose monolithic. Atoms (Button, IconButton, Tag, Badge, Spinner, Currency) are always monolithic.
When to invoke
- During
/spec-create, before writing thestructure:frontmatter. - Re-check during
/component-createwhen the spec isapproved(defense in depth).
Inputs
- The spec's Purpose, Props, Slots, and Sub-components sections (or the user's verbal description during
/spec-create). - The
figma-discoverJSON if available (for theregionsarray).
Workflow
- Apply the decision tree:
- If the spec lists Sub-components →
composition. - If the regions array includes a header + body + footer with optional reordering or omission →
composition. - If the component is an atom (no slots beyond
default, no sub-anatomy) →monolithic. - If the component has props + slots but fixed layout →
monolithic. - Otherwise →
monolithic(default when in doubt).
- If the spec lists Sub-components →
- Reference the canonicals to confirm:
- Composition: Dialog, Tabs, Accordion, composed Card, DropdownMenu, Sheet/Drawer, Form fields.
- Monolithic with slots:
card-pricing.vue(fixed layout, slot inversions). - Atomic:
button.vue,icon-button.vue.
- Emit a single line with the verdict and a one-sentence rationale:
orstructure: composition rationale: Consumer reorders/omits Header, Body, Footer.structure: monolithic rationale: Fixed layout with optional default + actions slots.
Outputs
- Two lines:
structure: <verdict>andrationale: <one sentence>.
Rules
- Do not choose Composition reflexively for "complex" components — the decision is about reordering, not about size.
- Do not restate the shadcn-vue criterion in the output — just the verdict and rationale.
- Do not edit the spec from this skill (the orchestrator writes the frontmatter).
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.
- 2mo ago First seen · 72 lines · 30 tokens per session scan A 0656385d0b83
structure-decide is a skill published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 635 once invoked, about $0.0001 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
monorepo-management
Sets up or audits a monorepo workspace: tool selection, package naming, shared tooling, inter-package dependencies, selective CI, and versioning strategy. Invoked when the user asks to set up a monorepo, add a workspace, or manage multiple packages in a single repository.
bazel-monorepo-expert
Expert knowledge for managing large-scale Bazel monorepos with multiple services, shared libraries, and cross-cutting concerns. Use for workspace structure, visibility, and dependency management.
pnpm
Skill "pnpm" from pledgeandgrow/pledge-skills, covering pnpm documentation skill, key benefits, file index, quick start and install pnpm.
data-dashboard
Build a dense, data-heavy screen - an analytics console or a trading terminal - with real charts drawn from tokens: candlestick, volume, depth, stacked area, waterfall, scatter, correlation matrix, donut, gauge, sparklines, heatmaps and order books. Use when the request is a dashboard, terminal, monitoring view, data…
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…