vesti-ui-prototype-sidepanel
Prototype-driven sidepanel UI refactor workflow and reusable design-unit architecture for Vesti. Use when requests include HTML/CSS prototypes, state-machine UI contracts, high-fidelity UI rebuilds, naming/icon semantics alignment, or cross-page sidepanel pattern reuse across Insights, Settings, and Timeline.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Vesti UI Prototype Sidepanel Skill
Scope
Use this skill to convert UI prototypes into stable, low-regression sidepanel implementations with reusable units and clear quality gates.
This skill is optimized for:
- Prototype -> state machine -> UI contract -> implementation flow.
- Sidepanel-wide pattern reuse (Insights, Settings, Timeline).
- Fast but disciplined UI iteration with explicit acceptance criteria.
Relationship With agent.md
-
agent.mdremains the constitutional layer (architecture, quality boundaries, release-line rules). - This skill is the execution layer for UI prototype-driven delivery.
- If conflicts appear, follow
agent.md.
Trigger Cues
Trigger this skill when the request includes one or more of:
- Provided prototype code (HTML/CSS, screenshot spec, interaction mock).
- Explicit state-machine UI requirements.
- High-fidelity UI refactor requests.
- Requests to reuse existing sidepanel style language and patterns.
Examples:
- "按这个原型重构 Insights accordion"
- "Keep Thread/Weekly naming semantics consistent across pages"
- "Build v1.8.x UI skeleton now, refine in v1.8.2"
Quick Start (Progressive Disclosure)
Read only what is needed:
- Start with
references/workflow-prototype-to-ui.mdfor step-by-step execution. - Load
references/design-unit-architecture.mdwhen deciding component boundaries and reuse. - Load
references/quality-gates-and-anti-patterns.mdbefore finalizing implementation. - Copy templates from
assets/templates/to produce plan/contract docs quickly.
Core Execution Rules
- Freeze semantics first (naming, grouping, icon meaning, trigger intent) before coding.
- Define state machine contracts before styling details.
- Prefer additive refactor with rollback safety over destructive replacement.
- Keep output decision-complete: no hidden decisions for the implementer.
- Treat "small readability details" (for example header descriptions) as first-class UX quality gates.
Required Deliverables Per Task
- Implementation plan (use
assets/templates/ui-refactor-plan-template.md). - State machine contract (use
assets/templates/state-machine-contract-template.md). - Design unit catalog/mapping (use
assets/templates/design-unit-catalog-template.md). - Acceptance checklist with build + manual sampling gates.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-03-11
- Index updated
- 2026-03-11
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!