mcpField
R
reference-sdk

reference-sdk

github.com/parcadeiDevelopment3.9k482 installsUpdated 39w ago
Repository

About reference-sdk

reference-sdk is a development skill for checking how configured SDKs handle implementation patterns and provider-specific issues. It uses btca ask to query references such as Vercel AI SDK, Anthropic SDK, and Zod.

Key features

  1. 01Query reference SDK implementations
  2. 02Use btca ask for questions
  3. 03Check streaming and tool-calling patterns
  4. 04Compare multi-provider approaches
  5. 05Inspect validation patterns

Use cases

  1. 01Researching an SDK feature before implementation
  2. 02Debugging provider-specific behavior
  3. 03Comparing SDK implementations
  4. 04Checking validation approaches

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill reference-sdk

After installing, type/reference-sdkin Claude Code to confirm it loaded.

Details

From the project README

Reference SDK Check

When implementing SDK features or debugging provider-specific issues, check reference implementations.

When to Use

  • Implementing SDK features
  • Debugging provider-specific issues
  • Understanding how other libraries solve similar problems
  • "How does Vercel AI SDK do X?"
  • "Check Anthropic SDK for Y"

Commands

Use btca ask to check how reference SDKs implement similar features:

# Check Vercel AI SDK for streaming patterns
btca ask -r vercel-ai -q "How does streamObject work?"

# Check Anthropic SDK for tool calling
btca ask -r anthropic-sdk -q "How are tools defined and called?"

# Check Zod for validation patterns
btca ask -r zod -q "How does safeParse handle errors?"

Configured Resources

  • vercel-ai - Streaming, tool calling, structured output
  • anthropic-sdk - Anthropic API patterns
  • zod - Schema validation

Add more: btca config resources add -n <name> -t git -u <url> -b <branch>

When to Check

  1. Before implementing - See how others solved similar problems
  2. When debugging - Find how reference code handles edge cases
  3. Multi-provider support - Compare implementations across SDKs
  4. Validation patterns - Check idiomatic approaches

Don't Use For

  • Documentation lookups (use /nia-docs instead)
  • Simple API questions (use WebSearch)
  • Project-specific patterns (use Grep/Glob)

Comments

Markdown supported