메뉴
Scaffold a new provider adapter at apps/server/src/domains/providers/service/<id>.ts following the existing pattern (claude, codex, gemini, claudeInteractive). Sets up the ProviderAdapter skeleton, extends ProviderId, registers in the registry.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Generate a commit message that explains WHAT changed and WHY in plain language. No code references. Humans read these, not machines.
Generate a PR description that explains WHAT is being built, WHY, and the high-level approach. Written for humans who will not read the code.
Create a new domains/<name>/ folder following the Huxflux domain pattern. Targets web, server, mobile, or shared. For server domains, also creates the routes plugin and registers it.
Run the structural check (check-domains) against the monorepo or a specific domain. Use after editing a domain to verify it still conforms.
Enter discussion mode. No code is written, no files are created or edited. Read the codebase to ground the conversation, reason through trade-offs, surface edge cases, brainstorm. Use when the user wants to think before building.
Establish shared understanding of a task before writing any code. Restate the ask, surface ambiguity, ask 1-3 structured questions, propose an approach with trade-offs, get sign-off. Use at the start of any non-trivial task.
| name | scaffold-provider |
| description | Scaffold a new provider adapter at apps/server/src/domains/providers/service/<id>.ts following the existing pattern (claude, codex, gemini, claudeInteractive). Sets up the ProviderAdapter skeleton, extends ProviderId, registers in the registry. |
The user wants to add a new provider (Mistral, Cohere, etc.) to the orchestrator. This skill produces a conforming ProviderAdapter skeleton plus the wiring.
The user provides:
mistral)mistral, defaults to the id)<ID>_BIN, e.g. MISTRAL_BIN)The provider-specific logic, parseStreamLine (provider's stream format) and buildSpawnArgs (CLI flag construction), cannot be auto-generated. The skill leaves TODO stubs for these. The agent must read the provider's CLI documentation and fill them in.
Verify nothing exists yet. If apps/server/src/domains/providers/service/<id>.ts already exists, refuse and tell the user.
Create apps/server/src/domains/providers/service/<id>.ts with a ProviderAdapter skeleton:
createBinaryResolver from ./binary.js, the adapter types from ../providers.types.jsMODELS array (empty placeholder)binary = createBinaryResolver({ defaultBin: "<binary>", envVar: "<ENV_VAR>" })<id>Provider: ProviderAdapter with:
id: "<id>", name: "<Display Name>"capabilities (everything false except basic text streaming)resolveBinary: binary.resolve, isAvailable: binary.isAvailablebuildSpawnArgs: stub returning { bin, args: [opts.prompt], env: {} } with a // TODO commentparseStreamLine: stub returning null with a // TODO commentresolveModel: returns first MODELS[i].api or a fallback stringgetModels: returns the MODELS arrayExtend apps/server/src/domains/providers/providers.types.ts ProviderId union to include "<id>".
Register in apps/server/src/domains/providers/registry.ts: import the new adapter and add it to the providers map.
Update the README under "Adding a new provider" if step 1 (scaffold) doesn't already reference /scaffold-provider.
Run pnpm typecheck and pnpm lint to confirm the scaffold compiles.
Print a TODO checklist for the agent to complete:
MODELS with the provider's actual model ids + display labelsparseStreamLine, see the "Writing parseStreamLine" section in providers/README.mdbuildSpawnArgs, read the provider CLI's flags from its docscapabilities (which features the CLI actually supports)apps/server/src/domains/providers/service/<id>.test.ts covering parseStreamLine with at least 6 cases (text chunk, tool use, tool result, session init, error, malformed JSON)createBinaryResolver for discovery.