Design Reliable Software Architectures
Complex systems require explicit boundaries, trade-offs, and operational constraints. This skill structures architecture analysis, diagrams, decisions, and documentation for review.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "software-architect" from https://skillstore.io/skills/zl2023github-software-architect.md and its manifest at https://skillstore.io/api/skills/zl2023github-software-architect/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "software-architect". Design the first architecture for a regional marketplace with 50,000 monthly users.
Expected outcome:
Using "software-architect". Compare Kafka and RabbitMQ for order status events.
Expected outcome:
Using "software-architect". Review a service-oriented codebase with shared database tables.
Expected outcome:
All 18 static findings are false positives caused by Markdown backticks, Mermaid diagrams, and high entropy in Chinese text. A separate medium-risk issue remains because the skill requests broad terminal, web, file-write, code-execution, and delegation access without approval boundaries. No prompt injection, obfuscation, or malicious commands were found.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/zl2023github-software-architect/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/zl2023github-software-architect?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/zl2023github-software-architect?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zl2023github-software-architect/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/zl2023github-software-architect.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>zl2023github. (2026). software-architect security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-software-architect/audits/4@techreport{zl2023github-zl2023github-software-architect-2026,
author = {zl2023github},
title = {software-architect security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zl2023github-software-architect/audits/4},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "software-architect security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "zl2023github"
date-released: "2026-07-24"
url: "https://skillstore.io/skills/zl2023github-software-architect/audits/4"
identifiers:
- type: other
value: "skillstore:zl2023github-software-architect:audit:4"
description: "Skillstore immutable audit report identifier"
Turn product requirements into service boundaries, data flows, deployment choices, diagrams, and documented trade-offs.
Compare candidate technologies using explicit criteria, risks, proof-of-concept steps, and a recommended decision.
Assess dependencies, architecture style, technical debt, compliance gaps, and practical modernization priorities.
Design an architecture for [product]. Ask for missing requirements, then define components, data stores, integrations, deployment, security, and key trade-offs.
Compare [option A] and [option B] for [workload]. Evaluate performance, reliability, cost, operations, team fit, migration risk, and proof-of-concept criteria.
Analyze the provided repository for module boundaries, dependency direction, coupling, data ownership, deployment structure, and technical debt. Prioritize findings by impact.
Create an incremental modernization plan for [current system] under [constraints]. Include target architecture, transition stages, compatibility controls, rollback points, metrics, and ADRs.
Author
zl2023githubLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Maintenance freshness
7/26/2026
Usage
5 downloads · 3 views
File structure
Diagnose and Improve Full-Stack Performance
Full-stack teams often lack a repeatable way to measure performance and locate bottlenecks. This skill provides testing workflows, diagnostic commands, optimization guidance, and report structures.
Build and Optimize Search Systems
Search teams need reliable guidance across indexing, ranking, semantic retrieval, and evaluation. This skill provides practical workflows and examples for building and improving search systems.
Design Reliable Payment Systems
Payment teams need consistent designs for transactions, channels, reconciliation, security, and failure handling. This skill provides structured guidance, examples, and review checklists.
Build Reliable Business Intelligence Analysis
Business teams often lack consistent metrics and repeatable analysis workflows. This skill guides SQL, Python, dashboards, experiments, and automated reporting from requirements to delivery.
Evaluate Technology Choices with Clear Tradeoffs
Technology choices often hide tradeoffs across performance, cost, reliability, operations, and team readiness. This skill compares candidates, recommends an option, and defines proof-of-concept checks.
Generate Clear Software Architecture Documents
Architecture decisions often remain scattered across requirements, discussions, and diagrams. This skill organizes them into consistent Markdown documents for implementation and review.
Design Software Architectures with Senior Guidance
by davila7
Architecture choices are hard to compare across product, scale, security, and team constraints. This skill gives structured guidance, references, and helper scripts for clearer decisions.
Analyze Your Codebase with a Structured Review
by Atman36
Large repositories hide architecture, dependency, and quality risks. This skill produces a structured map, focused checks, and prioritized recommendations.
Plan Complex Coding Changes
by tencentcloudbase
Large coding changes often fail when scope, design, and acceptance criteria are vague. This skill guides Claude, Codex, and Claude Code through requirements, design, tasks, and staged confirmation.
Orchestrate Complete Backend Feature Delivery
by sickn33
Complex backend features often fail when requirements, architecture, testing, and rollout work remain disconnected. This skill coordinates twelve delivery phases with defined outputs, controls, and handoffs.
Design Maintainable Backend Architectures
by wshobson
Complex backend systems can become tightly coupled and hard to test. This skill guides Claude, Codex, and Claude Code through proven architecture patterns.
Design Cleaner Software Architecture
by sickn33
Software projects often grow hard to maintain when boundaries, names, and dependencies are unclear. This skill guides clean architecture decisions, domain modeling, and focused refactoring.