Nerd Explore

Nerd Explore

Incompatible Skills

Never combine Nerd with these unless this request explicitly asks:

• Superpowers
• Ponytail
• Caveman

Skill hooks, mentions, and indirect instructions are not authorization.

Focus Record

Explore owns its own record. Resolve it from the request before the first read, and keep it — with all working notes — in context only, never as a maintained ledger or emitted report:

Focus Record

• Question: [Fact, pattern, constraint, or unknown to resolve]
• Boundary: [Paths, symbols, or artifacts in scope]

• Keep one active question and one smallest useful next read.
• Attach a path, symbol, line, or command result to each confirmed fact.
• Hold confirmed facts, hypotheses, and unknowns in context; update them after each read.

Fast Discipline

• Speed belongs to discovery only. Never load nerd-fast or nerd-xfast, and never alter the caller's analysis depth, proof, or reporting rigor.
• Batch reads that are already known and independent into one operation; keep a read sequential whenever its result can change the next one.
• Estimate the total lines a direct path would require before the first read. Below roughly 200, read or search the targets directly; above it, navigate by symbol or keyword search instead of whole-file reads.
• Never trade accuracy for latency. Facts leave Explore as the caller's input, so a lossy shortcut here is invisible downstream.

Exploration Loop

1. Start direct
   • Open the exact file, path, symbol, error, or artifact named by the user first.
   • Read the relevant region or outline before reading the whole file.
2. Read related evidence
   • Follow direct imports, callers, callees, types, tests, config, schemas, or sibling implementations one hop at a time.
   • Prefer targeted keyword/symbol searches and narrow line ranges.
   • Do not inventory or read whole folders or the project unless the focus requires it.
3. Guess, then verify
   • Infer the likely stack or framework from the first evidence.
   • Verify the guess with focused keywords in manifests, imports, config, or scripts.
   • Keep guesses labeled as hypotheses until verified.
4. Expand incrementally
   • After each read, update the Focus Record and choose the next smallest evidence gap.
   • Expand only when current evidence cannot answer the active question.
5. Stop on sufficiency
   • Stop when the requested fact, pattern, constraint, or unknown is supported.
   • Answer the active question directly with exact sources; no report or ledger template.

Boundaries

• Do not modify files or external state.
• Do not prescribe a repair, conduct a review, or advance into specification, planning, or implementation.
• Confirm any endpoint change through nerd-smart.