メニュー
Manage the dotfiles repository, stow packages, and configure agent skills. Use when adding a skill, modifying the stow setup, or working inside ~/dotfiles.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/susamn/aistuff --skill dotfiles-managementコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Practice LeetCode problems in a 3-tab mosaic dashboard (Problem, Intuition, Solution — Python + Go). Starter-seeded with 100 classic problems; add, swap, or remove any problem by URL or description. Use when asked to practice LeetCode, add/swap a coding-interview problem, or open the LeetCode practice dashboard.
Import external skills from Git repositories, local directories, or web URLs into the local skills library, adapting them to house conventions, auditing, and suggesting cross-skill integrations. Use when importing a skill, bringing in an external skill, or adding a skill from GitHub.
Guide for creating effective skills that extend different agents' capabilities. Use when creating new skills or updating existing skills with specialized knowledge, workflows, or tool integrations.
| name | dotfiles-management |
| description | Manage the dotfiles repository, stow packages, and configure agent skills. Use when adding a skill, modifying the stow setup, or working inside ~/dotfiles. |
| version | 3.1.0 |
| kind | guidance |
| triggers | ["manage dotfiles","add a skill","modify stow setup","work inside dotfiles"] |
| intent | system |
| guardrails | ["Do not stow the workspace/aistuff/ directory.","Do not use absolute paths when environment variables are available.","Document any new shell aliases in workspace/.alias_descriptions."] |
| resources | ["~/dotfiles/do-stow.sh","~/dotfiles/do-unstow.sh","~/dotfiles/workspace/aistuff/skills/AGENTS-TEMPLATE.md","<SKILL_PATH>/references/service-installation.md","<SKILL_PATH>/references/linux-system-manager-development.md","<SKILL_PATH>/references/personal-systemd-services.md","<SKILL_PATH>/references/music-sync-and-mpd.md"] |
| tools | ["bash","stow","git"] |
| created_at | 2026-05-30T00:00:00.000Z |
| updated_at | 2026-08-16T00:00:00.000Z |
Only relevant when you are explicitly helping the user manage their dotfiles (i.e. the user has asked you to add a skill, modify the stow setup, or work inside
~/dotfiles/). If you are helping with any other task, ignore this section.
~/dotfiles/
├── .config/ # app configs (Hyprland, kitty, nvim, waybar, rofi, …)
├── workspace/ # scripts, tools, sdk, services (stowed to ~/workspace/)
│ ├── aistuff/ # git submodule — agent assets, NOT stowed to ~
│ │ ├── mcp/ # MCP server definitions, synced by workspace/scripts/agm.sh
│ │ └── skills/ # canonical skills
│ │ ├── .agents # agent deployment config (4 columns, see below)
│ │ ├── AGENTS-TEMPLATE.md # source of every agent's instruction file
│ │ └── <skill-name>/
│ │ └── SKILL.md
├── .ignored # extra ignore patterns read by do-stow.sh
├── .stow-local-ignore # stow's ignore list (REPLACES stow's built-in defaults)
├── do-stow.sh # stow + deploy skills + generate instructions + sync mcp
├── do-unstow.sh # reverse of do-stow.sh
└── onboard.sh # first-run machine bootstrap
workspace/aistuff/ is excluded from stow via ^workspace/aistuff$ in .stow-local-ignore, so
neither the skills submodule nor the MCP definitions land in ~.
do-stow.sh then does three things beyond stowing:
workspace/aistuff/skills/AGENTS-TEMPLATE.md, substituting {{AGENT_SKILLS_PATH}} and
{{INSTRUCTION_PATH}}. These are real files, not symlinks, and they are
overwritten on every run. Never edit ~/.claude/CLAUDE.md directly — the
change will be silently lost. Edit workspace/aistuff/skills/AGENTS-TEMPLATE.md instead.workspace/scripts/agm.sh sync, which merges
workspace/aistuff/mcp/mcp-servers.json into each agent's MCP config.Deployment is decided by directory name alone: a skill directory suffixed
.disabled has its symlink actively removed from every agent and is not
deployed. Nothing reads the column in the skills table — it is
documentation that must be updated by hand to match.
Enabledmv ~/dotfiles/workspace/aistuff/skills/<name> ~/dotfiles/workspace/aistuff/skills/<name>.disabled # disable
mv ~/dotfiles/workspace/aistuff/skills/<name>.disabled ~/dotfiles/workspace/aistuff/skills/<name> # re-enable
bash ~/dotfiles/do-stow.sh # apply
./do-stow.sh # full setup
./do-unstow.sh # full teardown
stow -vt ~ . # manual stow (.stow-local-ignore handles exclusions)
stow -Dvt ~ . # manual unstow
stow -vt ~ . --adopt # resolve conflicts
---
name: skill-name
description: one-line summary
version: 1.0.0
triggers:
- "natural language phrase"
intent: code-review | git | system | debug | media | …
config_dir: ~/.config/skill-config/skill-name
guardrails:
- Do not X
resources:
- ./scripts/script-name.sh # Relative to skill directory
- $TOOLS_PATH/tool-name # Global tools
tools:
- bash
interface:
input:
param: "type — description"
output:
result: "type — description"
---
Markdown body: step-by-step instructions for the agent. Use <SKILL_PATH> placeholder for absolute paths.
Edit workspace/aistuff/skills/.agents — four whitespace-separated columns, - meaning "none":
| column | meaning |
|---|---|
name | agent identifier |
skills_path | where skill symlinks are deployed |
instruction_symlink | absolute path of the generated instruction file |
mcp_config_path | absolute path for the synced MCP servers JSON |
gemini ~/.gemini/skills ~/.gemini/GEMINI.md ~/.gemini/mcp.json
cursor ~/.cursor/rules - ~/.cursor/mcp.json
Then run ./do-stow.sh. Because workspace/aistuff is a submodule, committing is
two steps: commit changes inside ~/dotfiles/workspace/aistuff, then
git add workspace/aistuff in ~/dotfiles to bump the submodule pointer.
linux-system-manager is an in-tree tool at $TOOLS_PATH/linux-system-manager
(absorbed from its standalone repo; history on the lsm-history/* branches).
Unit files and engines live in $SERVICES_PATH, not inside the tool. Install and
inspect them from asm → Section 5: 54 shows what is installed, 55
installs or updates. Never hand-write per-profile unit files — an rclone sync
needs only a profile, since the profile name is the systemd instance.
Changing the tool itself (menu capability, new distro, installer) — read
references/linux-system-manager-development.md, which points at the tool's own
maintainer guide at $TOOLS_PATH/linux-system-manager/SKILL.md.
Membership in personal-services.target is declared by each unit's own
[Install] section, not by the target, and systemctl enable writes that link
whether or not the target exists. The failure modes here are silent: systemd
accepts the broken configuration and runs nothing.
Tracks and playlists arrive by different mechanisms. Audio is an rclone sync
from Drive on a timer. Playlists and lyrics are the music-metadata git repo,
pulled by hand — do not add a systemd unit to automate that pull: the SSH key is
passphrase-protected, so it has no way to authenticate and would fail every run.
~/.config/mpd/mpd.conf is generated, not stowed — mpdc configure rebuilds
it from the version-controlled mpd.conf.bak template, taking music_directory
from the tracks profile's LOCAL_PATH and playlist_directory from a path it
asks for. Direct edits to mpd.conf are silently discarded. The template ships
playlist_directory "@PLAYLIST_DIR@", a placeholder rather than a real path, so
an unconfigured mpd.conf fails loudly instead of pointing MPD somewhere nobody
chose.
Read references/music-sync-and-mpd.md before editing a sync profile, moving the
library, retiring a sync, or debugging a sync that ran but changed nothing.
| file | when |
|---|---|
references/service-installation.md | installing on a new machine, adding a sync or service, what lands where |
references/linux-system-manager-development.md | changing the tool: menu items, new distro, installer, the traps that have bitten |
references/personal-systemd-services.md | personal-services.target, scope semantics, debugging a unit that "enabled fine" but never runs |
references/music-sync-and-mpd.md | rclone sync profiles, mpd.conf generation, music library paths |