architect

Generate C4 diagrams, Arc42 documentation, ADRs, API contracts, and data models.

9|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/TykoDev/SupremeTeam --skill architect-tykodev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/TykoDev/SupremeTeam/tree/main/skills/design/architect
Command: npx skills add https://github.com/TykoDev/SupremeTeam --skill architect-tykodev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates uncertainty and manual effort in system architecture by producing a complete, gatekeeper-ready architecture package that downstream teams can trust and inherit. It consolidates architecture style selection, C4 diagrams, Arc42 documentation, ADRs, API contracts, data models, deployment topology, and a formal Backend Stack Lock so design decisions are explicit, versioned, and reviewable.

Core Features & Use Cases

  • Architecture Style Selection: Chooses and documents monolith, microservices, clean/hexagonal, event-driven, or serverless approaches with ADRs.
  • C4 Diagrams & Arc42 Docs: Generates System Context, Container, and Component diagrams (Mermaid) and a complete Arc42 v9.0 architecture document.
  • Decision Records & Stack Lock: Produces MADR v4.0 ADRs and a Backend Stack Lock referencing a specific tech-stack overlay and version tuple.
  • API & Data Specs: Outputs OpenAPI/AsyncAPI/gRPC or GraphQL contracts and logical ERD data models with migration and retention guidance.
  • Review Handoff: Packages deliverables into a gatekeeper-ready review packet for pipeline or standalone workflows.

Quick Start

Use the architect skill to produce an Arc42 architecture document with C4 diagrams, MADR ADRs, OpenAPI specs, a logical ERD, and a Backend Stack Lock for the provided requirements.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I create an Arc42 architecture document with C4 diagrams and ADRs?

To create an Arc42 architecture document, you need to generate Mermaid C4 diagrams, MADR v4.0 decision records, and a structured system architecture package consolidating API contracts and deployment topology.

What is the best way to lock a backend tech stack with specific version tuples?

Locking a backend tech stack requires producing a formal Backend Stack Lock document that references specific tech-stack overlays and version tuples, ensuring design decisions are explicit and reviewable for downstream teams.

How do I generate OpenAPI and AsyncAPI contracts for a new system architecture?

Generating API contracts involves creating OpenAPI, AsyncAPI, gRPC, or GraphQL specifications alongside logical ERD data models, ensuring the system architecture package includes complete interface definitions and migration guidance.

Can I use this approach to produce review-ready architecture packages for a gatekeeper pipeline?

Yes, you can package architecture deliverables into a gatekeeper-ready review packet that includes C4 diagrams, Arc42 documentation, and ADRs, satisfying requirements for pipeline or standalone architecture workflows.

When do I need to choose between monolith, microservices, and event-driven architecture styles?

Choosing between monolith, microservices, clean/hexagonal, event-driven, or serverless approaches is necessary when designing production-ready system architectures and requires documenting the selection with formal decision records.

Does the architecture generation process include logical ERD data models with retention guidance?

Yes, the architecture generation process outputs logical ERD data models that include data migration and retention guidance, ensuring the complete system architecture package covers data specifications alongside API contracts.