solution-design
Skill0 starsChanged 4 months agoMITView on GitHub
Use when translating approved requirements into a solution design, architecture fit, risks, and test strategy.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- anotb/forward-deployedtheir own version, first seen Nov 8, 2026
- seanforge/skillstheir own version, first seen Oct 15, 2026
- vekzz-dev/opencode-skillstheir own version, first seen Oct 13, 2026
- TeqfocusAdmin/ClaudeSkillsRepotheir own version, first seen Sep 22, 2026
- tony-adamson/groundworktheir own version, first seen Jul 15, 2026
- tmwgsicp/vibecoding-for-beginnerstheir own version, first seen May 31, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- tmwgsicp/vibecoding-for-beginners★ 42same name
- tony-adamson/groundwork★ 4same name
- vekzz-dev/opencode-skills★ 4same name
- anotb/forward-deployed★ 1same name
- seanforge/skills★ 1same name
- TeqfocusAdmin/ClaudeSkillsRepo★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- branch-safelySkill
- deployment-decisionsSkill
- deploySkill
- deploy-vercelSkill
- deploy-vpsSkill
- documentationSkill
- e2e-testingSkill
- feature-testingSkill
- monitoringSkill
- orchestrateSkill
- quality-reviewSkill
- requirements-gatheringSkill
- task-breakdownSkill
- ui-uxSkill
- unit-testingSkill
The file
Files
Solution Design
Prefer the smallest design consistent with the approved first feature and existing architecture. Propose a simple stack and lightweight implementation plan only for that feature, with necessary interfaces, data implications, risks, tradeoffs, and proportionate test strategy in plan.md. The test strategy must specify which test levels apply (unit, feature, end-to-end), what each covers, and how the developer will verify them. For a bug fix, the plan must include regression tests at all applicable levels before the fix. Keep future ideas short and non-binding. Do not add infrastructure, services, abstractions, or modules unless required. Escalate unresolved irreversible, security, cost, privacy, or credential decisions.
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.