Arkive Annotate
SkillMediaUse when adding, editing, or reviewing Arkive annotations — @ArkiveComposable, @ArkiveView, or curating what @Preview components show in the catalogue: names, groups, tags, skip, Figma designNodeId. Triggers every time a component or screen is added to the Arkive showcase or its catalogue metadata changes. Enforces the shared naming/grouping conventions so the sidebar tree stays consistent.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Arkive Annotate skill
What this skill tells your AI
The instructions your AI receives, as published by infinum/arkive in .agents/skills/annotate/SKILL.md and read by ahel’s review.
Add or edit Arkive catalogue annotations following the project's conventions. The full
standard lives in references/annotation-conventions.md — read it
before writing any annotation.
Procedure
- Inventory first. List the groups and tags that already exist (grep for
group =/tags =in the module's annotations, or read the latestarkive-showcase.json). Reuse exact spelling, casing, and pluralization. Only invent a new group when nothing existing fits — and say so. - Prefer
@ArkiveComposablewhen adding a component to the catalogue. A non-private@Previewis collected by default, but@ArkiveComposablecarries richer info (tags,designNodeId,skip) and is validated with build errors instead of silent skips — it's the standard for anything that stays in the catalogue. Don't mass-annotate a codebase unprompted, but when the task is "add/curate this component", annotate it properly rather than leaving a bare@Preview. - Check visibility. The processor drops
privatefunctions — raise annotated previews tointernalif needed. - Figma linking:
designNodeIdtakes theX-Ynode id from the component's Figma URL, and needsarkive { designFileKey }set once per module. If the user gives a Figma URL, extract both. - Verify when a recording already exists: after annotating,
generateShowcase<Variant>and confirm the component appears under the intended group with the intended name.
Red flags
- A preview that renders more than one instance of the component — a
Row/Columnof sizes, styles, or an enabled/disabled pair. One preview = one instance; variation goes through a@PreviewParameterprovider (one value per catalogue variant). - Inventing a group without listing the existing ones first.
"Buttons"/"Button"/"buttons"coexisting — casing/pluralization drift.- Encoding variant info (font, density, RTL) in tags — the variant system owns that.
- Deleting or privatizing a preview to hide it — that's what
skip = trueis for. - Overriding the project's own established conventions with this document's defaults.
Signals
- GitHub stars
- 28
- Forks
- 1
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
annotate-infinum- Source
- github.com/infinum/arkive