trove-component-spec
Generate component specifications from design requirements. Produces structured specs with props, states, interactions, and accessibility requirements.
- License 许可
- MIT
- 所属仓库
- bravew/trove
- 最近更新
- 2026-11-12
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- trove-component-spec
- metadata
- { "trove-category": "design", "trove-category-label": "Design" }
- description
- Generate component specifications from design requirements. Produces structured specs with props, states, interactions, and accessibility requirements.
- when_to_use
- component spec; design spec; component requirements
03 SKILL.md 正文
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run build:skills -->
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Component Specification Generator
Spec Template
When creating a component spec, include:
# Component: [Name]
## Purpose
What this component does and when to use it.
## Props / API
| Prop | Type | Default | Description |
|------|------|---------|-------------|
| variant | 'primary' \| 'secondary' | 'primary' | Visual variant |
## States
- Default
- Hover
- Focus
- Active
- Disabled
- Loading
- Error
## Responsive Behavior
- Mobile: [description]
- Tablet: [description]
- Desktop: [description]
## Accessibility
- Role: [ARIA role]
- Keyboard: [interactions]
- Screen reader: [announcements]
## Design Tokens
- Colors: [token names]
- Spacing: [token names]
- Typography: [token names]
04 同仓库更多 Skills
using-trove
Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.
trove-write-skill
Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.
trove-worktree
Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.
trove-why
Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for "why does X work this way", "why did we pick Y", regressions, and postmortems. Use trove-explain for how it works now.
trove-verify
Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.
trove-unslop
Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.