Designing Architecture
CheckedThis skill generates architectural designs based on your prompts, offering a quick and creative starting point for projects.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add cloudai-x/claude-workflow-v2 --skill designing-architecture -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
cloudai-x
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned cloudai-x/claude-workflow-v2 at 4c242af16f.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 4c242af16f
- Scanned
- 1 file, 210 lines
About this skill
What it does
This skill helps AI agents generate architectural designs for software projects. It provides a starting point by suggesting appropriate architecture patterns and directory structures based on project size, team capabilities, and other factors. The tool guides through a structured design process, including understanding requirements, assessing project scope, selecting patterns, defining structure, documenting decisions, and validating against established frameworks.
When to use it
This skill is useful in the following scenarios:
- Starting a new software project requiring architectural planning.
- Designing module structures for existing projects.
- Choosing appropriate architecture patterns (e.g., MVC/Layered, Clean Architecture, Microservices).
- Defining directory structures for codebases.
- When needing guidance on trade-offs and decision making in architectural design.
Key capabilities
- Suggests architecture patterns based on project size (Small, Medium, Large) and team size (1-3 developers, 4-10 developers, 10+ developers).
- Provides examples of common architectural patterns: Layered Architecture, Clean Architecture, Hexagonal Architecture (Ports & Adapters), Event-Driven Architecture, and CQRS.
- Offers a recommended feature-based directory structure pattern for medium to large projects.
- Includes a checklist to guide the architecture design workflow.
Example prompts
- "Suggest an architecture pattern for a small project with a team of 2 developers."
- "What's a good directory structure for a medium-sized application?"
- "Explain the benefits and drawbacks of Clean Architecture compared to Layered Architecture."
- “I need to design a system that needs to swap external dependencies easily. What architecture pattern should I consider?”
Tips & gotchas
- The skill is intended as a starting point, not a complete solution. Further refinement and customization will likely be needed.
- Consider the trade-offs associated with each suggested pattern before implementation.
- Project size is defined by lines of code (<10K LOC, 10K-100K LOC, >100K LOC).