Apply STRATEGY.md rules before recommending dotfiles setup changes.
npx skills add https://github.com/tnunamak/dotfiles --skill dotfiles-strategy
Please help me install this Agent Skill. Skill: dotfiles-strategy Source: https://github.com/tnunamak/dotfiles/tree/main/.agents/skills/dotfiles-strategy Command: npx skills add https://github.com/tnunamak/dotfiles --skill dotfiles-strategy
This Skill prevents inconsistent or risky changes by ensuring any proposed modification to the dotfiles setup process is grounded in the repo’s established strategy and decision rationale.
Ask an AI to propose a change to setup.sh or sync-mcps.sh while first summarizing the relevant rules from STRATEGY.md and explaining how the proposal follows them.
High-intent search queries and answers about installing and using this skill.
To keep dotfiles changes consistent across multiple agents, load the repository's strategy rules from STRATEGY.md first. This ensures all modifications to setup scripts and MCP management follow the same source-of-truth and separation of concerns.
The best way to govern stow packaging updates is to apply one-mechanism-per-concern rules from the repository's strategy document. This prevents conflicting behaviors by keeping symlinking and external tool responsibilities strictly separated.
To safely modify setup.sh without breaking the bootstrap flow, review the repository's strategy rules first. Grounding your proposed changes in the established decision rationale prevents risky or inconsistent updates to the installation logic.
You need to check STRATEGY.md before editing sync-mcps.sh whenever you propose changes to MCP management. Consulting this source-of-truth document ensures your updates maintain multi-agent parity and align with the core installation strategy.
Updating ai/mcp-servers.json requires reading the repository strategy first because it enforces multi-agent parity. This ensures any changes to MCP or skill management remain compatible with the established installer choices and tradeoff consistency.
Yes, you can use this strategy governance for modifying ai/skills/ configurations. It guides safe updates around skill management by ensuring proposals remain compatible with the repository's established source-of-truth and separation of concerns.
bendruckerImplement and manage ZSH completion files for CLI tools in dotfiles repositories.
withkynamAudit VC harness health across Claude/Codex parity and protocol wiring.
1Mangesh1Automate dotfile synchronization across machines using GNU Stow, Chezmoi, or Git bare repositories.
tizeeCreate and run standalone Python scripts with inline dependency metadata using uv.
