create-module

分类: 数据与AI | 上传者: pierreb-devkit | 下载: 0 | 版本: v1.0（最新）

每当用户要求“创建一个模块”、“搭建一个功能”、“添加一个 Vue 域”、“名为 X 的新模块”或开始在一个全新的垂直领域（视图 + 组件 + 存储 + 路由器条目 + 测试）工作时，请使用此选项。复制规范的“src/modules/tasks”模板，应用 kebab/Pascal/camel/ UPPER 重命名，并连接配置驱动值。模块保持独立。 --- # 创建模块技巧通过复制“tasks”模板模块并重命名来创建一个新模块。 ## 先决条件 - 规范模板模块 `src/modules/tasks` 必须存在 - 您需要新模块的名称 (kebab-case) ## 步骤 ### 1. 询问模块名称提示用户以 kebab-case 格式输入新模块名称（例如，`my-feature`、`user-settings`） ### 2. 派生命名约定遵循 `/naming` 获取完整参考。从模块名称快速摘要（例如，`my-feature`）： - **kebab-case**：`my-feature`（文件夹名称、文件前缀、路由） - **PascalCase**：`MyFeature`（JS/模板中的组件名称） - **UPPER_SNAKE_CASE**：`MY_FEATURE`（环境键、常量） - **lowerCamelCase**：`myFeature`（变量名称、函数名称、存储） Exports) ### 3. 复制模块 ```bash cp -r src/modules/tasks src/modules/{new-module-name} ``` ### 4. 重命名引用

更新日志: Source: GitHub https://github.com/pierreb-devkit/Vue

目录结构

当前层级: tree/master/.claude/skills/create-module/

📄 SKILL.md 2.5 KB

SKILL.md

---
name: create-module
description: >
  Use this whenever the user asks to "create a module", "scaffold a feature",
  "add a Vue domain", "new module called X", or starts work on a brand-new
  vertical (views + components + store + router entry + tests). Duplicates
  the canonical `src/modules/tasks` template, applies kebab/Pascal/camel/
  UPPER renames, and wires config-driven values. Module stays self-contained.
---

# Create Module Skill

Create a new module by copying and renaming the `tasks` template module.

## Prerequisites

- The canonical template module `src/modules/tasks` must exist
- You need a name for the new module (kebab-case)

## Steps

### 1. Ask for the module name

Prompt user for the new module name in kebab-case (e.g., `my-feature`, `user-settings`)

### 2. Derive naming conventions

Follow `/naming` for the full reference. Quick summary from the module name (e.g., `my-feature`):

- **kebab-case**: `my-feature` (folder names, file prefixes, routes)
- **PascalCase**: `MyFeature` (component names in JS/templates)
- **UPPER_SNAKE_CASE**: `MY_FEATURE` (env keys, constants)
- **lowerCamelCase**: `myFeature` (variable names, function names, store exports)

### 3. Duplicate the module

```bash
cp -r src/modules/tasks src/modules/{new-module-name}
```

### 4. Rename references

Search and replace the following tokens across the new module:

- `tasks` → `{new-module-name}` (kebab-case)
- `Tasks` → `{NewModuleName}` (PascalCase)
- `TASKS` → `{NEW_MODULE_NAME}` (UPPER_SNAKE_CASE)
- `task` → `{new-module}` (singular kebab-case, if applicable)
- `Task` → `{NewModule}` (singular PascalCase, if applicable)

Files to check:

- Component names and file names
- Route paths and names
- Store/Pinia modules
- API endpoint names
- Type/interface names
- Config keys
- Test file names and test descriptions

### 5. Apply renames carefully

- Case-sensitive, whole-word matches where possible
- Show plan before applying if many files affected
- Don't rename unrelated code (e.g., "tasks" in comments about other features)

### 6. Config-driven values

Business values (plans, roles, feature flags) should be driven by module config, not hardcoded in stores or components.

Pattern:
- Define in `src/modules/{module}/config/{module}.development.config.js` (and env-specific variants)
- Access via the centralized config service (`import config from '@/lib/services/config'`)

### 7. Verify & report

Run `/verify`, then report: module path, renamed tokens, lint/test results, next steps (customize logic, update routes in `src/router`).

登录后下载/点赞/收藏 ❤ 20 | ★ 0

create-module

目录结构

SKILL.md

举报内容

提示