SkillsAdd

smithery/vichannnnn

design-feature

Guide feature development through contract establishment and UI design phases.

Installation

$ npx skills add smithery/vichannnnn --skill design-feature
View on skills.sh ↗ Website ↗

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Shared topics
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Shared topics
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs
azure-enterprise-infra-planner Shared topics
microsoft/azure-skills

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…

402.8K installs

Also in this package

Other skills from smithery/vichannnnn.

npx skills add smithery/vichannnnn
create-ticket 0 create-script 0

Browse all from smithery/vichannnnn

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,101 B
  • docs SUMMARY.md 303 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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)