Skills designing-architecture
📦
designing-architecture
Content revision r2 Safe ⚙️ External commands
Design a practical software architecture
Architecture decisions can become unclear when requirements, team skills, and future growth compete. This skill compares suitable patterns and helps document a clear, reasoned decision.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "designing-architecture" from https://skillstore.io/skills/cloudai-x-designing-architecture.md and its manifest at https://skillstore.io/api/skills/cloudai-x-designing-architecture/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.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "designing-architecture". Recommend an architecture for a medium-sized application with complex business rules.
Expected outcome:
- Recommended pattern: Clean Architecture.
- Reason: It separates business rules from framework and database details.
- Trade-off: It requires more initial structure and discipline than a layered design.
Using "designing-architecture". Help document a choice between a modular monolith and microservices.
Expected outcome:
- Context: The team needs independent modules but has limited operational capacity.
- Decision: Start with a modular monolith.
- Consequence: Define strict module boundaries and reconsider service extraction when operational needs justify it.
Security Audit
Safev9 • 7/18/2026 Open versioned report
All 19 static findings are false positives. The analyzer interpreted Markdown code fences in SKILL.md as shell backticks, but the file contains only architecture guidance, diagrams, checklists, and a documentation template. No executable commands, prompt injection, secret handling, or data-exfiltration intent was found.
1
Files scanned
230
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (19)
SKILL.md:17-25 SKILL.md:25-49 SKILL.md:49-59 SKILL.md:59-65 SKILL.md:65-78 SKILL.md:78-84 SKILL.md:84-99 SKILL.md:99-105 SKILL.md:105-111 SKILL.md:111-117 SKILL.md:117-129 SKILL.md:129-137 SKILL.md:137-156 SKILL.md:156-160 SKILL.md:160-167 SKILL.md:167-183 SKILL.md:183-211 SKILL.md:211-217 SKILL.md:217-227
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: claude View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/cloudai-x-designing-architecture/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cloudai-x-designing-architecture?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cloudai-x-designing-architecture?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cloudai-x-designing-architecture/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cloudai-x-designing-architecture.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
CloudAI-X. (2026). designing-architecture security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cloudai-x-designing-architecture/audits/9BibTeX citation
@techreport{cloudai-x-cloudai-x-designing-architecture-2026,
author = {CloudAI-X},
title = {designing-architecture security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/cloudai-x-designing-architecture/audits/9},
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: "designing-architecture security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "CloudAI-X"
date-released: "2026-07-18"
url: "https://skillstore.io/skills/cloudai-x-designing-architecture/audits/9"
identifiers:
- type: other
value: "skillstore:cloudai-x-designing-architecture:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
71
Community
83
Spec Compliance
What You Can Build
Plan a new product foundation
Compare a modular monolith with other patterns before a small product team begins implementation.
Document an architecture decision
Record options, trade-offs, and consequences for a system change in a consistent format.
Choose a project structure
Select a feature-based or layer-based directory layout that fits a growing application.
Try These Prompts
Choose a simple starting pattern
I am building a small CRUD web application with three developers. Recommend an architecture pattern and explain why.
Compare two approaches
Compare a modular monolith and microservices for an e-commerce platform with a team of eight developers. Include trade-offs.
Create a decision record
Create an architecture decision record for choosing clean architecture in a long-lived billing service. Include context, options, trade-offs, decision, and consequences.
Validate a proposed design
Evaluate this proposed event-driven architecture against team skills, testing needs, module boundaries, scalability, and operational complexity: [describe the system].
Best Practices
- Start with the simplest design that meets current requirements.
- Document assumptions, alternatives, and consequences with every major decision.
- Validate the proposed design with developers who will build and maintain it.
Avoid
- Choosing microservices only because they are popular.
- Copying an architecture without considering team skills and operational capacity.
- Treating an architecture decision as permanent when requirements change.
Frequently Asked Questions
What architecture patterns does this skill cover?
It covers layered, clean, hexagonal, event-driven, CQRS, modular monolith, and microservice approaches.
Can it choose an architecture without project details?
It can provide a starting point, but project size, requirements, team skills, and constraints improve recommendations.
Does it recommend microservices by default?
No. It recommends starting simply and using microservices only when the benefits justify their added complexity.
Can it help create an architecture decision record?
Yes. It includes a template for documenting context, options, trade-offs, decisions, and consequences.
Does it generate a directory structure?
It provides feature-based and layer-based examples that you can adapt to your application.
Does it replace an architecture review?
No. Use its guidance as input to an engineering review with relevant stakeholders.