design-feature

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. Use when this capability is needed.
metadata	{"author":"vichannnnn"}

Design Feature Skill

Guide new feature development through structured planning phases before implementation.

Workflow

Phase 1: Contract Establishment

Before any design or code, establish the feature contract:

1. Clarify requirements - Ask questions to fully understand the feature
2. Define scope - What is and isn't included
3. Set acceptance criteria - Specific, testable conditions for completion
4. Identify constraints - Technical limitations, dependencies, edge cases

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]

Phase 2: UI Design

After contract agreement, draft the UI layout (to be included in the ticket).

Include:

1. Desktop layout - Full-width design
2. Mobile layout - Responsive/stacked design
3. Component hierarchy - Parent-child relationships
4. Interactions - User actions and responses
5. Required assets - Icons, images, fonts

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

Process Flow

1. User describes feature idea
2. Ask clarifying questions (no assumptions)
3. Draft and agree on contract
4. Draft UI layout
5. Review UI together, adjust as needed
6. Only after agreement, proceed to creation of ticket (include UI layout in the ticket)

---

Converted and distributed by TomeVault — claim your Tome and manage your conversions.