wyndomb/claude-code-starter — Summary

wyndomb/claude-code-starter is a productivity-workflow Claude Code starter oriented toward knowledge workers rather than software developers. It ships 7 slash commands (daily-planning, meeting-prep, project-status, research-deep-dive, standup, productivity-analyzer, weekly-synthesis) and 1 named subagent (weekly-synthesis) with a pre-configured Perplexity and Firecrawl MCP integration. The CLAUDE.md is a deliberately incomplete template requiring the user to fill in their role, priorities, and communication preferences. The central value proposition is time savings for recurring knowledge-work tasks: "Saves 15-30 min/day" (daily planning), "Saves 2-3 hours" (research), "Saves 15-20 min per switch" (project status). No hooks, no tests, no git automation — the framework is maximally simple with minimal behavioral enforcement.

differs_from_seeds: Closest to agent-os (markdown scaffold, zero automation) but oriented toward personal productivity rather than software engineering. Unlike agent-os's standards/ content for code quality, wyndomb's value is in the weekly-synthesis agent that reads daily plan files across a week and generates reflection. No seed in the reference set targets knowledge-worker productivity workflows. Compared to claude-conductor (error ledger as first-class artifact), wyndomb focuses on future planning artifacts rather than error tracking.

wyndomb/claude-code-starter — Overview

Origin

Personal Claude Code starter published by wyndomb. 6 GitHub stars, no license, language classification: null (markdown-only). Last pushed 2026-01-29. Single contributor.

Philosophy

The README positions this as a 15-minute setup for knowledge workers:

"Get started with Claude Code in 15 minutes. Clone, customize, use."

The CLAUDE.md template's preamble sets the philosophical intent:

"What This File Does: This is Claude's instruction manual for working with you. It persists across sessions, so you're not starting from zero every time. Think of it as teaching Claude your work style, preferences, and decision-making patterns."

"How to Use This Template: Start minimal. Use this as-is for your first week, then customize based on what Claude actually needs to know about how you work."

The template explicitly names anti-patterns to watch for (over-engineering, getting stuck on options) and asks users to fill in their own failure modes.

Target User

Knowledge workers (not necessarily developers): analysts, consultants, product managers, writers. The commands are named daily-planning, meeting-prep, standup, productivity-analyzer — clearly productivity-workflow focused. The research-deep-dive command specifically references Perplexity MCP integration.

Weekly Synthesis Agent

The only agent is weekly-synthesis, designed to run automatically on Fridays:

"Automatic Friday reflection compiling accomplishments, blockers, and next week's focus (saves 45 min/week)"

The agent reads daily-plans/ files, projects/ files, git commits, and file changes to compile a weekly synthesis.

MCP Pre-Configuration

The .mcp.json file is pre-configured with 4 MCP servers (Firecrawl, Perplexity, Notion, Obsidian), unusual for such a simple starter — reflecting the research-workflow orientation.

wyndomb/claude-code-starter — Architecture

Distribution

Standalone GitHub repository. Manual copy of files to user's workspace.

Install Method

git clone https://github.com/wyndomb/claude-code-starter
# Or download as ZIP

# Copy CLAUDE.md to workspace
cp CLAUDE.md ~/your-workspace/

# Copy desired commands
mkdir -p ~/your-workspace/.claude/commands/
cp .claude/commands/daily-planning.md ~/your-workspace/.claude/commands/

Directory Tree

wyndomb/claude-code-starter/
├── .claude/
│   ├── agents/
│   │   └── weekly-synthesis.md    (Friday reflection agent)
│   └── commands/
│       ├── daily-planning.md
│       ├── meeting-prep.md
│       ├── productivity-analyzer.md
│       ├── project-status.md
│       ├── research-deep-dive.md
│       ├── standup.md
│       └── weekly-synthesis.md   (also available as command)
├── .gitignore
├── .mcp.json                      (Firecrawl, Perplexity, Notion, Obsidian)
├── CLAUDE.md                      (customizable template)
├── README.md
├── REPOSITORY-SUMMARY.md
├── docs/
│   ├── claude-md/                 (CLAUDE.md design docs)
│   ├── customization-guide.md
│   ├── daily-plan-template.md
│   ├── mcp-setup-guide.md
│   ├── project-template.md
│   └── troubleshooting.md
├── examples/                      (sample outputs)
└── templates/                     (template files for daily plans, projects)

Required Runtime

• Claude Code (with Anthropic API key)
• Optional: Perplexity API key (for research-deep-dive command)
• Optional: Firecrawl API key (for web scraping)
• Optional: Notion integration (for Notion MCP)
• Optional: Obsidian vault path (for Obsidian MCP)

