software-architect
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.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「software-architect」を使用しています。 Design the first architecture for a regional marketplace with 50,000 monthly users.
期待される結果:
- Recommended a modular monolith with clear commerce, payment, inventory, and identity boundaries.
- Selected PostgreSQL and Redis, with asynchronous events for notifications and reporting.
- Documented scaling triggers, failure handling, security controls, and a phased deployment plan.
「software-architect」を使用しています。 Compare Kafka and RabbitMQ for order status events.
期待される結果:
- Compared throughput, delivery behavior, routing, retention, operations, and team experience.
- Recommended RabbitMQ for current routing needs and lower operational complexity.
- Defined volume and replay requirements that would justify reconsidering Kafka.
「software-architect」を使用しています。 Review a service-oriented codebase with shared database tables.
期待される結果:
- Identified shared data ownership as the primary coupling risk.
- Proposed ownership boundaries, migration stages, contract tests, and measurable exit criteria.
- Separated immediate reliability fixes from longer-term service extraction work.
セキュリティ監査
中リスク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.
確認済みのセキュリティ上の懸念 (1)
リスク要因
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/zl2023github-software-architect/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/zl2023github-software-architect?utm_source=security_passport_badge)HTMLバッジ
<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>学術引用 (APA · BibTeX · CFF)
APA形式の引用
zl2023github. (2026). software-architect security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-software-architect/audits/4BibTeX形式の引用
@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}
}CITATION.cff
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"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Design a New Platform
Turn product requirements into service boundaries, data flows, deployment choices, diagrams, and documented trade-offs.
Evaluate a Technology Decision
Compare candidate technologies using explicit criteria, risks, proof-of-concept steps, and a recommended decision.
Review an Existing System
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.
ベストプラクティス
- Provide business goals, constraints, expected scale, reliability targets, compliance needs, and team capabilities.
- Request alternatives with explicit trade-offs, decision criteria, assumptions, and validation steps.
- Review generated diagrams and decisions with engineering, security, operations, data, and product stakeholders.
回避
- Do not select microservices before validating domain boundaries, scale needs, and operational capacity.
- Do not accept diagrams without ownership, failure behavior, data flows, and deployment assumptions.
- Do not treat generated recommendations as proof of performance, security, compliance, or production readiness.
よくある質問
Can this skill design microservices?
Can it analyze an existing repository?
Which diagram formats does it support?
Does it make final technology decisions?
Can it create architecture decision records?
Will it deploy or modify production systems?
開発者情報
作成者
zl2023githubライセンス
MIT
Skillstore リビジョン
r2
バージョンに関する注意
作者はバージョンを宣言していません。
参照
88a8e9a07f4c54ab105c1c41b6267c287146b07b
メンテナンスの新しさ
2026/7/26
利用状況
5 ダウンロード · 3 閲覧