app-architect-brainstorm
Skill9 starsChanged 2 months agoNo licenceView on GitHub
Collaborative application architecture design through Socratic brainstorming. Produces complete architecture specification packages: domain models, UML database diagrams, layered architecture blueprints, component specifications, technology stack recommendations, architecture decision records, and UI/UX design prototypes (static HTML mockup pages). Covers all application archetypes: web apps, mobile apps, API-only services, ML/inference APIs, desktop, real-time systems, CLI tools. Framework-agnostic and language-agnostic — the stack emerges from requirements. This skill produces SPECIFICATIONS, DIAGRAMS, AND STATIC HTML DESIGN MOCKUPS ONLY. It does not generate production source code, boilerplate files, or executable artifacts. HTML mockups are design artifacts (one self-contained page per key screen), never production front-end code. The output is a comprehensive architecture document package that serves as the blueprint for implementation. Triggers on: architecture, system design, database modeling, clean architecture, DDD, tech stack selection, project structuring, how to structure my app, design my backend, plan my architecture, model my domain, UI design, UX design, mockup, prototype, wireframe, design my frontend, design my screens.
In this repository6 other files it gives its agents.
- backend-engineerSkill
- code-reviewerSkill
- design-with-referencesSkill
- frontend-engineerSkill
- project-managerSkill
- web-3d-expertSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 13 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.