software-architecture-design

software-architecture-design is a skill for Claude Code from ddddjaak/se-skills. It costs 117 tokens per session (4,881 once invoked), scanned A, original, MIT.

A firmware planning guide for deciding how software modules run on a real-time operating system (RTOS), use memory, communicate, and move data. It turns system requirements into a documented software architecture.

In plain words
What is it for?
Designing RTOS thread and interrupt models, allocating memory and stack budgets, planning inter-process communication, and documenting data flows between firmware modules.
Why use it?
It makes thread ownership, timing, memory use, locks, and communication explicit before implementation. This helps expose race conditions, deadlocks, and missing design decisions early.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the se-skills plugin — 16 skills, 6 commands, 5 agents, 1 hook, 3 MCP servers shipped together

Good fit Designing RTOS thread and interrupt models, allocating memory and stack budgets, planning inter-process communication, and documenting data flows between firmware modules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ddddjaak/se-skills/software-architecture-design
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ddddjaak/se-skills --skill software-architecture-design
Clone the repo
git clone --depth 1 https://github.com/ddddjaak/se-skills

Made for: Claude Code.

Or install se-skills, the plugin that ships this one along with the rest of its 16 skills, 6 commands, 5 agents, 1 hook, 3 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for software-architecture-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/ddddjaak/se-skills/software-architecture-design/github.svg)](https://agentmods.dev/skills/ddddjaak/se-skills/software-architecture-design)
Your own site
<a href="https://agentmods.dev/skills/ddddjaak/se-skills/software-architecture-design"><img src="https://agentmods.dev/badge/skills/ddddjaak/se-skills/software-architecture-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for software-architecture-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/ddddjaak/se-skills/software-architecture-design"><img src="https://agentmods.dev/badge/skills/ddddjaak/se-skills/software-architecture-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 117 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,881 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00117 $0.04881
Opus 5 $0.00059 $0.02440
Sonnet 5 $0.00023 $0.00976
Haiku 4.5 $0.00012 $0.00488

Measured 9d ago against content hash 5731b70469f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

software-architecture-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/software-architecture-design/SKILL.md · 342 lines

How it starts

The opening of the file, as written. The whole thing — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Software Architecture Design

Overview

System architecture says which modules exist and how they interface. Software architecture says how those modules run — which thread owns which module, how much stack each thread gets, which ISRs are latency-critical, and how data flows between modules without deadlocks or race conditions.

This skill transforms the software-domain slice of system requirements and system architecture into a concrete software architecture document — the contract between the SE and the firmware team. Every thread assignment traces to a timing requirement. Every memory allocation is justified. Every lock is documented. If the RTOS or framework imposes a constraint, this skill verifies it rather than assuming.

When to Use

  • System architecture is confirmed and software-domain requirements are extracted
  • Starting firmware architecture design (thread model, memory map, IPC design)
  • Evaluating RTOS selection or framework architecture alternatives
  • A design review or downstream skill detects a software architecture gap
  • The firmware team needs a formal software architecture document before module implementation

When NOT to use:

  • System architecture is not yet designed (run architecture-design first)
  • The change is a single function implementation with no module or interface impact
  • Pure hardware architecture (use hardware-architecture-design)
  • Writing actual firmware code (this skill produces architecture, not implementation)

Context Boundary

Read ONLY:

  • System architecture document (module decomposition, interface definitions)
  • SW-domain system requirements (timing, throughput, reliability, memory constraints)
  • RTOS / framework documentation (API reference, configuration limits, ISR architecture)
  • Target MCU/SoC technical reference manual (memory map, interrupt controller, MPU/MMU)

Do NOT read: hardware specifications (pin assignments, voltage domains, PCB constraints), chip datasheets beyond the memory map section, test plans, or build system files.

Read the full file on GitHub · 342 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 342 lines · 117 tokens per session scan A 5731b70469f7

Subscribe to this mod's changes

software-architecture-design is a skill published in the GitHub repository ddddjaak/se-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session and 4,881 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

jetson-diagnostic

Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.

NVIDIA/skills · 30 tokens

doca-socket-relay

Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…

NVIDIA/skills · 236 tokens

offensive-z-wave

Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…

SnailSploit/Claude-Red · 113 tokens

hsb-flash

Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…

NVIDIA/skills · 94 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens