[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SNKAAXNESHFB5Z2R2EGTR":3,"skill-same:01M71SNKAAXNESHFB5Z2R2EGTR":63},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":42,"updatedAt":43,"install":44,"resources":56},"01M71SNKAAXNESHFB5Z2R2EGTR","bootstrap-prelude",null,"Prelude bootstrapping for TypeScript. Use when creating or rebuilding a prelude.ts from ambient generic helpers and types.","sanurb\u002F.dotfiles","sanurb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60886336?v=4","01M71SKJS17F5YPRE27CVMEH1X","Santiago U","01M71SKJSTGEXEQ82HMAQP4ZAF",2,"MIT","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fbootstrap-prelude\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"bootstrap prelude","bootstrap","types","generic","for","typescript","ambient","true","use","when","helpers","2026-11-10 13:02:02",false,"---\nname: bootstrap-prelude\ndescription: Prelude bootstrapping for TypeScript. Use when creating or rebuilding a prelude.ts from ambient generic helpers and types.\ndisable-model-invocation: true\n---\n\n# Bootstrap a TypeScript Prelude\n\nA prelude is an explicitly imported module for **ambient** helpers and types: ubiquitous, domain-neutral building blocks that have no more precise owner. Use the bundled [`prelude.ts`](prelude.ts) as the foundation, then adapt it to evidence from the target repository. Apply [`..\u002Fcoding-standards\u002FSKILL.md`](..\u002Fcoding-standards\u002FSKILL.md) throughout.\n\nAmbient describes a helper's role, not a TypeScript global. Keep prelude exports behind ordinary imports; do not add global declarations or global augmentation.\n\n## 1. Map the repository\n\nRead repository instructions, package manifests, TypeScript configuration, source layout, and import conventions. Locate:\n\n- an existing prelude or equivalent shared module;\n- files named `utils`, `helpers`, `common`, `types`, `result`, `errors`, or similar;\n- generic type aliases and tiny generic functions repeated across modules;\n- established libraries for results, schemas, redaction, branding, collections, and exhaustive matching;\n- every caller of plausible ambient helpers.\n\nSearch by both filenames and concepts. Use the ubiquitous generic helper\u002Ftype categories in the coding standards as seed search terms, then inspect definitions and callers rather than classifying from names alone.\n\n**Completion criterion:** Every plausible ambient definition found by repository-wide filename, symbol, and duplication scans is inventoried with its owner, callers, dependencies, and current behavior.\n\n## 2. Classify every candidate\n\nA symbol belongs in the prelude when all of these hold:\n\n- it is domain-neutral and useful across unrelated modules;\n- no domain, application service, adapter, protocol, or focused generic module is a more precise owner;\n- centralizing it reduces duplication or gives a ubiquitous concept one canonical implementation;\n- its dependencies are minimal, stable, and already justified by the project;\n- its behavior is small enough to understand at the import site or hidden behind a precise type.\n\nKeep a symbol with its focused owner when it encodes domain meaning, application policy, boundary translation, framework behavior, I\u002FO, or a cohesive generic concept such as string casing or non-trivial collection operations. Prefer an established library over a local duplicate. A prelude is a curated foundation, not a barrel or miscellaneous dumping ground.\n\nRecord one decision for every candidate: use the established library, keep the current owner, move into the prelude, merge with a template symbol, or delete as an unused duplicate.\n\n**Completion criterion:** Every inventoried candidate has one decision grounded in its semantics and callers; no candidate remains classified only by its filename or name.\n\n## 3. Seed from the template\n\nRead the bundled [`prelude.ts`](prelude.ts) completely. Copy it to the project's established shared-module location as the starting point. If a prelude already exists, merge deliberately instead of overwriting it.\n\nChoose exactly one expected-failure foundation:\n\n1. When the project uses Effect, use Effect's result\u002Ferror facilities and remove the template's local `Result` fallback.\n2. When the project uses `better-result`, use it and remove the local fallback.\n3. When the project uses neither, ask whether to install `better-result`.\n   - If accepted, install it and remove the local fallback.\n   - If declined, enable the template's local `Result` types and helpers.\n\nRetain each other template export only when repository usage, the coding standards, or the requested foundation justifies it. Preserve compatible existing behavior when merging equivalent helpers; surface semantic conflicts rather than silently choosing one implementation.\n\n**Completion criterion:** The target file is founded on the template, has exactly one result strategy, and every retained template export has an explicit justification.\n\n## 4. Consolidate ambient helpers and types\n\nMove or merge the approved repository candidates into the prelude. For each moved symbol:\n\n- preserve behavior unless a behavior change was requested;\n- preserve or deliberately migrate its public name and type contract;\n- update every caller to import from the prelude directly;\n- retain required JSDoc, safety comments, and targeted lint suppressions;\n- remove superseded definitions and compatibility re-exports after their callers move.\n\nKeep the resulting module side-effect free. It must not read configuration, acquire resources, register handlers, perform I\u002FO, contain domain\u002Fapplication policy, or re-export unrelated modules.\n\n**Completion criterion:** Every approved candidate has one canonical definition, every caller uses it, and no removed source remains as a second source of truth.\n\n## 5. Verify the foundation\n\nRun the repository's formatter, type checker, linter, and focused tests. Search again for the old symbols, duplicate definitions, stale import paths, and broad utility files that were part of the inventory. Review every prelude export for current usage or an explicit foundational reason.\n\nReport:\n\n- the chosen result strategy;\n- template exports retained or removed;\n- repository helpers moved, merged, left in place, or deleted;\n- verification commands and outcomes.\n\n**Completion criterion:** Repository checks pass, every inventory decision is reflected in code, duplicate ambient definitions are gone, and every prelude export is justified.\n","# Bootstrap a TypeScript Prelude\n\nA prelude is an explicitly imported module for **ambient** helpers and types: ubiquitous, domain-neutral building blocks that have no more precise owner. Use the bundled [`prelude.ts`](prelude.ts) as the foundation, then adapt it to evidence from the target repository. Apply [`..\u002Fcoding-standards\u002FSKILL.md`](..\u002Fcoding-standards\u002FSKILL.md) throughout.\n\nAmbient describes a helper's role, not a TypeScript global. Keep prelude exports behind ordinary imports; do not add global declarations or global augmentation.\n\n## 1. Map the repository\n\nRead repository instructions, package manifests, TypeScript configuration, source layout, and import conventions. Locate:\n\n- an existing prelude or equivalent shared module;\n- files named `utils`, `helpers`, `common`, `types`, `result`, `errors`, or similar;\n- generic type aliases and tiny generic functions repeated across modules;\n- established libraries for results, schemas, redaction, branding, collections, and exhaustive matching;\n- every caller of plausible ambient helpers.\n\nSearch by both filenames and concepts. Use the ubiquitous generic helper\u002Ftype categories in the coding standards as seed search terms, then inspect definitions and callers rather than classifying from names alone.\n\n**Completion criterion:** Every plausible ambient definition found by repository-wide filename, symbol, and duplication scans is inventoried with its owner, callers, dependencies, and current behavior.\n\n## 2. Classify every candidate\n\nA symbol belongs in the prelude when all of these hold:\n\n- it is domain-neutral and useful across unrelated modules;\n- no domain, application service, adapter, protocol, or focused generic module is a more precise owner;\n- centralizing it reduces duplication or gives a ubiquitous concept one canonical implementation;\n- its dependencies are minimal, stable, and already justified by the project;\n- its behavior is small enough to understand at the import site or hidden behind a precise type.\n\nKeep a symbol with its focused owner when it encodes domain meaning, application policy, boundary translation, framework behavior, I\u002FO, or a cohesive generic concept such as string casing or non-trivial collection operations. Prefer an established library over a local duplicate. A prelude is a curated foundation, not a barrel or miscellaneous dumping ground.\n\nRecord one decision for every candidate: use the established library, keep the current owner, move into the prelude, merge with a template symbol, or delete as an unused duplicate.\n\n**Completion criterion:** Every inventoried candidate has one decision grounded in its semantics and callers; no candidate remains classified only by its filename or name.\n\n## 3. Seed from the template\n\nRead the bundled [`prelude.ts`](prelude.ts) completely. Copy it to the project's established shared-module location as the starting point. If a prelude already exists, merge deliberately instead of overwriting it.\n\nChoose exactly one expected-failure foundation:\n\n1. When the project uses Effect, use Effect's result\u002Ferror facilities and remove the template's local `Result` fallback.\n2. When the project uses `better-result`, use it and remove the local fallback.\n3. When the project uses neither, ask whether to install `better-result`.\n   - If accepted, install it and remove the local fallback.\n   - If declined, enable the template's local `Result` types and helpers.\n\nRetain each other template export only when repository usage, the coding standards, or the requested foundation justifies it. Preserve compatible existing behavior when merging equivalent helpers; surface semantic conflicts rather than silently choosing one implementation.\n\n**Completion criterion:** The target file is founded on the template, has exactly one result strategy, and every retained template export has an explicit justification.\n\n## 4. Consolidate ambient helpers and types\n\nMove or merge the approved repository candidates into the prelude. For each moved symbol:\n\n- preserve behavior unless a behavior change was requested;\n- preserve or deliberately migrate its public name and type contract;\n- update every caller to import from the prelude directly;\n- retain required JSDoc, safety comments, and targeted lint suppressions;\n- remove superseded definitions and compatibility re-exports after their callers move.\n\nKeep the resulting module side-effect free. It must not read configuration, acquire resources, register handlers, perform I\u002FO, contain domain\u002Fapplication policy, or re-export unrelated modules.\n\n**Completion criterion:** Every approved candidate has one canonical definition, every caller uses it, and no removed source remains as a second source of truth.\n\n## 5. Verify the foundation\n\nRun the repository's formatter, type checker, linter, and focused tests. Search again for the old symbols, duplicate definitions, stale import paths, and broad utility files that were part of the inventory. Review every prelude export for current usage or an explicit foundational reason.\n\nReport:\n\n- the chosen result strategy;\n- template exports retained or removed;\n- repository helpers moved, merged, left in place, or deleted;\n- verification commands and outcomes.\n\n**Completion criterion:** Repository checks pass, every inventory decision is reflected in code, duplicate ambient definitions are gone, and every prelude export is justified.\n",{"name":5,"description":7,"disable-model-invocation":35},true,"main","5acbba39180bbea80204d1a58db40ccbd813a13a","config\u002Fpi\u002Fagent\u002Fskills\u002Fbootstrap-prelude",0,"https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles","https:\u002F\u002Fgithub.com\u002Fsanurb","Building things","2026-11-12 05:25:20",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":35},[46,49,52],{"tool":47,"command":48},"npx","npx skills add sanurb\u002F.dotfiles --skill bootstrap-prelude",{"tool":50,"command":51},"bunx","bunx skills add sanurb\u002F.dotfiles --skill bootstrap-prelude",{"tool":53,"command":54},"pnpm","pnpm dlx skills add sanurb\u002F.dotfiles --skill bootstrap-prelude","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fbootstrap-prelude\u002FSKILL.md",[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"prelude.ts","SCRIPT","脚本",4313,"https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fbootstrap-prelude\u002Fprelude.ts",[64,89,116,144,161,189],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":80,"publishedAt":30},"01M71SS19VAM2YZ2SA7HD0PT2P","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fwriting-great-skills\u002FSKILL.md",[70,75],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[81,82,83,23,84,85,26,86,87,88],"writing great skills","writing","principles","editing","a skill","reference","make","vocabulary",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":98,"publishedAt":30},"01M71SRXKJN6RYXPN9GFRVYSR3","write-discoverable-code","Rules for writing code that coding agents (and humans) can find and understand through\nplain-text search. Apply whenever writing or renaming code: functions, types, constants,\nfiles, error messages, doc comments.\n\nGrounded in measurement: agents navigate by plain-text search, not by AST or\nlanguage server, so every identifier is a search query and every search miss\ncosts wasted reads.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fwrite-discoverable-code\u002FSKILL.md",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000030","开发工程师",[99,100,101,102,103,104,21,105,23,106,107,108,109,110,82,111,112,113,114,115],"write discoverable code","code","discoverable code","write","measurement","error","error messages","search","messages","constants","plain-text","files","Rules","query","apply","comments","can",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":125,"publishedAt":30},"01M71SRT760335ES5WSEAAQDN2","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fwrangler\u002FSKILL.md",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000010","后端与接口",[118,126,127,128,129,130,131,132,133,134,135,136,137,23,138,139,140,141,142,143],"cloudflare","d1","knowledge","workflows","cli","secrets","commands","syntax","cloudflare workers","r2","queues","running","containers","correct","load","workers","best practices","store",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":30},"01M71SRPHE452V400HD2EZC4XG","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[151,141,142,152,153,154,23,126,155,128,156,118,82,140,28,100,157,158,159,160],"workers best practices","observability","reviews","promises","worker","new","common","streaming","state","anti-patterns",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":170,"publishedAt":30},"01M71SRJ36HWMTQ9ZMQ2RB008S","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fweb-perf\u002FSKILL.md",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000023","Skill与智能体开发",[171,172,173,174,175,176,177,178,179,180,128,181,28,182,183,184,185,186,187,188],"web perf","perf","web","resources","vitals","chrome devtools","performance","render","issues","devtools","MCP","caching","documentation","optimize","layout","audit","dependency","network",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":30},"01M71SREWXFKFN6DM80YCCQZ46","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[191,196,197,198,199,200,201,26,202,203,204,205,115,206,207,208,209,210,211,212],"shared","as","chunk","time","session","decision","more","map","one","one at a time","agent session","work","plan","tracker","tickets","at","destination"]