/SKILL.md
Generate complete CRUD module code in Vue Vben Admin projects, including pages, forms, tables, and API interfaces. Must use this Skill when users say "generate CRUD", "create module", "add page", "write CRUD", "generate table page", "create xxx management", "generate xxx module". Do not skip even if the task seems simple. Do not generate code directly. All questions about component usage must be answered by reading the corresponding component documentation first, never from memory.
npx skillsauth add susiecmy/vben-skills vue-vben-crudInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Before generating any code, if the user has not provided the following information, ask one by one and wait for confirmation before proceeding to step 2. Do not guess from context and generate directly:
Prioritize reading the default CRUD template: assets/crud-template.md
Before generating any component, you must read the corresponding documentation first. Never generate from memory.
Before using useVbenModal, useVbenDrawer, useVbenVxeGrid, search the project to find the actual import path. Never guess.
| Component Type | Read This Doc First | Then Refer to This Template |
|---|---|---|
| Form | references/vben-form.md | assets/form-template.md |
| Table | references/vben-table.md | assets/table-usage-template.md |
| Modal | references/vben-modal.md | assets/modal-template.md |
| Drawer | references/vben-drawer.md | assets/drawer-template.md |
| Page | None | assets/page-template.md |
| Count Animator | references/vben-count-animator.md | assets/count-to-template.md |
| Ellipsis Text | references/vben-ellipsis-text.md | assets/ellipsis-text-template.md |
| Alert | references/vben-alert.md | assets/alert-template.md |
All files below must be generated. Not a single one can be skipped, even if the user has already provided information:
src/
├── api/
│ └── [module]/
│ ├── types.ts # Type definitions, must generate
│ └── index.ts # API interfaces, must generate
├── router/
│ └── routes/
│ └── modules/
│ └── [module].ts # Route config, must generate
└── views/
└── [module]/ # e.g. push/
├── index.vue # Main page, must generate
└── modules/ # Sub-component directory
├── form.vue # Form component, must generate
└── data.ts # Data config, must generate
Important: index.vue and data.ts are in [module]/ root. form.vue, drawer.vue and other components are in [module]/modules/. Do NOT nest an extra [module] subdirectory.
File responsibilities:
types.ts: Define request/response types and entity typesindex.ts: Encapsulate CRUD API methods (create, read, update, delete)[module].ts: Route config, define menu and page routesform.vue: Form component using useVbenModal or useVbenDrawerdata.ts: Table column config and search form schemaindex.vue: Main page using useVbenVxeGrid to integrate the tablebash .claude/skills/vue-vben-crud/scripts/check.sh <api-path> <views-path>
# Example: bash .claude/skills/vue-vben-crud/scripts/check.sh src/api/system/push src/views/system/push
If the script outputs exit 1, fix the errors and re-run.
Only proceed to 4.2 after the script outputs "🎉 All checks passed".
Scripts cannot verify component API usage. You must manually check against the docs:
references/vben-form.md, verify form API usage in form.vuereferences/vben-table.md, verify table column config in data.tsreferences/vben-modal.md or vben-drawer.md, verify modal/drawer usageFix any inconsistencies found. Only output the final summary after all checks pass.
After generation completes, output the summary in this exact format:
✅ [Module Name] CRUD Module Generation Complete
📁 Generated Files:
- src/api/[module]/types.ts
- src/api/[module]/index.ts
- src/router/routes/modules/[module].ts
- src/views/[module]/index.vue
- src/views/[module]/modules/form.vue
- src/views/[module]/data.ts
🎯 Next Steps:
1. Adjust API endpoint URLs to match actual backend paths
2. Add route configuration
3. Adjust field validation and display logic based on business requirements
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.