Goal Reference
This issue was generated from .fleet/goals/sdk-examples.md. The worker agent should read this file for full context including verification commands, constraints, and structural guidance.
Objective
Implement Tier 4 and 5 examples, including exposing the SDK via an MCP Server, a Tool Filtering workflow for AI SDK integration, and a CI Visual Testing workflow.
Code-Level Diagnosis
Code path: packages/sdk/examples/
Mechanism: Advanced orchestration capabilities like compound MCP tools (generate_and_extract), dynamic tool filtering (stitchTools({ include: [...] })), and visual regression hybrid workflows are currently undocumented and unexampled.
Root cause: Missing advanced examples demonstrating MCP server wrapping, tool filtering, and CI integration.
Current Implementation
// No existing examples for advanced MCP, AI SDK tool filtering, or CI workflows.
Proposed Implementation
Files to modify: Create directories for the MCP Server, Tool Filtering script, and CI Visual Testing hybrid example.
Integration (Before -> After)
+ packages/sdk/examples/mcp-server/SKILL.md
+ packages/sdk/examples/mcp-server/README.md
+ packages/sdk/examples/tool-filtering/README.md
+ packages/sdk/examples/tool-filtering/index.ts
+ packages/sdk/examples/ci-visual-testing/SKILL.md
+ packages/sdk/examples/ci-visual-testing/scripts/ci-runner.ts
+ packages/sdk/examples/ci-visual-testing/README.md
Test Scenarios
- Tool Filtering: Execute
bun index.ts -> Verify that only the specified tools are passed to the AI SDK generator.
- CI Runner: Execute
bun run scripts/ci-runner.ts -> Fetches screenshot CDN URL and compares it deterministically.
Target Files
- packages/sdk/examples/mcp-server/SKILL.md
- packages/sdk/examples/mcp-server/README.md
- packages/sdk/examples/tool-filtering/README.md
- packages/sdk/examples/tool-filtering/index.ts
- packages/sdk/examples/ci-visual-testing/SKILL.md
- packages/sdk/examples/ci-visual-testing/scripts/ci-runner.ts
- packages/sdk/examples/ci-visual-testing/README.md
- packages/sdk/README.md
Boundary Rules
Restrict your modifications exclusively to the files listed in the Target Files section. Ensure your source changes are entirely backward-compatible if unowned tests outside your boundary fail. Retain all existing file names and locations outside your explicitly declared target list.
Fleet Context
Goal Reference
This issue was generated from
.fleet/goals/sdk-examples.md. The worker agent should read this file for full context including verification commands, constraints, and structural guidance.Objective
Implement Tier 4 and 5 examples, including exposing the SDK via an MCP Server, a Tool Filtering workflow for AI SDK integration, and a CI Visual Testing workflow.
Code-Level Diagnosis
Code path: packages/sdk/examples/
Mechanism: Advanced orchestration capabilities like compound MCP tools (
generate_and_extract), dynamic tool filtering (stitchTools({ include: [...] })), and visual regression hybrid workflows are currently undocumented and unexampled.Root cause: Missing advanced examples demonstrating MCP server wrapping, tool filtering, and CI integration.
Current Implementation
// No existing examples for advanced MCP, AI SDK tool filtering, or CI workflows.Proposed Implementation
Files to modify: Create directories for the MCP Server, Tool Filtering script, and CI Visual Testing hybrid example.
Integration (Before -> After)
Test Scenarios
bun index.ts-> Verify that only the specified tools are passed to the AI SDK generator.bun run scripts/ci-runner.ts-> Fetches screenshot CDN URL and compares it deterministically.Target Files
Boundary Rules
Restrict your modifications exclusively to the files listed in the Target Files section. Ensure your source changes are entirely backward-compatible if unowned tests outside your boundary fail. Retain all existing file names and locations outside your explicitly declared target list.
Fleet Context
jules:session:9669267881517057542