菜单
Guide feature development through contract establishment and UI design phases. Use when discussing, designing, or planning a new feature that is not yet implemented. Ensures requirements are clarified, acceptance criteria defined, and UI layouts drafted before any code is written.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Update CLAUDE.md sections through interactive Q&A. Use when the user wants to update project documentation, refresh CLAUDE.md content, or says "/update-claude-md". Guides user through questions to update auto-generated sections (overview, objectives, commands, notes).
Codify discovered processes into standalone, reusable Python scripts. Use when the user has figured out a process (API integration, data pipeline, automation task) and wants to turn it into a reusable script, or when the user says "/create-script".
Meta-skill by Anthropic to help guide creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Generate and execute git commits following conventional commit format. Use when the user wants to commit changes, create a commit, or says "/commit". Analyzes staged/unstaged changes and creates properly formatted commit messages with type, optional scope, and descriptive subject.
Create GitHub pull requests with properly structured descriptions. Use when the user explicitly asks to create a PR, open a pull request, or says "/create-pr". Analyzes commits and changes to generate clear PR descriptions with summary, changes list, and UI changes when applicable.
Create task tickets with proper numbering, template structure, and ticket-list.md updates. Use when the user wants to create a ticket, add a task, or says "/create-ticket". Automatically finds the next ticket number, creates the ticket file, and updates the centralized ticket list.
| name | design-feature |
| description | Guide feature development through contract establishment and UI design phases. Use when discussing, designing, or planning a new feature that is not yet implemented. Ensures requirements are clarified, acceptance criteria defined, and UI layouts drafted before any code is written. |
Guide new feature development through structured planning phases before implementation.
Before any design or code, establish the feature contract:
Output a contract summary:
## Feature Contract: [Feature Name]
### Scope
- [What's included]
- [What's excluded]
### Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
### Constraints
- [Technical constraints]
- [Dependencies]
After contract agreement, draft the UI layout (to be included in the ticket).
Include:
UI Layout template:
# [Feature Name] - UI Layout
## Desktop Layout
┌─────────────────────────────────────┐ │ Header │ ├─────────────────────────────────────┤ │ Component A │ Component B │ │ │ │ ├─────────────────────────────────────┤ │ Footer │ └─────────────────────────────────────┘
## Mobile Layout
┌─────────────┐ │ Header │ ├─────────────┤ │ Component A │ ├─────────────┤ │ Component B │ ├─────────────┤ │ Footer │ └─────────────┘
## Component Hierarchy
- ParentComponent
- ChildComponent1
- ChildComponent2
- GrandchildComponent
## Interactions
| Action | Response |
|--------|----------|
| Click X | Shows Y |
| Hover Z | Highlights |
## Required Assets
- [ ] Icon: description
- [ ] Image: description