[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78822DXTMFBKTJCET1B4WHZ":3,"skill-same:01M78822DXTMFBKTJCET1B4WHZ":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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78822DXTMFBKTJCET1B4WHZ","effect",null,"Work with Effect v4 \u002F effect-smol TypeScript code in this repo","preetbiswas12\u002FBlitz","preetbiswas12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F183638463?v=4","01M75JMVJJFGZ24MXTDF029W3A","Preet Biswas","01M7881E46B88TNBSCYERXSPVR",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpreetbiswas12\u002FBlitz\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Feffect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: effect\ndescription: Work with Effect v4 \u002F effect-smol TypeScript code in this repo\n---\n\n# Effect\n\nThis codebase uses Effect for typed, composable TypeScript services, schemas, and workflows.\n\n## Source Of Truth\n\nUse the current Effect v4 \u002F effect-smol source, not memory or older Effect v2\u002Fv3 examples.\n\n1. If `.opencode\u002Freferences\u002Feffect-smol` is missing, clone `https:\u002F\u002Fgithub.com\u002FEffect-TS\u002Feffect-smol` there. Do this in the project, not in the skill folder.\n2. Search `.opencode\u002Freferences\u002Feffect-smol` for exact APIs, examples, tests, and naming patterns before answering or implementing Effect-specific code.\n3. Also inspect existing repo code for local house style before introducing new patterns.\n4. Prefer answers and implementations backed by specific source files or nearby repo examples.\n\n## Guidelines\n\n- Prefer current Effect v4 APIs and project-local patterns over old blog posts, examples, or package-memory guesses.\n- Use `Effect.gen(function* () { ... })` for multi-step workflows.\n- Use `Effect.fn(\"Name\")` or `Effect.fnUntraced(...)` for named effects when adding reusable service methods or important workflows.\n- Prefer Effect `Schema` for API and domain data shapes. Use branded schemas for IDs and `Schema.TaggedErrorClass` for typed domain errors when modeling new error surfaces.\n- Keep HTTP handlers thin: decode input, read request context, call services, and map transport errors. Put business rules in services.\n- In Effect service code, prefer Effect-aware platform abstractions and dependencies over ad hoc promises where the surrounding code already does so.\n- Keep layer composition explicit. Avoid broad hidden provisioning that makes missing dependencies hard to see.\n- In tests, prefer the repo's existing Effect test helpers and live tests for filesystem, git, child process, locks, or timing behavior.\n- Do not introduce `any`, non-null assertions, unchecked casts, or older Effect APIs just to satisfy types.\n- Do not answer from memory. Verify against `.opencode\u002Freferences\u002Feffect-smol` or nearby code first.\n\n## Testing Patterns\n\n- Use `testEffect(...)` from `packages\u002Fopencode\u002Ftest\u002Flib\u002Feffect.ts` for tests that exercise Effect services, layers, runtime context, scoped resources, or platform integrations.\n- Use `it.live(...)` for filesystem, git repositories, HTTP servers, sockets, child processes, locks, real time, and other live platform behavior.\n- Run tests from package directories such as `packages\u002Fopencode`; never run package tests from the repo root.\n- Prefer explicit test layers over ad hoc managed runtimes. Keep dependency provisioning visible in the test file.\n- Use scoped fixtures and finalizers for resources that must be cleaned up, including temporary directories, flags, databases, fibers, servers, and global state.\n","# Effect\n\nThis codebase uses Effect for typed, composable TypeScript services, schemas, and workflows.\n\n## Source Of Truth\n\nUse the current Effect v4 \u002F effect-smol source, not memory or older Effect v2\u002Fv3 examples.\n\n1. If `.opencode\u002Freferences\u002Feffect-smol` is missing, clone `https:\u002F\u002Fgithub.com\u002FEffect-TS\u002Feffect-smol` there. Do this in the project, not in the skill folder.\n2. Search `.opencode\u002Freferences\u002Feffect-smol` for exact APIs, examples, tests, and naming patterns before answering or implementing Effect-specific code.\n3. Also inspect existing repo code for local house style before introducing new patterns.\n4. Prefer answers and implementations backed by specific source files or nearby repo examples.\n\n## Guidelines\n\n- Prefer current Effect v4 APIs and project-local patterns over old blog posts, examples, or package-memory guesses.\n- Use `Effect.gen(function* () { ... })` for multi-step workflows.\n- Use `Effect.fn(\"Name\")` or `Effect.fnUntraced(...)` for named effects when adding reusable service methods or important workflows.\n- Prefer Effect `Schema` for API and domain data shapes. Use branded schemas for IDs and `Schema.TaggedErrorClass` for typed domain errors when modeling new error surfaces.\n- Keep HTTP handlers thin: decode input, read request context, call services, and map transport errors. Put business rules in services.\n- In Effect service code, prefer Effect-aware platform abstractions and dependencies over ad hoc promises where the surrounding code already does so.\n- Keep layer composition explicit. Avoid broad hidden provisioning that makes missing dependencies hard to see.\n- In tests, prefer the repo's existing Effect test helpers and live tests for filesystem, git, child process, locks, or timing behavior.\n- Do not introduce `any`, non-null assertions, unchecked casts, or older Effect APIs just to satisfy types.\n- Do not answer from memory. Verify against `.opencode\u002Freferences\u002Feffect-smol` or nearby code first.\n\n## Testing Patterns\n\n- Use `testEffect(...)` from `packages\u002Fopencode\u002Ftest\u002Flib\u002Feffect.ts` for tests that exercise Effect services, layers, runtime context, scoped resources, or platform integrations.\n- Use `it.live(...)` for filesystem, git repositories, HTTP servers, sockets, child processes, locks, real time, and other live platform behavior.\n- Run tests from package directories such as `packages\u002Fopencode`; never run package tests from the repo root.\n- Prefer explicit test layers over ad hoc managed runtimes. Keep dependency provisioning visible in the test file.\n- Use scoped fixtures and finalizers for resources that must be cleaned up, including temporary directories, flags, databases, fibers, servers, and global state.\n",{"name":5,"description":7},"main","342e9dd5d9b9f0e74269a7628faebb54d7ef2900",".opencode\u002Fskills\u002Feffect","https:\u002F\u002Fgithub.com\u002Fpreetbiswas12\u002FBlitz","https:\u002F\u002Fpreetbiswas12.github.io\u002FBlitz\u002F","https:\u002F\u002Fgithub.com\u002Fpreetbiswas12","https:\u002F\u002Fpreet-biswas.vercel.app","Building code blocks","2026-11-11 13:49:49",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add preetbiswas12\u002FBlitz --skill effect",{"tool":39,"command":40},"bunx","bunx skills add preetbiswas12\u002FBlitz --skill effect",{"tool":42,"command":43},"pnpm","pnpm dlx skills add preetbiswas12\u002FBlitz --skill effect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpreetbiswas12\u002FBlitz\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Feffect\u002FSKILL.md",true,[],[48,55,62,70,77,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},"01M7882EZ55JE258GCKN0N41XG","cloudflare","Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task.","https:\u002F\u002Fgithub.com\u002Fpreetbiswas12\u002FBlitz\u002Fblob\u002Fmain\u002Fpackages\u002Fopencode\u002Ftest\u002Ffixture\u002Fskills\u002Fcloudflare\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},"01M7882BKAMZ23N24JCPVK3F41","agents-sdk","Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks.","https:\u002F\u002Fgithub.com\u002Fpreetbiswas12\u002FBlitz\u002Fblob\u002Fmain\u002Fpackages\u002Fopencode\u002Ftest\u002Ffixture\u002Fskills\u002Fagents-sdk\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":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M78824V4TE9CJ31HBV3HTZ0V","humanizer","Rewrite AI-sounding text so it reads naturally without changing what it says.\nUse when editing or reviewing prose for inflated claims,\nsales language, vague sources, repetitive structure, stock AI words, passive\nvoice, filler, or chatbot artifacts. Based on Wikipedia's \"Signs of AI writing.\"","https:\u002F\u002Fgithub.com\u002Fpreetbiswas12\u002FBlitz\u002Fblob\u002Fmain\u002Fhumanizer-main\u002Fhumanizer-main\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fpreetbiswas12\u002FBlitz\u002Fblob\u002Fmain\u002Fhumanizer-main\u002Fhumanizer-main\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7881XC5MXE9BQYF3DEDSDT4","vscode-visual-regression","Write Storybook stories and visual regression tests for the Kilo VS Code extension webview UI","https:\u002F\u002Fgithub.com\u002Fpreetbiswas12\u002FBlitz\u002Fblob\u002Fmain\u002F.kilocode\u002Fskills\u002Fvscode-visual-regression\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7881RWCG22482CWGN226RMM","release-jetbrains","Use when releasing the Kilo JetBrains plugin -- resolve a version (\"next rc\" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.","https:\u002F\u002Fgithub.com\u002Fpreetbiswas12\u002FBlitz\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Frelease-jetbrains\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7881NBDBBMXG6ZSZ6A4N8WN","kilocode-merge-minimizer","Use when changing shared upstream-owned files to add Kilo-specific behavior, editing `kilocode_change` markers in shared code, or moving additive behavior out of shared code to reduce upstream merge conflicts. Do not use for changes confined to Kilo-owned paths such as `packages\u002Fkilo-vscode\u002F` or `packages\u002Fkilo-ui\u002F`.","https:\u002F\u002Fgithub.com\u002Fpreetbiswas12\u002FBlitz\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fkilocode-merge-minimizer\u002FSKILL.md",[],[]]