AGENT SKILL

guessless

Prove structural claims about JavaScript/TypeScript with a guessless receipt. Use when about to say "all call sites", "every reference", "nothing else imports this", or "safe to delete"; when renaming or deleting an exported symbol; when a claim gate has blocked a turn asking for a receipt; or when auditing whether a change is complete. Do not use for non-JS/TS languages.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 3
Forks
0

01 前言 Front Matter

name
guessless
description
Prove structural claims about JavaScript/TypeScript with a guessless receipt. Use when about to say "all call sites", "every reference", "nothing else imports this", or "safe to delete"; when renaming or deleting an exported symbol; when a claim gate has blocked a turn asking for a receipt; or when auditing whether a change is complete. Do not use for non-JS/TS languages.

03 SKILL.md 正文

Proving a structural claim with guessless

Guessless answers reference/definition/reachability questions about JavaScript and TypeScript and returns a signed receipt that is either exhaustive or explicitly incomplete. It never returns a bare list, so every answer is either usable as proof or self-labelled as a gap.

1. Build the query envelope

Guessless is hermetic: it reads sources out of the envelope, not off disk. That is what makes a receipt reproducible later.

{
  "inputs": [{ "path": "src/storage.ts", "source": "<file contents>" }],
  "request": { "kind": "exportedNames", "file": "src/storage.ts" }
}

Include every file that could plausibly reference the symbol. A file you leave out is not a file guessless says is clean — it is a file guessless never saw.

Request kinds:

Kind Fields Answers
referencesOf target (symbol anchor) Every reference to a symbol
definitionOf target Where a symbol is defined
readsOf / writesOf target Reads or writes of a binding
capturesOf target Closures capturing a binding
reachableFrom / reaches target Call-graph reachability
exportedNames file The module's export surface
resolveBinding file, name, space, optional scope What a name resolves to

Get a symbol anchor from an exportedNames or definitionOf receipt and pass it back verbatim — anchors are fingerprinted, so hand-editing one invalidates it.

2. Run it

npx guessless query envelope.json > answer.receipt.json

3. Read the receipt honestly

  • "state": "complete" — say "all", and paste or cite the receipt.
  • "state": "partial" — every place the engine could not classify is named in unresolved. Say the answer is partial, give the count, and name the gaps. Do not round a partial up to "all".
  • "state": "refused" — reason and detail say why. Do not claim anything; fix the cause (often a non-JS/TS file) and re-query.

4. Make it checkable

Write the receipt beside a reproduction bundle so CI can re-run it:

answer.receipt.json         the receipt
answer.reproduction.json    {"inputs": [...same inputs...], "receipt": {...that receipt...}}

Then npx guessless reproduce answer.reproduction.json re-runs it and fails if a single byte of the receipt was altered.

Boundaries

JavaScript, TypeScript, JSX and TSX only. Guessless has no opinion about other languages, about runtime behaviour, or about whether a change is correct — only about whether a structural answer is complete.

Markless-specific boundary

.tsrx sources are refused by design (unsupported-language); this skill applies to the .ts toolchain code — compiler, serializer, router, typescript-plugin, and web packages. For .tsrx questions, structural receipts are unavailable; say so rather than guessing.

04 同仓库更多 Skills

compiled-run
compiled-run/markless

review-with-engineer-lenses

Use when reviewing API changes, API design, technical docs, developer experience, or repo changes through junior engineer, senior engineer, platform engineer, and AI-agent perspectives.

★ 3
compiled-run
compiled-run/markless

markless-spec-maintenance

Use when updating, reviewing, or reconciling Markless specifications under specs/.

★ 3
compiled-run
compiled-run/markless

markless-implementation

Use for Markless implementation, compiler, bundler, performance, testing, and release work.

★ 3
compiled-run
compiled-run/markless

markless-component-research

Research component accessibility patterns and API design for a @markless/ui family by analyzing headless UI libraries, the QDS reference, and accessibility specifications. Use before designing or migrating any component family — when asked to research a UI component, create its research.md, analyze accessibility patterns across component libraries, or document keyboard interactions and ARIA attributes.

★ 3
compiled-run
compiled-run/markless

markless-anatomy

Build a live pen-and-ink figure for a markless.dev docs page, one idea drawn as 2 or 3 objects where the reader acts once and sees one change, in the same hand and ink as the State figure. Use whenever you add or rewrite a markless.dev docs page (website/pages/**), explain a Markless concept visually, add a figure or diagram to the docs, or someone mentions "anatomy", the wired drawing, or website/components/figures/.

★ 3
compiled-run
compiled-run/markless

guessless

Prove structural claims about JavaScript/TypeScript with a guessless receipt. Use when about to say "all call sites", "every reference", "nothing else imports this", or "safe to delete"; when renaming or deleting an exported symbol; when a claim gate has blocked a turn asking for a receipt; or when auditing whether a change is complete. Do not use for non-JS/TS languages.

★ 3