home / skills / willsigmon / sigstack / interface-picker

This skill helps you choose the right Claude interface for your task, maximizing efficiency and cost savings.

npx playbooks add skill willsigmon/sigstack --skill interface-picker

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.7 KB
---
name: Interface Picker
description: When to use Claude Code vs API vs CLI vs MCP vs Desktop
allowed-tools: Read, Bash
model: haiku
---

# Interface Picker

Right tool for the job.

## Interface Comparison

| Interface | Best For | Token Cost | Setup |
|-----------|----------|------------|-------|
| Claude Code | Codebase work | Pro plan | Installed |
| Claude Desktop | Chat, docs, images | Pro plan | Installed |
| API | Automation, batch | Pay-per-use | API key |
| CLI (claude) | Quick queries | Pro plan | Installed |
| MCP | Tool access | Varies | Config |

## Claude Code

**Use when:**
- Working in a codebase
- Need file read/write/edit
- Multi-file changes
- Running tests/builds
- Agent swarms for parallel work

**Strengths:**
- Full codebase context
- Tool access (Bash, Edit, etc.)
- Agent spawning
- Skill/plugin system

**Example:**
```
"Refactor the auth module to use async/await"
→ Claude reads, plans, edits, tests
```

## Claude Desktop

**Use when:**
- Document analysis (PDFs, images)
- Long-form writing
- Research and summarization
- Conversational exploration
- Projects (persistent context)

**Strengths:**
- Native image/PDF handling
- Projects for organization
- Clean UI for long docs
- MCP server access

**Example:**
```
Upload design PDF → "Extract the color palette"
```

## API (Direct)

**Use when:**
- Batch processing
- Automation pipelines
- Custom applications
- Embedding in products
- High-volume, predictable costs

**Strengths:**
- Full control
- Batch API for async (50% off)
- Streaming support
- Function calling

**Example:**
```python
# Process 1000 documents overnight
for doc in documents:
    result = client.messages.create(
        model="claude-sonnet-4-20250514",
        messages=[{"role": "user", "content": doc}]
    )
```

## CLI (claude command)

**Use when:**
- Quick one-off queries
- Scripting/automation
- Pipeline integration
- No need for conversation

**Strengths:**
- Fast startup
- Pipe input/output
- Shell integration
- Non-interactive use

**Example:**
```bash
# Quick question
echo "What's the Swift syntax for async?" | claude

# Process file
cat code.swift | claude "review this code"

# Generate and save
claude "write a gitignore for iOS" > .gitignore
```

## MCP Servers

**Use when:**
- Need external data (Supabase, GitHub, etc.)
- Tool access beyond file system
- Real-time information
- Database operations

**Strengths:**
- Direct tool access
- No manual copy/paste
- Structured data handling
- Composable tools

**Example:**
```
"Query our Supabase for users created today"
→ MCP fetches, no tokens wasted on raw data
```

## Decision Flowchart

```
Need to work with code files?
  YES → Claude Code
  NO ↓

Need to process images/PDFs?
  YES → Claude Desktop
  NO ↓

Batch processing 100+ items?
  YES → API (Batch)
  NO ↓

Quick one-liner question?
  YES → CLI
  NO ↓

Need external data/tools?
  YES → MCP-enabled interface
  NO ↓

Default → Claude Code (most capable)
```

## Hybrid Patterns

### Claude Code + MCP
```
Claude Code with Supabase MCP:
- Code changes + database queries
- Best of both worlds
```

### API + Claude Code
```
API for batch generation →
Claude Code for review/integration
```

### Desktop + Code Handoff
```
Research in Desktop (images, docs) →
Copy findings to Claude Code for implementation
```

## Cost Optimization

```
Pro Plan ($20/mo):
- Unlimited Claude Code
- Unlimited Desktop
- Unlimited CLI
- Best for: Daily heavy use

API Pay-per-use:
- $3/M input, $15/M output (Sonnet)
- Best for: Automation, batch jobs
- Batch API: 50% off for async

Hybrid:
- Pro for interactive work
- API for automation
- Best overall efficiency
```

Use when: Choosing interfaces, optimizing workflow, reducing friction

Overview

This skill helps you pick the right Claude interface for a task: Code, Desktop, API, CLI, or MCP. It clarifies strengths, costs, and setup trade-offs so you use the most efficient tool. The goal is faster outcomes, lower token waste, and smoother integration into workflows.

How this skill works

It compares interfaces by primary use case, token cost implications, and required setup. Follow the decision flow: check if you need file edits, PDF/image handling, batch automation, quick CLI queries, or external tool access. Hybrid patterns show how to combine interfaces for best results.

When to use it

  • Working directly in a codebase, editing multiple files, running tests → Claude Code
  • Analyzing PDFs, images, long-form writing, or research projects → Claude Desktop
  • High-volume or scheduled processing, embedding LLMs, or async jobs → API (batch or streaming)
  • Quick one-off questions, shell scripts, or piping input/output → CLI
  • Accessing databases, GitHub, or external tools in structured flows → MCP-enabled interface

Best practices

  • Use Claude Code as the default when full repo context and edits are needed
  • Reserve API for batch, predictable pipelines to control cost and latency
  • Use Desktop for document/image-heavy research before handing off to Code for implementation
  • Pipe CLI into scripts for fast checks and CI-friendly automation
  • Combine MCP with Code or API when you need direct, authenticated access to external data

Example use cases

  • Refactor authentication across a repo: Claude Code reads, edits, runs tests, and commits changes
  • Extract color palettes and specs from a design PDF: Claude Desktop handles images and exports findings
  • Process 1,000 documents overnight: API batch jobs with async processing and lower cost
  • Quick syntax lookup or generate small files from shell: echo 'question' | claude in a script
  • Run a code-driven workflow that queries Supabase during edits: Claude Code + Supabase MCP

FAQ

Which interface is cheapest for heavy interactive use?

A Pro plan is most cost-effective for heavy interactive work since Claude Code, Desktop, and CLI are unlimited under Pro.

When should I prefer Batch API over interactive tools?

Choose Batch API for large, predictable jobs (hundreds to thousands of items) or when you need asynchronous processing and predictable billing.