agentleFS
saint0xsaint0x/my-skills/lamp-method-first-principles-thinking/SKILL.md

lamp-method-first-principles-thinking

Skill1 starsChanged 3 months agoMITView on GitHub

Use when the user wants first-principles analysis, conceptual reframing, hidden-assumption discovery, research-direction synthesis, or a falsifiable thesis for a complex question. Especially useful for strategy, systems design, research positioning, product direction, contradiction analysis, and abstraction discovery.

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. About 0 are common, 20 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈20

    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:

    Use this skill when the task is to discover the right abstraction, not just produce the next local answer.

    line 8
  2. Distinctive:

    Never confuse the second for the first.

    line 19
  3. Distinctive:

    Every important discovery can become the lamp that reveals another.

    line 33
  4. Distinctive:

    Ask what larger system must exist if the observation is true.

    line 44
  5. Distinctive:

    Prefer the stronger abstraction over attachment to the current framing.

    line 46
  6. Distinctive:

    Do not only search for answers.

    line 52
  7. Distinctive:

    Do not ask, "Is this idea correct?" as a single question.

    line 66
  8. Distinctive:

    Do not accept them uncritically.

    line 83
  9. Distinctive:

    Before searching for a better answer, search for:

    line 106
  10. Distinctive:

    Never study an isolated object when the real behavior belongs to a system.

    line 118
  11. Distinctive:

    When one discovery appears, ask:

    line 122
  12. Distinctive:

    Do not rely on intuition alone.

    line 132
  13. Distinctive:

    Every interesting hypothesis should become the smallest experiment capable of disproving it.

    line 134
  14. Distinctive:

    When useful, structure the answer around:

    line 142
  15. Distinctive:

    Do not overclaim from narrow evidence.

    line 158
  16. Distinctive:

    Do not confuse an implementation, convention, or current practice with a first principle.

    line 159
  17. Distinctive:

    Do not preserve old framing if evidence points to a better layer.

    line 160
  18. Distinctive:

    Treat invalidated beliefs as progress.

    line 161
  19. Distinctive:

    Prefer questions that expand the research program over conclusions that prematurely close it.

    line 162
  20. Distinctive:

    When external facts may have changed, verify them with the best available current source before relying on them.

    line 163

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

LAMP Method First Principles Thinking

Use this skill when the task is to discover the right abstraction, not just produce the next local answer.

The LAMP Method treats a surprising observation as a lamp: it is not the discovery itself, but it illuminates assumptions, contradictions, and adjacent territory worth investigating.

Core Idea

Everything humans build exists in two layers:

  • Reality: physics, mathematics, information, energy, time, probability, causality, and evidence.
  • Interpretation: conventions, institutions, software, economics, organizations, traditions, best practices, accepted wisdom, and historical accidents.

Never confuse the second for the first. Many constraints people experience are interpretations rather than physical necessities.

First-principles thinking separates the two.

The Lamp

Brilliant ideas rarely appear fully formed. They often begin as small observations.

These observations are lamps.

The lamp is not the discovery. It illuminates previously unseen territory.

Most people notice the lamp and stop. The method is to keep walking.

Every important discovery can become the lamp that reveals another. Do not stop at the first answer when the observation points to a deeper structure.

Workflow

  1. Separate reality from interpretation.
  2. Identify the lamp: the observation that revealed new territory.
  3. List contradictions between expectation, evidence, and constraints.
  4. Decompose the idea into independent claims.
  5. Mark each claim as proven, unproven, speculative, or likely false.
  6. Ground the analysis with available evidence. Use web search, literature search, official documentation, source-provided materials, local files, or domain databases as appropriate to the environment and task.
  7. Change coordinate systems if the current framing is too local, too inherited, or too implementation-shaped.
  8. Ask what larger system must exist if the observation is true.
  9. Convert the insight into falsifiable next experiments.
  10. Prefer the stronger abstraction over attachment to the current framing.

Reasoning Moves

Chase Contradictions

Do not only search for answers. Search for contradictions.

Whenever reality and expectation disagree, stop. That disagreement is valuable because it reveals hidden assumptions.

Ask:

  • What assumption must be false for this contradiction to exist?
  • Which part of the current explanation fails?
  • Is the contradiction caused by evidence, interpretation, measurement, incentives, or language?

Decompose Everything

Large ideas should be decomposed.

Do not ask, "Is this idea correct?" as a single question.

Ask:

  • Which pieces are correct?
  • Which pieces are incorrect?
  • Which pieces are unknown?
  • Which pieces are useful even if the original framing is wrong?

Almost every idea contains a mixture of signal and noise. Extract the signal. Discard the noise.

Search Outside The Distribution

Novel ideas rarely originate entirely inside mainstream thinking.

Deliberately inspect ideas that are unusual, unconventional, unfashionable, incomplete, poorly articulated, speculative, or outside the dominant frame.

Do not accept them uncritically. Do not dismiss them reflexively. Disassemble them.

Ask:

  • What percentage of value exists here?
  • Which claim survives contact with evidence?
  • What does this framing see that conventional framing misses?
  • What does conventional framing correctly reject?

The goal is not to believe unusual ideas. The goal is to recover valuable structure when it exists.

Stay Grounded

Imagination without reality becomes fantasy. Reality without imagination becomes incrementalism.

Operate between the two.

Ground conclusions in evidence whenever possible. Use imagination to generate hypotheses. Use experiments and evidence to eliminate them.

Change Coordinate Systems

Many difficult problems become easier when represented differently.

Before searching for a better answer, search for:

  • a better question
  • a better representation
  • a better coordinate system
  • a better unit of analysis
  • a better timescale

Sometimes the discovery is not the solution. It is the language that makes the solution obvious.

Think In Systems

Never study an isolated object when the real behavior belongs to a system.

Everything exists within relationships. Changing one assumption often changes surrounding assumptions.

When one discovery appears, ask:

  • What else must change if this is true?
  • Which incentives, constraints, interfaces, or feedback loops move with it?
  • Does the local observation imply a larger system-level pattern?

Often the real discovery emerges from interactions.

Build Small Experiments

Do not rely on intuition alone.

Every interesting hypothesis should become the smallest experiment capable of disproving it.

Design experiments that attempt to destroy the idea. Ideas that survive repeated attempts to falsify them become more valuable.

Reality is the final judge.

Output Shape

When useful, structure the answer around:

  • Reality
  • Interpretation
  • Contradictions
  • What The Lamp Reveals
  • Better Abstraction
  • What Is Proven
  • What Is Still Unknown
  • Next Experiments
  • Honest Thesis

Adapt the headings when the user asks for a different format, but preserve the underlying reasoning discipline.

Guardrails

  • Do not overclaim from narrow evidence.
  • Do not confuse an implementation, convention, or current practice with a first principle.
  • Do not preserve old framing if evidence points to a better layer.
  • Treat invalidated beliefs as progress.
  • Prefer questions that expand the research program over conclusions that prematurely close it.
  • When external facts may have changed, verify them with the best available current source before relying on them.

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.