Augemented (AI/agentic) Coding Rubric

This rubric will be a fanciful place for sharing really excellent content. This content is a list of high quality resources that have stood tall. However, it is not meant to be exhaustive. There is much to learn beyond here! Let's dig in.

LEGEND:

• 🎥 - video
• 💾 - source code
• 📕 - book
• 📑 - blog

Coding/working with an Agent

1. Augmented Coding: Mapping the Uncharted Territory - Lada Kesseler 🎥
2. How I Use Every Claude Code Feature - Shrivu Shankar 📑
3. When it comes to MCPs, everything we know about API design is wrong - Jesse Vincent 📑
4. Claude Code Reference Docs 💾

Process Improvement

Vibes won't do squat for existing and long lived codebases. Creating a process to reproduce results time and again is paramount. These articles are aimed at process improvement enabled by AI.

1. Field notes from shipping real code with claude 📑
2. Getting LLMs to Work In Legacy Codebases - BoundaryML Team 💾
3. My LLM Codegen Workflow ATM (Feb 2026) - Harper Reed 📑
4. The new calculus of AI-based Coding - Joe Magerramov 📑
5. Vibing a Non-Trivial Ghostty Feature - Mitchell Hashimoto 📑

Agent Interaction Improvements

1. Reduce the verbosity:

Be extremely concise. Sacrifice grammar for the sake of concision.

source

2. Establish ground rules with in your Agent|Claude.md:

## Ground rules

**Always follow these rules**

Start replies with 🍀 + SPACE. Stack emojis when requested, don't replace.

Tell me something I need to know even if I do not want to hear it.

Push back when something is wrong, don't agree with mistakes.

Ask questions when something is not clear and you need to make a choice.

Don't choose randomly if it's important for what we're doing.

When you show a potential error or miss, start your response with ❗ emoji

3. /catchup Claude Code slash command

# Catch Up on Branch Changes

This command reviews all changes between the current branch and main, analyzes key files, and provides a comprehensive summary to help you catch up on what's been done.

## Steps:

1. Get the current branch name and verify we're not on main

2. Run `git fetch origin main` to ensure we have the latest main branch

3. Run `git diff main...HEAD --name-only` to get list of changed files

4. Run `git diff main...HEAD --stat` to get a summary of changes

5. Run `git log main..HEAD --oneline` to get the commit history for this branch

6. Read and analyze the most important changed files (prioritize: manifests, configs, core logic files)

7. Provide a high-level summary including:

- Branch purpose and scope of changes

- Key files modified and their significance

- Potential impact areas

- Any notable patterns or architectural changes

- Suggested review focus areas  

source