Skip to Content
UseCustomization

Customization

The defaults are meant to be good. Customize when you notice repeated friction.

The rule

  • Edit: .dotpack/ (source of truth)
  • Regenerate: dotpack build
  • Don’t hand-edit: .gemini/, .cursor/, .claude/ (generated)

When to customize (and when not to)

  • Don’t customize on day 1. Use the defaults until patterns emerge.
  • Customize when you keep correcting the same behaviors:
    • Skills: conventions, stack patterns, “how we do X here”
    • Commands: workflow steps / definition-of-done (tests, review gates)
    • Agents: tone/process preferences (concise vs verbose, strictness, etc.)

Customize commands

Commands live in .dotpack/commands/.

echo "# Deploy\n\nDeploy the app to production." > .dotpack/commands/deploy.md dotpack build

Customize agents

Agents live in .dotpack/agents/.

echo "# Security Reviewer\n\nFocus on auth, secrets, and dependencies." > .dotpack/agents/security.md dotpack build

Customize skills

Skills live in .dotpack/skills/. Use them to encode stack conventions and best practices.

Team sharing

  • Commit .dotpack/ always
  • Commit generated outputs if not everyone installs Dotpack locally
Last updated on