Menu
Use when building, reviewing, or maintaining Alpine.js frontends for lightweight HTML-first interactions, static reports, server-rendered pages, simple toggles, filters, disclosure UI, or no-build enhancements.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Define, implement, and review the Volt GUI desktop design language and user experience. Use for any Volt GUI Svelte/Wails UI work involving visual styling, layout, navigation, Work/Code workbenches, composer interactions, settings, dialogs, lists, empty/loading/error states, responsive behavior, or design-system decisions.
Use when designing, implementing, or reviewing Volt GUI operational task-lifecycle UX: running message queues and Steer, activity centers, result receipts, structured recovery, explainable approvals, Diff comments to fixes, automation result inboxes, or managed worktree snapshot/Handoff flows. Enforces real Wails-backed state, safe mutation preflights, Work/Code ownership, and behavioral plus visual verification; pair with the project volt-gui-design-language skill for broad visual or layout work.
Use when configuring, verifying, or debugging the 西谷智灯暗涌系统 (Anyong/Xigu AI) white-label branding on the VoltUI fork. Covers BrandConfig env vars, voltui.toml [brand] section, desktop-build.sh VOLTUI_BRAND_NAME, and GitHub Actions/CNB release naming.
Use when configuring, debugging, or modifying CNB (Cloud Native Build) CI/CD pipelines for VoltUI/西谷智灯暗涌系统. Covers .cnb.yml structure, auto-release conventional commit workflow, merge-request CI checks, cross-repo PR creation, and CNB Release API.
Use when tasks involve 西谷AI (Xigu AI) internal operations, 西谷智灯暗涌系统 product strategy, Chinese AI market context, local regulations, or fork-specific workflow decisions. Covers upstream sync strategy, release workflow, internal tooling, and product-market-fit decisions for the 西谷智灯暗涌系统 coding agent.
Design and review REST, OpenAPI, GraphQL, webhook, and internal service APIs. Use for contracts, versioning, idempotency, pagination, errors, auth, and SDK ergonomics.
| name | alpine-frontend |
| description | Use when building, reviewing, or maintaining Alpine.js frontends for lightweight HTML-first interactions, static reports, server-rendered pages, simple toggles, filters, disclosure UI, or no-build enhancements. |
Use Alpine for small HTML-first interactions where a full component framework is unnecessary. Alpine is not the default for complex app workbenches or dashboards.
stack-profile-selector when choosing Alpine as a stack decision.tailwind-v4 when Tailwind is used for styling.Load this skill when the project or task mentions:
x-data, x-show, x-bind, x-on, x-model, x-for, x-iffrontend_profile:
framework: "alpine"
decision_source: "user | docs | detected | project-overlay | recommended-fallback | blocked"
evidence: []
ui_complexity: "static | light-interaction"
required_skills:
- "stack-profile-selector"
- "alpine-frontend"
verification:
build: ""
runtime_or_visual_checks: ""
non_goals:
- "do not use Alpine for complex app state or large dashboard workflows"
- "do not migrate frontend framework unless explicitly requested"
Use the project's existing commands first. Typical checks:
Block when the UI has app-grade routing, shared state, nested components, complex forms, realtime data, or dashboard-level interactions that make Alpine a poor fit.