Menu
Use when choosing, validating, or recording database/storage decisions, especially SQLite, Cloudflare D1, PostgreSQL, migrations, data residency, edge/runtime constraints, or Task Contract database_profile fields.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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 | database-profile-selector |
| description | Use when choosing, validating, or recording database/storage decisions, especially SQLite, Cloudflare D1, PostgreSQL, migrations, data residency, edge/runtime constraints, or Task Contract database_profile fields. |
Use this skill to prevent agents from silently picking a database because a backend exists. Database choice is a contract decision with evidence, constraints, and verification.
stack-profile-selector for app/backend/fullstack stack decisions.deployment-target-selector when platform, region, or runtime affects storage.sqlite-database, cloudflare-d1-database, or postgres-database after the
target is selected.Use the first source that applies:
database_profile:
target: "none | existing | sqlite | cloudflare-d1 | postgres | blocked"
decision_source: "user | docs | detected | project-overlay | recommended-fallback | blocked"
evidence: []
data_scope: "none | local-single-user | edge-app | multi-user | enterprise | unknown"
consistency: "local-file | relational | transactional | globally-distributed | unknown"
access_pattern: "embedded | server-only | edge-binding | direct-tcp | http-api | unknown"
migration_strategy: ""
backup_restore: ""
required_skills: []
verification:
schema_check: ""
migration_check: ""
integration_test: ""
runtime_smoke: ""
non_goals:
- "do not migrate database unless explicitly requested"
none when the project has no persistence need.Block when data ownership, multi-tenancy, backup/restore, migrations, region, compliance, offline sync, write concurrency, provider access, secrets, or runtime connectivity are unclear.