share-learning
Skill4 starsChanged 3 days agoMITView on GitHub
Record a non-obvious bug, useful pattern, or edge case into the project's AGENTS.md self-evolving learnings log. Use when you hit a WordPress/library gotcha that another session or teammate's agent would benefit from knowing. Keeps knowledge in the repo, not in a forgotten chat.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- darkroomengineering/cc-settingstheir own version, first seen Sep 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- darkroomengineering/cc-settings★ 52same 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 repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- diagnosing-bugsSkill
- domain-modelingSkill
- fixSkill
- frontend-designSkill
- grill-meSkill
- grill-with-docsSkill
- gsap-coreSkill
- gsap-performanceSkill
- gsap-pluginsSkill
- gsap-scrolltriggerSkill
- gsap-timelineSkill
- gsap-utilsSkill
- handoffSkill
- landing-page-conversion-auditSkill
- refactorSkill
- researchSkill
- reviewSkill
- tddSkill
- threejs-animationSkill
- threejs-fundamentalsSkill
- threejs-geometrySkill
- threejs-interactionSkill
- threejs-lightingSkill
- threejs-loadersSkill
- threejs-materialsSkill
- threejs-postprocessingSkill
- threejs-shadersSkill
- threejs-texturesSkill
- to-specSkill
- to-ticketsSkill
- verifySkill
- wp-accessibilitySkill
- wp-accessibility-standardsSkill
- wp-css-standardsSkill
- wp-github-actions-standardsSkill
- wp-html-standardsSkill
- wp-i18nSkill
- wp-js-standardsSkill
- wp-performanceSkill
- wp-php-standardsSkill
- wp-pluginSkill
- wp-security-auditSkill
- wp-themeSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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 36
Keep entries terse and factual — one line each.
- Distinctive: line 40
If another project's agent would benefit, log it — the log is the team knowledge surface
- Distinctive: line 42
Prefer the log over prose: one line beats a paragraph for retrieval
- Distinctive: line 43
If the entry contradicts an existing one, flag the conflict rather than overwriting silently
≈ “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.
Files
Share-Learning — Knowledge Routing
The learnings log is the debt you pay down for the next engineer (human or agent). One line per entry, dated, factual.
When to log
- A non-obvious bug and its root cause (e.g. "Vite
basemust be the absolute theme URL or font URLs 404") - A WordPress gotcha that cost time (e.g. "wp_enqueue_script strategy defer + module rewrite must happen via script_loader_tag")
- A convention the team must follow (e.g. "all template output is escaped at echo time")
- A library integration pattern (Lenis + Tempus order, GSAP context cleanup)
When NOT to log
- Personal workflow preferences → auto-memory
- Project state/deadlines → auto-memory (project)
- Anything already documented
Format
Append under ## Self-Evolving Learnings in the project's AGENTS.md:
- [2026-08-04] vite: manifest entry CSS must be enqueued with the hashed path or fonts 404
- [2026-08-04] wordpress: check_admin_referer dies with 403 — verify before the expensive workCategories: wordpress, php, security, gsap, lenis, vite, tailwind, build, tooling. Keep entries terse and factual — one line each.
Rules
- If another project's agent would benefit, log it — the log is the team knowledge surface
- Prefer the log over prose: one line beats a paragraph for retrieval
- If the entry contradicts an existing one, flag the conflict rather than overwriting silently
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.