Skip to content

_Next: AI Config SSoT — Continue After Reboot

Section titled “_Next: AI Config SSoT — Continue After Reboot”

Date: 2026-02-20 Status: ⏸️ Paused — reboot required Context: WSL + Windows AI tool configuration unified under ~/config-ai as single source of truth


Building ~/config-ai as a git-managed SSoT for all AI tool configurations across WSL and Windows. The repo already exists with a working deploy.sh and post-commit hook that auto-deploys on commit. We then analyzed all the AI effectiveness components (skills, plugins, MCP servers, hooks, etc.) to understand how each fits into the SSoT model, and began installing skill-creator from Anthropic’s plugin marketplace.

  • Audited config-ai structure vs what actually exists in ~/.claude/
  • Documented how each component category is (or isn’t) managed
  • Installed skill-creator plugin into cache + registry (needs new session to activate)
  • Found plan file at ~/.claude/plans/compressed-crunching-lobster.md with full analysis

config-ai/
├── claude/
│ ├── CLAUDE.md ✅ SSoT for WSL Claude instructions
│ ├── CLAUDE.windows.md ✅ Windows-specific additions (appended on deploy)
│ ├── settings.wsl.json ✅ WSL settings (permissions, status line)
│ ├── settings.win.json ✅ Windows settings
│ ├── mcp.json ✅ MCP servers (Playwright currently)
│ └── commands/ ✅ Skills/slash commands (aic, cpw, now, nowcpw, ptr, ss)
├── cursor/
│ └── rules/ ✅ .mdc rule files for Cursor IDE
├── antigravity/
│ └── skills/ ✅ Gemini/AntiGravity skill files
├── deploy.sh ✅ Sync script (runs on post-commit hook)
└── README.md ⚠️ Needs updating — doesn't cover all components

deploy.sh currently handles:

  • claude/CLAUDE.md~/.claude/CLAUDE.md (WSL + Windows)
  • claude/settings.*.json~/.claude/settings.json
  • claude/mcp.json~/.claude/mcp.json
  • claude/commands/*~/.claude/commands/ (WSL + Windows)
  • cursor/rules/*monorepo/.cursor/rules/
  • antigravity/skills/*~/.gemini/antigravity/skills/ + monorepo/.agent/skills/

What they are: Slash commands invoked via /skill-name or the Skill tool. Plain .md files whose content becomes the AI prompt. SSoT location: config-ai/claude/commands/*.md Deployed to: ~/.claude/commands/ (WSL) and /mnt/c/Users/Admin/.claude/commands/ (Windows) Current skills: aic, cpw, now, nowcpw, ptr, ss (global) + deploy, deploy-kb, test-all (project-level in monorepo) Note: In Claude Code, “skills” and “commands” are the same thing — both are .md files in commands/. The README should call them “skills/commands” to be clear. To add a new skill: Create config-ai/claude/commands/skill-name.md → commit → auto-deploys.

What they are: Richer bundles that can include skills, MCP servers, agents, or commands. Installed from the marketplace. SSoT location: ~/.claude/plugins/installed_plugins.jsonNOT in config-ai (plugin installs require Claude Code CLI, can’t be scripted in deploy.sh) Marketplace: ~/.claude/plugins/marketplaces/claude-plugins-official/plugins/ Cache: ~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/ Registry: ~/.claude/plugins/installed_plugins.json (V2 format) Currently installed: skill-creator@claude-plugins-official (installed today, needs new session to activate) To install: /plugin install plugin-name@claude-plugins-official (interactive Claude Code command) To manually install (without interactive CLI):

  1. Copy plugin dir to cache: cp -r ~/.claude/plugins/marketplaces/claude-plugins-official/plugins/<name>/. ~/.claude/plugins/cache/claude-plugins-official/<name>/unknown/
  2. Update installed_plugins.json with entry pointing to unknown version

Available plugins of interest (not yet installed):

  • hookify — GUI for configuring hooks
  • commit-commands — enhanced git commit workflow
  • claude-md-management — manage CLAUDE.md files across projects
  • feature-dev — structured feature development workflow
  • pr-review-toolkit — PR review assistance
  • playground — skill/agent testing sandbox
  • plugin-dev — plugin development tools

What they are: External tools that give Claude Code extra capabilities (file systems, browsers, APIs, databases). SSoT location: config-ai/claude/mcp.json Deployed to: ~/.claude/mcp.json Current servers: playwright via @executeautomation/playwright-mcp-server Gap: Windows mcp.json is not deployed (deploy.sh only copies to WSL) To add a new MCP server: Edit config-ai/claude/mcp.json, add entry under mcpServers, commit. MCP can also be bundled in plugins (via .mcp.json in plugin package).

What they are: Shell commands that run automatically in response to Claude Code events (before/after tool calls, session start/end, etc.). SSoT location: Would be in config-ai/claude/settings.wsl.json under a hooks key Currently: NOT CONFIGURED — this is an untapped capability How they work: Defined in settings.json:

{
"hooks": {
"PreToolUse": [{ "matcher": "Bash", "hooks": [{ "type": "command", "command": "echo 'before bash'" }] }],
"PostToolUse": [...],
"Notification": [...],
"Stop": [...]
}
}

Hook types: PreToolUse, PostToolUse, Notification, Stop, SubagentStop Shortcut: The hookify plugin from the marketplace provides a UI for configuring hooks — consider installing. To add hooks: Edit config-ai/claude/settings.wsl.json, add hooks section, commit → deploys.

What they are: Built-in task tracking tools (TaskCreate, TaskList, TaskGet, TaskUpdate) — no configuration needed. Storage: ~/.claude/tasks/ (task state) + ~/.claude/todos/ (session todos) SSoT: N/A — this is a runtime system, not a config artifact Usage: TaskCreate to create, TaskUpdate to change status, TaskList to see all Note: Tasks are per-session and don’t persist meaningfully across sessions — use _Now.md for durable task tracking.

What they are: Claude Code behavior, permissions allow/deny list, status line config. SSoT location: config-ai/claude/settings.wsl.json / settings.win.json Deployed to: ~/.claude/settings.json Current permissions: All standard tools allowed; destructive bash commands denied (rm -rf /, dd *, mkfs.*, format *) Status line: Custom shell command at ~/.claude/statusline-command.sh (not in config-ai — gap!)

7. Memory (Project-specific persistent context)

Section titled “7. Memory (Project-specific persistent context)”

What it is: Persistent notes Claude reads at session start for a given project. Location: ~/.claude/projects/<path-hash>/memory/MEMORY.md (auto-loaded) Current monorepo memory: ~/.claude/projects/-home-ta-projects-monorepo/memory/MEMORY.md SSoT: NOT in config-ai — memory is project-specific runtime knowledge, not config Note: Keep under 200 lines (truncated after that). Use topic files for details.

What they are: Custom keyboard shortcuts for Claude Code actions. Location: ~/.claude/keybindings.json SSoT: Should be in config-ai/claude/keybindings.json → deployed to ~/.claude/keybindings.json Currently: Not customized, not in config-ai (gap!) To customize: /keybindings in Claude Code, or use the keybindings-help skill.

What they are: Agent definitions bundled inside plugins (sub-AI workflows). Location: Plugin’s agents/ directory — auto-activated when plugin is installed SSoT: Managed by plugin system (same as plugins — not scriptable in deploy.sh) Currently: None installed beyond what skill-creator may include

What they are: Skills for the AntiGravity IDE (Gemini-backed VS Code fork) — parallel system to Claude skills. SSoT location: config-ai/antigravity/skills/*/skill.md Deployed to: ~/.gemini/antigravity/skills/ (global) + monorepo/.agent/skills/ (workspace) Current skills: aic, now, ptr, ss

