# Portable Config Baseline Pattern

> Extract machine-agnostic settings into portable template files while keeping machine-specific hooks and plugins separate

- Skill: `vamseeachanta/portable-config-baseline-pattern-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vamseeachanta/portable-config-baseline-pattern-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vamseeachanta/portable-config-baseline-pattern-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: vamseeachanta (https://skillmd.com/u/vamseeachanta)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vamseeachanta/portable-config-baseline-pattern-2

---


# Portable Config Baseline Pattern

When managing config files across multiple machines, separate portable baseline settings (safe everywhere) from machine-specific wiring (hooks, plugins, local paths). Use a template file (e.g., `config/agents/claude/settings.json`) as the canonical portable baseline, then layer machine-specific overrides in the live config. Verify separation by grepping for actual execution paths—only comments and diagnostic messages should reference machine-specific tools; all real calls use portable resolution patterns like `command -v python3 || command -v python`.