Reusable AI agent configurations for development workflows. Designed for XP/TDD practitioners who want consistent, high-quality AI assistance.
.
βββ .agent/
β βββ workflows/ # Antigravity workflows (context-driven-development, tdd-cycle)
βββ .agents/
β βββ rules/ # Canonical agent rules (shared across tools)
β β βββ base.md
β β βββ ai-feedback-learning-loop.md
β β βββ python-project.md
β β βββ makefile-project.md
β β βββ react-best-practices.md
β β βββ codex-default.rules # Shared Codex approval defaults
β βββ skills/ # Canonical skills (native + skill-factory symlinks)
β β βββ xp-*/ # Native: xp-code-review, xp-increase-coverage, xp-mikado-method, etc.
β β βββ test-doubles-first/
β β βββ cwv-improvement-planner/
β β βββ code-notify/
β β βββ lean-ai-adoption-coach/
β β βββ github-host-alias/
β β βββ (symlinks) # From skill-factory: tdd, refactoring, approval-tests, etc.
β βββ mcp.json # Canonical MCP servers config (shared across tools)
β βββ commands/ # Slash commands (FIC + project workflows); .cursor/commands β here
β βββ fic-*.md
β βββ review-pr/install-command/bug-fixing-agent
βββ .cursor/
β βββ rules/ # Cursor rules (.mdc); reference .agents/rules where applicable
β β βββ use-base-rules.mdc
β β βββ ai-feedback-learning-loop.mdc
β β βββ cursor-config-management.mdc
β β βββ project-status-maintenance.mdc
β β βββ fic-workflow.mdc
β β βββ tdd-workflow.mdc
β β βββ refactoring.mdc
β β βββ debugging.mdc
β β βββ python-dev.mdc
β β βββ makefile-dev.mdc
β β βββ react-best-practices.mdc
β β βββ tlz-connection.mdc
β βββ skills/ # Symlink β .agents/skills/
β βββ mcp.json # Symlink β ../.agents/mcp.json
β βββ cli-config.json # Canonical Cursor model/agent config
β βββ skills-cursor/ # Cursor-only skills (create-skill, create-rule, update-cursor-settings, etc.)
βββ .codex/
β βββ config.toml # Canonical Codex model/trust config
βββ .gemini/
β βββ mcp_config.json # Symlink β ../.agents/mcp.json
β βββ GEMINI.md # Symlink β ../GEMINI.md
βββ src/thoughts/ # Node/TS CLI for thoughts/ management
βββ thoughts/ # Research and plans (see thoughts/ tree below)
βββ docs/ # Pre-symlink structure, validation notes
βββ setup-symlinks.sh # Setup / validate / commit symlinks (home β repo)
βββ sync-skill-factory.sh # Symlink skill-factory output_skills into .agents/skills/
βββ pull-and-sync-skills.sh # Pull skill-factory + run sync (recommended one-liner)
βββ backup-cursor-config.sh # Backup Cursor config before changes
βββ (optional) AGENTS.md / CLAUDE.md / GEMINI.md β .agents/rules/base.md
This repository is the single source of truth for AI tool configuration. Configuration is shared via symlinks:
Symlink structure:
~/.cursor/rules β ~/saski/augmentedcode-configuration/.cursor/rules/
~/.cursor/commands β ~/saski/augmentedcode-configuration/.cursor/commands/
~/.cursor/skills β ~/saski/augmentedcode-configuration/.agents/skills/
~/.cursor/.agents β ~/saski/augmentedcode-configuration/.agents/
~/.cursor/mcp.json β ~/saski/augmentedcode-configuration/.agents/mcp.json
~/.cursor/cli-config.json β ~/saski/augmentedcode-configuration/.cursor/cli-config.json
~/.agents β ~/saski/augmentedcode-configuration/.agents/
~/.codex/config.toml β ~/saski/augmentedcode-configuration/.codex/config.toml
~/.codex/skills/skills β ~/saski/augmentedcode-configuration/.agents/skills/ (Codex keeps system skills in ~/.codex/skills/.system)
~/.codex/rules/default.rules β ~/saski/augmentedcode-configuration/.agents/rules/codex-default.rules
~/.codex/AGENTS.md β ~/saski/augmentedcode-configuration/AGENTS.md
~/.antigravity/skills β ~/saski/augmentedcode-configuration/.agents/skills/ (if using Antigravity)
~/.claude/ β ~/saski/augmentedcode-configuration/.claude/
~/.gemini/antigravity/mcp_config.json β ~/saski/augmentedcode-configuration/.agents/mcp.json
~/.gemini/GEMINI.md β ~/saski/augmentedcode-configuration/.gemini/GEMINI.md
~/CLAUDE.md β ~/saski/augmentedcode-configuration/CLAUDE.md
~/AGENTS.md β ~/saski/augmentedcode-configuration/AGENTS.md
~/GEMINI.md β ~/saski/augmentedcode-configuration/GEMINI.md
Shared skills live in .agents/skills/ (canonical). Cursor and other dev tools (Codex, Antigravity, etc.) point their skills directory at this repo path so all tools use the same XP and project skills. Shared MCP servers config is also canonicalized at .agents/mcp.json and reused across tools. Codex approval defaults are centralized at .agents/rules/codex-default.rules.
Volatile runtime state (for example Cursor ide_state.json, Codex session/history databases, Gemini brain artifacts) intentionally remains local and outside the canonical config scope.
cd ~/saski/augmentedcode-configuration
./setup-symlinks.sh setup# Validate all symlinks are correct
./setup-symlinks.sh validate
# Check for uncommitted changes
./setup-symlinks.sh statusAll configuration edits (in Cursor, VS Code, or any editor) automatically modify the repository files. Commit changes with:
./setup-symlinks.sh commitSymlinks broken: Run ./setup-symlinks.sh setup to recreate
Config not loading: Run ./setup-symlinks.sh validate to diagnose
Restore backup: See ~/.cursor-backups/ for timestamped backups
Based on stepwise-dev and the FIC methodology.
Problem: LLMs lose attention after ~60% context usage.
Solution: Structured phases with intentional context clearing:
π Research β Save to thoughts/ β Clear context
π Plan β Save to thoughts/ β Clear context
βοΈ Implement (phase by phase) β Clear between phases
β
Validate β Report
| Command | Purpose |
|---|---|
/fic-research |
Document codebase comprehensively, save to thoughts/shared/research/ |
/fic-create-plan |
Create detailed implementation plans iteratively |
/fic-implement-plan |
Execute plans phase by phase with verification |
/fic-validate-plan |
Verify implementation against plan |
FIC workflows are also available as trigger-based skills in .agents/skills/:
| Skill | Purpose |
|---|---|
fic-research |
Research current implementation and document findings only |
fic-create-plan |
Build a phased implementation plan from research/task context |
fic-implement-plan |
Execute approved plans phase by phase with verification |
fic-validate-plan |
Validate implementation completeness against a plan |
| Tool | fic-* Commands |
fic-* Skills |
Recommendation |
|---|---|---|---|
| Codex | No native slash-command flow from this repo | Yes (via ~/.codex/skills/skills symlink) |
Use skills as primary FIC interface |
| Cursor | Yes (.agents/commands exposed as commands) |
Yes (~/.cursor/skills) |
Keep both: commands for explicit invocation, skills for natural-language trigger |
| Claude | Commands available through .claude/commands |
Yes (~/.claude/skills) |
Keep both; prefer skills for portability |
| Gemini | Commands are not standardized in this repo setup | Yes (~/.gemini/skills) |
Use skills |
| Antigravity/Langflow | Commands not standardized here | Yes (~/.antigravity/skills, ~/.langflow/skills) |
Use skills |
Persistent storage for research and plans (tracked in git). The repo contains thoughts/shared/research/ and thoughts/shared/plans/. Run npx thoughts init to create the full structure:
thoughts/
βββ {username}/ # Personal notes (you write); created by init
β βββ tickets/
β βββ notes/
βββ shared/ # Team-shared (AI writes, tracked in git)
β βββ research/ # Research documents
β βββ plans/ # Implementation plans
β βββ prs/ # PR descriptions; created by init
βββ searchable/ # Hardlinks for grep; created by init (gitignored)
Research documents and implementation plans in thoughts/shared/ are committed to the repository to maintain project knowledge and enable collaboration.
Node/TS CLI for managing thoughts/:
cd src/thoughts
npm install
npm run build
# Commands
npx thoughts init # Initialize thoughts/ structure
npx thoughts sync # Sync hardlinks after adding files
npx thoughts metadata # Get git metadata for frontmatterXP behaviors are provided as trigger-based skills under .agents/skills/. They are applied when the user's request matches the skill description (e.g. "technical debt", "code review", "Mikado Method"). All tools (Cursor, Codex, Antigravity, etc.) resolve skills from repo .agents/skills/ via symlinks (e.g. ~/.cursor/skills β repo .agents/skills/).
Skills sources: .agents/skills/ contains native skills (tracked in this repo, e.g. xp-*, test-doubles-first, cwv-improvement-planner, code-notify, lean-ai-adoption-coach), skill-factory skills (symlinked from the skill-factory repo after running ./pull-and-sync-skills.sh), and product-management skills (vendored or synced; provenance in repo-root skills-lock.json, skill-foundry taxonomy in .agents/skills/skill-foundry/agents/catalog-product-management.yaml). AI agents should consider all skills in this directory and read the matching skill's SKILL.md when the user's request matches a skill description. The combined routing index is .agents/docs/skill-factory-skills.md.
| Skill | Purpose |
|---|---|
xp-code-review |
Review pending changes (tests, maintainability, project rules) |
xp-increase-coverage |
Identify and test high-value untested code |
xp-plan-untested-code |
Create actionable plan to cover untested code and coverage gaps |
xp-predict-problems |
Predict likely production failures and edge cases |
xp-mikado-method |
Guide safe refactoring via dependency graph (Mikado Method) |
xp-technical-debt |
Catalog and prioritize technical debt; quick wins, strategic debt |
xp-simple-design-refactor |
Maintainability & Simple Design refactoring with ROI focus |
xp-security-analysis |
Pragmatic security risk analysis (OWASP, threat modeling) |
| Command | Purpose |
|---|---|
/bug-fixing-agent |
Security-focused bug fixing workflow with OWASP, threat modeling, and cloud risk analysis |
/review-pr |
Interactive PR review workflow with walkthrough, comments, and optional fixes |
/install-command |
Install and customize command templates for the current repository |
Reusable project-level skills live in .agents/skills/ and are exposed to Cursor, Codex, Claude, Gemini, Antigravity, and other configured tools via symlinks to repo .agents/skills/. They are applied when user prompts match the skill description (trigger-based).
| Skill | Purpose |
|---|---|
test-doubles-first |
Choose the lightest effective test double, preferring fake/stub/spy before mock. |
cwv-improvement-planner |
Create prioritized Core Web Vitals plans for LCP/INP/TTFB, including edge caching/compression and safe experimentation. |
code-notify |
Recognize and use the local code-notify integration for end-of-task notifications across supported AI tools after verifying the installed command or hook. |
lean-ai-adoption-coach |
Evaluate AI tools, agents, workflows, and automations with a Lean/XP simplicity lens; recommend the smallest useful experiment and guardrails. |
planning-with-files |
Use file-based planning for complex multi-step work with persistent task_plan.md, findings.md, and progress.md tracking. |
github-host-alias |
Ensure correct SSH host alias is used when authenticating via SSH, based on local paths (~/work vs ~/saski). |
Skills from the skill-factory repo can be made available here without duplication by symlinking them into .agents/skills/. Run the sync script after pulling skill-factory (or on first setup). All skills in .agents/skills/ (skill-factory, product-management pack, and native) are listed for request-matching in .agents/docs/skill-factory-skills.md; usage is defined in .agents/rules/base.md Β§10.
Recommended one-liner: ./pull-and-sync-skills.sh β pulls skill-factory then runs sync; respects SKILL_FACTORY. For a preview without creating symlinks: ./pull-and-sync-skills.sh --dry-run.
# From augmentedcode-configuration repo root (skill-factory as sibling: ../skill-factory)
./sync-skill-factory.sh- What it does: Creates relative symlinks in
.agents/skills/for each skill inskill-factory/output_skills/that does not already exist. Native skills (e.g.xp-*,test-doubles-first) are never overwritten. - When to run: After
git pullin skill-factory, or when you add new skills there. Re-running is safe (adds only new skills). - Layout: Clone skill-factory as a sibling of this repo (e.g.
saski/skill-factoryandsaski/augmentedcode-configuration). Override withSKILL_FACTORY=/path/to/skill-factory ./sync-skill-factory.sh. - Dry run:
./sync-skill-factory.sh --dry-runlists what would be linked without creating symlinks.
Development rules live in .agents/rules/ (canonical). base.md is the universal rulebook, and python-project.md / makefile-project.md extend it for those repository contexts. Cursor rules in .cursor/rules/ point to the canonical files or add Cursor-specific behavior.
| Rule | Purpose | Activation |
|---|---|---|
use-base-rules.mdc |
Use .agents/rules/base.md as development rulebook |
Always active |
ai-feedback-learning-loop.mdc |
Points to .agents/rules/ai-feedback-learning-loop.md |
Always active |
cursor-config-management.mdc |
Symlink setup and config workflow | Always active |
project-status-maintenance.mdc |
PROJECT_STATUS.md maintenance | Always active |
fic-workflow.mdc |
FIC context management | Manual |
tdd-workflow.mdc |
TDD-specific rules | Manual |
refactoring.mdc |
Safe refactoring | Manual |
debugging.mdc |
Systematic debugging | Manual |
python-dev.mdc |
Python-specific | Auto on *.py |
makefile-dev.mdc |
Makefile-specific | Auto on Makefile, *.mk, *.mak |
react-best-practices.mdc |
React/TS rules (points to .agents/rules) | Auto on *.tsx, *.ts, *.jsx, *.js |
tlz-connection.mdc |
TLZ/aws/setup context | Globs (package.json, setup*.sh, etc.) |
cd ~/saski/augmentedcode-configuration
./setup-symlinks.sh setup
# Optional: pull skill-factory + sync skills into .agents/skills (no duplication)
# ./pull-and-sync-skills.sh
# Restart CursorSee Configuration Management above and .cursor/rules/cursor-config-management.mdc for symlink workflow.
# Copy to your project
cp -r .cursor /path/to/your/project/Canonical rules are in .agents/rules/base.md. To use them in Claude Code, Codex, or Gemini, create a symlink in your project root:
# Symlink for Claude Code
ln -s .agents/rules/base.md CLAUDE.md
# Optional: for Codex or Gemini
ln -s .agents/rules/base.md AGENTS.md
ln -s .agents/rules/base.md GEMINI.mdThese configurations enforce:
- TDD: Test-first, one failing test at a time
- Baby Steps: Small, incremental changes
- Simple Design: Clarity over cleverness
- High Quality: Strict validation before commits
- Context Engineering: Manage AI context effectively
Unlicense β Public Domain