Developer tooling · meta-tool · Claude Code

Starter Pack

A reusable scaffold I pull into every new Claude Code project — the rules, templates, skills and habits that make a build start clean, instead of from a blank slate.

$ cd new-project
$ claude

> bootstrap from
  starter-pack

  ✓ profile
  ✓ templates
  ✓ workflows
  ✓ skills
  ✓ checklists
  ✓ guardrails

→ ready to build.
ScopeRules · templates · skills · workflows
PlatformClaude Code
StatusIn daily use · versioned
Built inEvolving

What it is

It isn't an app — it's the infrastructure behind how I build. A Git-versioned kit I pull into every new Claude Code project so it starts with my conventions, guardrails and templates already in place. Most designers never build their own scaffolding; this is a systems mindset turned on my own workflow.

Profiles

Soft context about how I work and where my edges are — applied by reference so the AI tunes its defaults to me, without overriding the hard rules.

Templates

Skeletons for the canonical project docs — CLAUDE.md, PRD, plan, HANDOVER, settings — so every project documents itself the same way.

Workflows

Reusable rule sets — no soft fallbacks, docs-evolve-with-code, explore-plan-execute — that travel with every build.

Skills

Slash commands I reuse, like a why-focused commit (/asia-commit) and a session close-out (/asia-wrapup).

Checklists

A kickoff sequence for new projects and a return checklist for picking work back up cleanly.

References

The gotchas, anti-patterns and model facts I don't want to relearn each time — kept current by a refresh ritual.

starter-pack/
├─ profile/      about-me · working-together
├─ templates/    CLAUDE.md · settings · PRD · HANDOVER
├─ workflows/    no-soft-fallbacks · tdd-default · …
├─ skills/       /asia-commit · /asia-wrapup
├─ checklists/   new-project · return
└─ references/   gotchas · anti-patterns · mcp
What's in the pack

Decisions I made

  1. Tooling for how I buildRather than start each project from scratch, I built the scaffold once — a systems mindset applied to my own workflow.
  2. Rules as guardrails, not ceremonyNo soft fallbacks, docs evolve with code, ask before anything destructive — defaults that ride along to every project, not process for its own sake.
  3. Phase-aware disciplineIt distinguishes expand (explore widely, scope open) from commit (scope locked, build cleanly), so the discipline matches the moment.
  4. By reference, not copyProjects pull the pack in by reference, so an improvement flows everywhere at once instead of being frozen at copy time.
  5. Kept current by ritualA refresh command checks the pack against the latest official docs and proposes changes one at a time — I approve each.
Outcome

In daily use across my projects

In use

Pulled into every new build — including the two alongside it.

The point

Personal tooling, not a product — I build the thing that makes my builds better.

← All builds Build 03 / 03 Next build →