skills.rest
mkarrmann
mkarrmannCOMMUNITY
Explore all skills by this author →
GitHub

personal-development-setup-and-env

Document portable and machine-local overrides for Neovim, shell, and editor configurations.

1|Updated Nov 29, 2021
Search Tags:#development#dotfiles#config#setup#organization#environment#overrides
One-click install
npx skills add https://github.com/mkarrmann/dotfiles --skill personal-development-setup-and-env
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: personal-development-setup-and-env
Source: https://github.com/mkarrmann/dotfiles/tree/main/agent_config/skills/personal-development-setup-and-env
Command: npx skills add https://github.com/mkarrmann/dotfiles --skill personal-development-setup-and-env

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps you understand and organize your development environment, clarifying which files should be kept in source control versus stored locally.

Core Features & Use Cases

  • Document the portable vs local configuration layout across tools like Neovim, shells, and editors, so setups are reproducible on any machine.
  • Provide a clear pattern for local overrides, showing how portable config loads first and local overrides are applied silently.
  • Guide the creation of new configuration files and skills with explicit source-control boundaries to reduce drift and confusion.

Quick Start

Describe your current setup and identify which files belong in source control versus local overrides, then apply the portable/local pattern to your dotfiles.

Frequently Asked Questions about personal-development-setup-and-env

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I separate portable dotfiles from local machine overrides?▼

To separate portable dotfiles from local overrides, enforce a clear layout where portable source-controlled configurations load first, and machine-local overrides are applied silently afterward to prevent drift and ensure reproducibility.

What is the best way to keep my Neovim and shell config consistent across multiple machines?▼

Keeping Neovim and shell config consistent across multiple machines requires documenting your environment layout with explicit source-control boundaries, applying portable configurations first and local overrides second for reproducible setups.

Which development environment files should be kept in source control versus stored locally?▼

Development environment files should be organized by keeping portable configurations in source control, while machine-specific settings are stored locally as overrides, reducing confusion and drift between different setups.

How do I set up local overrides for my editor configurations without breaking portable setups?▼

Setting up local overrides for editor configurations involves applying a consistent override pattern where portable config loads first and local overrides are applied silently, maintaining a portable setup across machines.

When do I need to document my development environment organization?▼

You need to document your development environment organization when you want reproducible setups across multiple machines and easy onboarding for new skills, ensuring clear separation between portable and local configurations.

Related Skills

Explore More Software Engineering Skills→
bfowlebfowle

backup-and-restore

Back up and restore dotfiles in Unix-like environments with timestamped manifests.

Community
Basic
rtfpessoartfpessoa

workspace

Configure and manage AI development environments for Claude Code, MCP servers, and OpenCode CLI.

Community
Intermediate
vemolistavemolista

editing-dotfiles

Manage dotfiles across machines with chezmoi-backed source control.

Community
Intermediate
pax-kpax-k
6

wiki-switch

Switch active Obsidian vault profiles by updating a symlink.

Community
Intermediate