[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EH8PPW1R0DZPXEXD7GV32S":3,"skill-same:01M7EH8PPW1R0DZPXEXD7GV32S":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7EH8PPW1R0DZPXEXD7GV32S","effect",null,"Work with Effect v4 TypeScript code in this repo","Aporia-Nous\u002Faporia","Aporia-Nous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F340938986?v=4","01M7EH89HGF9SP10BSW714S9VR","01M7EH89J4EWPB78163JWRRD62",1,"MIT","https:\u002F\u002Fgithub.com\u002FAporia-Nous\u002Faporia\u002Fblob\u002Fpublic\u002F.opencode\u002Fskills\u002Feffect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: effect\ndescription: Work with Effect v4 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 source, not memory or older Effect v2\u002Fv3 examples.\n\n1. If `.opencode\u002Freferences\u002Feffect` is missing, clone `https:\u002F\u002Fgithub.com\u002FEffect-TS\u002Feffect` there. Do this in the project, not in the skill folder.\n2. Search `.opencode\u002Freferences\u002Feffect` 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` or nearby code first.\n\n## Testing Patterns\n\n- Use `testEffect(...)` from `packages\u002Fcore\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\u002Fcore`; 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 source, not memory or older Effect v2\u002Fv3 examples.\n\n1. If `.opencode\u002Freferences\u002Feffect` is missing, clone `https:\u002F\u002Fgithub.com\u002FEffect-TS\u002Feffect` there. Do this in the project, not in the skill folder.\n2. Search `.opencode\u002Freferences\u002Feffect` 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` or nearby code first.\n\n## Testing Patterns\n\n- Use `testEffect(...)` from `packages\u002Fcore\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\u002Fcore`; 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},"public","f7026da47b23172d898da85b053935274702b30e",".opencode\u002Fskills\u002Feffect",0,"https:\u002F\u002Fgithub.com\u002FAporia-Nous\u002Faporia","https:\u002F\u002Fgithub.com\u002FAporia-Nous","2026-11-02 02:42:40",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Aporia-Nous\u002Faporia --skill effect",{"tool":36,"command":37},"bunx","bunx skills add Aporia-Nous\u002Faporia --skill effect",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Aporia-Nous\u002Faporia --skill effect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAporia-Nous\u002Faporia\u002Fblob\u002Fpublic\u002F.opencode\u002Fskills\u002Feffect\u002FSKILL.md",true,[],[45,52,59,66],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7EH8X5HQMJ1SAFBCZYPGVND","second","Second skill","https:\u002F\u002Fgithub.com\u002FAporia-Nous\u002Faporia\u002Fblob\u002Fpublic\u002Fpackages\u002Fcore\u002Ftest\u002Fconfig\u002Ffixture\u002Fskills\u002Fsecond-source\u002Fsecond\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7EH8W9YFZNGG8PK6MF602ZQ","first","First skill","https:\u002F\u002Fgithub.com\u002FAporia-Nous\u002Faporia\u002Fblob\u002Fpublic\u002Fpackages\u002Fcore\u002Ftest\u002Fconfig\u002Ffixture\u002Fskills\u002Ffirst-source\u002Ffirst\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7EH8T6B0YT05DBBPXC7C1Y3","sample-skill","Use when the user says sample skill, skill demo, or asks how an opencode SKILL.md should be structured; demonstrates a tiny project-local skill with practical assistant workflow guidance.","https:\u002F\u002Fgithub.com\u002FAporia-Nous\u002Faporia\u002Fblob\u002Fpublic\u002F.opencode\u002Fskills\u002Fsample-skill\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7EH8QWV4X9F90K0YES4HZDF","rtl-aware-development","OpenCode Desktop should be RTL-aware. Use when implementing or reviewing RTL\u002FLTR behavior in the web app, desktop app, CSS, menus, scrolling, resizing, icons, mixed-direction text, or Electron title bars.","https:\u002F\u002Fgithub.com\u002FAporia-Nous\u002Faporia\u002Fblob\u002Fpublic\u002F.opencode\u002Fskills\u002Frtl-aware-development\u002FSKILL.md",[],[]]