design

Facilitates design discussions and captures outcomes as tickets or document updates.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/kang-sw/devenv --skill design-kang-sw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/kang-sw/devenv/tree/main/claude-skills/design
Command: npx skills add https://github.com/kang-sw/devenv --skill design-kang-sw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of discussing design concepts, ensuring that ideas are clearly articulated, potential issues are identified, and conclusions are captured in a structured, actionable format like tickets or documentation updates.

Core Features & Use Cases

  • Facilitates Design Discussions: Engages in free-form conversation to explore design topics.
  • Context Management: Loads relevant documentation on demand and delegates deep dives to subagents to keep the main context focused.
  • Actionable Output: Captures discussion outcomes by creating new tickets, updating existing ones, or revising mental models based on user approval.
  • Use Case: Discussing a new feature's architecture, identifying trade-offs, and then having the skill draft a new ticket with integration test criteria.

Quick Start

Initiate a design discussion about the proposed user authentication flow.

Frequently Asked Questions about design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn architecture discussions into actionable tickets?

To turn architecture discussions into actionable tickets, engage in free-form conversation to explore design concepts and identify trade-offs, then capture conclusions by creating new tickets or updating existing documentation.

What is the best way to manage context when discussing complex design requirements?

The best way to manage context for complex design requirements is loading relevant mental-model documents on demand and delegating source exploration to subagents, keeping the main discussion context focused.

Can I update existing documentation based on design discussion outcomes?

Yes, you can update existing documentation based on design discussion outcomes. The skill revises mental models or modifies tickets after receiving user approval, ensuring read-only operations until conclusions are explicitly captured.

How do I document software architecture trade-offs during a brainstorming session?

To document software architecture trade-offs during brainstorming, discuss the feature's architecture freely, identify potential issues, and then have conclusions drafted into structured tickets or mental-model updates.

Does the design discussion process automatically create tickets without approval?

No, the design discussion process does not automatically create tickets without approval. It ensures read-only operations during exploration and only captures outcomes by creating tickets or updating documents based on explicit user approval.