scenario
Skill1 starsChanged 44 days agoLicence not identifiedView on GitHub
Find the edge cases a feature will meet before it is built: decompose it across 12 dimensions (user types, input extremes, timing, scale, state, environment, failures, authorization, data integrity, integrations, compliance, business rules) and turn the dangerous ones into test anchors. Use before implementing anything stateful, multi-user, money- or auth-related, when the user asks \"what could go wrong\", \"what edge cases\", \"what should we test\", or when `plan` runs with --tdd or classifies a change as high-risk. Flags: --saturation (keep going until no new cases appear), --focus DIMENSION.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- scenario-labs/skillstheir own version, first seen Nov 7, 2026
- Holojerm/drawthesystemtheir own version, first seen Oct 11, 2026
- caoergou/windows-xptheir own version, first seen Oct 8, 2026
- ffroliva/gflow-clitheir own version, first seen Sep 14, 2026
- b-urge/scenario-skilltheir own version, first seen Jun 15, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- scenario-labs/skills★ 3.5ksame name
- ffroliva/gflow-cli★ 367same name
- caoergou/windows-xp★ 5same name
- b-urge/scenario-skill★ 1same name
- Holojerm/drawthesystem★ 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 repository13 other files it gives its agents.
- skillsSkill
- brainstormSkill
- cicdSkill
- cookSkill
- design-taste-frontendSkill
- fixSkill
- frontend-mindsetSkill
- minimalist-uiSkill
- planSkill
- problem-solvingSkill
- skill-creatorSkill
- specSkill
- sumupSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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.