add-lens
Skill1 starsChanged 37 days agoMITView on GitHub
Add a new engineering lens (skill) to TheCouncil and register it everywhere it must appear.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- redis/agent-skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- redis/agent-skills★ 174same 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 repository19 other files it gives its agents.
- dhh-majestic-monolithSkill
- fowler-evolutionary-designSkill
- ousterhout-deep-modulesSkill
- uncle-bob-solid-orthodoxSkill
- kleppmann-data-contractsSkill
- lamport-state-invariantsSkill
- carmack-inlined-executionSkill
- danluu-empirical-systemsSkill
- muratori-data-orientedSkill
- armstrong-fault-isolationSkill
- ask-councilSkill
- djb-isolated-privilegeSkill
- hickey-simple-valuesSkill
- antirez-pragmatic-cSkill
- bellard-autonomous-engineSkill
- cantrill-observability-firstSkill
- pike-unix-minimalismSkill
- stenberg-defensive-cSkill
- king-type-driven-designSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Add the lens $ARGUMENTS. Categories in use: architecture, distributed, formal, performance, resilience, security, state, systems, types, …
- Very specific: line 10
Read one existing skills/<category>/*/SKILL.md in the same category and match its structure, tone and length.
- Very specific: line 17
Update the seat count ("18") in README, INSTALL.md, package.json, plugin.json, gemini-extension.json, .claude-plugin/*.json and …
- Very specific: line 18
If an existing lens conflicts with the new one, add the new slug to that lens's conflicts_with too.
- Very specific: line 19
Run python3 scripts/check-manifests.py and fix every error.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Add the lens $ARGUMENTS. Categories in use: architecture, distributed, formal, performance, resilience, security, state, systems, types, router.
- Read one existing
skills/<category>/*/SKILL.mdin the same category and match its structure, tone and length. - Create
skills/<category>/<slug>/SKILL.md. Required frontmatter:name(equals the directory name),description,triggers(JSON list),conflicts_with(JSON list ofcategory/slug),primary_sources(title + url, real sources only). Required sections, in order: an**Apply**paragraph copied verbatim from a sibling lens (directly under the H1), then Core Philosophy & Deliberate Rejections, Hard Implementation Rules, Code Review Checklist, Canonical Idiom. Writedescriptionas the lens's leading concept followed byUse when ...branches. - Register it:
.claude-plugin/plugin.json: add./skills/<category>/<slug>toskills, keep alphabetical order.skills/registry.json: add an entry toskillswithname,path,category,author, and the sametriggers,conflicts_with,primary_sourcesas the SKILL.md.skills/registry.jsonconflict_matrix: add a pair for each real conflict (tension, thesis_a, thesis_b).README.md: add a row to the seats table, a line to the layout tree, and the author's works to Primary Engineering Works.- Update the seat count ("18") in README, INSTALL.md,
package.json,plugin.json,gemini-extension.json,.claude-plugin/*.jsonandregistry.jsondescriptions. - If an existing lens conflicts with the new one, add the new slug to that lens's
conflicts_withtoo.
- Run
python3 scripts/check-manifests.pyand fix every error. Report warnings you did not fix.
Cite only sources you have verified. Write plain prose.
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.

