system-architecture

Plan and document system architectures, ADRs, and NFRs before coding.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mrsknetwork/nemodev --skill system-architecture-mrsknetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-architecture
Source: https://github.com/mrsknetwork/nemodev/tree/main/skills/domains/references/system-architecture
Command: npx skills add https://github.com/mrsknetwork/nemodev --skill system-architecture-mrsknetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architecture decisions are expensive; this skill helps plan and document system architectures, ADRs, and NFRs before coding.

Core Features & Use Cases

  • Generate C4 model diagrams (Level 1 & 2) and ADRs.
  • Define Non-Functional Requirements and align architecture decisions with targets.
  • Provide templates and best practices for planning migrations and evaluating architecture patterns.

Quick Start

Draft an initial architecture for a new project by outlining components, constraints, and ADRs in a planning session.

Frequently Asked Questions about system-architecture

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

FAQPage Schema
How do I document system architecture decisions before coding?

You can document system architecture decisions by generating Architecture Decision Records (ADRs) to capture context, decisions, and consequences. This skill provides standardized templates and conventions for storing ADRs under a docs/adr directory.

What is the best way to choose between a monolith and microservices?

To choose between a monolith, modular monolith, and microservices, apply structured architecture evaluation workflows. This skill guides technology evaluations by aligning Non-Functional Requirements (NFRs) with your target architectural pattern.

How do I generate C4 diagrams for system design?

Generate C4 diagrams for system design by modeling Level 1 and Level 2 views of your architecture. This skill outputs C4 model diagrams to visualize system context and container interactions during planning.

How do I define Non-Functional Requirements for a new project?

Define Non-Functional Requirements (NFRs) by performing structured NFR analysis to guide design decisions. This skill helps outline constraints and targets, ensuring your architecture aligns with required scalability and performance metrics.

Can I use this skill to plan a system migration?

Yes, you can use this skill to plan system migrations by evaluating architecture patterns and producing structured ADRs. It provides best practices and templates to guide migration planning and technology evaluations.

Do I need to define NFRs before creating ADRs?

Defining Non-Functional Requirements (NFRs) before creating ADRs is recommended to align architecture decisions with scalability targets. This skill includes structured NFR analysis to guide and justify your design choices.