Skip to content
TrustedSkillsbeta
Back to all skills

System Design

Checked
s-hiraoku·vlatest·frontend

Designs scalable, resilient, and efficient systems leveraging cloud infrastructure and modern architectural patterns.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add s-hiraoku/synapse-a2a --skill system-design -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

s-hiraoku

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned s-hiraoku/synapse-a2a at 844eb75d92.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
844eb75d92
Manifest
.agents/skills/system-design/SKILL.md
Scanned
3 files, 333 lines
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill assists in designing scalable, resilient, and efficient systems by guiding architectural decisions and producing structured design artifacts. It breaks down the system design process into distinct steps, including requirements clarification, component identification, alternative evaluation, and document creation. The skill helps users evaluate trade-offs between different approaches and ultimately produce a comprehensive design document outlining key components, decisions, and potential risks.

When to use it

  • Designing a new system or major feature from scratch
  • Evaluating trade-offs between architectural approaches
  • Creating Architecture Decision Records (ADRs)
  • Reviewing existing architecture for scalability, reliability, or maintainability concerns
  • Decomposing a monolith or planning a migration

Key capabilities

  • Requirements clarification: Gathers and clarifies functional, non-functional, scope, and constraint requirements.
  • Component identification: Breaks down systems into data stores, services/modules, interfaces, and external dependencies.
  • Alternative evaluation: Documents and compares at least two options for each significant architectural decision based on criteria like complexity, scalability, operational cost, and team familiarity.
  • Design artifact generation: Produces a structured design document including context, requirements, architecture diagrams, key decisions, data models, API surfaces, risks & mitigations, and open questions.
  • Review checklist: Provides a list of items to verify before finalizing the design (e.g., single responsibility, failure modes, security boundaries).

Example prompts

  • "I need to design a new user authentication system. Can you help me outline the requirements?"
  • "We're considering using microservices for our order processing pipeline. What are some architectural trade-offs I should consider?"
  • "Can you generate an Architecture Decision Record for choosing between relational and NoSQL databases for storing product catalog data?"

Tips & gotchas

  • The skill emphasizes clarifying requirements upfront; be prepared to answer questions about the system's purpose, constraints, and scope.
  • The output is a structured design document – expect a detailed outline rather than a fully implemented solution.
  • The skill recommends documenting at least two options for each significant architectural decision to ensure trade-offs are explicitly considered.