Architecture decisions often remain scattered across requirements, discussions, and diagrams. This skill organizes them into consistent Markdown documents for implementation and review.
Review the Skillstore skill "arch-doc-generation" from https://skillstore.io/skills/zl2023github-arch-doc-generation.md and its manifest at https://skillstore.io/api/skills/zl2023github-arch-doc-generation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
正在使用“arch-doc-generation”。 Document the architecture for a multi-region order platform with strict availability requirements.
预期结果:
A structured Markdown specification covering system context, service responsibilities, data ownership, regional failover, recovery objectives, monitoring, security, tradeoffs, and architecture decisions.
正在使用“arch-doc-generation”。 Create an API design for an inventory reservation service.
预期结果:
An API document defining authentication, resource models, reservation operations, idempotency, concurrency behavior, pagination, error handling, and representative request flows.
正在使用“arch-doc-generation”。 Prepare a technical proposal for replacing scheduled synchronization with events.
预期结果:
A proposal comparing synchronization approaches, selecting event-driven integration, describing topics and consumers, planning migration stages, and recording delivery risks.
All nine static findings are false positives. Eight findings identify Markdown fences or inline code, while the entropy heuristic reflects readable Chinese documentation and structured templates. No executable commands, obfuscated content, prompt injection, or other semantic security issues were found.
zl2023github. (2026). arch-doc-generation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-arch-doc-generation/audits/4
BibTeX 引用
@techreport{zl2023github-zl2023github-arch-doc-generation-2026,
author = {zl2023github},
title = {arch-doc-generation security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zl2023github-arch-doc-generation/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: "arch-doc-generation security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "zl2023github"
date-released: "2026-07-24"
url: "https://skillstore.io/skills/zl2023github-arch-doc-generation/audits/4"
identifiers:
- type: other
value: "skillstore:zl2023github-arch-doc-generation:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore 评分
评分依据证据置信度: 中
41
架构
85
可维护性
87
内容
65
社区
83
规范符合性
你能构建什么
Prepare a system design review
Convert project requirements and constraints into a structured architecture document for stakeholder review.
Define a service API
Document endpoint conventions, authentication, resources, request behavior, responses, and error handling.
Plan a production deployment
Describe topology, availability, recovery, observability, security controls, and operational risks before release.
试试这些提示
Create a basic architecture outline
Create a Markdown architecture outline for {{system_name}}. Include background, scope, key modules, data storage, deployment, security, and open questions.
Draft an API design document
Write an API design document for {{service_name}}. Cover protocol, authentication, versioning, resources, endpoint behavior, pagination, errors, and example interactions.
Develop a technical proposal
Develop a technical proposal for {{initiative}} using these requirements: {{requirements}}. Compare options, explain decisions, map core flows, identify risks, and propose delivery stages.
Produce a complete architecture specification
Produce a review-ready architecture specification for {{system_name}} using {{context}}. Include C4 descriptions, module contracts, data flows, deployment, security, reliability targets, tradeoffs, ADRs, and unresolved decisions.
最佳实践
Provide business goals, scope, constraints, expected scale, and existing technology before requesting a document.
Separate confirmed decisions from assumptions, alternatives, and unresolved questions.
Review generated security, reliability, and operational claims with responsible specialists.
避免
Do not present placeholders or inferred details as approved architecture decisions.
Do not request a complete design without supplying system boundaries and measurable requirements.
Do not treat generated diagrams or examples as proof that an implementation meets its targets.
常见问题
Which document types can this skill create?
It supports architecture specifications, technical proposals, API design documents, and deployment architecture documents.
What output format does it use?
It produces structured Markdown with headings, tables, placeholders, examples, and decision records.
Can it generate a PDF?
No. Use a separate PDF generation skill after the Markdown content is complete.
What information should I provide?
Provide goals, scope, users, constraints, expected scale, current systems, technology preferences, and known decisions.
Does it verify architecture feasibility?
No. Engineers must validate assumptions, capacity estimates, security controls, and operational procedures.
Can it document an existing system?
Yes. Supply accurate module, interface, data, deployment, and operational details for the current system.