[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758TYW1SAR16XV8KBQDF039":3,"skill-same:01M758TYW1SAR16XV8KBQDF039":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":28,"ownerHtmlUrl":29,"ownerBlogUrl":28,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M758TYW1SAR16XV8KBQDF039","service-architecture",null,"Structure every domain using @repo\u002Fapi-client (preferred) or as three independent tiers — HTTP\u002FDrizzle implementation, business logic factory, and wiring composition","CliqRelay\u002Fcliqrelay","CliqRelay","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F290753656?v=4","01M758RPDEB11FEYA2XK17DSHA","01M758RPEKP0NKH6P43GD2FBDG",41,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend\u002Fservice-architecture\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: service-architecture\ndescription: Structure every domain using @repo\u002Fapi-client (preferred) or as three independent tiers — HTTP\u002FDrizzle implementation, business logic factory, and wiring composition\n---\n\n# Service Architecture\n\nThis project has **two service architectures** depending on whether `@repo\u002Fapi-client` covers the domain:\n\n- **Primary**: Use `@repo\u002Fapi-client` directly — no custom service layers needed\n- **Fallback**: Three-tier architecture (implementation → factory → composition)\n\n---\n\n## Primary Architecture: Using `@repo\u002Fapi-client`\n\n### Web App (TanStack Start): Server Functions\n\nRoute loader calls server function, which calls `api.*`:\n\n```\nRoute Loader\n    │\n    ▼  (calls server function from server-fns\u002F)\ncreateServerFn({...}).handler(async () => {\n    │\n    ▼  (imports api from @repo\u002Fapi-client)\n    return api.guides.*(...)\n    │\n    ▼\nAPI Server (Go backend)\n```\n\n### Folder Structure\n\n```\napps\u002Fweb\u002Fsrc\u002F\n├── server-fns\u002F\n│   ├── guides.ts         ← Server functions wrapping api.guides.*\n│   └── steps.ts\n├── routes\u002F\n│   ├── dashboard\u002F\n│   │   ├── index.tsx     ← Loader calls getAllGuides()\n│   │   └── guides\u002F\n│   │       └── $guideId.tsx  ← Loader calls getGuideById()\n│   └── ...\n```\n\n### Server Function Example\n\n```typescript\n\u002F\u002F server-fns\u002Fguides.ts\nimport { createServerFn } from \"@tanstack\u002Freact-start\";\nimport { api } from \"@repo\u002Fapi-client\";\nimport type { GuideUpdateInput } from \"@\u002Fmodels\";\n\nexport const getAllGuides = createServerFn({ method: \"GET\" })\n  .handler(async () => {\n    const { data, status } = await api.guides.getAllGuides();\n    if (status !== 200) {\n      console.error(\"Failed to fetch guides:\", data);\n      throw new Error(\"Failed to fetch guides\");\n    }\n    return data.guides;\n  });\n\nexport const getGuideById = createServerFn({ method: \"GET\" })\n  .inputValidator((guideId: string) => guideId)\n  .handler(async ({ data: guideId }) => {\n    const response = await api.guides.getGuideById(guideId);\n    if (response.status !== 200 || !response.data?.guide) {\n      return null;\n    }\n    return response.data.guide;\n  });\n\nexport const createGuide = createServerFn({ method: \"POST\" })\n  .inputValidator((input: { title: string; description?: string }) => input)\n  .handler(async ({ data }) => {\n    const response = await api.guides.createGuide({\n      title: data.title,\n      description: data.description ?? null,\n    });\n    if (response.status !== 201 || !response.data?.guide) {\n      console.error(\"Failed to create guide:\", response.data);\n      return null;\n    }\n    return response.data.guide;\n  });\n```\n\n### Route Loader Example\n\n```typescript\n\u002F\u002F routes\u002Fdashboard\u002Fguides\u002Findex.tsx\nimport { api } from \"@repo\u002Fapi-client\";\n\u002F\u002F OR import from server-fns:\nimport { getAllGuides } from \"@\u002Fserver-fns\u002Fguides\";\n\nexport const Route = createFileRoute(\"\u002Fdashboard\u002Fguides\u002F\")({\n  loader: async () => {\n    \u002F\u002F Option A: call server-fn\n    const guides = await getAllGuides();\n    \u002F\u002F Option B: call api-client directly (simpler when no caching needed)\n    \u002F\u002F const guides = await api.guides.getAllGuides();\n    return { guides };\n  },\n  component: GuidesPage,\n});\n```\n\n### Rules (api-client pattern):\n- Server functions go in `server-fns\u002F{domain}.ts`\n- One function per API operation\n- Import `api` from `@repo\u002Fapi-client`\n- Check `response.status` and `response.data` for error handling\n- Route loaders call server functions (or api-client directly for simple cases)\n- No factory functions, no DI, no composition needed\n\n---\n\n### Extension App (WXT \u002F SPA): Use `@repo\u002Fapi-client` Directly\n\nThe extension uses `@repo\u002Fapi-client` directly for all API calls. The SDK's `api.*` functions use `fetch` under the hood, so no manual HTTP implementations, factory functions, or service layers are needed:\n\n```\n\u002F\u002F Programmatic usage (background scripts, non-React):\nimport { api } from \"@repo\u002Fapi-client\"\n    │\napi.guides.*(...)\n    │\n    ▼\nAPI Server\n\n\u002F\u002F React components (auto-generated hooks):\nimport { useGetAllGuides } from \"@repo\u002Fapi-client\"\n    │\nuseGetAllGuides()\n    │\n    ▼\nAPI Server\n```\n\n```typescript\n\u002F\u002F ✅ DO — Use api.* for programmatic calls\nimport { api } from \"@repo\u002Fapi-client\";\n\nasync function handlePublish(guideId: string) {\n  const response = await api.guides.publishGuide(guideId);\n  if (response.status >= 400 || !response.data?.guide) {\n    throw new Error(\"Failed to publish guide\");\n  }\n  return response.data.guide;\n}\n\n\u002F\u002F ✅ DO — Use auto-generated hooks in React components\nimport { useGetAllGuides, useCreateGuide } from \"@repo\u002Fapi-client\";\n\nfunction GuideList() {\n  const { data, isLoading } = useGetAllGuides();\n  const createMutation = useCreateGuide({ ... });\n  \u002F\u002F ...\n}\n```\n\n### Rules (extension api-client pattern):\n- Import `api` from `@repo\u002Fapi-client` for programmatic HTTP calls\n- Import hooks from `@repo\u002Fapi-client` for React components\n- No manual `http-{domain}.service.ts` files — the SDK uses `fetch` internally\n- No factory functions, no DI, no composition\n- No `constants\u002Fapi-endpoints.ts` — URLs are handled by the SDK\n\n---\n\n## Fallback Architecture: Three-Tier (Non-api-client Domains)\n\nFor domains **not covered by `@repo\u002Fapi-client`**, use the traditional three-tier architecture.\n\nThis is built on the **[functional-dependency-injection](..\u002Ffunctional-dependency-injection\u002FSKILL.md)** pattern.\n\n### Architecture A: Web App (Server-side \u002F Drizzle)\n\n```\nTier 1: Drizzle Implementation  →  services\u002Fserver\u002Fdrizzle-{domain}.service.ts\nTier 2: Business Logic          →  services\u002F{domain}\u002F{domain}.service.ts\nTier 3: Composition             →  services\u002F{domain}\u002F{domain}.composition.ts\n```\n\n### Architecture B: Extension App (Client-side \u002F HTTP)\n\n```\nTier 1: HTTP Implementation  →  services\u002F{domain}\u002Fhttp-{domain}.service.ts\nTier 2: Business Logic       →  services\u002F{domain}\u002F{domain}.service.ts\nWiring:                       →  services\u002F{domain}\u002Findex.ts\n```\n\n### Tier Details (Fallback)\n\n**Tier 1 (Web):** `services\u002Fserver\u002Fdrizzle-{domain}.service.ts` — One async function per DB operation.\n\n```typescript\nexport const drizzleCreateGuide = async (db: DB, input: GuideCreateInput): Promise\u003CGuide> => {\n  const [guide] = await db.insert(guidesTable).values(input).returning();\n  return guide;\n};\n```\n\n**Tier 1 (Web):** `services\u002Fserver\u002Fdrizzle-{domain}.service.ts` — One async function per DB operation.\n\n```typescript\nexport const drizzleCreateGuide = async (db: DB, input: GuideCreateInput): Promise\u003CGuide> => {\n  const [guide] = await db.insert(guidesTable).values(input).returning();\n  return guide;\n};\n```\n\n**Tier 2:** `services\u002F{domain}\u002F{domain}.service.ts` — Factory functions receiving dependencies via DI.\n\n```typescript\nexport const createGuideFactory = (createGuide: CreateGuide) => {\n  return async (input: GuideCreateInput): Promise\u003CGuide> => createGuide(input);\n};\n```\n\n**Tier 3 (Web):** `services\u002F{domain}\u002F{domain}.composition.ts` — Wires factories to Drizzle implementations.\n\n```typescript\nexport const guideService = {\n  createGuide: createGuideFactory((input) => drizzleCreateGuide(db, input)),\n};\n```\n\n---\n\n## Data Flow Comparison\n\n```\napi-client (Preferred):\n  Web:   Component → Loader → Server Function → api.* → API Server\n  Ext:   Component → use*() Hook → API Server\n  Ext:   Background script → api.* → API Server\n\nFallback (Web, non-api-client domains):\n  Component → Composition → Factory → Drizzle → DB\n```\n\n---\n\n## Rules Summary\n\n### ✅ DO\n- Use `@repo\u002Fapi-client` + server functions (web) as the primary pattern\n- Use `@repo\u002Fapi-client` directly (both `api.*` and hooks) for the extension\n- Fall back to three-tier architecture only for non-api-client domains\n- Keep tiers independent — factories never import implementations directly\n\n### ❌ DON'T\n- Don't create `http-{domain}.service.ts` files for domains covered by `@repo\u002Fapi-client`\n- Don't mix api-client and three-tier patterns for the same domain\n- Don't create factory\u002Fservice files for domains covered by `@repo\u002Fapi-client`\n- Don't define types that already exist in `@repo\u002Fapi-client`\n- Don't instantiate classes — use factory functions + closures for fallback domains\n","# Service Architecture\n\nThis project has **two service architectures** depending on whether `@repo\u002Fapi-client` covers the domain:\n\n- **Primary**: Use `@repo\u002Fapi-client` directly — no custom service layers needed\n- **Fallback**: Three-tier architecture (implementation → factory → composition)\n\n---\n\n## Primary Architecture: Using `@repo\u002Fapi-client`\n\n### Web App (TanStack Start): Server Functions\n\nRoute loader calls server function, which calls `api.*`:\n\n```\nRoute Loader\n    │\n    ▼  (calls server function from server-fns\u002F)\ncreateServerFn({...}).handler(async () => {\n    │\n    ▼  (imports api from @repo\u002Fapi-client)\n    return api.guides.*(...)\n    │\n    ▼\nAPI Server (Go backend)\n```\n\n### Folder Structure\n\n```\napps\u002Fweb\u002Fsrc\u002F\n├── server-fns\u002F\n│   ├── guides.ts         ← Server functions wrapping api.guides.*\n│   └── steps.ts\n├── routes\u002F\n│   ├── dashboard\u002F\n│   │   ├── index.tsx     ← Loader calls getAllGuides()\n│   │   └── guides\u002F\n│   │       └── $guideId.tsx  ← Loader calls getGuideById()\n│   └── ...\n```\n\n### Server Function Example\n\n```typescript\n\u002F\u002F server-fns\u002Fguides.ts\nimport { createServerFn } from \"@tanstack\u002Freact-start\";\nimport { api } from \"@repo\u002Fapi-client\";\nimport type { GuideUpdateInput } from \"@\u002Fmodels\";\n\nexport const getAllGuides = createServerFn({ method: \"GET\" })\n  .handler(async () => {\n    const { data, status } = await api.guides.getAllGuides();\n    if (status !== 200) {\n      console.error(\"Failed to fetch guides:\", data);\n      throw new Error(\"Failed to fetch guides\");\n    }\n    return data.guides;\n  });\n\nexport const getGuideById = createServerFn({ method: \"GET\" })\n  .inputValidator((guideId: string) => guideId)\n  .handler(async ({ data: guideId }) => {\n    const response = await api.guides.getGuideById(guideId);\n    if (response.status !== 200 || !response.data?.guide) {\n      return null;\n    }\n    return response.data.guide;\n  });\n\nexport const createGuide = createServerFn({ method: \"POST\" })\n  .inputValidator((input: { title: string; description?: string }) => input)\n  .handler(async ({ data }) => {\n    const response = await api.guides.createGuide({\n      title: data.title,\n      description: data.description ?? null,\n    });\n    if (response.status !== 201 || !response.data?.guide) {\n      console.error(\"Failed to create guide:\", response.data);\n      return null;\n    }\n    return response.data.guide;\n  });\n```\n\n### Route Loader Example\n\n```typescript\n\u002F\u002F routes\u002Fdashboard\u002Fguides\u002Findex.tsx\nimport { api } from \"@repo\u002Fapi-client\";\n\u002F\u002F OR import from server-fns:\nimport { getAllGuides } from \"@\u002Fserver-fns\u002Fguides\";\n\nexport const Route = createFileRoute(\"\u002Fdashboard\u002Fguides\u002F\")({\n  loader: async () => {\n    \u002F\u002F Option A: call server-fn\n    const guides = await getAllGuides();\n    \u002F\u002F Option B: call api-client directly (simpler when no caching needed)\n    \u002F\u002F const guides = await api.guides.getAllGuides();\n    return { guides };\n  },\n  component: GuidesPage,\n});\n```\n\n### Rules (api-client pattern):\n- Server functions go in `server-fns\u002F{domain}.ts`\n- One function per API operation\n- Import `api` from `@repo\u002Fapi-client`\n- Check `response.status` and `response.data` for error handling\n- Route loaders call server functions (or api-client directly for simple cases)\n- No factory functions, no DI, no composition needed\n\n---\n\n### Extension App (WXT \u002F SPA): Use `@repo\u002Fapi-client` Directly\n\nThe extension uses `@repo\u002Fapi-client` directly for all API calls. The SDK's `api.*` functions use `fetch` under the hood, so no manual HTTP implementations, factory functions, or service layers are needed:\n\n```\n\u002F\u002F Programmatic usage (background scripts, non-React):\nimport { api } from \"@repo\u002Fapi-client\"\n    │\napi.guides.*(...)\n    │\n    ▼\nAPI Server\n\n\u002F\u002F React components (auto-generated hooks):\nimport { useGetAllGuides } from \"@repo\u002Fapi-client\"\n    │\nuseGetAllGuides()\n    │\n    ▼\nAPI Server\n```\n\n```typescript\n\u002F\u002F ✅ DO — Use api.* for programmatic calls\nimport { api } from \"@repo\u002Fapi-client\";\n\nasync function handlePublish(guideId: string) {\n  const response = await api.guides.publishGuide(guideId);\n  if (response.status >= 400 || !response.data?.guide) {\n    throw new Error(\"Failed to publish guide\");\n  }\n  return response.data.guide;\n}\n\n\u002F\u002F ✅ DO — Use auto-generated hooks in React components\nimport { useGetAllGuides, useCreateGuide } from \"@repo\u002Fapi-client\";\n\nfunction GuideList() {\n  const { data, isLoading } = useGetAllGuides();\n  const createMutation = useCreateGuide({ ... });\n  \u002F\u002F ...\n}\n```\n\n### Rules (extension api-client pattern):\n- Import `api` from `@repo\u002Fapi-client` for programmatic HTTP calls\n- Import hooks from `@repo\u002Fapi-client` for React components\n- No manual `http-{domain}.service.ts` files — the SDK uses `fetch` internally\n- No factory functions, no DI, no composition\n- No `constants\u002Fapi-endpoints.ts` — URLs are handled by the SDK\n\n---\n\n## Fallback Architecture: Three-Tier (Non-api-client Domains)\n\nFor domains **not covered by `@repo\u002Fapi-client`**, use the traditional three-tier architecture.\n\nThis is built on the **[functional-dependency-injection](..\u002Ffunctional-dependency-injection\u002FSKILL.md)** pattern.\n\n### Architecture A: Web App (Server-side \u002F Drizzle)\n\n```\nTier 1: Drizzle Implementation  →  services\u002Fserver\u002Fdrizzle-{domain}.service.ts\nTier 2: Business Logic          →  services\u002F{domain}\u002F{domain}.service.ts\nTier 3: Composition             →  services\u002F{domain}\u002F{domain}.composition.ts\n```\n\n### Architecture B: Extension App (Client-side \u002F HTTP)\n\n```\nTier 1: HTTP Implementation  →  services\u002F{domain}\u002Fhttp-{domain}.service.ts\nTier 2: Business Logic       →  services\u002F{domain}\u002F{domain}.service.ts\nWiring:                       →  services\u002F{domain}\u002Findex.ts\n```\n\n### Tier Details (Fallback)\n\n**Tier 1 (Web):** `services\u002Fserver\u002Fdrizzle-{domain}.service.ts` — One async function per DB operation.\n\n```typescript\nexport const drizzleCreateGuide = async (db: DB, input: GuideCreateInput): Promise\u003CGuide> => {\n  const [guide] = await db.insert(guidesTable).values(input).returning();\n  return guide;\n};\n```\n\n**Tier 1 (Web):** `services\u002Fserver\u002Fdrizzle-{domain}.service.ts` — One async function per DB operation.\n\n```typescript\nexport const drizzleCreateGuide = async (db: DB, input: GuideCreateInput): Promise\u003CGuide> => {\n  const [guide] = await db.insert(guidesTable).values(input).returning();\n  return guide;\n};\n```\n\n**Tier 2:** `services\u002F{domain}\u002F{domain}.service.ts` — Factory functions receiving dependencies via DI.\n\n```typescript\nexport const createGuideFactory = (createGuide: CreateGuide) => {\n  return async (input: GuideCreateInput): Promise\u003CGuide> => createGuide(input);\n};\n```\n\n**Tier 3 (Web):** `services\u002F{domain}\u002F{domain}.composition.ts` — Wires factories to Drizzle implementations.\n\n```typescript\nexport const guideService = {\n  createGuide: createGuideFactory((input) => drizzleCreateGuide(db, input)),\n};\n```\n\n---\n\n## Data Flow Comparison\n\n```\napi-client (Preferred):\n  Web:   Component → Loader → Server Function → api.* → API Server\n  Ext:   Component → use*() Hook → API Server\n  Ext:   Background script → api.* → API Server\n\nFallback (Web, non-api-client domains):\n  Component → Composition → Factory → Drizzle → DB\n```\n\n---\n\n## Rules Summary\n\n### ✅ DO\n- Use `@repo\u002Fapi-client` + server functions (web) as the primary pattern\n- Use `@repo\u002Fapi-client` directly (both `api.*` and hooks) for the extension\n- Fall back to three-tier architecture only for non-api-client domains\n- Keep tiers independent — factories never import implementations directly\n\n### ❌ DON'T\n- Don't create `http-{domain}.service.ts` files for domains covered by `@repo\u002Fapi-client`\n- Don't mix api-client and three-tier patterns for the same domain\n- Don't create factory\u002Fservice files for domains covered by `@repo\u002Fapi-client`\n- Don't define types that already exist in `@repo\u002Fapi-client`\n- Don't instantiate classes — use factory functions + closures for fallback domains\n",{"name":5,"description":7},"main","f06510bcaf955afc66bbbc1606871e1a1576492e",".agents\u002Fskills\u002Ffrontend\u002Fservice-architecture",0,"https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay","https:\u002F\u002Fcliqrelay.com","https:\u002F\u002Fgithub.com\u002FCliqRelay","Capture and refine workflows instantly to help your teams and AI agents perform at their best.","2026-11-04 22:56:05",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add CliqRelay\u002Fcliqrelay --skill service-architecture",{"tool":38,"command":39},"bunx","bunx skills add CliqRelay\u002Fcliqrelay --skill service-architecture",{"tool":41,"command":42},"pnpm","pnpm dlx skills add CliqRelay\u002Fcliqrelay --skill service-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend\u002Fservice-architecture\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M758WG0JG18W5MZD6ZPM6PGG","typst","Typst document creation and package development. Use when: (1) Working with .typ files, (2) User mentions typst, typst.toml, or typst-cli, (3) Creating or using Typst packages, (4) Developing document templates, (5) Converting Markdown\u002FLaTeX to Typst","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftypst\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M758WACKQMHG2BFF7T758J12","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", or \"switch to --preset\".","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M758W82G2QQ5Q14FKYNHRXQW","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Fhandoff\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M758W63H60EK55A93199B6NR","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Fgrilling\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M758W4HD4PF66929V7MDGKW8","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Fgrill-me\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M758VYC5CCTP7EA5VKE7YWM5","dont-waffle","Use this skill when answering questions, explaining concepts, writing technical responses, reviewing code, or helping with development tasks. Communicate in clear, simple, standard English. Keep answers concise and focused, remove unnecessary filler and repetition, explain technical ideas in plain language, and structure information so it is easy to read and understand. When showing code, present it clearly with enough context for the developer to understand what it does and where it belongs.","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Fdont-waffle\u002FSKILL.md",[],[]]