Skip to content
TrustedSkillsbeta
Back to all skills

Architecture Decision

Checked
jwynia·vlatest·backend

This skill helps document and justify architectural decisions, ensuring clarity and alignment for better project outcomes.

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 jwynia/agent-skills --skill architecture-decision --full-depth -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

jwynia

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 jwynia/agent-skills at e02ec7e226.

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

Commit
e02ec7e226
Manifest
skills/tech/development/architecture/architecture-decision/SKILL.md
Scanned
1 file, 195 lines
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

The architecture-decision skill enables AI agents to evaluate, compare, and select optimal system design patterns based on specific project constraints and requirements. It assists in documenting these choices by generating structured records that capture the reasoning behind technical decisions for future reference.

When to use it

  • Evaluating multiple microservices vs. monolithic approaches for a new application startup.
  • Selecting database storage solutions (e.g., SQL vs. NoSQL) based on data consistency needs.
  • Determining cloud infrastructure strategies when scaling an existing legacy system.
  • Documenting trade-offs between security protocols and development speed during a sprint.

Key capabilities

  • Compares distinct architectural patterns against defined criteria.
  • Generates detailed decision records including context, options considered, and rationale.
  • Identifies potential risks and long-term implications of chosen designs.
  • Adapts recommendations based on team size, budget limits, and timeline constraints.

Example prompts

  • "Analyze the pros and cons of event-driven architecture versus request-response for our real-time analytics platform."
  • "Create an architecture decision record for migrating our monolith to a serverless environment, considering cost and latency."
  • "Recommend a caching strategy for a high-traffic e-commerce site with strict data consistency requirements."

Tips & gotchas

Ensure you provide clear constraints such as budget, team expertise, and performance targets to get relevant recommendations. This skill focuses on strategic design choices rather than implementation details like specific coding syntax or library versions.