design

Create detailed design maps for components, interfaces, and data flows.

Updated Jan 5, 2025

Search Tags:#design #architecture #interfaces #code-organization #single-responsibility #data-flows #module-placement

Ready to run

npx skills add https://github.com/pkuppens/pkuppens --skill design-pkuppens

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/design
Command: npx skills add https://github.com/pkuppens/pkuppens --skill design-pkuppens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams define and align detailed design components, interfaces, and data flows to ensure correct layering and single responsibility across architectural boundaries.

Core Features & Use Cases

Detailed design mapping and interface contracts that guide implementation
Data-flow diagrams and module layouts that align with architecture-consult
Use Case: when starting a new feature, create a precise design map to place code correctly and reduce rework

Quick Start

Draft the design map for the target feature by detailing components, interfaces, and data flows in a new file under the design directory.

Frequently Asked Questions about design

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

FAQPage Schema

How do I define detailed design placement for components and interfaces across my architecture?▼

Detailed design placement is defined by mapping components, interfaces, and data flows into a design directory file. This ensures correct layering and single responsibility across architectural boundaries before implementation begins.

When do I need to create a detailed design map for code organization?▼

You need a detailed design map when starting a new feature that requires precise module placement. It is applicable after architecture consultation identifies a module and you need public APIs, file layout, and data-flow constraints defined.

What's the best way to ensure single responsibility and clean layering in software design?▼

The best way to ensure single responsibility and clean layering is by drafting a design map that details components, interfaces, and data flows. This aligns code organization with architectural boundaries to reduce rework.

How do I map data flows and module layouts before implementation?▼

You map data flows and module layouts by detailing component placement and interface contracts in a new design directory file. This provides precise data-flow constraints and file layout definitions that guide implementation.

Does this detailed design approach work after an architecture consult has identified a module?▼

Yes, this approach works specifically for lifecycle stage 4.x workflows where architecture consultation has identified a module. It satisfies the requirements for defining public APIs and data-flow constraints needed before implementation.

Why does code organization fail without precise component and interface placement?▼

Code organization fails without precise placement because components lack correct layering and single responsibility across boundaries. Defining interface contracts and data-flow constraints before implementation reduces rework and ensures alignment.