[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78FGG4ZAE8AR5P0TPRGP2PZ":3,"skill-same:01M78FGG4ZAE8AR5P0TPRGP2PZ":86},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M78FGG4ZAE8AR5P0TPRGP2PZ","effect-best-practices",null,"Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.","niieani\u002Fcaara","niieani","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F563469?v=4","01M78FG192M2YME2A622701717","Bazyli Brzóska","01M78FG19QQVXNN7EZAFM2MA78",5,"MIT","https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: effect-best-practices\ndescription: Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.\nversion: 1.0.0\n---\n\n# Effect-TS Best Practices\n\nThis skill enforces opinionated, consistent patterns for Effect-TS codebases. These patterns optimize for type safety, testability, observability, and maintainability.\n\n## Effect Language Server (Required)\n\n**The Effect Language Server is essential for Effect development.** It catches errors at edit-time that TypeScript alone cannot detect, provides Effect-specific refactors, and improves developer productivity.\n\n### Setup\n\n1. Install:\n```bash\nnpm install @effect\u002Flanguage-service --save-dev\n```\n\n2. Add to `tsconfig.json`:\n```json\n{\n  \"compilerOptions\": {\n    \"plugins\": [{ \"name\": \"@effect\u002Flanguage-service\" }]\n  }\n}\n```\n\n3. Configure your editor to use workspace TypeScript:\n   - **VSCode**: F1 → \"TypeScript: Select TypeScript Version\" → \"Use Workspace Version\"\n   - **JetBrains**: Settings → Languages & Frameworks → TypeScript → Use workspace version\n\n### Features\n\n- **Diagnostics**: Detects 30+ Effect-specific issues (floating Effects, missing requirements, incorrect yield patterns)\n- **Quick Info**: Hover to see Effect type parameters (Success, Error, Requirements)\n- **Completions**: Auto-complete `Self`, Duration strings, Schema brands\n- **Refactors**: Convert async → Effect.gen, auto-compose Layers, transform to Schema\n\n### Build-Time Diagnostics\n\nFor CI enforcement:\n```bash\nnpx effect-language-service patch\n```\n\nSee `references\u002Flanguage-server.md` for configuration options and CLI tools.\n\n## Quick Reference: Critical Rules\n\n| Category | DO | DON'T |\n|----------|-----|-------|\n| Services | `Effect.Service` with `accessors: true` | `Context.Tag` for business logic |\n| Dependencies | `dependencies: [Dep.Default]` in service | Manual `Layer.provide` at usage sites |\n| Layers | `Layer.mergeAll` for flat composition | Deeply nested `Layer.provide` chains |\n| Layer Chaining | `Layer.provideMerge` for incremental composition | Multiple `Layer.provide` (creates nested types) |\n| Errors | `Schema.TaggedError` with `message` field | Plain classes or generic Error |\n| Error Specificity | `UserNotFoundError`, `SessionExpiredError` | Generic `NotFoundError`, `BadRequestError` |\n| Error Handling | `catchTag`\u002F`catchTags` | `catchAll` or `mapError` |\n| IDs | `Schema.UUID.pipe(Schema.brand(\"@App\u002FEntityId\"))` | Plain `string` for entity IDs |\n| Functions | `Effect.fn(\"Service.method\")` | Anonymous generators |\n| Logging | `Effect.log` with structured data | `console.log` |\n| Config | `Config.*` with validation | `process.env` directly |\n| Options | `Option.match` with both cases | `Option.getOrThrow` |\n| Nullability | `Option\u003CT>` in domain types | `null`\u002F`undefined` |\n| Atoms | `Atom.make` outside components | Creating atoms inside render |\n| Atom State | `Atom.keepAlive` for global state | Forgetting keepAlive for persistent state |\n| Atom Updates | `useAtomSet` in React components | `Atom.update` imperatively from React |\n| Atom Cleanup | `get.addFinalizer()` for side effects | Missing cleanup for event listeners |\n| Atom Results | `Result.builder` with `onErrorTag` | Ignoring loading\u002Ferror states |\n\n## Service Definition Pattern\n\n**Always use `Effect.Service`** for business logic services. This provides automatic accessors, built-in `Default` layer, and proper dependency declaration.\n\n```typescript\nimport { Effect } from \"effect\"\n\nexport class UserService extends Effect.Service\u003CUserService>()(\"UserService\", {\n    accessors: true,\n    dependencies: [UserRepo.Default, CacheService.Default],\n    effect: Effect.gen(function* () {\n        const repo = yield* UserRepo\n        const cache = yield* CacheService\n\n        const findById = Effect.fn(\"UserService.findById\")(function* (id: UserId) {\n            const cached = yield* cache.get(id)\n            if (Option.isSome(cached)) return cached.value\n\n            const user = yield* repo.findById(id)\n            yield* cache.set(id, user)\n            return user\n        })\n\n        const create = Effect.fn(\"UserService.create\")(function* (data: CreateUserInput) {\n            const user = yield* repo.create(data)\n            yield* Effect.log(\"User created\", { userId: user.id })\n            return user\n        })\n\n        return { findById, create }\n    }),\n}) {}\n\n\u002F\u002F Usage - dependencies are already wired\nconst program = Effect.gen(function* () {\n    const user = yield* UserService.findById(userId)\n    return user\n})\n\n\u002F\u002F At app root\nconst MainLive = Layer.mergeAll(UserService.Default, OtherService.Default)\n```\n\n**When `Context.Tag` is acceptable:**\n- Infrastructure with runtime injection (Cloudflare KV, worker bindings)\n- Factory patterns where resources are provided externally\n\nSee `references\u002Fservice-patterns.md` for detailed patterns.\n\n## Error Definition Pattern\n\n**Always use `Schema.TaggedError`** for errors. This makes them serializable (required for RPC) and provides consistent structure.\n\n```typescript\nimport { Schema } from \"effect\"\nimport { HttpApiSchema } from \"@effect\u002Fplatform\"\n\nexport class UserNotFoundError extends Schema.TaggedError\u003CUserNotFoundError>()(\n    \"UserNotFoundError\",\n    {\n        userId: UserId,\n        message: Schema.String,\n    },\n    HttpApiSchema.annotations({ status: 404 }),\n) {}\n\nexport class UserCreateError extends Schema.TaggedError\u003CUserCreateError>()(\n    \"UserCreateError\",\n    {\n        message: Schema.String,\n        cause: Schema.optional(Schema.String),\n    },\n    HttpApiSchema.annotations({ status: 400 }),\n) {}\n```\n\n**Error handling - use `catchTag`\u002F`catchTags`:**\n\n```typescript\n\u002F\u002F CORRECT - preserves type information\nyield* repo.findById(id).pipe(\n    Effect.catchTag(\"DatabaseError\", (err) =>\n        Effect.fail(new UserNotFoundError({ userId: id, message: \"Lookup failed\" }))\n    ),\n    Effect.catchTag(\"ConnectionError\", (err) =>\n        Effect.fail(new ServiceUnavailableError({ message: \"Database unreachable\" }))\n    ),\n)\n\n\u002F\u002F CORRECT - multiple tags at once\nyield* effect.pipe(\n    Effect.catchTags({\n        DatabaseError: (err) => Effect.fail(new UserNotFoundError({ userId: id, message: err.message })),\n        ValidationError: (err) => Effect.fail(new InvalidEmailError({ email: input.email, message: err.message })),\n    }),\n)\n```\n\n### Prefer Explicit Over Generic Errors\n\n**Every distinct failure reason deserves its own error type.** Don't collapse multiple failure modes into generic HTTP errors.\n\n```typescript\n\u002F\u002F WRONG - Generic errors lose information\nexport class NotFoundError extends Schema.TaggedError\u003CNotFoundError>()(\n    \"NotFoundError\",\n    { message: Schema.String },\n    HttpApiSchema.annotations({ status: 404 }),\n) {}\n\n\u002F\u002F Then mapping everything to it:\nEffect.catchTags({\n    UserNotFoundError: (err) => Effect.fail(new NotFoundError({ message: \"Not found\" })),\n    ChannelNotFoundError: (err) => Effect.fail(new NotFoundError({ message: \"Not found\" })),\n    MessageNotFoundError: (err) => Effect.fail(new NotFoundError({ message: \"Not found\" })),\n})\n\u002F\u002F Frontend gets useless: { _tag: \"NotFoundError\", message: \"Not found\" }\n\u002F\u002F Which resource? User? Channel? Message? Can't tell!\n```\n\n```typescript\n\u002F\u002F CORRECT - Explicit domain errors with rich context\nexport class UserNotFoundError extends Schema.TaggedError\u003CUserNotFoundError>()(\n    \"UserNotFoundError\",\n    { userId: UserId, message: Schema.String },\n    HttpApiSchema.annotations({ status: 404 }),\n) {}\n\nexport class ChannelNotFoundError extends Schema.TaggedError\u003CChannelNotFoundError>()(\n    \"ChannelNotFoundError\",\n    { channelId: ChannelId, message: Schema.String },\n    HttpApiSchema.annotations({ status: 404 }),\n) {}\n\nexport class SessionExpiredError extends Schema.TaggedError\u003CSessionExpiredError>()(\n    \"SessionExpiredError\",\n    { sessionId: SessionId, expiredAt: Schema.DateTimeUtc, message: Schema.String },\n    HttpApiSchema.annotations({ status: 401 }),\n) {}\n\n\u002F\u002F Frontend can now show specific UI:\n\u002F\u002F - UserNotFoundError → \"User doesn't exist\"\n\u002F\u002F - ChannelNotFoundError → \"Channel was deleted\"\n\u002F\u002F - SessionExpiredError → \"Your session expired. Please log in again.\"\n```\n\nSee `references\u002Ferror-patterns.md` for error remapping and retry patterns.\n\n## Schema & Branded Types Pattern\n\n**Brand all entity IDs** for type safety across service boundaries:\n\n```typescript\nimport { Schema } from \"effect\"\n\n\u002F\u002F Entity IDs - always branded\nexport const UserId = Schema.UUID.pipe(Schema.brand(\"@App\u002FUserId\"))\nexport type UserId = Schema.Schema.Type\u003Ctypeof UserId>\n\nexport const OrganizationId = Schema.UUID.pipe(Schema.brand(\"@App\u002FOrganizationId\"))\nexport type OrganizationId = Schema.Schema.Type\u003Ctypeof OrganizationId>\n\n\u002F\u002F Domain types - use Schema.Struct\nexport const User = Schema.Struct({\n    id: UserId,\n    email: Schema.String,\n    name: Schema.String,\n    organizationId: OrganizationId,\n    createdAt: Schema.DateTimeUtc,\n})\nexport type User = Schema.Schema.Type\u003Ctypeof User>\n\n\u002F\u002F Input types for mutations\nexport const CreateUserInput = Schema.Struct({\n    email: Schema.String.pipe(Schema.pattern(\u002F^[^\\s@]+@[^\\s@]+\\.[^\\s@]+$\u002F)),\n    name: Schema.String.pipe(Schema.minLength(1)),\n    organizationId: OrganizationId,\n})\nexport type CreateUserInput = Schema.Schema.Type\u003Ctypeof CreateUserInput>\n```\n\n**When NOT to brand:**\n- Simple strings that don't cross service boundaries (URLs, file paths)\n- Primitive config values\n\nSee `references\u002Fschema-patterns.md` for transforms and advanced patterns.\n\n## Function Pattern with Effect.fn\n\n**Always use `Effect.fn`** for service methods. This provides automatic tracing with proper span names:\n\n```typescript\n\u002F\u002F CORRECT - Effect.fn with descriptive name\nconst findById = Effect.fn(\"UserService.findById\")(function* (id: UserId) {\n    yield* Effect.annotateCurrentSpan(\"userId\", id)\n    const user = yield* repo.findById(id)\n    return user\n})\n\n\u002F\u002F CORRECT - Effect.fn with multiple parameters\nconst transfer = Effect.fn(\"AccountService.transfer\")(\n    function* (fromId: AccountId, toId: AccountId, amount: number) {\n        yield* Effect.annotateCurrentSpan(\"fromId\", fromId)\n        yield* Effect.annotateCurrentSpan(\"toId\", toId)\n        yield* Effect.annotateCurrentSpan(\"amount\", amount)\n        \u002F\u002F ...\n    }\n)\n```\n\n## Layer Composition\n\n**Declare dependencies in the service**, not at usage sites:\n\n```typescript\n\u002F\u002F CORRECT - dependencies in service definition\nexport class OrderService extends Effect.Service\u003COrderService>()(\"OrderService\", {\n    accessors: true,\n    dependencies: [\n        UserService.Default,\n        ProductService.Default,\n        PaymentService.Default,\n    ],\n    effect: Effect.gen(function* () {\n        const users = yield* UserService\n        const products = yield* ProductService\n        const payments = yield* PaymentService\n        \u002F\u002F ...\n    }),\n}) {}\n\n\u002F\u002F At app root - simple merge\nconst AppLive = Layer.mergeAll(\n    OrderService.Default,\n    \u002F\u002F Infrastructure layers (intentionally not in dependencies)\n    DatabaseLive,\n    RedisLive,\n)\n```\n\n**Layer composition patterns:**\n\n```typescript\n\u002F\u002F Use Layer.mergeAll for flat composition of same-level layers\nconst RepoLive = Layer.mergeAll(\n    UserRepo.Default,\n    OrderRepo.Default,\n    ProductRepo.Default,\n)\n\n\u002F\u002F Use Layer.provideMerge for incremental chaining (flatter types than Layer.provide)\nconst MainLive = DatabaseLive.pipe(\n    Layer.provideMerge(ConfigServiceLive),\n    Layer.provideMerge(LoggerLive),\n    Layer.provideMerge(CacheLive),\n)\n```\n\n**Why layers over `Effect.provide`:**\n- **Deduplication**: Layers memoize construction - same service instantiated once. `Effect.provide` creates new instances each call.\n- **TypeScript performance**: Deep `Layer.provide` nesting creates complex recursive types that slow the LSP. `Layer.mergeAll` and `Layer.provideMerge` produce flatter types.\n- **Resource management**: Scoped layers properly share and clean up resources.\n\nSee `references\u002Flayer-patterns.md` for testing layers, config-dependent layers, and the `layerConfig` pattern.\n\n## Option Handling\n\n**Never use `Option.getOrThrow`**. Always handle both cases explicitly:\n\n```typescript\n\u002F\u002F CORRECT - explicit handling\nyield* Option.match(maybeUser, {\n    onNone: () => Effect.fail(new UserNotFoundError({ userId, message: \"Not found\" })),\n    onSome: (user) => Effect.succeed(user),\n})\n\n\u002F\u002F CORRECT - with getOrElse for defaults\nconst name = Option.getOrElse(maybeName, () => \"Anonymous\")\n\n\u002F\u002F CORRECT - Option.map for transformations\nconst upperName = Option.map(maybeName, (n) => n.toUpperCase())\n```\n\n## Effect Atom (Frontend State)\n\nEffect Atom provides reactive state management for React with Effect integration.\n\n### Basic Atoms\n\n```typescript\nimport { Atom } from \"@effect-atom\u002Fatom-react\"\n\n\u002F\u002F Define atoms OUTSIDE components\nconst countAtom = Atom.make(0)\n\n\u002F\u002F Use keepAlive for global state that should persist\nconst userPrefsAtom = Atom.make({ theme: \"dark\" }).pipe(Atom.keepAlive)\n\n\u002F\u002F Atom families for per-entity state\nconst modalAtomFamily = Atom.family((type: string) =>\n    Atom.make({ isOpen: false }).pipe(Atom.keepAlive)\n)\n```\n\n### React Integration\n\n```typescript\nimport { useAtomValue, useAtomSet, useAtom, useAtomMount } from \"@effect-atom\u002Fatom-react\"\n\nfunction Counter() {\n    const count = useAtomValue(countAtom)           \u002F\u002F Read only\n    const setCount = useAtomSet(countAtom)          \u002F\u002F Write only\n    const [value, setValue] = useAtom(countAtom)    \u002F\u002F Read + write\n\n    return \u003Cbutton onClick={() => setCount((c) => c + 1)}>{count}\u003C\u002Fbutton>\n}\n\n\u002F\u002F Mount side-effect atoms without reading value\nfunction App() {\n    useAtomMount(keyboardShortcutsAtom)\n    return \u003C>{children}\u003C\u002F>\n}\n```\n\n### Handling Results with Result.builder\n\n**Use `Result.builder`** for rendering effectful atom results. It provides chainable error handling with `onErrorTag`:\n\n```typescript\nimport { Result } from \"@effect-atom\u002Fatom-react\"\n\nfunction UserProfile() {\n    const userResult = useAtomValue(userAtom) \u002F\u002F Result\u003CUser, Error>\n\n    return Result.builder(userResult)\n        .onInitial(() => \u003Cdiv>Loading...\u003C\u002Fdiv>)\n        .onErrorTag(\"NotFoundError\", () => \u003Cdiv>User not found\u003C\u002Fdiv>)\n        .onError((error) => \u003Cdiv>Error: {error.message}\u003C\u002Fdiv>)\n        .onSuccess((user) => \u003Cdiv>Hello, {user.name}\u003C\u002Fdiv>)\n        .render()\n}\n```\n\n### Atoms with Side Effects\n\n```typescript\nconst scrollYAtom = Atom.make((get) => {\n    const onScroll = () => get.setSelf(window.scrollY)\n\n    window.addEventListener(\"scroll\", onScroll)\n    get.addFinalizer(() => window.removeEventListener(\"scroll\", onScroll)) \u002F\u002F REQUIRED\n\n    return window.scrollY\n}).pipe(Atom.keepAlive)\n```\n\n### React Mutations\n\nFor mutation atoms, derive loading state from `result.waiting` instead of `useState`:\n\n```typescript\nconst [result, mutate] = useAtom(deleteMutation, { mode: \"promise\" })\nconst isLoading = result.waiting \u002F\u002F Updates automatically, no useState\u002Ffinally needed\n```\n\n**Dialog ownership:** Move mutation logic into dialog components. Dialog owns the mutation hook, loading state, and toasts. Parent provides data props and an `onSuccess` callback.\n\n**Cache invalidation:** Use `reactivityKeys` on both mutation and query atoms to auto-invalidate queries after mutations — replaces manual `refresh()` calls.\n\nSee `references\u002Feffect-atom-patterns.md` for complete patterns including families, localStorage, mutations, and anti-patterns.\n\n## RPC & Cluster Patterns\n\nFor RPC contracts and cluster workflows, see:\n- `references\u002Frpc-cluster-patterns.md` - RpcGroup, Workflow.make, Activity patterns\n\n## Anti-Patterns (Forbidden)\n\nThese patterns are **never acceptable**:\n\n```typescript\n\u002F\u002F FORBIDDEN - runSync\u002FrunPromise inside services\nconst result = Effect.runSync(someEffect) \u002F\u002F Never do this\n\n\u002F\u002F FORBIDDEN - throw inside Effect.gen\nyield* Effect.gen(function* () {\n    if (bad) throw new Error(\"No!\") \u002F\u002F Use Effect.fail instead\n})\n\n\u002F\u002F FORBIDDEN - catchAll losing type info\nyield* effect.pipe(Effect.catchAll(() => Effect.fail(new GenericError())))\n\n\u002F\u002F FORBIDDEN - console.log\nconsole.log(\"debug\") \u002F\u002F Use Effect.log\n\n\u002F\u002F FORBIDDEN - process.env directly\nconst key = process.env.API_KEY \u002F\u002F Use Config.string(\"API_KEY\")\n\n\u002F\u002F FORBIDDEN - null\u002Fundefined in domain types\ntype User = { name: string | null } \u002F\u002F Use Option\u003Cstring>\n```\n\nSee `references\u002Fanti-patterns.md` for the complete list with rationale.\n\n## Observability\n\n```typescript\n\u002F\u002F Structured logging\nyield* Effect.log(\"Processing order\", { orderId, userId, amount })\n\n\u002F\u002F Metrics\nconst orderCounter = Metric.counter(\"orders_processed\")\nyield* Metric.increment(orderCounter)\n\n\u002F\u002F Config with validation\nconst config = Config.all({\n    port: Config.integer(\"PORT\").pipe(Config.withDefault(3000)),\n    apiKey: Config.redacted(\"API_KEY\"),\n    maxRetries: Config.integer(\"MAX_RETRIES\").pipe(\n        Config.validate({ message: \"Must be positive\", validation: (n) => n > 0 })\n    ),\n})\n```\n\nSee `references\u002Fobservability-patterns.md` for metrics and tracing patterns.\n\n## Reference Files\n\nFor detailed patterns, consult these reference files in the `references\u002F` directory:\n\n- `language-server.md` - Effect Language Service setup, diagnostics, refactors, CLI tools\n- `service-patterns.md` - Service definition, Effect.fn, Context.Tag exceptions\n- `error-patterns.md` - Schema.TaggedError, error remapping, retry patterns\n- `schema-patterns.md` - Branded types, transforms, Schema.Class\n- `layer-patterns.md` - Dependency composition, testing layers\n- `rpc-cluster-patterns.md` - RpcGroup, Workflow, Activity patterns\n- `effect-atom-patterns.md` - Atom, families, React hooks, Result handling\n- `anti-patterns.md` - Complete list of forbidden patterns\n- `observability-patterns.md` - Logging, metrics, config patterns\n","# Effect-TS Best Practices\n\nThis skill enforces opinionated, consistent patterns for Effect-TS codebases. These patterns optimize for type safety, testability, observability, and maintainability.\n\n## Effect Language Server (Required)\n\n**The Effect Language Server is essential for Effect development.** It catches errors at edit-time that TypeScript alone cannot detect, provides Effect-specific refactors, and improves developer productivity.\n\n### Setup\n\n1. Install:\n```bash\nnpm install @effect\u002Flanguage-service --save-dev\n```\n\n2. Add to `tsconfig.json`:\n```json\n{\n  \"compilerOptions\": {\n    \"plugins\": [{ \"name\": \"@effect\u002Flanguage-service\" }]\n  }\n}\n```\n\n3. Configure your editor to use workspace TypeScript:\n   - **VSCode**: F1 → \"TypeScript: Select TypeScript Version\" → \"Use Workspace Version\"\n   - **JetBrains**: Settings → Languages & Frameworks → TypeScript → Use workspace version\n\n### Features\n\n- **Diagnostics**: Detects 30+ Effect-specific issues (floating Effects, missing requirements, incorrect yield patterns)\n- **Quick Info**: Hover to see Effect type parameters (Success, Error, Requirements)\n- **Completions**: Auto-complete `Self`, Duration strings, Schema brands\n- **Refactors**: Convert async → Effect.gen, auto-compose Layers, transform to Schema\n\n### Build-Time Diagnostics\n\nFor CI enforcement:\n```bash\nnpx effect-language-service patch\n```\n\nSee `references\u002Flanguage-server.md` for configuration options and CLI tools.\n\n## Quick Reference: Critical Rules\n\n| Category | DO | DON'T |\n|----------|-----|-------|\n| Services | `Effect.Service` with `accessors: true` | `Context.Tag` for business logic |\n| Dependencies | `dependencies: [Dep.Default]` in service | Manual `Layer.provide` at usage sites |\n| Layers | `Layer.mergeAll` for flat composition | Deeply nested `Layer.provide` chains |\n| Layer Chaining | `Layer.provideMerge` for incremental composition | Multiple `Layer.provide` (creates nested types) |\n| Errors | `Schema.TaggedError` with `message` field | Plain classes or generic Error |\n| Error Specificity | `UserNotFoundError`, `SessionExpiredError` | Generic `NotFoundError`, `BadRequestError` |\n| Error Handling | `catchTag`\u002F`catchTags` | `catchAll` or `mapError` |\n| IDs | `Schema.UUID.pipe(Schema.brand(\"@App\u002FEntityId\"))` | Plain `string` for entity IDs |\n| Functions | `Effect.fn(\"Service.method\")` | Anonymous generators |\n| Logging | `Effect.log` with structured data | `console.log` |\n| Config | `Config.*` with validation | `process.env` directly |\n| Options | `Option.match` with both cases | `Option.getOrThrow` |\n| Nullability | `Option\u003CT>` in domain types | `null`\u002F`undefined` |\n| Atoms | `Atom.make` outside components | Creating atoms inside render |\n| Atom State | `Atom.keepAlive` for global state | Forgetting keepAlive for persistent state |\n| Atom Updates | `useAtomSet` in React components | `Atom.update` imperatively from React |\n| Atom Cleanup | `get.addFinalizer()` for side effects | Missing cleanup for event listeners |\n| Atom Results | `Result.builder` with `onErrorTag` | Ignoring loading\u002Ferror states |\n\n## Service Definition Pattern\n\n**Always use `Effect.Service`** for business logic services. This provides automatic accessors, built-in `Default` layer, and proper dependency declaration.\n\n```typescript\nimport { Effect } from \"effect\"\n\nexport class UserService extends Effect.Service\u003CUserService>()(\"UserService\", {\n    accessors: true,\n    dependencies: [UserRepo.Default, CacheService.Default],\n    effect: Effect.gen(function* () {\n        const repo = yield* UserRepo\n        const cache = yield* CacheService\n\n        const findById = Effect.fn(\"UserService.findById\")(function* (id: UserId) {\n            const cached = yield* cache.get(id)\n            if (Option.isSome(cached)) return cached.value\n\n            const user = yield* repo.findById(id)\n            yield* cache.set(id, user)\n            return user\n        })\n\n        const create = Effect.fn(\"UserService.create\")(function* (data: CreateUserInput) {\n            const user = yield* repo.create(data)\n            yield* Effect.log(\"User created\", { userId: user.id })\n            return user\n        })\n\n        return { findById, create }\n    }),\n}) {}\n\n\u002F\u002F Usage - dependencies are already wired\nconst program = Effect.gen(function* () {\n    const user = yield* UserService.findById(userId)\n    return user\n})\n\n\u002F\u002F At app root\nconst MainLive = Layer.mergeAll(UserService.Default, OtherService.Default)\n```\n\n**When `Context.Tag` is acceptable:**\n- Infrastructure with runtime injection (Cloudflare KV, worker bindings)\n- Factory patterns where resources are provided externally\n\nSee `references\u002Fservice-patterns.md` for detailed patterns.\n\n## Error Definition Pattern\n\n**Always use `Schema.TaggedError`** for errors. This makes them serializable (required for RPC) and provides consistent structure.\n\n```typescript\nimport { Schema } from \"effect\"\nimport { HttpApiSchema } from \"@effect\u002Fplatform\"\n\nexport class UserNotFoundError extends Schema.TaggedError\u003CUserNotFoundError>()(\n    \"UserNotFoundError\",\n    {\n        userId: UserId,\n        message: Schema.String,\n    },\n    HttpApiSchema.annotations({ status: 404 }),\n) {}\n\nexport class UserCreateError extends Schema.TaggedError\u003CUserCreateError>()(\n    \"UserCreateError\",\n    {\n        message: Schema.String,\n        cause: Schema.optional(Schema.String),\n    },\n    HttpApiSchema.annotations({ status: 400 }),\n) {}\n```\n\n**Error handling - use `catchTag`\u002F`catchTags`:**\n\n```typescript\n\u002F\u002F CORRECT - preserves type information\nyield* repo.findById(id).pipe(\n    Effect.catchTag(\"DatabaseError\", (err) =>\n        Effect.fail(new UserNotFoundError({ userId: id, message: \"Lookup failed\" }))\n    ),\n    Effect.catchTag(\"ConnectionError\", (err) =>\n        Effect.fail(new ServiceUnavailableError({ message: \"Database unreachable\" }))\n    ),\n)\n\n\u002F\u002F CORRECT - multiple tags at once\nyield* effect.pipe(\n    Effect.catchTags({\n        DatabaseError: (err) => Effect.fail(new UserNotFoundError({ userId: id, message: err.message })),\n        ValidationError: (err) => Effect.fail(new InvalidEmailError({ email: input.email, message: err.message })),\n    }),\n)\n```\n\n### Prefer Explicit Over Generic Errors\n\n**Every distinct failure reason deserves its own error type.** Don't collapse multiple failure modes into generic HTTP errors.\n\n```typescript\n\u002F\u002F WRONG - Generic errors lose information\nexport class NotFoundError extends Schema.TaggedError\u003CNotFoundError>()(\n    \"NotFoundError\",\n    { message: Schema.String },\n    HttpApiSchema.annotations({ status: 404 }),\n) {}\n\n\u002F\u002F Then mapping everything to it:\nEffect.catchTags({\n    UserNotFoundError: (err) => Effect.fail(new NotFoundError({ message: \"Not found\" })),\n    ChannelNotFoundError: (err) => Effect.fail(new NotFoundError({ message: \"Not found\" })),\n    MessageNotFoundError: (err) => Effect.fail(new NotFoundError({ message: \"Not found\" })),\n})\n\u002F\u002F Frontend gets useless: { _tag: \"NotFoundError\", message: \"Not found\" }\n\u002F\u002F Which resource? User? Channel? Message? Can't tell!\n```\n\n```typescript\n\u002F\u002F CORRECT - Explicit domain errors with rich context\nexport class UserNotFoundError extends Schema.TaggedError\u003CUserNotFoundError>()(\n    \"UserNotFoundError\",\n    { userId: UserId, message: Schema.String },\n    HttpApiSchema.annotations({ status: 404 }),\n) {}\n\nexport class ChannelNotFoundError extends Schema.TaggedError\u003CChannelNotFoundError>()(\n    \"ChannelNotFoundError\",\n    { channelId: ChannelId, message: Schema.String },\n    HttpApiSchema.annotations({ status: 404 }),\n) {}\n\nexport class SessionExpiredError extends Schema.TaggedError\u003CSessionExpiredError>()(\n    \"SessionExpiredError\",\n    { sessionId: SessionId, expiredAt: Schema.DateTimeUtc, message: Schema.String },\n    HttpApiSchema.annotations({ status: 401 }),\n) {}\n\n\u002F\u002F Frontend can now show specific UI:\n\u002F\u002F - UserNotFoundError → \"User doesn't exist\"\n\u002F\u002F - ChannelNotFoundError → \"Channel was deleted\"\n\u002F\u002F - SessionExpiredError → \"Your session expired. Please log in again.\"\n```\n\nSee `references\u002Ferror-patterns.md` for error remapping and retry patterns.\n\n## Schema & Branded Types Pattern\n\n**Brand all entity IDs** for type safety across service boundaries:\n\n```typescript\nimport { Schema } from \"effect\"\n\n\u002F\u002F Entity IDs - always branded\nexport const UserId = Schema.UUID.pipe(Schema.brand(\"@App\u002FUserId\"))\nexport type UserId = Schema.Schema.Type\u003Ctypeof UserId>\n\nexport const OrganizationId = Schema.UUID.pipe(Schema.brand(\"@App\u002FOrganizationId\"))\nexport type OrganizationId = Schema.Schema.Type\u003Ctypeof OrganizationId>\n\n\u002F\u002F Domain types - use Schema.Struct\nexport const User = Schema.Struct({\n    id: UserId,\n    email: Schema.String,\n    name: Schema.String,\n    organizationId: OrganizationId,\n    createdAt: Schema.DateTimeUtc,\n})\nexport type User = Schema.Schema.Type\u003Ctypeof User>\n\n\u002F\u002F Input types for mutations\nexport const CreateUserInput = Schema.Struct({\n    email: Schema.String.pipe(Schema.pattern(\u002F^[^\\s@]+@[^\\s@]+\\.[^\\s@]+$\u002F)),\n    name: Schema.String.pipe(Schema.minLength(1)),\n    organizationId: OrganizationId,\n})\nexport type CreateUserInput = Schema.Schema.Type\u003Ctypeof CreateUserInput>\n```\n\n**When NOT to brand:**\n- Simple strings that don't cross service boundaries (URLs, file paths)\n- Primitive config values\n\nSee `references\u002Fschema-patterns.md` for transforms and advanced patterns.\n\n## Function Pattern with Effect.fn\n\n**Always use `Effect.fn`** for service methods. This provides automatic tracing with proper span names:\n\n```typescript\n\u002F\u002F CORRECT - Effect.fn with descriptive name\nconst findById = Effect.fn(\"UserService.findById\")(function* (id: UserId) {\n    yield* Effect.annotateCurrentSpan(\"userId\", id)\n    const user = yield* repo.findById(id)\n    return user\n})\n\n\u002F\u002F CORRECT - Effect.fn with multiple parameters\nconst transfer = Effect.fn(\"AccountService.transfer\")(\n    function* (fromId: AccountId, toId: AccountId, amount: number) {\n        yield* Effect.annotateCurrentSpan(\"fromId\", fromId)\n        yield* Effect.annotateCurrentSpan(\"toId\", toId)\n        yield* Effect.annotateCurrentSpan(\"amount\", amount)\n        \u002F\u002F ...\n    }\n)\n```\n\n## Layer Composition\n\n**Declare dependencies in the service**, not at usage sites:\n\n```typescript\n\u002F\u002F CORRECT - dependencies in service definition\nexport class OrderService extends Effect.Service\u003COrderService>()(\"OrderService\", {\n    accessors: true,\n    dependencies: [\n        UserService.Default,\n        ProductService.Default,\n        PaymentService.Default,\n    ],\n    effect: Effect.gen(function* () {\n        const users = yield* UserService\n        const products = yield* ProductService\n        const payments = yield* PaymentService\n        \u002F\u002F ...\n    }),\n}) {}\n\n\u002F\u002F At app root - simple merge\nconst AppLive = Layer.mergeAll(\n    OrderService.Default,\n    \u002F\u002F Infrastructure layers (intentionally not in dependencies)\n    DatabaseLive,\n    RedisLive,\n)\n```\n\n**Layer composition patterns:**\n\n```typescript\n\u002F\u002F Use Layer.mergeAll for flat composition of same-level layers\nconst RepoLive = Layer.mergeAll(\n    UserRepo.Default,\n    OrderRepo.Default,\n    ProductRepo.Default,\n)\n\n\u002F\u002F Use Layer.provideMerge for incremental chaining (flatter types than Layer.provide)\nconst MainLive = DatabaseLive.pipe(\n    Layer.provideMerge(ConfigServiceLive),\n    Layer.provideMerge(LoggerLive),\n    Layer.provideMerge(CacheLive),\n)\n```\n\n**Why layers over `Effect.provide`:**\n- **Deduplication**: Layers memoize construction - same service instantiated once. `Effect.provide` creates new instances each call.\n- **TypeScript performance**: Deep `Layer.provide` nesting creates complex recursive types that slow the LSP. `Layer.mergeAll` and `Layer.provideMerge` produce flatter types.\n- **Resource management**: Scoped layers properly share and clean up resources.\n\nSee `references\u002Flayer-patterns.md` for testing layers, config-dependent layers, and the `layerConfig` pattern.\n\n## Option Handling\n\n**Never use `Option.getOrThrow`**. Always handle both cases explicitly:\n\n```typescript\n\u002F\u002F CORRECT - explicit handling\nyield* Option.match(maybeUser, {\n    onNone: () => Effect.fail(new UserNotFoundError({ userId, message: \"Not found\" })),\n    onSome: (user) => Effect.succeed(user),\n})\n\n\u002F\u002F CORRECT - with getOrElse for defaults\nconst name = Option.getOrElse(maybeName, () => \"Anonymous\")\n\n\u002F\u002F CORRECT - Option.map for transformations\nconst upperName = Option.map(maybeName, (n) => n.toUpperCase())\n```\n\n## Effect Atom (Frontend State)\n\nEffect Atom provides reactive state management for React with Effect integration.\n\n### Basic Atoms\n\n```typescript\nimport { Atom } from \"@effect-atom\u002Fatom-react\"\n\n\u002F\u002F Define atoms OUTSIDE components\nconst countAtom = Atom.make(0)\n\n\u002F\u002F Use keepAlive for global state that should persist\nconst userPrefsAtom = Atom.make({ theme: \"dark\" }).pipe(Atom.keepAlive)\n\n\u002F\u002F Atom families for per-entity state\nconst modalAtomFamily = Atom.family((type: string) =>\n    Atom.make({ isOpen: false }).pipe(Atom.keepAlive)\n)\n```\n\n### React Integration\n\n```typescript\nimport { useAtomValue, useAtomSet, useAtom, useAtomMount } from \"@effect-atom\u002Fatom-react\"\n\nfunction Counter() {\n    const count = useAtomValue(countAtom)           \u002F\u002F Read only\n    const setCount = useAtomSet(countAtom)          \u002F\u002F Write only\n    const [value, setValue] = useAtom(countAtom)    \u002F\u002F Read + write\n\n    return \u003Cbutton onClick={() => setCount((c) => c + 1)}>{count}\u003C\u002Fbutton>\n}\n\n\u002F\u002F Mount side-effect atoms without reading value\nfunction App() {\n    useAtomMount(keyboardShortcutsAtom)\n    return \u003C>{children}\u003C\u002F>\n}\n```\n\n### Handling Results with Result.builder\n\n**Use `Result.builder`** for rendering effectful atom results. It provides chainable error handling with `onErrorTag`:\n\n```typescript\nimport { Result } from \"@effect-atom\u002Fatom-react\"\n\nfunction UserProfile() {\n    const userResult = useAtomValue(userAtom) \u002F\u002F Result\u003CUser, Error>\n\n    return Result.builder(userResult)\n        .onInitial(() => \u003Cdiv>Loading...\u003C\u002Fdiv>)\n        .onErrorTag(\"NotFoundError\", () => \u003Cdiv>User not found\u003C\u002Fdiv>)\n        .onError((error) => \u003Cdiv>Error: {error.message}\u003C\u002Fdiv>)\n        .onSuccess((user) => \u003Cdiv>Hello, {user.name}\u003C\u002Fdiv>)\n        .render()\n}\n```\n\n### Atoms with Side Effects\n\n```typescript\nconst scrollYAtom = Atom.make((get) => {\n    const onScroll = () => get.setSelf(window.scrollY)\n\n    window.addEventListener(\"scroll\", onScroll)\n    get.addFinalizer(() => window.removeEventListener(\"scroll\", onScroll)) \u002F\u002F REQUIRED\n\n    return window.scrollY\n}).pipe(Atom.keepAlive)\n```\n\n### React Mutations\n\nFor mutation atoms, derive loading state from `result.waiting` instead of `useState`:\n\n```typescript\nconst [result, mutate] = useAtom(deleteMutation, { mode: \"promise\" })\nconst isLoading = result.waiting \u002F\u002F Updates automatically, no useState\u002Ffinally needed\n```\n\n**Dialog ownership:** Move mutation logic into dialog components. Dialog owns the mutation hook, loading state, and toasts. Parent provides data props and an `onSuccess` callback.\n\n**Cache invalidation:** Use `reactivityKeys` on both mutation and query atoms to auto-invalidate queries after mutations — replaces manual `refresh()` calls.\n\nSee `references\u002Feffect-atom-patterns.md` for complete patterns including families, localStorage, mutations, and anti-patterns.\n\n## RPC & Cluster Patterns\n\nFor RPC contracts and cluster workflows, see:\n- `references\u002Frpc-cluster-patterns.md` - RpcGroup, Workflow.make, Activity patterns\n\n## Anti-Patterns (Forbidden)\n\nThese patterns are **never acceptable**:\n\n```typescript\n\u002F\u002F FORBIDDEN - runSync\u002FrunPromise inside services\nconst result = Effect.runSync(someEffect) \u002F\u002F Never do this\n\n\u002F\u002F FORBIDDEN - throw inside Effect.gen\nyield* Effect.gen(function* () {\n    if (bad) throw new Error(\"No!\") \u002F\u002F Use Effect.fail instead\n})\n\n\u002F\u002F FORBIDDEN - catchAll losing type info\nyield* effect.pipe(Effect.catchAll(() => Effect.fail(new GenericError())))\n\n\u002F\u002F FORBIDDEN - console.log\nconsole.log(\"debug\") \u002F\u002F Use Effect.log\n\n\u002F\u002F FORBIDDEN - process.env directly\nconst key = process.env.API_KEY \u002F\u002F Use Config.string(\"API_KEY\")\n\n\u002F\u002F FORBIDDEN - null\u002Fundefined in domain types\ntype User = { name: string | null } \u002F\u002F Use Option\u003Cstring>\n```\n\nSee `references\u002Fanti-patterns.md` for the complete list with rationale.\n\n## Observability\n\n```typescript\n\u002F\u002F Structured logging\nyield* Effect.log(\"Processing order\", { orderId, userId, amount })\n\n\u002F\u002F Metrics\nconst orderCounter = Metric.counter(\"orders_processed\")\nyield* Metric.increment(orderCounter)\n\n\u002F\u002F Config with validation\nconst config = Config.all({\n    port: Config.integer(\"PORT\").pipe(Config.withDefault(3000)),\n    apiKey: Config.redacted(\"API_KEY\"),\n    maxRetries: Config.integer(\"MAX_RETRIES\").pipe(\n        Config.validate({ message: \"Must be positive\", validation: (n) => n > 0 })\n    ),\n})\n```\n\nSee `references\u002Fobservability-patterns.md` for metrics and tracing patterns.\n\n## Reference Files\n\nFor detailed patterns, consult these reference files in the `references\u002F` directory:\n\n- `language-server.md` - Effect Language Service setup, diagnostics, refactors, CLI tools\n- `service-patterns.md` - Service definition, Effect.fn, Context.Tag exceptions\n- `error-patterns.md` - Schema.TaggedError, error remapping, retry patterns\n- `schema-patterns.md` - Branded types, transforms, Schema.Class\n- `layer-patterns.md` - Dependency composition, testing layers\n- `rpc-cluster-patterns.md` - RpcGroup, Workflow, Activity patterns\n- `effect-atom-patterns.md` - Atom, families, React hooks, Result handling\n- `anti-patterns.md` - Complete list of forbidden patterns\n- `observability-patterns.md` - Logging, metrics, config patterns\n",{"name":5,"version":24,"description":7},"1.0.0","main","8a58f33f93c8b7bd2326feac4a5716ae139b7d9f",".agents\u002Fskills\u002Feffect-best-practices",0,"https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara","https:\u002F\u002Fniieani.github.io\u002Fcaara\u002F","https:\u002F\u002Fgithub.com\u002Fniieani","https:\u002F\u002Finvent.life","An inventor passionate about HCI workflows that help humanity innovate responsibly, for happiness and global thriving.\r\n\r\nOfficial @zendesk account: @bbrzoska","2026-11-09 09:58:53",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add niieani\u002Fcaara --skill effect-best-practices",{"tool":41,"command":42},"bunx","bunx skills add niieani\u002Fcaara --skill effect-best-practices",{"tool":44,"command":45},"pnpm","pnpm dlx skills add niieani\u002Fcaara --skill effect-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002FSKILL.md",true,[49,55,59,63,67,71,75,79,83],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fanti-patterns.md","REFERENCE","参考文档",8907,"https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002Freferences\u002Fanti-patterns.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Feffect-atom-patterns.md",17839,"https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002Freferences\u002Feffect-atom-patterns.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Ferror-patterns.md",14953,"https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002Freferences\u002Ferror-patterns.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Flanguage-server.md",6861,"https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002Freferences\u002Flanguage-server.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Flayer-patterns.md",13983,"https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002Freferences\u002Flayer-patterns.md",{"path":72,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fobservability-patterns.md",9278,"https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002Freferences\u002Fobservability-patterns.md",{"path":76,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Frpc-cluster-patterns.md",11845,"https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002Freferences\u002Frpc-cluster-patterns.md",{"path":80,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fschema-patterns.md",9823,"https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002Freferences\u002Fschema-patterns.md",{"path":84,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":85},"references\u002Fservice-patterns.md","https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-best-practices\u002Freferences\u002Fservice-patterns.md",[87,94,101,108,115,122],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M78FH7JRMKXG8GDVZP4S106P","worktree-setup","Create a ready-to-work git worktree — branch, deps, local config, green build — and report it.","https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworktree-setup\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M78FH5NF893DW194BYZT2XQC","panel","Convene a cross-model panel of Caara-backed subagents — ensemble, debate, or cross-review — for results no single model reaches.","https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpanel\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M78FH2Y3XGMJ51Y75G8SZKPJ","logging-best-practices","Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics","https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Flogging-best-practices\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M78FGW0QA6T3BY28RG3SVTKS","imagegen-frontend-web","Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text \u002F right-image), background-image freedom, varied CTAs, varied hero scales (giant \u002F mid \u002F mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.","https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimagegen-frontend-web\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M78FGQ5QJMZSEQP40J1DFZ5K","effect-ts","Write idiomatic Effect v4 TypeScript following official best practices from effect-solutions and the Effect source. Use when writing, reviewing, or refactoring Effect code: services (ServiceMap.Service), layers and dependency injection, error handling (Schema.TaggedErrorClass), data modeling (Schema.Class, branded types, variants), testing (@effect\u002Fvitest), HTTP clients (effect\u002Funstable\u002Fhttp), CLI tools (effect\u002Funstable\u002Fcli), config, observability, and project setup. Triggers on: 'Effect', 'effect-ts', '@effect\u002F', 'Schema', 'ServiceMap', 'Layer', 'Effect.gen', 'Effect.fn', 'TaggedError', 'branded types', or any Effect-TS related code.","https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-ts\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M78FGKFTPADMVTHRCM42FH6W","effect-review","This skill should be used when the user asks to \"review code\", \"review my changes\", \"check effect patterns\", \"run effect review\", \"effect review\", \"review for effect best practices\", or wants a comprehensive code review against Effect-TS conventions, branded types, observability, error handling, test coverage, and UI quality.","https:\u002F\u002Fgithub.com\u002Fniieani\u002Fcaara\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-review\u002FSKILL.md",[],[]]