Repository files navigation

Starter template repo for all your Claude Code needs — pre-configured MCP servers, skills, sub-agents, commands, and hooks for AI-powered development workflows.

This is a template repository that gives you a ready-to-use Claude Code development environment. It ships with mcp servers, development-related skills, task orchestration tooling, hooks, slash commands — all configured and wired together.

Four servers, configured at user-level (~/.claude.json) to keep API keys out of the repo:

Skills are specialized workflows Claude invokes during different development phases:

Three agents for task-driven development workflows:

Slash commands organized hierarchically:

• Task Master (/project:tm/) — 47 commands covering the full task lifecycle:
  • Setup:init,install-taskmaster,setup-models
  • Daily workflow:next,list,show,set-status/to-{done,in-progress,review,...}
  • Task management:add-task,update,expand,remove-task
  • Analysis:analyze-complexity,complexity-report,analyze-project
  • Dependencies:add-dependency,remove-dependency,validate-dependencies,fix-dependencies
  • Subtasks:add-subtask,remove-subtask,clear-subtasks
  • Workflows:smart-workflow,command-pipeline,auto-implement-tasks
  • Full reference:.claude/TM_COMMANDS_GUIDE.md
• CoVe (/project:cove/) — 2 commands for Chain-of-Verification prompting (standard and isolated modes)

• Bash validation (PreToolUse) — blocks bash commands that touch.env,.git/,node_modules,build/,dist/,venv/, and other sensitive paths

• Permission allowlist/denylist (.claude/settings.json) — auto-approves safe tools (context7, serena read-only, task master, pal code review) while blocking dangerous ones
• Status line (.claude/scripts/statusline.sh) — minimalistic statusline that shows current model and context window usage percentage
• Serena config (.serena/project.yml) — language detection, gitignore integration, encoding settings
• Task Master config (.taskmaster/config.json) — AI model roles (main/research/fallback), task defaults

• template-cleanup workflow — one-click GitHub Action to initialize a new repo from this template
• template-sync workflow — pull upstream configuration updates into your project via PR
• Sync exclusions — prevent specific files from being re-added during sync
• Test suite — 72 tests across 3 suites covering the sync/cleanup infrastructure

• npm
• uv
• jq — required for template-cleanup

• Context7 API key
• Gemini API key forPal (orany other provider)

