agentleFS
nuttakulsvnuttakulsv/think-like/skills/minds/SKILL.md

minds

Skill2 starsChanged 41 days agoMITView on GitHub

Index of the think-like pack: lists every great mind available, what each one makes the agent do, and which to pick for a given problem. Use when the user asks which mind to use, what minds are available, for help with think-like, or describes a problem and wants a recommendation. Triggers: "think-like help", "which mind", "list minds", "who should I ask", "what minds are there", "/minds", "มีใครบ้าง", "ควรใช้ใครดี", "รายชื่ออัจฉริยะ".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    When the user describes a problem, recommend one to three minds from the table and say why in one line each.

    line 18

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

think-like: the minds

Each mind is a skill that changes how the agent works: what it checks, in what order, and what it must produce. Invoke one by name ("think like Ohno", /think-like:ohno) or let the agent pick it up from the task. For important decisions use several at once with /think-like:council.

When the user describes a problem, recommend one to three minds from the table and say why in one line each. Answer in the user's language.

Understand and debug

MindMakes the agent…Use for
feynmanexplain in plain words, find the gap in understanding, test a predictionconfusing code, unexplained fixes
polyawrite down unknown, data and condition; solve a simpler case; look backbeing stuck after failed fixes
ohnocollect evidence, ask why until an actionable cause, add a countermeasureincidents, bugs that come back
shannontransform the problem six ways to find a new approach; separate signal from noiseno obvious approach, noisy alerts

Correctness and design

MindMakes the agent…Use for
dijkstrastate contracts and invariants, argue correctness before testingalgorithms, money, concurrency
liskovwrite the caller's contract, check every implementation can substituteinterfaces, inheritance, adapters
ousterhoutfind shallow modules and leaked knowledge, design it twicemodule and API design
hickeyfind complected concerns, push effects to the edges, prefer valuesstate, data models, tool choices
knuthsize the problem, analyze candidates, optimize only the critical partalgorithms, "is this fast enough"
einsteinlist assumptions, run thought experiments at the limitsdistributed systems, time, scale
teslabuild and run the whole system in the head before codingmulti-part features, migrations

Build and ship

MindMakes the agent…Use for
beckwork in red, green, refactor steps; tidy firstimplementing behavior safely
fowlername the smells, apply catalog refactorings in small stepsmessy code, cleanup
torvaldsread the diff, remove special cases, never break existing userscode review, public interfaces
carmackset a budget, measure, remove work, re-measureperformance
brooksseparate essential from accidental, count communication pathsestimates, staffing, rewrites

Decide

MindMakes the agent…Use for
muskquestion each requirement's owner, delete, simplify, speed up, then automatebloated specs and processes
bezoswrite the press release first, sort one-way and two-way doorsproduct decisions, slow decisions
mungerinvert, follow incentives, run a bias checklistrisky or expensive choices
kahnemanstart from the outside view, run a pre-mortem, give rangesestimates, confident plans
turingturn a vague question into a pass/fail procedurespecs, acceptance criteria, evals
socratesask the few questions that define the real requirementambiguous requests
hoppermake costs concrete, demo instead of debateconvincing stakeholders

Tools

SkillWhat it does
council3–5 minds review one decision and a synthesis names the trade-offs
mind-makerbuild a new mind skill from sources you provide

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.