Skip to content

saski/augmentedcode-configuration

Β 
Β 

Repository files navigation

Augmented Code Configuration

Reusable AI agent configurations for development workflows. Designed for XP/TDD practitioners who want consistent, high-quality AI assistance.

Repository Structure

.
β”œβ”€β”€ .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

Configuration Management

Architecture

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.

Setup on New Machine

cd ~/saski/augmentedcode-configuration
./setup-symlinks.sh setup

Verifying Configuration

# Validate all symlinks are correct
./setup-symlinks.sh validate

# Check for uncommitted changes
./setup-symlinks.sh status

Making Changes

All configuration edits (in Cursor, VS Code, or any editor) automatically modify the repository files. Commit changes with:

./setup-symlinks.sh commit

Troubleshooting

Symlinks 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

FIC Workflow (Context Engineering)

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

FIC Commands

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 Skills (Cross-Tool)

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 Evaluation: Commands vs Skills

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

thoughts/ Directory

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.

thoughts CLI

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 frontmatter

XP Skills

XP 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)

Project Commands

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

Shared Project Skills (from .agents/skills/)

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).

Syncing skills from skill-factory

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 in skill-factory/output_skills/ that does not already exist. Native skills (e.g. xp-*, test-doubles-first) are never overwritten.
  • When to run: After git pull in 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-factory and saski/augmentedcode-configuration). Override with SKILL_FACTORY=/path/to/skill-factory ./sync-skill-factory.sh.
  • Dry run: ./sync-skill-factory.sh --dry-run lists what would be linked without creating symlinks.

Cursor Rules

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.)

Installation

Global (applies to all projects)

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 Cursor

See Configuration Management above and .cursor/rules/cursor-config-management.mdc for symlink workflow.

Per-project

# Copy to your project
cp -r .cursor /path/to/your/project/

For Other AI Tools

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.md

Philosophy

These 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

References

License

Unlicense β€” Public Domain

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • Shell 64.2%
  • JavaScript 35.8%