{"context7": {"type":"http","url":"https://mcp.context7.com/mcp","headers": {"CONTEXT7_API_KEY":"YOUR_CONTEXT7_API_KEY"    }  },"serena": {"type":"stdio","command":"uvx","args": ["--from","git+https://github.com/oraios/serena","serena","start-mcp-server","--context","ide-assistant","--project","."    ],"env": {}  },"task-master-ai": {"type":"stdio","command":"npx","args": ["-y","--package=task-master-ai","task-master-ai"    ],"headers": {}  },"pal": {"command":"sh","args": ["-c","$HOME/.local/bin/uvx --from git+https://github.com/BeehiveInnovations/pal-mcp-server.git pal-mcp-server"    ],"env": {"PATH":"/usr/local/bin:/usr/bin:/bin:$HOME/.local/bin",# see https://github.com/BeehiveInnovations/pal-mcp-server/blob/main/docs/configuration.md#model-configuration"DEFAULT_MODEL":"auto",# see https://github.com/BeehiveInnovations/pal-mcp-server/blob/main/docs/advanced-usage.md#thinking-modes"DEFAULT_THINKING_MODE_THINKDEEP":"high","GEMINI_API_KEY":"YOUR_GEMINI_API_KEY",# see https://github.com/BeehiveInnovations/pal-mcp-server/blob/main/docs/configuration.md#model-usage-restrictions"GOOGLE_ALLOWED_MODELS":"gemini-3-pro-preview,gemini-2.5-pro,gemini-2.5-flash"    }  }}

"serena": {"type":"stdio","command":"serena","args": ["start-mcp-server","--context","ide-assistant","--project","."    ],"env": {}  },"task-master-ai": {"type":"stdio","command":"task-master-ai","args": [],"headers": {}  },"pal": {"command":"pal-mcp-server","args": [],"env": {...}  }

1. Create a new project from this template using theUse this template button.

2. A scaffold repo will appear in your GitHub account.

3. Run thetemplate-cleanup workflow from your new repo's Actions tab. Provide inputs:

Serena:

• LANGUAGES (required) — programming languages, comma-separated (e.g.,python,python,typescript).Seesupported languages.
• SERENA_INITIAL_PROMPT — initial prompt given to the LLM on project activation

Task Master:

• TM_CUSTOM_SYSTEM_PROMPT — override Claude Code's default system prompt

• TM_APPEND_SYSTEM_PROMPT — append to the system prompt

• TM_PERMISSION_MODE — permission mode for file system operations

  [!TIP]SeeTask Master advanced settings for details on these parameters.

4. Clone your new repo and cd into it

   Runclaude /mcp, you should see the mcp servers configured and active:

   > /mcp╭────────────────────────────────────────────────────────────────────╮│ Manage MCP servers                                                 ││                                                                    ││ ❯ 1. context7                  ✔ connected · Enter to view details ││   2. serena                    ✔ connected · Enter to view details ││   3. task-master-ai            ✔ connected · Enter to view details ││   4. pal                       ✔ connected · Enter to view details │╰────────────────────────────────────────────────────────────────────╯

   Runclaude "list your skills", you should see the skills from this repo present:

   > list your skills● I have access to the following skills:  Available Skills  ...  ---  These skills provide specialized workflows for different stages of development. You can invoke any of them by asking me to use a specific skill (e.g., "use the analysis-process skill" or "help me document this feature").

5. Update theREADME.md with your project description, then runchmod +x bootstrap.sh && ./bootstrap.sh to finalize initialization.

6. Profit

Repos created from this template can pull configuration updates via theTemplate Sync workflow.

• .github/template-state.json must exist (created automatically for new repos, ormanually for older ones)
• Allow actions to create pull-requests: repoSettings →Actions

1. Go toActions →Template Sync →Run workflow
2. Choose a version:latest (default),master, or a specific tag (e.g.,v1.2.3)
3. Optionally enabledry_run to preview changes without creating a PR
4. Review and merge the created PR
5. Merge to apply updates

Updated:.claude/ (commands, skills, agents, scripts, settings),.serena/,.taskmaster/ configs, and the sync infrastructure itself

Preserved: Project-specific values (name, language, prompts), user-scoped files (tasks, PRDs, local settings), gitignored files

If you've removed template files you don't need, prevent sync from re-adding them:

Edit.github/template-state.json and add async_exclusions array:

{  "schema_version": "1",  "upstream_repo": "serpro69/claude-starter-kit",  "template_version": "v0.2.0",  "synced_at": "2025-01-27T10:00:00Z",+ "sync_exclusions": [+   ".claude/commands/cove/*",+   ".claude/skills/cove/*"+ ],  "variables": { "..." : "..." }}

Pattern syntax:

• Patterns use glob syntax where* matches any characters including directory separators
• Patterns are matched against project-relative paths (e.g.,.claude/commands/cove/cove.md)
• Common patterns:.claude/commands/cove/* (entire directory),.taskmaster/templates/example_prd.txt (single file)

Behavior:

• Excluded files are NOT added if they exist upstream but not locally
• Excluded files are NOT updated if they exist in both places
• Excluded files are NOT flagged as deleted if they exist locally but not upstream
• Excluded files appear as "Excluded" in the sync report for transparency

If your repo was created before the sync feature (or even if your repo wasn't created from this template at all), create.github/template-state.json:

{"schema_version":"1","upstream_repo":"serpro69/claude-starter-kit","template_version":"v1.0.0","synced_at":"1970-01-01T00:00:00Z","variables": {"PROJECT_NAME":"my-cool-project","LANGUAGES":"go","CC_MODEL":"default","SERENA_INITIAL_PROMPT":"","TM_CUSTOM_SYSTEM_PROMPT":"","TM_APPEND_SYSTEM_PROMPT":"","TM_PERMISSION_MODE":"default"  }}

Then copy.github/workflows/template-sync.yml and.github/scripts/template-sync.sh from thetemplate repository.

The following tweaks are not mandatory, but will more often than not improve your experience with CC

> /config──────────────────────────────────────────────────────────── Configure Claude Code preferences    Auto-compact                              false    Show tips                                 true    Reduce motion                             false    Thinking mode                             true    Prompt suggestions                        true    Rewind code (checkpoints)                 true    Verbose output                            false    Terminal progress bar                     true    Default permission mode                   Default    Respect .gitignore in file picker         true    Auto-update channel                       latest    Theme                                     Dark mode    Notifications                             Auto    Output style                              default    Language                                  Default (English)    Editor mode                               vim    Show code diff footer                     true    Show PR status footer                     true    Model                                     opus    Auto-connect to IDE (external terminal)   false    Claude in Chrome enabled by default       false

Tests across 3 suites covere the template sync/cleanup infrastructure:

# Run all test suitesfortestin test/test-*.sh;do$test;done# Run individual suites./test/test-manifest-jq.sh# jq JSON pattern tests./test/test-template-sync.sh# template-sync.sh function tests./test/test-template-cleanup.sh# generate_manifest() tests

.claude/├── agents/                 # 3 sub-agents (orchestrator, executor, checker)├── commands/│   ├── cove/              # 2 CoVe verification commands│   └── tm/                # 47 Task Master commands├── hooks/                 # Bash validation hook config├── scripts/               # statusline.sh, validate-bash.sh├── skills/                # 7 development workflow skills├── settings.json          # Shared permission config└── TM_COMMANDS_GUIDE.md   # Task Master command reference.serena/└── project.yml            # Serena LSP configuration.taskmaster/├── config.json            # AI model configuration├── docs/                  # PRDs and requirements├── reports/               # Analysis reports├── tasks/                 # Task database and generated files├── templates/             # Example PRD template└── CLAUDE.md              # Task Master integration guide (400+ lines).github/├── scripts/               # template-cleanup.sh, template-sync.sh, bootstrap.sh├── workflows/             # template-cleanup, template-sync└── template-state.json    # Sync manifest and variablestest/├── helpers.sh             # Shared test utilities and assertions├── test-*.sh              # 3 test suites└── fixtures/              # Test manifests and templates

Examples of actual Claude Code workflows executed using this template's configs, skills, and tools:examples/

Feel free to open new PRs/issues. Any contributions you make are greatly appreciated.

Copyright © 2025 - present,serpro69

Distributed under the MIT License.

SeeLICENSE.md file for more information.