oss

🏠 Borda's AI-Rig

Personal AI coding assistant configuration for Python/ML OSS development. Version-controlled, opinionated, continuously improved.

Contents

• 🎯 Why
• 💡 Design Principles
• ⚡ Quick Start
• 🔁 Daily OSS Workflow
• 📦 What's Here
• 🧩 Agents
• 🤖 Claude Code
• 🤖 Codex CLI
• 🤝 Claude + Codex Integration
• 🛠 Recommended Add-ons
• 🔌 Plugin Management

🎯 Why

Managing AI coding workflows for Python/ML OSS is complex — you need domain-aware agents, not generic chat. This config packages 12 specialist agents and 20+ slash-command skill workflows across four focused plugins, in a version-controlled, continuously benchmarked setup optimized for:

• Python/ML OSS libraries requiring SemVer discipline and deprecation cycles
• ML training and inference codebases needing GPU profiling and data pipeline validation
• Multi-contributor projects with CI/CD, pre-commit hooks, and automated releases

[!NOTE] What this adds over vanilla Claude Code: With defaults, Claude reviews code as a generalist. With this config, it reviews as 6 specialists in parallel, with a Codex pre-pass for unbiased coverage, file-based handoff to prevent context flooding, automatic lint-on-save, and token compression via RTK — all orchestrated by slash commands that chain into complete workflows.

💡 Design Principles

• Agents are roles, skills are workflows — agents carry domain expertise, skills orchestrate multi-step processes
• No duplication — agents reference each other instead of repeating content
• Profile-first, measure-last — performance skills always bracket changes with measurements
• Link integrity — never cite a URL without fetching it first (enforced in all research agents)
• Python 3.10+ baseline — all configs target py310 minimum (3.9 EOL was Oct 2025)
• Modern toolchain — uv, ruff, mypy, pytest, GitHub Actions with trusted publishing

⚡ Quick Start

# Install Claude Code
npm install -g @anthropic-ai/claude-code

# 1. Clone (run from the directory that will CONTAIN the clone)
git clone https://github.com/Borda/AI-Rig Borda-AI-Rig

# 2. Register as a local marketplace
claude plugin marketplace add ./Borda-AI-Rig

# 3. Install all four plugins
claude plugin install foundry@borda-ai-rig   # base agents + audit, manage, calibrate, brainstorm, …
claude plugin install oss@borda-ai-rig       # OSS workflow: analyse, review, resolve, release
claude plugin install develop@borda-ai-rig   # development: feature, fix, refactor, plan, debug
claude plugin install research@borda-ai-rig  # ML research: topic, plan, judge, run, sweep

[!NOTE] Safe to install alongside any existing Claude Code setup. Plugins live in a private cache (~/.claude/plugins/cache/<plugin>/) under their own namespace. Your existing ~/.claude/agents/, ~/.claude/skills/, and settings.json are never modified or overwritten — custom agents and skills you have created remain fully independent. See the Claude Code plugin reference for details.

4. One-time settings merge — run inside Claude Code:

/foundry:init link

link symlinks foundry agents and skills into ~/.claude/ so you can type /audit, /manage, /brainstorm, etc. without a foundry: prefix. OSS, develop, and research skills always use their plugin prefix (/oss:review, /develop:fix, /research:run). Safe to re-run.

[!IMPORTANT] Codex CLI — optional companion; the plugins install Claude Code agents and skills only:

npm install -g @openai/codex
cp -r Borda-AI-Rig/.codex/ ~/.codex/   # Codex agents and profiles

→ See Token Savings (RTK) for RTK install details.

🔁 Daily OSS Workflow

A typical maintainer morning — 15 new issues, 3 PRs waiting, a release due:

# 1. Morning triage — what needs attention?
/oss:analyse health                # repo overview, duplicate issue clustering, stale PR detection

# 2. Review incoming PRs
/oss:review 55 --reply             # 7-agent review + welcoming contributor comment

# — or: full review first, then apply every finding in one automated pass
/oss:review 21                     # 7-agent review → saved findings report
/oss:resolve 21 report             # Codex reads the report and applies every comment

# 3. Fix the critical bug from overnight
/oss:analyse 42                    # understand the issue
/develop:fix 42                    # reproduce → regression test → minimal fix → quality stack

# 4. Ship the release
/oss:release prepare v2.1.0        # changelog, notes, migration guide, readiness audit