스킬 software-architect

📦

software-architect

Name: software-architect
Author: zl2023github

콘텐츠 리비전 r2 중간 위험 ⚙️ 외부 명령어

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.

지원: Claude Codex Code(CC)

📊 66 적절함

Maintain this Skill? Claim it 📊 66 적절함

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 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 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/zl2023github-software-architect.md 서명된 manifest GET /api/skills/zl2023github-software-architect/manifest 서명된 lockfile GET /api/skills/zl2023github-software-architect/lockfile

테스트해 보기

"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.

보안 감사

중간 위험

v4 • 2026. 7. 24. 버전별 보고서 열기

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.

스캔된 파일

920

분석된 줄 수

검토 항목

오탐 무시됨

확인된 보안 우려 사항 (1)

중간

SKILL.md:67-78 SKILL.md:153-162

Unscoped Powerful Tool Enablement

The skill directs agents to enable web, terminal, file-writing, code-execution, and delegation tools without approval or target restrictions. Adversarial input could misuse these privileges.

The instructions explicitly request these powerful toolsets in two sections. No consent, command allowlist, path boundary, or network restriction is stated.

위험 요인

⚙️ 외부 명령어 (14)

SKILL.md:105 SKILL.md:109-155 SKILL.md:155-157 SKILL.md:157-168 SKILL.md:168-169 SKILL.md:169-170 SKILL.md:170-171 SKILL.md:171-172 SKILL.md:172-188 SKILL.md:188-197 SKILL.md:197-200 SKILL.md:200-202 SKILL.md:202-251 SKILL.md:251

감사자: codex 감사 이력 보기 →

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/zl2023github-software-architect/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/zl2023github-software-architect/security.svg)](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/4

BibTeX 인용

@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.

이 프롬프트를 사용해 보세요

Outline a System Architecture

Design an architecture for [product]. Ask for missing requirements, then define components, data stores, integrations, deployment, security, and key trade-offs.

Compare Technology Options

Compare [option A] and [option B] for [workload]. Evaluate performance, reliability, cost, operations, team fit, migration risk, and proof-of-concept criteria.

Review a Codebase Architecture

Analyze the provided repository for module boundaries, dependency direction, coupling, data ownership, deployment structure, and technical debt. Prioritize findings by impact.

Plan a System Modernization

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?

Yes. It can define service boundaries, data ownership, communication patterns, deployment choices, and trade-offs.

Can it analyze an existing repository?

Yes, when repository access is available. It can assess dependencies, boundaries, architecture style, debt, and compliance.

Which diagram formats does it support?

It guides C4, UML, deployment, data-flow, and entity-relationship diagrams, primarily through Mermaid or PlantUML.

Does it make final technology decisions?

It recommends options and explains trade-offs. Project owners remain responsible for validation and final approval.

Can it create architecture decision records?

Yes. It structures context, status, decision, alternatives, consequences, and follow-up actions.

Will it deploy or modify production systems?

The architect role focuses on design and documentation. Tool-based commands or file changes require explicit authorization and review.

개발자 세부 정보

작성자

zl2023github

라이선스

MIT

Skillstore 리비전

버전 안내

작성자가 버전을 선언하지 않았습니다.

리포지토리

https://github.com/zl2023github/software-engineer-skills/tree/main/software-architecture/software-architect

참조

88a8e9a07f4c54ab105c1c41b6267c287146b07b

유지보수 최신성

2026. 7. 26.

사용량

5 다운로드 · 3 조회

파일 구조

📁 references/

📄 credit-ecommerce-architecture.md

📄 software-engineer-agents-overview.md

📄 SKILL.md