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.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
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.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 "arch-doc-generation". Document the architecture for a multi-region order platform with strict availability requirements.
Expected outcome:
A structured Markdown specification covering system context, service responsibilities, data ownership, regional failover, recovery objectives, monitoring, security, tradeoffs, and architecture decisions.
Using "arch-doc-generation". Create an API design for an inventory reservation service.
Expected outcome:
An API document defining authentication, resource models, reservation operations, idempotency, concurrency behavior, pagination, error handling, and representative request flows.
Using "arch-doc-generation". Prepare a technical proposal for replacing scheduled synchronization with events.
Expected outcome:
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.
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-arch-doc-generation/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/zl2023github-arch-doc-generation?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/zl2023github-arch-doc-generation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zl2023github-arch-doc-generation/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/zl2023github-arch-doc-generation.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). arch-doc-generation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-arch-doc-generation/audits/4@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}
}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"
Convert project requirements and constraints into a structured architecture document for stakeholder review.
Document endpoint conventions, authentication, resources, request behavior, responses, and error handling.
Describe topology, availability, recovery, observability, security controls, and operational risks before release.
Create a Markdown architecture outline for {{system_name}}. Include background, scope, key modules, data storage, deployment, security, and open questions.Write an API design document for {{service_name}}. Cover protocol, authentication, versioning, resources, endpoint behavior, pagination, errors, and example interactions.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 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.Author
zl2023githubLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Maintenance freshness
7/26/2026
Usage
2 downloads · 0 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.
Build Reliable Data Pipelines and Warehouses
Data teams need dependable pipelines across fragmented platforms. This skill designs implementation-ready batch, streaming, modeling, orchestration, and quality workflows.
Create Clear C4 Architecture Diagrams
by Consiliency
Architecture discussions become confusing when diagrams mix detail levels or omit relationships. This skill creates structured C4 views and reviews them against consistent guidelines.
Create Mermaid Diagrams for Software Documentation
by softaworks
Teams often need clear diagrams that stay close to code and documentation. This skill guides Claude, Codex, and Claude Code through Mermaid syntax for maintainable visual models.
Write Evidence-Based Wiki Pages
by sickn33
Technical docs often drift from implementation details. This skill guides Claude, Codex, and Claude Code to write cited wiki pages with diagrams.
Build FastAPI APIs with Reusable Patterns
by 0xDarkMatter
FastAPI projects need consistent choices for validation, dependencies, middleware, and background work. This skill gives Claude, Codex, and Claude Code reusable patterns for practical Python API development.
Design Production-Ready APIs
by AutumnsGrove
Inconsistent API contracts create integration errors and costly migrations. This skill guides REST, GraphQL, OpenAPI, authentication, versioning, validation, and documentation decisions.
Build Reliable Backend APIs
by alirezarezvani
Backend projects often need consistent planning across APIs, databases, security, and deployment. This skill gives Claude, Codex, and Claude Code structured backend guidance with simple helper scripts and references.