cunninghams-law
Skill6 starsChanged 34 days agoMITView on GitHub
Apply Cunningham's Law when someone wants to elicit information, feedback, or corrections from others—especially online. Trigger on phrases like "how do I get people to respond?", "nobody is answering my question", "I want to get feedback on this", or when someone is drafting a question for Stack Overflow, a forum, a team Slack, or a pull request. Also useful when discussing how to get a conversation started or surface hidden knowledge within a team. Cunningham's Law is a surprisingly powerful practical tool for anyone trying to learn or get unstuck.
In this repository79 other files it gives its agents.
- adr-phase-coverageSkill
- aposd-red-flag-reviewSkill
- apple-on-device-aiSkill
- artifact-gatesSkill
- asc-app-create-uiSkill
- asc-build-lifecycleSkill
- asc-cli-usageSkill
- asc-crash-triageSkill
- asc-id-resolverSkill
- asc-localize-metadataSkill
- asc-metadata-syncSkill
- asc-notarizationSkill
- asc-ppp-pricingSkill
- asc-release-flowSkill
- asc-revenuecat-catalog-syncSkill
- asc-shots-pipelineSkill
- asc-signing-setupSkill
- asc-submission-healthSkill
- asc-subscription-localizationSkill
- asc-testflight-orchestrationSkill
- asc-wall-submitSkill
- asc-workflowSkill
- asc-xcode-buildSkill
- choose-boring-technologySkill
- ci-preflightSkill
- conways-lawSkill
- cost-routingSkill
- cost-tier-routingSkill
- ddd-strategic-auditSkill
- ddd-tactical-reviewSkill
- debug-test-captureSkill
- developing-ios-appsSkill
- doerrs-lawSkill
- fitts-lawSkill
- fix-regression-guardSkill
- galls-lawSkill
- goodharts-lawSkill
- greenspuns-tenth-ruleSkill
- gsd-core-hooksSkill
- hofstadters-lawSkill
- hyrums-lawSkill
- ios-accessibilitySkill
- ios-simulator-boot-healthSkill
- kerckhoffs-principleSkill
- kernighans-lawSkill
- knuths-optimization-principleSkill
- lady-lovelaces-objectionSkill
- leaky-abstractionsSkill
- linuss-lawSkill
- mobile-ios-designSkill
- money-boundary-judgmentSkill
- moores-lawSkill
- no-deferSkill
- norvigs-lawSkill
- parkinsons-lawSkill
- peter-principleSkill
- postels-lawSkill
- post-fix-traceSkill
- qa-test-architectSkill
- rubber-duckSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Instead of: "Does anyone know how to configure Redis persistence?" Try: "I'm pretty sure you configure Redis persistence by editing …
- Distinctive: line 38
If a discussion stalls, propose something specific — even a deliberately imperfect proposal — to give people something to react to.
- Distinctive: line 42
Use this tool responsibly.
≈ “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
Cunningham's Law
"The best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer." — Ward Cunningham, ~1980 (attributed)
The core idea
People are more motivated to correct a wrong statement than to answer an open question. An open question requires someone to do mental work from scratch. A wrong answer hands them something concrete to push against — and people love pushing against wrong things.
This is counterintuitive but reliably true. It works in forums, in Slack, in code reviews, in design reviews, and in meetings.
Why it works
- Answering an open question requires generating content from nothing. That's cognitively expensive.
- Correcting a wrong answer requires only spotting the error and fixing it. That's easier and, frankly, more satisfying.
- There's a social element: correcting someone is a chance to demonstrate knowledge and be helpful simultaneously.
- The specificity of a wrong answer gives people a clear target. "Is X the right approach?" generates more engagement than "What approach should I take?"
How to apply it in practice
Getting answers in forums or Slack:
Instead of: "Does anyone know how to configure Redis persistence?"
Try: "I'm pretty sure you configure Redis persistence by editing redis.conf and setting appendonly no, right?"
The people who know will correct you immediately — and you'll get a better answer.
In code reviews and design docs: Post a draft with a specific (possibly wrong) implementation choice. People will engage much more energetically with a concrete proposal than with a blank page.
Surfacing team knowledge: If you want to know whether your team has experience with a technology, state a mildly wrong opinion about it: "I don't think anyone here has worked with Kafka before, so we'd be starting from scratch." You'll quickly find out if that's true.
Unsticking a meeting: If a discussion stalls, propose something specific — even a deliberately imperfect proposal — to give people something to react to. Blank-slate brainstorming is hard; critique is easy.
Ethical notes
Use this tool responsibly. Posting deliberately false information on public forums can spread misinformation if nobody corrects it. The law works best in settings where you can trust that knowledgeable people will engage, and where the stakes of an uncorrected wrong answer are low.
Key questions to surface
- What concrete (possibly wrong) statement could I make to invite correction?
- Is there a specific proposal I could draft — even a rough one — to give people something to react to?
- Am I asking an open question when I could be proposing an answer?
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.

