From 388b7da1dbbbc3f53a6c70875a049faaf999779d Mon Sep 17 00:00:00 2001 From: itelo Date: Tue, 25 Aug 2026 11:14:20 -0300 Subject: [PATCH] feat(wizard): pull provider context packs via get_context_pack MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The wizard consumed the context-mill's example-apps but never its context-packs. Extend the integration agent's system prompt (buildSystemAppend) to call mcp__seam-docs__list_context_packs + get_context_pack for a targeted provider, so runs benefit from the per-provider SKILL.md guidance the MCP already serves. Gated to JavaScript/Python (the only SDKs the mill compiles packs for — none for ruby/php), and phrased to fetch a pack only when a specific provider is in play (a Connect Webview defers the provider choice, so generic guidance applies then). This also makes context-mill/ARCHITECTURE.md's "wizard run" diagram — which already showed get_context_pack — accurate. Closes ENG-2939. --- src/lib/steps/integrate.ts | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/lib/steps/integrate.ts b/src/lib/steps/integrate.ts index 27ec538..3096261 100644 --- a/src/lib/steps/integrate.ts +++ b/src/lib/steps/integrate.ts @@ -255,6 +255,19 @@ function buildSystemAppend( ` ${modeLabel} approach. Model your integration on it — match its structure and Seam API`, ` usage — but ADAPT it to this project's actual framework version, conventions, and file`, ` layout. Do not copy it verbatim, and don't add files this project doesn't need.`, + // Context packs are per-(provider, SDK) and only exist for JavaScript/Python, + // so only point the agent at them for those SDKs — and only when a specific + // provider is in play (a Connect Webview defers the provider choice). + ...(sdk === 'javascript' || sdk === 'python' + ? [ + `- If the integration targets a specific device or access-control provider (e.g. the developer`, + ` named August, Schlage, …), call mcp__seam-docs__list_context_packs, then`, + ` mcp__seam-docs__get_context_pack with that provider and the "${sdk}" SDK to pull its`, + ` provider-specific SKILL.md (connect + access-grant guidance grounded in that provider's real`, + ` Seam capabilities), and follow it. Skip this when no specific provider is targeted — a Connect`, + ` Webview lets the end user pick, so generic Access Grant guidance applies.`, + ] + : []), `- Find and read the installed Seam skill. Glob for a directory named like "*seam*" under`, ` .claude/skills and .agents/skills, and read its SKILL.md and any referenced files.`, `- Use the seam-docs MCP tools (prefixed mcp__seam-docs__) to confirm current Seam API usage.`,