[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77Z3KF69G2YZVPC0ED1AC1J":3,"skill-same:01M77Z3KF69G2YZVPC0ED1AC1J":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77Z3KF69G2YZVPC0ED1AC1J","guessless",null,"Prove structural claims about JavaScript\u002FTypeScript 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\u002FTS languages.","compiled-run\u002Fmarkless","compiled-run","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F312797118?v=4","01M77Z248Q9PCPK92HPHM6X174","Compiled.Run","01M77Z249DKAP6PE0Y5CNFSSMM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fcompiled-run\u002Fmarkless\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fguessless\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: guessless\ndescription: Prove structural claims about JavaScript\u002FTypeScript 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\u002FTS languages.\n---\n\n# Proving a structural claim with guessless\n\nGuessless answers reference\u002Fdefinition\u002Freachability questions about JavaScript and TypeScript and\nreturns a signed receipt that is either exhaustive or explicitly incomplete. It never returns a bare\nlist, so every answer is either usable as proof or self-labelled as a gap.\n\n## 1. Build the query envelope\n\nGuessless is hermetic: it reads sources out of the envelope, not off disk. That is what makes a\nreceipt reproducible later.\n\n```json\n{\n  \"inputs\": [{ \"path\": \"src\u002Fstorage.ts\", \"source\": \"\u003Cfile contents>\" }],\n  \"request\": { \"kind\": \"exportedNames\", \"file\": \"src\u002Fstorage.ts\" }\n}\n```\n\nInclude every file that could plausibly reference the symbol. A file you leave out is not a file\nguessless says is clean — it is a file guessless never saw.\n\nRequest kinds:\n\n| Kind | Fields | Answers |\n| --- | --- | --- |\n| `referencesOf` | `target` (symbol anchor) | Every reference to a symbol |\n| `definitionOf` | `target` | Where a symbol is defined |\n| `readsOf` \u002F `writesOf` | `target` | Reads or writes of a binding |\n| `capturesOf` | `target` | Closures capturing a binding |\n| `reachableFrom` \u002F `reaches` | `target` | Call-graph reachability |\n| `exportedNames` | `file` | The module's export surface |\n| `resolveBinding` | `file`, `name`, `space`, optional `scope` | What a name resolves to |\n\nGet a symbol anchor from an `exportedNames` or `definitionOf` receipt and pass it back verbatim —\nanchors are fingerprinted, so hand-editing one invalidates it.\n\n## 2. Run it\n\n```bash\nnpx guessless query envelope.json > answer.receipt.json\n```\n\n## 3. Read the receipt honestly\n\n- `\"state\": \"complete\"` — say \"all\", and paste or cite the receipt.\n- `\"state\": \"partial\"` — every place the engine could not classify is named in `unresolved`. Say the\n  answer is partial, give the count, and name the gaps. Do not round a partial up to \"all\".\n- `\"state\": \"refused\"` — `reason` and `detail` say why. Do not claim anything; fix the cause (often a\n  non-JS\u002FTS file) and re-query.\n\n## 4. Make it checkable\n\nWrite the receipt beside a reproduction bundle so CI can re-run it:\n\n```\nanswer.receipt.json         the receipt\nanswer.reproduction.json    {\"inputs\": [...same inputs...], \"receipt\": {...that receipt...}}\n```\n\nThen `npx guessless reproduce answer.reproduction.json` re-runs it and fails if a single byte of\nthe receipt was altered.\n\n## Boundaries\n\nJavaScript, TypeScript, JSX and TSX only. Guessless has no opinion about other languages, about\nruntime behaviour, or about whether a change is *correct* — only about whether a structural answer\nis complete.\n\n## Markless-specific boundary\n\n`.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.\n","# Proving a structural claim with guessless\n\nGuessless answers reference\u002Fdefinition\u002Freachability questions about JavaScript and TypeScript and\nreturns a signed receipt that is either exhaustive or explicitly incomplete. It never returns a bare\nlist, so every answer is either usable as proof or self-labelled as a gap.\n\n## 1. Build the query envelope\n\nGuessless is hermetic: it reads sources out of the envelope, not off disk. That is what makes a\nreceipt reproducible later.\n\n```json\n{\n  \"inputs\": [{ \"path\": \"src\u002Fstorage.ts\", \"source\": \"\u003Cfile contents>\" }],\n  \"request\": { \"kind\": \"exportedNames\", \"file\": \"src\u002Fstorage.ts\" }\n}\n```\n\nInclude every file that could plausibly reference the symbol. A file you leave out is not a file\nguessless says is clean — it is a file guessless never saw.\n\nRequest kinds:\n\n| Kind | Fields | Answers |\n| --- | --- | --- |\n| `referencesOf` | `target` (symbol anchor) | Every reference to a symbol |\n| `definitionOf` | `target` | Where a symbol is defined |\n| `readsOf` \u002F `writesOf` | `target` | Reads or writes of a binding |\n| `capturesOf` | `target` | Closures capturing a binding |\n| `reachableFrom` \u002F `reaches` | `target` | Call-graph reachability |\n| `exportedNames` | `file` | The module's export surface |\n| `resolveBinding` | `file`, `name`, `space`, optional `scope` | What a name resolves to |\n\nGet a symbol anchor from an `exportedNames` or `definitionOf` receipt and pass it back verbatim —\nanchors are fingerprinted, so hand-editing one invalidates it.\n\n## 2. Run it\n\n```bash\nnpx guessless query envelope.json > answer.receipt.json\n```\n\n## 3. Read the receipt honestly\n\n- `\"state\": \"complete\"` — say \"all\", and paste or cite the receipt.\n- `\"state\": \"partial\"` — every place the engine could not classify is named in `unresolved`. Say the\n  answer is partial, give the count, and name the gaps. Do not round a partial up to \"all\".\n- `\"state\": \"refused\"` — `reason` and `detail` say why. Do not claim anything; fix the cause (often a\n  non-JS\u002FTS file) and re-query.\n\n## 4. Make it checkable\n\nWrite the receipt beside a reproduction bundle so CI can re-run it:\n\n```\nanswer.receipt.json         the receipt\nanswer.reproduction.json    {\"inputs\": [...same inputs...], \"receipt\": {...that receipt...}}\n```\n\nThen `npx guessless reproduce answer.reproduction.json` re-runs it and fails if a single byte of\nthe receipt was altered.\n\n## Boundaries\n\nJavaScript, TypeScript, JSX and TSX only. Guessless has no opinion about other languages, about\nruntime behaviour, or about whether a change is *correct* — only about whether a structural answer\nis complete.\n\n## Markless-specific boundary\n\n`.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.\n",{"name":5,"description":7},"main","a65038eb31b69b03c9d7b57b7a8149386d02064c",".claude\u002Fskills\u002Fguessless",0,"https:\u002F\u002Fgithub.com\u002Fcompiled-run\u002Fmarkless","https:\u002F\u002Fgithub.com\u002Fcompiled-run","https:\u002F\u002Fcompiled.run\u002F","Building the next generation of compiler software","2026-11-15 05:16:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add compiled-run\u002Fmarkless --skill guessless",{"tool":39,"command":40},"bunx","bunx skills add compiled-run\u002Fmarkless --skill guessless",{"tool":42,"command":43},"pnpm","pnpm dlx skills add compiled-run\u002Fmarkless --skill guessless","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcompiled-run\u002Fmarkless\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fguessless\u002FSKILL.md",true,[],[48,55,62,69,76,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M77Z5Z2DN4WKQD805NF4DBQC","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.","https:\u002F\u002Fgithub.com\u002Fcompiled-run\u002Fmarkless\u002Fblob\u002Fmain\u002F.ruler\u002Fskills\u002Freview-with-engineer-lenses\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M77Z5XCP92P5J58JK56SGTHS","markless-spec-maintenance","Use when updating, reviewing, or reconciling Markless specifications under specs\u002F.","https:\u002F\u002Fgithub.com\u002Fcompiled-run\u002Fmarkless\u002Fblob\u002Fmain\u002F.ruler\u002Fskills\u002Fmarkless-spec-maintenance\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M77Z5TXA1T7A32ECR5R3PB1S","markless-implementation","Use for Markless implementation, compiler, bundler, performance, testing, and release work.","https:\u002F\u002Fgithub.com\u002Fcompiled-run\u002Fmarkless\u002Fblob\u002Fmain\u002F.ruler\u002Fskills\u002Fmarkless-implementation\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M77Z5NWFHXM8Z0EAWV3X3598","markless-component-research","Research component accessibility patterns and API design for a @markless\u002Fui 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.","https:\u002F\u002Fgithub.com\u002Fcompiled-run\u002Fmarkless\u002Fblob\u002Fmain\u002F.ruler\u002Fskills\u002Fmarkless-component-research\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77Z5HFPMKEZYB1MWWNRFSND","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\u002Fpages\u002F**), explain a Markless concept visually, add a figure or diagram to the docs, or someone mentions \"anatomy\", the wired drawing, or website\u002Fcomponents\u002Ffigures\u002F.","https:\u002F\u002Fgithub.com\u002Fcompiled-run\u002Fmarkless\u002Fblob\u002Fmain\u002F.ruler\u002Fskills\u002Fmarkless-anatomy\u002FLICENSE-UPSTREAM","https:\u002F\u002Fgithub.com\u002Fcompiled-run\u002Fmarkless\u002Fblob\u002Fmain\u002F.ruler\u002Fskills\u002Fmarkless-anatomy\u002FSKILL.md",[],[],{"skillNo":85,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77Z5D0FTA3XSEVNVNX2P7HV","https:\u002F\u002Fgithub.com\u002Fcompiled-run\u002Fmarkless\u002Fblob\u002Fmain\u002F.ruler\u002Fskills\u002Fguessless\u002FSKILL.md",[],[]]