What they are: AI behavior rules for Cursor IDE. SSoT location: config-ai/cursor/rules/*.mdc Deployed to: monorepo/.cursor/rules/ Current rules: 00-behavior.mdc, 01-project.mdc, 02-conventions.mdc


  • Open new Claude Code session — verify skill-creator appears in available skills
  • Test it: /skill-creator or use the Skill tool with skill: "skill-creator"
  • Add statusline-command.sh to config-ai — currently lives only in ~/.claude/, not version-controlled
    • config-ai/claude/statusline-command.sh → deployed to ~/.claude/statusline-command.sh
  • Add keybindings — create config-ai/claude/keybindings.json → deploy to ~/.claude/keybindings.json
  • Fix Windows MCP gapdeploy.sh should also copy mcp.json to Windows Claude path
  • Add hooks to settings.wsl.json — start simple (e.g., auto-log tool usage, notify on long tasks)
    • Consider installing hookify plugin first for UI-guided hook setup
  • Update README — add all component categories (skills, plugins, hooks, keybindings, agents, memory, AntiGravity, Cursor)

Evaluate and consider installing:

  • hookify — helps set up hooks with a GUI (do this before writing hooks manually)
  • commit-commands — enhanced git workflow
  • claude-md-management — useful if managing CLAUDE.md across many projects
  • feature-dev — consider if we want structured feature workflows

Once skill-creator is confirmed working:

  • Create a deploy skill for config-ai deployment reminders
  • Consider: review-plan skill for structured plan reviews
  • Evaluate: session-close skill that prompts writing a SESSION note + updating _Now.md

ItemConfig-AI SourceDeployed To
Claude instructionsclaude/CLAUDE.md~/.claude/CLAUDE.md
Windows additionsclaude/CLAUDE.windows.mdappended to Windows CLAUDE.md
WSL settingsclaude/settings.wsl.json~/.claude/settings.json
Win settingsclaude/settings.win.json/mnt/c/Users/Admin/.claude/settings.json
MCP serversclaude/mcp.json~/.claude/mcp.json
Skills/Commandsclaude/commands/*.md~/.claude/commands/ (+ Windows)
Keybindingsclaude/keybindings.json ❌ missing~/.claude/keybindings.json
Status line script❌ not in config-ai~/.claude/statusline-command.sh
Plugins❌ not in config-ai (CLI-managed)~/.claude/plugins/
HooksIn settings.wsl.json (not yet added)~/.claude/settings.json
Cursor rulescursor/rules/*.mdcmonorepo/.cursor/rules/
AntiGravity skillsantigravity/skills/*/skill.md~/.gemini/antigravity/skills/
Project memory❌ not in config-ai (runtime)~/.claude/projects/.../memory/MEMORY.md

Terminal window
# Edit any config file
vim ~/config-ai/claude/CLAUDE.md # or any file in the repo
# Commit → post-commit hook auto-deploys everything
cd ~/config-ai
git add -A && git commit -m "feat: ..."
# Manual deploy if needed
~/config-ai/deploy.sh

  • Plan: ~/.claude/plans/compressed-crunching-lobster.md — full component analysis from this session
  • Config repo: ~/config-ai/
  • Plugin registry: ~/.claude/plugins/installed_plugins.json
  • Marketplace: ~/.claude/plugins/marketplaces/claude-plugins-official/