Target AI Tools

Claude Code primarily. MCP servers add Perplexity, Firecrawl, Notion, Obsidian access.

MCP Config (.mcp.json)

{
  "mcpServers": {
    "firecrawl-mcp": { "command": "npx", "args": ["-y", "firecrawl-mcp"] },
    "perplexity-ask": { "command": "npx", "args": ["-y", "server-perplexity-ask"] },
    "notion": { "url": "https://mcp.notion.com/mcp" },
    "obsidian": { "command": "npx", "args": ["@mauricio.wolff/mcp-obsidian@latest"] }
  }
}

wyndomb/claude-code-starter — Components

Slash Commands (7)

• daily-planning.md — generates focused daily plan from calendar + yesterday's notes; produces time-blocked schedule with high/medium/low priority tasks; claims "saves 15-30 min/day"
• meeting-prep.md — prepares for upcoming meetings by summarizing context and generating questions
• productivity-analyzer.md — analyzes productivity patterns from daily plans and project files
• project-status.md — instant context switch between projects; reads project files, recent commits, current blockers; "saves 15-20 min per switch"
• research-deep-dive.md — comprehensive research using Perplexity MCP; synthesizes sources into structured report; "saves 2-3 hours"
• standup.md — generates daily standup notes from git commits and project activity
• weekly-synthesis.md — can also be invoked as a command (same capability as the agent)

Agents (1)

• weekly-synthesis.md — Weekly Synthesis Specialist; reads daily-plans/ directory, projects/ directory, git commits; compiles: HIGH-IMPACT WINS, SOLID PROGRESS, LEARNING & GROWTH, DEFERRED INTENTIONALLY, BLOCKED, DROPPED; identifies time/energy patterns, decision quality, workflow friction; sets next week's THEME + TOP 3 PRIORITIES; writes output as markdown file; model: sonnet; color: blue; trigger: Friday or "I'm wrapping up for the week"

Hooks

None.

Skills

None (commands/agents only).

MCP Servers (4, pre-configured)

• firecrawl-mcp — web scraping for research workflows
• server-perplexity-ask — Perplexity AI search for research-deep-dive
• notion — Notion workspace integration (HTTP MCP)
• obsidian — Obsidian vault integration

Templates

• docs/daily-plan-template.md — daily plan output format
• docs/project-template.md — project status format
• examples/ — sample command outputs

CLAUDE.md Template Sections

The CLAUDE.md requires user to fill in:

• Project Overview (role, goals, tools)
• Voice & Tone preferences
• Key Preferences (decision-making patterns, AI collaboration style)
• Anti-Patterns to Avoid
• Quick Reference (key context always loaded)
• Session Rhythm (how to start/end sessions)
• Growth Areas (skills being developed)

wyndomb/claude-code-starter — Uniqueness

differs_from_seeds

The most distinctive positioning in this batch: wyndomb is the only "claude-code-starter" that explicitly targets knowledge workers rather than software developers. Closest seed is agent-os (markdown scaffold, minimal automation) but agent-os focuses on software development standards. The weekly-synthesis agent that reads a week's worth of daily plan files and git commits to generate structured reflection is a unique workflow not present in any seed or reference framework. The pre-configured 4-MCP bundle (Firecrawl + Perplexity + Notion + Obsidian) is unusual for a simple starter — it positions the framework as a research-and-knowledge-management tool. Compared to claude-conductor (error ledger + P0/P1 task tracking), wyndomb focuses on forward-planning artifacts (daily plans, weekly synthesis) rather than error tracking.

Positioning

"Get started with Claude Code in 15 minutes" — explicitly time-bounded setup for non-developer users. The README's time-savings claims (15-30 min/day, 2-3 hours/research) are the primary value proposition, framing Claude Code as a personal productivity assistant rather than a coding tool.

Observable Failure Modes

1. No license: No license file in the repo. Users cannot legally determine usage rights.
2. User-maintained context files: Daily plan files and project files must be created and maintained by the user. If user doesn't create daily-plans/ directory, weekly-synthesis agent has nothing to read.
3. Template completeness: CLAUDE.md has many [bracket] placeholders. An unfilled template provides low-quality context to Claude.
4. MCP API key requirements: Perplexity, Firecrawl, and Notion require API keys. The research-deep-dive command fails without Perplexity.
5. Low maintenance signal: 6 stars, 1 contributor, last commit 2026-01-29. Abandoned risk.

Category Note

The only "productivity-workflow" starter in this batch — not a coding assistant toolkit but a knowledge-work amplifier. Represents a different market segment for Claude Code than the other 9 frameworks analyzed here.