[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M753FJT4QBZPV1FK9QJ80WQM":3,"skill-same:01M753FJT4QBZPV1FK9QJ80WQM":61},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M753FJT4QBZPV1FK9QJ80WQM","app-renderer-systems",null,"Guides creation and modification of domain feature systems organized under a systems\u002F directory. Covers directory layout, API service layer patterns, TanStack Query hooks (queries, mutations, optimistic updates), React context and XState store conventions, hook organization, and public API barrel exports. Use when adding a new domain system, extending an existing one, or fixing bugs in a system-layer codebase. Don't use for generic React component work, backend API implementation, or codebases not organized around a systems\u002F domain pattern.","haryelramalho\u002Fskills","haryelramalho","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38708454?v=4","01M753ESC6XNS6GXGV5X9YMKGA","Haryel Ramalho","01M753ESCSPRNDTEJRVRYY1VJ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fapp-renderer-systems\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: app-renderer-systems\ndescription: Guides creation and modification of domain feature systems organized under a systems\u002F directory. Covers directory layout, API service layer patterns, TanStack Query hooks (queries, mutations, optimistic updates), React context and XState store conventions, hook organization, and public API barrel exports. Use when adding a new domain system, extending an existing one, or fixing bugs in a system-layer codebase. Don't use for generic React component work, backend API implementation, or codebases not organized around a systems\u002F domain pattern.\nallowed-tools: Read, Grep, Glob\nmetadata:\n  author: Pedro Nauck\n  github: https:\u002F\u002Fgithub.com\u002Fpedronauck\n  repository: https:\u002F\u002Fgithub.com\u002Fpedronauck\u002Fskills\n---\n# Feature Systems Guide\n\nA \"system\" is a self-contained, domain-driven module that owns everything related to one domain: its API calls, query layer, hooks, components, and public API. Systems live under a `systems\u002F\u003Cdomain>\u002F` directory.\n\nRead `references\u002Fdirectory-layout.md` for the full directory structure and naming conventions.\nRead `references\u002Fpatterns.md` for annotated implementation patterns per layer.\n\n## Quick Reference\n\n### Mandatory Companion Skills\n\nActivate alongside this skill — systems span multiple technical domains:\n\n| Situation             | Activate                                  |\n| --------------------- | ----------------------------------------- |\n| Any hook or component | `react` + `tanstack-query-best-practices` |\n| Data fetching\u002Fcaching | `tanstack-query-best-practices`           |\n| Mutations             | `tanstack-query-best-practices`           |\n| XState store          | `xstate`                                  |\n| Utility functions     | `es-toolkit`                              |\n| Writing\u002Ffixing tests  | `test-antipatterns` + `vitest`            |\n| Bug fix               | `systematic-debugging` + `no-workarounds` |\n\n### System Directory at a Glance\n\n```\nsystems\u002F\u003Cdomain>\u002F\n├── index.ts               # Public API barrel — required for every system\n├── types.ts               # TypeScript types for this domain\n├── adapters\u002F              # API service layer (HTTP calls, error types)\n│   └── \u003Cdomain>-api.ts\n├── lib\u002F                   # Pure utilities, schemas, constants, query keys\n│   ├── query-keys.ts      # TanStack Query key factory\n│   ├── query-options.ts   # Reusable queryOptions \u002F mutationOptions\n│   ├── \u003Cdomain>-schemas.ts\n│   └── constants.ts\n├── hooks\u002F                 # React hooks (queries, mutations, view-models)\n│   ├── __tests__\u002F\n│   ├── use-\u003Caction>.ts    # Query hooks\n│   ├── use-create-\u003Centity>.ts  # Mutation hooks\n│   ├── use-update-\u003Centity>.ts\n│   ├── use-delete-\u003Centity>.ts\n│   └── use-\u003Cdomain>-view-model.ts\n├── contexts\u002F              # React contexts + providers\n│   └── \u003Cdomain>-context.tsx\n├── stores\u002F                # XState stores (complex async state machines)\n│   └── \u003Cdomain>-store.ts\n├── components\u002F            # React UI components\n│   ├── stories\u002F\n│   └── index.ts\n└── guards\u002F                # Route guards \u002F access checks\n```\n\n## Step-by-Step: Creating a New System\n\n### Step 1 — Define types.ts\n\n- Export clean domain types; never expose raw API response shapes.\n- Derive from the project's API contract types when available.\n- Document complex aggregated types with JSDoc explaining derivation rules and invariants.\n\n### Step 2 — Build the API service layer\n\n- Create `adapters\u002F\u003Cdomain>-api.ts`.\n- Use the project's HTTP client for API calls.\n- Export a single namespace object: `export const \u003Cdomain>Api = { list, create, update, delete }`.\n- Export a typed error class: `export class \u003CDomain>ApiError extends Error { ... }`.\n- Accept `signal?: AbortSignal` on every function to support query cancellation.\n- Keep all internal helpers (error extraction, response normalization) private to the module.\n\n### Step 3 — Add lib\u002Fquery-keys.ts\n\n```ts\nexport const \u003Cdomain>Keys = {\n  all: [\"\u003Cdomain>\"] as const,\n  lists: () => [...\u003Cdomain>Keys.all, \"list\"] as const,\n  list: (scopeId: string | null) => [...\u003Cdomain>Keys.lists(), scopeId] as const,\n  details: () => [...\u003Cdomain>Keys.all, \"detail\"] as const,\n  detail: (id: string) => [...\u003Cdomain>Keys.details(), id] as const,\n};\n```\n\n- Use hierarchical key structure for granular invalidation.\n- Scope keys with any identifier (userId, orgId, etc.) that isolates the cache correctly.\n- Use `as const` on every key tuple.\n\n### Step 4 — Add lib\u002Fquery-options.ts\n\n```ts\nimport { queryOptions } from \"@tanstack\u002Freact-query\";\nimport { \u003Cdomain>Api } from \"..\u002Fadapters\u002F\u003Cdomain>-api\";\nimport { \u003Cdomain>Keys } from \".\u002Fquery-keys\";\n\nexport function \u003Cdomain>ListOptions(scopeId: string | null) {\n  return queryOptions({\n    queryKey: \u003Cdomain>Keys.list(scopeId),\n    queryFn: ({ signal }) => \u003Cdomain>Api.list(scopeId!, signal),\n    staleTime: 60_000,\n    enabled: Boolean(scopeId),\n  });\n}\n\nexport function \u003Cdomain>DetailOptions(id: string) {\n  return queryOptions({\n    queryKey: \u003Cdomain>Keys.detail(id),\n    queryFn: ({ signal }) => \u003Cdomain>Api.get(id, signal),\n    enabled: Boolean(id),\n  });\n}\n```\n\n- Co-locate `queryKey` and `queryFn` via `queryOptions` for type safety and reuse.\n- Export each option factory for use in hooks, prefetching, and route loaders.\n- Always pass `signal` from the query context through to the API layer.\n\n### Step 5 — Write hooks\n\n- **Query hooks**: Wrap `useQuery` with the `queryOptions` factories; accept a scope ID + optional `{ enabled? }`.\n- **Mutation hooks**: Use `useMutation` with proper `onMutate` \u002F `onError` \u002F `onSettled` callbacks for optimistic updates.\n- **View-model hooks**: Compose multiple hooks for a page\u002Fshell component; return a flat object.\n- Place tests in `hooks\u002F__tests__\u002F` or co-locate as `use-xxx.test.tsx`.\n\nRead `references\u002Fpatterns.md` for complete mutation and optimistic update patterns.\n\n### Step 6 — (Optional) Add context\n\nCreate `contexts\u002F\u003Cdomain>-context.tsx` when query data or combined state must be shared across a component subtree without prop-drilling.\n\n```ts\n\u002F\u002F Always nullable context — consumer hook throws if used outside provider\nexport const \u003CDomain>Context = createContext\u003C\u003CDomain>ContextValue | null>(null);\n```\n\n- Export the context, provider component, and re-export consumer hooks from the same file.\n- For performance-sensitive trees, split into Core \u002F UI \u002F Operations sub-contexts.\n\n### Step 7 — (Optional) Add an XState store\n\nCreate `stores\u002F\u003Cdomain>-store.ts` for complex async state machines (multi-step flows, polling, event emission).\n\n```ts\nexport const \u003Cdomain>Store = createStore({\n  context: { ... } as \u003CDomain>Context,\n  emits: { ... },\n  on: {\n    someEvent: (context, event, enqueue) => {\n      enqueue.effect(async () => { ... });\n      return { ...context, isLoading: true };\n    },\n  },\n});\n```\n\n### Step 8 — Wire up index.ts\n\nOrganize the barrel with labeled sections and explicit named exports:\n\n```ts\n\u002F\u002F Types\nexport type { \u003CDomain>Type } from \".\u002Ftypes\";\n\n\u002F\u002F Hooks\nexport { use\u003CDomain>List, use\u003CDomain>Detail } from \".\u002Fhooks\";\nexport { useCreate\u003CDomain>, useUpdate\u003CDomain>, useDelete\u003CDomain> } from \".\u002Fhooks\";\n\n\u002F\u002F Components\nexport { \u003CDomain>Component } from \".\u002Fcomponents\";\n\n\u002F\u002F Utilities\nexport { \u003Cdomain>HelperFn } from \".\u002Flib\u002F\u003Cdomain>-utils\";\n\n\u002F\u002F Query Keys & Options\nexport { \u003Cdomain>Keys } from \".\u002Flib\u002Fquery-keys\";\nexport { \u003Cdomain>ListOptions, \u003Cdomain>DetailOptions } from \".\u002Flib\u002Fquery-options\";\n\n\u002F\u002F API\nexport { \u003Cdomain>Api, \u003CDomain>ApiError } from \".\u002Fadapters\u002F\u003Cdomain>-api\";\n```\n\n## Critical Rules\n\n1. **Use `queryOptions` for co-location.** Co-locate `queryKey` and `queryFn` in reusable option factories. Never scatter the same query key across multiple files.\n2. **Unidirectional dependency flow.** `adapters -> lib -> hooks -> components`. Adapters never import from hooks or components.\n3. **Scope query keys.** Any query depending on an authenticated scope (user, org, tenant) must include that scope ID in its key to prevent stale cross-scope data.\n4. **Typed errors in the API layer.** Never throw raw errors from adapters. Use a typed error class so consumers can distinguish error types without inspecting message strings.\n5. **AbortSignal propagation.** Pass `signal` from the `queryFn` context through to every API call for proper query cancellation.\n6. **Always invalidate after mutations.** Use `queryClient.invalidateQueries` in `onSettled` to ensure eventual consistency with the server.\n7. **Optimistic updates require rollback.** When using cache-based optimistic updates, snapshot previous data in `onMutate` and restore in `onError`.\n8. **Cancel outgoing queries before optimistic updates.** Call `queryClient.cancelQueries` in `onMutate` to prevent refetches from overwriting optimistic state.\n9. **Zod schemas in lib\u002F.** Place all Zod schemas in `lib\u002F\u003Cdomain>-schemas.ts` for runtime validation at API boundaries.\n\n## Error Handling\n\n- **API layer throws typed error**: TanStack Query catches and exposes it via `query.error`.\n- **Mutation fails with optimistic update**: `onError` callback rolls back the cache to the snapshot from `onMutate`, then `onSettled` invalidates to refetch fresh data.\n- **Stale cross-scope data**: Add the scope ID to the query key and verify that `enabled` guards check `Boolean(scopeId)`.\n- **Query cancellation on unmount**: TanStack Query automatically cancels in-flight queries via the `signal` when a component unmounts — ensure `signal` is propagated to the API layer.\n\n## Detailed References\n\n- `references\u002Fdirectory-layout.md` — Full directory structure, file naming, and barrel conventions\n- `references\u002Fpatterns.md` — Annotated code patterns for the API layer, query options, hooks, mutations, optimistic updates, contexts, and stores\n","# Feature Systems Guide\n\nA \"system\" is a self-contained, domain-driven module that owns everything related to one domain: its API calls, query layer, hooks, components, and public API. Systems live under a `systems\u002F\u003Cdomain>\u002F` directory.\n\nRead `references\u002Fdirectory-layout.md` for the full directory structure and naming conventions.\nRead `references\u002Fpatterns.md` for annotated implementation patterns per layer.\n\n## Quick Reference\n\n### Mandatory Companion Skills\n\nActivate alongside this skill — systems span multiple technical domains:\n\n| Situation             | Activate                                  |\n| --------------------- | ----------------------------------------- |\n| Any hook or component | `react` + `tanstack-query-best-practices` |\n| Data fetching\u002Fcaching | `tanstack-query-best-practices`           |\n| Mutations             | `tanstack-query-best-practices`           |\n| XState store          | `xstate`                                  |\n| Utility functions     | `es-toolkit`                              |\n| Writing\u002Ffixing tests  | `test-antipatterns` + `vitest`            |\n| Bug fix               | `systematic-debugging` + `no-workarounds` |\n\n### System Directory at a Glance\n\n```\nsystems\u002F\u003Cdomain>\u002F\n├── index.ts               # Public API barrel — required for every system\n├── types.ts               # TypeScript types for this domain\n├── adapters\u002F              # API service layer (HTTP calls, error types)\n│   └── \u003Cdomain>-api.ts\n├── lib\u002F                   # Pure utilities, schemas, constants, query keys\n│   ├── query-keys.ts      # TanStack Query key factory\n│   ├── query-options.ts   # Reusable queryOptions \u002F mutationOptions\n│   ├── \u003Cdomain>-schemas.ts\n│   └── constants.ts\n├── hooks\u002F                 # React hooks (queries, mutations, view-models)\n│   ├── __tests__\u002F\n│   ├── use-\u003Caction>.ts    # Query hooks\n│   ├── use-create-\u003Centity>.ts  # Mutation hooks\n│   ├── use-update-\u003Centity>.ts\n│   ├── use-delete-\u003Centity>.ts\n│   └── use-\u003Cdomain>-view-model.ts\n├── contexts\u002F              # React contexts + providers\n│   └── \u003Cdomain>-context.tsx\n├── stores\u002F                # XState stores (complex async state machines)\n│   └── \u003Cdomain>-store.ts\n├── components\u002F            # React UI components\n│   ├── stories\u002F\n│   └── index.ts\n└── guards\u002F                # Route guards \u002F access checks\n```\n\n## Step-by-Step: Creating a New System\n\n### Step 1 — Define types.ts\n\n- Export clean domain types; never expose raw API response shapes.\n- Derive from the project's API contract types when available.\n- Document complex aggregated types with JSDoc explaining derivation rules and invariants.\n\n### Step 2 — Build the API service layer\n\n- Create `adapters\u002F\u003Cdomain>-api.ts`.\n- Use the project's HTTP client for API calls.\n- Export a single namespace object: `export const \u003Cdomain>Api = { list, create, update, delete }`.\n- Export a typed error class: `export class \u003CDomain>ApiError extends Error { ... }`.\n- Accept `signal?: AbortSignal` on every function to support query cancellation.\n- Keep all internal helpers (error extraction, response normalization) private to the module.\n\n### Step 3 — Add lib\u002Fquery-keys.ts\n\n```ts\nexport const \u003Cdomain>Keys = {\n  all: [\"\u003Cdomain>\"] as const,\n  lists: () => [...\u003Cdomain>Keys.all, \"list\"] as const,\n  list: (scopeId: string | null) => [...\u003Cdomain>Keys.lists(), scopeId] as const,\n  details: () => [...\u003Cdomain>Keys.all, \"detail\"] as const,\n  detail: (id: string) => [...\u003Cdomain>Keys.details(), id] as const,\n};\n```\n\n- Use hierarchical key structure for granular invalidation.\n- Scope keys with any identifier (userId, orgId, etc.) that isolates the cache correctly.\n- Use `as const` on every key tuple.\n\n### Step 4 — Add lib\u002Fquery-options.ts\n\n```ts\nimport { queryOptions } from \"@tanstack\u002Freact-query\";\nimport { \u003Cdomain>Api } from \"..\u002Fadapters\u002F\u003Cdomain>-api\";\nimport { \u003Cdomain>Keys } from \".\u002Fquery-keys\";\n\nexport function \u003Cdomain>ListOptions(scopeId: string | null) {\n  return queryOptions({\n    queryKey: \u003Cdomain>Keys.list(scopeId),\n    queryFn: ({ signal }) => \u003Cdomain>Api.list(scopeId!, signal),\n    staleTime: 60_000,\n    enabled: Boolean(scopeId),\n  });\n}\n\nexport function \u003Cdomain>DetailOptions(id: string) {\n  return queryOptions({\n    queryKey: \u003Cdomain>Keys.detail(id),\n    queryFn: ({ signal }) => \u003Cdomain>Api.get(id, signal),\n    enabled: Boolean(id),\n  });\n}\n```\n\n- Co-locate `queryKey` and `queryFn` via `queryOptions` for type safety and reuse.\n- Export each option factory for use in hooks, prefetching, and route loaders.\n- Always pass `signal` from the query context through to the API layer.\n\n### Step 5 — Write hooks\n\n- **Query hooks**: Wrap `useQuery` with the `queryOptions` factories; accept a scope ID + optional `{ enabled? }`.\n- **Mutation hooks**: Use `useMutation` with proper `onMutate` \u002F `onError` \u002F `onSettled` callbacks for optimistic updates.\n- **View-model hooks**: Compose multiple hooks for a page\u002Fshell component; return a flat object.\n- Place tests in `hooks\u002F__tests__\u002F` or co-locate as `use-xxx.test.tsx`.\n\nRead `references\u002Fpatterns.md` for complete mutation and optimistic update patterns.\n\n### Step 6 — (Optional) Add context\n\nCreate `contexts\u002F\u003Cdomain>-context.tsx` when query data or combined state must be shared across a component subtree without prop-drilling.\n\n```ts\n\u002F\u002F Always nullable context — consumer hook throws if used outside provider\nexport const \u003CDomain>Context = createContext\u003C\u003CDomain>ContextValue | null>(null);\n```\n\n- Export the context, provider component, and re-export consumer hooks from the same file.\n- For performance-sensitive trees, split into Core \u002F UI \u002F Operations sub-contexts.\n\n### Step 7 — (Optional) Add an XState store\n\nCreate `stores\u002F\u003Cdomain>-store.ts` for complex async state machines (multi-step flows, polling, event emission).\n\n```ts\nexport const \u003Cdomain>Store = createStore({\n  context: { ... } as \u003CDomain>Context,\n  emits: { ... },\n  on: {\n    someEvent: (context, event, enqueue) => {\n      enqueue.effect(async () => { ... });\n      return { ...context, isLoading: true };\n    },\n  },\n});\n```\n\n### Step 8 — Wire up index.ts\n\nOrganize the barrel with labeled sections and explicit named exports:\n\n```ts\n\u002F\u002F Types\nexport type { \u003CDomain>Type } from \".\u002Ftypes\";\n\n\u002F\u002F Hooks\nexport { use\u003CDomain>List, use\u003CDomain>Detail } from \".\u002Fhooks\";\nexport { useCreate\u003CDomain>, useUpdate\u003CDomain>, useDelete\u003CDomain> } from \".\u002Fhooks\";\n\n\u002F\u002F Components\nexport { \u003CDomain>Component } from \".\u002Fcomponents\";\n\n\u002F\u002F Utilities\nexport { \u003Cdomain>HelperFn } from \".\u002Flib\u002F\u003Cdomain>-utils\";\n\n\u002F\u002F Query Keys & Options\nexport { \u003Cdomain>Keys } from \".\u002Flib\u002Fquery-keys\";\nexport { \u003Cdomain>ListOptions, \u003Cdomain>DetailOptions } from \".\u002Flib\u002Fquery-options\";\n\n\u002F\u002F API\nexport { \u003Cdomain>Api, \u003CDomain>ApiError } from \".\u002Fadapters\u002F\u003Cdomain>-api\";\n```\n\n## Critical Rules\n\n1. **Use `queryOptions` for co-location.** Co-locate `queryKey` and `queryFn` in reusable option factories. Never scatter the same query key across multiple files.\n2. **Unidirectional dependency flow.** `adapters -> lib -> hooks -> components`. Adapters never import from hooks or components.\n3. **Scope query keys.** Any query depending on an authenticated scope (user, org, tenant) must include that scope ID in its key to prevent stale cross-scope data.\n4. **Typed errors in the API layer.** Never throw raw errors from adapters. Use a typed error class so consumers can distinguish error types without inspecting message strings.\n5. **AbortSignal propagation.** Pass `signal` from the `queryFn` context through to every API call for proper query cancellation.\n6. **Always invalidate after mutations.** Use `queryClient.invalidateQueries` in `onSettled` to ensure eventual consistency with the server.\n7. **Optimistic updates require rollback.** When using cache-based optimistic updates, snapshot previous data in `onMutate` and restore in `onError`.\n8. **Cancel outgoing queries before optimistic updates.** Call `queryClient.cancelQueries` in `onMutate` to prevent refetches from overwriting optimistic state.\n9. **Zod schemas in lib\u002F.** Place all Zod schemas in `lib\u002F\u003Cdomain>-schemas.ts` for runtime validation at API boundaries.\n\n## Error Handling\n\n- **API layer throws typed error**: TanStack Query catches and exposes it via `query.error`.\n- **Mutation fails with optimistic update**: `onError` callback rolls back the cache to the snapshot from `onMutate`, then `onSettled` invalidates to refetch fresh data.\n- **Stale cross-scope data**: Add the scope ID to the query key and verify that `enabled` guards check `Boolean(scopeId)`.\n- **Query cancellation on unmount**: TanStack Query automatically cancels in-flight queries via the `signal` when a component unmounts — ensure `signal` is propagated to the API layer.\n\n## Detailed References\n\n- `references\u002Fdirectory-layout.md` — Full directory structure, file naming, and barrel conventions\n- `references\u002Fpatterns.md` — Annotated code patterns for the API layer, query options, hooks, mutations, optimistic updates, contexts, and stores\n",{"name":5,"metadata":24,"description":7,"allowed-tools":28},{"author":25,"github":26,"repository":27},"Pedro Nauck","https:\u002F\u002Fgithub.com\u002Fpedronauck","https:\u002F\u002Fgithub.com\u002Fpedronauck\u002Fskills","Read, Grep, Glob","main","a5b533be2d244bbf3e5606e851742f0e0ba99423","skills\u002Fcommunity\u002Fapp-renderer-systems","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills","https:\u002F\u002Fgithub.com\u002Fharyelramalho","linkedin.com\u002Fin\u002Fharyelramalho\u002F","Software Engineer @ SKORR •  Former Vice President of the Junior Computer Association - TecnoJr","2026-07-16 01:34:58",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add haryelramalho\u002Fskills --skill app-renderer-systems",{"tool":43,"command":44},"bunx","bunx skills add haryelramalho\u002Fskills --skill app-renderer-systems",{"tool":46,"command":47},"pnpm","pnpm dlx skills add haryelramalho\u002Fskills --skill app-renderer-systems","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fapp-renderer-systems\u002FSKILL.md",true,[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fdirectory-layout.md","REFERENCE","参考文档",4662,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fapp-renderer-systems\u002Freferences\u002Fdirectory-layout.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fpatterns.md",16096,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fapp-renderer-systems\u002Freferences\u002Fpatterns.md",[62,69,76,83,90,97],{"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":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M753YDMKSDB7320THEQ2CVW5","to-prompt-opus","Use when preparing or rewriting prompts for Claude Opus 4.8, Anthropic API agents, XML-structured prompts, long-context document work, coding agents, research synthesis, frontend\u002Fdesign tasks, or model-specific prompt optimization. Do not use for GPT\u002FOpenAI prompts or raw context packaging without Opus-specific tuning.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fto-prompt-opus\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M753YAP95W4K2MCEAEEAV6YA","to-prompt-gpt","Use when preparing or rewriting prompts for GPT-5.5, OpenAI API agents, Responses workflows, coding agents, research synthesis, support assistants, or model-specific prompt optimization. Do not use for Claude\u002FOpus prompts or raw context packaging without GPT-specific tuning.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fto-prompt-gpt\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M753Y700AZ0GVJDNW9Q1Q54F","plan-refactor-qa","Plans and runs qa-report before executing Compozy refactor tasks. Use when the user provides a refactor or issue slug and wants Codex to inspect the matching .compozy\u002Ftasks directory, related PRD\u002FTechSpec\u002FADR\u002Ftask artifacts, affected code, and existing tests, then invoke $qa-report with a repository-grounded prompt. Do not use to run tests, execute qa-execution, implement code, or perform post-refactor verification.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fplan-refactor-qa\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M753XZENG0Z8S2ET75EM8CGB","multi-tool-branch-review","Orchestrates a multi-tool branch review of the current git branch against a base branch. By default it runs two independent thermo-nuclear maintainability audits, one on Codex GPT-5.5 xhigh and one on Claude Opus xhigh, then consolidates the findings into a single remediation plan via writing-plans. If the user explicitly asks for native reviews, it can add the Claude native review pass, the Codex native review pass, or both. Use when the user wants a deep cross-model review of a branch or PR before merge, or asks to review this branch with multiple tools or models. Encodes known infra failure modes and their fixes (missing Claude ACP adapter, Codex MCP auth hangs, false-positive report files, long jobs orphaned inside subagents). Do not use for reviewing a single uncommitted snippet, for non-git work, for running only one reviewer, or when the user only wants a quick lint or test run.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fmulti-tool-branch-review\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M753XQM40XCK55BH5WPA88EW","create-pr-with-template","Create a GitHub Pull Request with gh CLI and prefer repository PR templates automatically. Use this whenever the user asks to open\u002Fcreate a PR, especially when template compliance is needed. If multiple templates exist, ask the user which template to use.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fcreate-pr-with-template\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M753XJMBJ8VFPRCDCC1JJ9G4","ui-craft","Provides guardrails for user-facing UI work: usability heuristics, accessibility floors, design-system discipline, component states, microcopy, motion, dark mode, responsive behavior, and human-AI UX. Use when designing, generating, reviewing, or refactoring visible product surfaces such as components, pages, dashboards, forms, dialogs, loading\u002Fempty\u002Ferror states, or AI interfaces. Do not use for backend-only work, infrastructure, CLI\u002FTUI design, or pure documentation editing.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated\u002Fui-craft\u002FSKILL.md",[],[]]