prior-art
Skill0 starsChanged 7 days agoMITView on GitHub
Spike a topic in its prior art and first principles before a PRD session. Surfaces the established primitives, canonical prior work, and the one essential mechanism for a context/topic.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Mattie/mattie_skillstheir own version, first seen Nov 8, 2026
- damacus/agent-skillstheir own version, first seen Oct 29, 2026
- crsmithdev/alephtheir own version, first seen Oct 15, 2026
- Timi-Fish/chinese-pm-skillstheir own version, first seen Oct 15, 2026
- runxhq/runxtheir own version, first seen Oct 13, 2026
- dylanpulver/prior-arttheir own version, first seen Jul 20, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- runxhq/runx★ 97same name
- damacus/agent-skills★ 2same name
- Mattie/mattie_skills★ 1same name
- crsmithdev/aleph★ 0same name
- dylanpulver/prior-art★ 0same name
- Timi-Fish/chinese-pm-skills★ 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 repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- capture-componentSkill
- digest-videoSkill
- no-visual-diffSkill
- pr-createSkill
- pr-feedbackSkill
- pr-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Stop there - this primes the PRD session, it does not start it.
“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.
Files
For the topic I name, gather the prior art before we design: the foundational primitives, the canonical prior work (papers, standards, named patterns) and the industry-standard vocabulary for each, how the best existing systems structure this space, and their known trade-offs and failure modes. Prefer established sources over invention - search the web, cite what you find, and use the standard name for every concept, never a coined one.
Then give me a one-screen primer: the 3-5 load-bearing primitives, the single essential mechanism the whole design should turn on, the main design axes (with the prevailing default on each), and the traps to avoid.
Stop there - this primes the PRD session, it does not start it. Do not propose a design or a plan yet.
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.