Continuous-Claude-v3 reference-sdk

Check reference SDK implementations using btca ask

install

source · Clone the upstream repo

git clone https://github.com/parcadei/Continuous-Claude-v3

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/parcadei/Continuous-Claude-v3 "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/reference-sdk" ~/.claude/skills/parcadei-continuous-claude-v3-reference-sdk && rm -rf "$T"

manifest: .claude/skills/reference-sdk/SKILL.md

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

Before implementing - See how others solved similar problems
When debugging - Find how reference code handles edge cases
Multi-provider support - Compare implementations across SDKs
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)