sds

Compile architecture diagrams, ERDs, and API contracts into a single SDS blueprint.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/khairulariffinka/codexen --skill sds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sds
Source: https://github.com/khairulariffinka/codexen/tree/main/core/skills/sds
Command: npx skills add https://github.com/khairulariffinka/codexen --skill sds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SDS addresses the complexity of designing scalable systems by providing a unified framework for architecture design, ERD generation, and API contract management.

Core Features & Use Cases

  • Architecture design: define stack components, deployment diagrams, and infrastructure guidance
  • ERD generation: produce Mermaid ERDs and data models with clear relationships
  • API contracts: specify endpoints, requests, responses, and validation rules
  • Change governance: maintain traceability with changelogs and versioning For example, use SDS to document a new microservice with architecture, ERD, and contract specs.

Quick Start

Draft an SDS specification for a new service to generate architecture diagrams, ERD, and API contracts.

Frequently Asked Questions about sds

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

FAQPage Schema
How do I generate architecture diagrams, ERDs, and API contracts in one place?

To generate architecture diagrams, ERDs, and API contracts together, you can compile system design elements into a unified SDS blueprint that covers stack components, Mermaid data models, and endpoint specifications.

What is the best way to document a microservice architecture and data model?

Documenting a microservice architecture and data model is best handled by drafting a single blueprint specification that defines deployment diagrams, infrastructure guidance, and clear entity relationships.

Can I specify API endpoints and validation rules alongside an ERD?

You can specify API endpoints, requests, responses, and validation rules alongside an ERD by compiling them into a unified system design specification that governs both data modeling and contract definitions.

How do I maintain traceability and versioning for system design changes?

To maintain traceability and versioning for system design changes, apply change governance features that track modifications through changelogs, ensuring architecture and API contract updates remain documented.

Does this approach support system design from initial concept through deployment?

This approach supports system design from initial concept through deployment by applying a unified framework that covers architecture design, data modeling, and contract governance across the entire project lifecycle.