Shareable source of truth for AI-related configurations: rules, skills, commands, hooks, context, and MCP server definitions.
Project .claude/ ──promote──▶ ai/ (source) ──build──▶ global (~/.claude/)
│
▼
dotfiles/
(deployment layer)
This repo contains atomic, reusable components that can be composed into tool-specific configurations based on machine profiles.
ai/
├── components/ # Atomic, reusable pieces
│ ├── rules/ # Instruction rules (schema'd JSON, future)
│ ├── skills/ # Claude Code skills (SKILL.md + files)
│ ├── commands/ # Slash command templates
│ ├── hooks/ # Hook definitions
│ └── context/ # Shared context fragments
│
├── profiles/ # Machine/use-case profiles (future)
│ ├── personal.profile.json
│ ├── work.profile.json
│ └── minimal.profile.json
│
├── tools/ # Tool-specific output schemas (future)
│ ├── claude-code/
│ ├── zed/
│ ├── claude-desktop/
│ └── vscode/
│
├── mcp/ # MCP server definitions
│ ├── global/ # Remote/HTTP MCP servers
│ └── local/ # Project-scoped MCP templates
│
├── schemas/ # JSON schemas for validation (future)
├── build/ # Build/compile tooling (future)
├── dist/ # Generated output (gitignored)
│
└── legacy/ # Previous content (migrating from)
# In your dotfiles repo
git submodule add git@github.com:aRustyDev/ai.git ai/
git submodule update --init --recursiveFor now, manually copy components to target locations:
# Claude Code
cp -r ai/components/commands/* ~/.claude/commands/
cp -r ai/components/skills/* ~/.claude/skills/
cp -r ai/components/rules/* ~/.claude/rules/Future: Use just ai-build and just ai-deploy from dotfiles repo.
Create/test configs in your project's .claude/ directory.
# Future: promote-component script
cp -r .claude/skills/new-skill/ ~/repos/configs/ai/components/skills/
cd ~/repos/configs/ai
git add -A && git commit -m "feat: add new-skill"
git push# On each machine
cd ~/repos/configs/dotfiles
git submodule update --remote ai/
just install-ai- Phase 1: Directory structure and legacy migration
- Phase 2: Basic promote/build/deploy workflow
- Phase 3: JSON schemas and compilation
- Phase 4: Profiles and dynamic MCP config generation
See Issue #1 for full details.
Previous content is preserved in legacy/ during migration. This includes:
agents/- Agent definitions
prompts/commands/- Slash commands (/audit, /plan, /report, etc.)prompts/processes/- Workflow processes (CI/CD, code-review, testing)prompts/core/- Core patterns (error handling, validation, git operations)prompts/patterns/- Development patterns (BDD, TDD, CDD)prompts/templates/- Issue, report, and documentation templatesprompts/roles/- Role definitions (developer levels, security engineer)prompts/guides/- Tool usage guidesprompts/knowledge/- Knowledge basesprompts/hooks/- Validation hooks and scriptsprompts/automation/- Automation scriptsprompts/docs/- Architecture and planning documentation
commands/- Slash commandsrules/- Instruction rulesskills/- Skill definitionsplugins/- Various pluginsroles/- Role definitionscontext/- Context documents- And more...
Content will be migrated to the new structure over time. Valuable content can be promoted to components/ using the /promote-skill command or similar workflows.
The following repositories have been archived and merged into this repo:
- arustydev/agents →
legacy/agents/ - arustydev/prompts →
legacy/prompts/
See .ai/plans/merge-agents-prompts.md for the full merge plan and history.
MIT