design

Design system architectures and API specifications for scalable software.

Updated Dec 22, 2025
One-click install
npx skills add https://github.com/senior-sigan/llm-skills --skill design-senior-sigan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/senior-sigan/llm-skills/tree/main/skills/design
Command: npx skills add https://github.com/senior-sigan/llm-skills --skill design-senior-sigan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams and engineers often struggle to produce clear, maintainable design specifications for complex systems, APIs, and component interfaces, leading to ambiguity during development.

Core Features & Use Cases

  • Architecture Design: define system structure, interactions, and scalability considerations.
  • API Specification: outline endpoints, contracts, data models, versioning, and documentation.
  • Component Interfaces: specify module contracts, integration points, and interoperability guidelines.

Quick Start

Create a comprehensive design specification for a new service including architecture, API interfaces, and data models.

Frequently Asked Questions about design

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

FAQPage Schema
How do I design scalable system architecture and API specifications for a new service?

Design scalable system architecture and API specifications by defining system structure, interactions, endpoints, data models, and versioning. This creates clear, maintainable design specifications that reduce ambiguity during development across products.

What is the best way to specify component interfaces and module contracts for complex systems?

Specifying component interfaces involves defining module contracts, integration points, and interoperability guidelines. This ensures maintainable design specifications for complex systems, preventing ambiguity when engineers develop and integrate product components.

How do I document API contracts and data models for scalable software?

Document API contracts and data models by outlining endpoints, versioning rules, and specifications. This produces clear architecture diagrams and documentation required to satisfy development requirements for scalable software products.

Can I use this to plan architecture diagrams and data models for a new service?

Yes, you can apply this to architecture planning for new services. It generates required architecture diagrams, data models, API contracts, and component interface specifications needed to satisfy comprehensive design documentation requirements.

When do I need formal API versioning and component interface documentation?

You need formal API versioning and component interface documentation when producing clear, maintainable design specifications for complex systems. It prevents ambiguity during development by defining explicit module contracts and integration points.