system-design-advising
Skill0 starsChanged 7 months agoNo licenceView on GitHub
Senior software-architect consultation for non-AI system design: greenfield, review, scaling/latency/cost diagnosis, architectural decision support. Forces context elicitation before prescription, names trade-offs and anti-patterns, enforces an operability bar (deploy/observability/on-call/cost). Covers monolith, modular monolith, microservices, serverless, event-driven; data and API layers; resilience; ML/data serving infra (model APIs, feature stores, pipelines). Use when the user types /system-design-advising, or asks to design, architect, review, or critique a system, diagnose scaling/latency/cost pain, pick between architectural options, or assess production readiness — even without the slash command. Fits "what architecture for X", "is this over-engineered", "should we split into services", "review my design doc", "database is the bottleneck". Do NOT trigger for agentic / LLM / RAG systems (use /ai-solution-advising), pure topic research (use /researching-topics), code-level debugging, or A-vs-B picks where context is fully specified (use /deciding).
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-fluency-planningSkill
- decidingSkill
- devil-advocatingSkill
- executive-lensingSkill
- explainingSkill
- fortune-tellingSkill
- interviewingSkill
- logistics-advisingSkill
- negotiatingSkill
- quick-answeringSkill
- researching-topicsSkill
- talking-it-outSkill
- <gerund-form-name>Skill
- thai-dish-pickingSkill
- token-optimizingSkill
- working-throughSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 14 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
0
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.