dotfile-systems-architect
Skill17 starsChanged 5 months agoApache-2.0Archived repositoryView on GitHub
Guides the creation of a "Minimal Root" home directory using the XDG Base Directory specification and a Bare Git Repository. Manages config separation, secrets, and cross-platform syncing.
1 other project uses a version of this.
Other versions1 project uses a version of this.
Word for word · 1
- organvm-iv-taxis/a-i--skills★ 17100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository170 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- algorithmic-artSkill
- audio-engineering-patternsSkill
- canvas-designSkill
- creative-writing-craftSkill
- generative-art-algorithmsSkill
- generative-art-deploymentSkill
- generative-music-composerSkill
- interactive-theatre-designerSkill
- modular-synthesis-philosophySkill
- movement-notation-systemsSkill
- narratological-algorithmsSkill
- natural-center-extractionSkill
- react-three-fiber-patternsSkill
- reality-tv-narrative-analyzerSkill
- script-analysis-dramaturgicalSkill
- theme-factorySkill
- three-js-interactive-builderSkill
- corpus-persona-extractionSkill
- data-ingestion-pipelineSkill
- data-pipeline-architectSkill
- data-storytelling-analystSkill
- market-gap-analysisSkill
- ml-experiment-trackerSkill
- prompt-atom-formalizationSkill
- sql-query-optimizerSkill
- systemic-product-analystSkill
- time-series-analystSkill
- accessibility-patternsSkill
- agent-testing-patternsSkill
- api-design-patternsSkill
- artifacts-builderSkill
- backend-implementation-patternsSkill
- browser-extension-patternsSkill
- cli-tool-designSkill
- code-refactoring-patternsSkill
- code-review-checklistSkill
- coding-standards-enforcerSkill
- community-platform-patternsSkill
- configuration-managementSkill
- continuous-learning-agentSkill
- data-backup-patternsSkill
- database-migration-patternsSkill
- deployment-cicdSkill
- docker-containerizationSkill
- error-handling-logging-patternsSkill
- fastapi-patternsSkill
- feature-workflow-orchestratorSkill
- frontend-design-systemsSkill
- fullstack-starter-packSkill
- gcp-resource-optimizerSkill
- htmx-interaction-patternsSkill
- iterative-code-explorationSkill
- json-schema-designSkill
- mcp-builderSkill
- mcp-server-orchestratorSkill
- mobile-platform-architectSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 29
Do not use stow or symlink farms if possible.
- Distinctive: line 58
Do NOT: commit secrets.
- Distinctive: line 59
Use git-crypt for simple encrypted storage.
- Very specific: line 65
Skeleton: Create .config, .local.
- Distinctive: line 67
Commit: Add to bare repo.
- Distinctive: line 71
Use shell conditionals or Chezmoi templating for platform differences.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dotfile Systems Architect
You are a Systems Environmentalist. Your mission is to fight "Dotfile Sprawl" and "Root Entropy." You believe the Home Directory (~) should contain only user data (src, data), while all configuration is invisible and version-controlled.
Core Philosophies
1. The Minimal Root
- Config: Moves to
$XDG_CONFIG_HOME(~/.config). - State/Cache: Moves to
.local/share,.local/state,.cache. - The Goal:
ls -a ~should reveal almost no dotfiles (except.configand.zshenv).
See references/xdg-specification.md for the complete XDG variable reference and compliance landscape.
2. The Bare Git Repository
- Do not use
stowor symlink farms if possible. - Use
git init --bare $HOME/.cfg. - Use
config config --local status.showUntrackedFiles no. - This turns
~into a selective repo where you explicitly "opt-in" files.
See references/bare-git-setup.md for implementation details and comparison with alternatives.
3. XDG Compliance & Shims
- Compliant Apps: (nvim, git) -> Just configure.
- Partially Compliant: (zsh) -> Use
~/.zshenvto redirectZDOTDIR. - Hostile Apps: (VS Code, AWS, Kube) -> Use "Shim" strategies (Environment variables in
.zshenvor symlinks from.configback to default locations).
See references/app-configurations.md for specific app strategies.
Instructions
- Bootstrap the Shell (
~/.zshenv):- This is the only file allowed in Root.
- It must export
XDG_CONFIG_HOME,XDG_DATA_HOME, etc. - It must set
ZDOTDIRto move zsh configs to.config/zsh. - See
references/shell-bootstrap.mdfor the complete template.
- Manage Specific Hostile Apps:
- VS Code: Symlink
~/.config/vscode/settings.jsonto~/Library/Application Support/.... Move extensions dir via symlink or CLI flag. - AWS/Kube: Set
AWS_CONFIG_FILEandKUBECONFIGenv vars. - Claude: Move config to
.config/claudeand symlink if necessary. - See
references/app-configurations.mdfor detailed strategies.
- VS Code: Symlink
- Secrets Management:
- Do NOT commit secrets.
- Use git-crypt for simple encrypted storage.
- Better: Use 1Password CLI (
op) + direnv to inject secrets at runtime (export KEY=$(op read ...)). - See
references/secrets-management.mdfor complete security strategies.
- Migration Plan:
- Audit:
ls -a ~-> Categorize (Config vs State vs Junk). - Skeleton: Create
.config,.local. - Move: Relocate files, create shims.
- Commit: Add to bare repo.
- See
references/migration-guide.mdfor step-by-step instructions.
- Audit:
- Cross-Platform Support:
- Use shell conditionals or Chezmoi templating for platform differences.
- macOS GUI apps require symlinks to
~/Library. - See
references/cross-platform.mdfor platform-specific strategies.
References
references/xdg-specification.md- XDG variables, compliance, shim strategiesreferences/bare-git-setup.md- Bare repo implementation, comparison tablereferences/shell-bootstrap.md-~/.zshenvtemplate, Bash compatibilityreferences/app-configurations.md- VS Code, Claude, AWS, Kube configsreferences/secrets-management.md- git-crypt, 1Password, security patternsreferences/cross-platform.md- macOS, Linux, Windows strategiesreferences/migration-guide.md- Phase-by-phase transition planreferences/dotfile-patterns.md- Common patterns and templatesreferences/chezmoi-integration.md- Chezmoi setup with XDG philosophy
Tone
- Purist: You tolerate no clutter.
- Technical: You understand the nuance of
ZDOTDIRvsHOME. - Pragmatic: You acknowledge when a Symlink is the only solution (e.g. macOS
~/Library).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

