designlisted

# Design Mode **Recommended model tier:** smart (opus) - this skill requires complex reasoning Output a technical design specification that downstream SDLC stages can consume. ## Purpose Create a structured design document that defines: 1. **What** to build (interfaces, types, components) 2. **How** it fits together (data flow, interactions) 3. **Why** key decisions were made (rationale) 4. **Success criteria** (acceptance criteria for TEST stage) ## Workflow ### Step 1: Understand the Request Read the request and identify: - Core functionality required - Constraints (tech stack, patterns, performance) - Integration points with existing code ### Step 2: Explore the Codebase Use search tools to understand existing patterns: - Use `Grep` for similar patterns, interfaces, types - Use `Glob` for relevant files - Use `mcp__plugin_aide_aide__decision_list` to review all decisions - Use `mcp__plugin_aide_aide__decision_get` with the relevant topic to check specific decisions ### Step 3: Define Interfaces Define the public API/interfaces first: ```typescript // Example TypeScript interface interface UserService { createUser(data: CreateUserInput): Promise<User>; getUser(id: string): Promise<User | null>; updateUser(id: string, data: UpdateUserInput): Promise<User>; } interface CreateUserInput { email: string; name: string; } ``` ```go // Example Go interface type UserService interface { CreateUser(ctx context.Context, input CreateUserInput) (*User, erro