dkneeland

Agentic Guardrails — AI skill for Claude Code

AI community

Modular markdown workflow templates to keep AI coding agents from shipping sloppy code.

How to install Agentic Guardrails

This entry records only its repository, not the path inside it, so there is no exact command to give. Open dkneeland/agentic-guardrails and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Agentic Guardrails does

Modular markdown workflow templates to keep AI coding agents from shipping sloppy code. Catch defensive over-engineering, redundant logic, and "AI slop" before they hit your commit history. Works with Opencode, Cursor, Claude Code, Aider, and any agent. Includes hardening, consolidation, slop-removal, and quality-gated commit workflows.

Alternatives in AI

  • macOS App Skills — AI coding agent skills for building, shipping, and maintaining native macOS apps 657 ★
  • The Pair — Open-source AI pair programming for desktop: a Mentor + Executor agent cross-check each other's code to catch 358 ★
  • Coding Agent Account Manager — Sub-100ms auth switching for AI coding CLIs (Claude Code, Codex, Gemini): swap subscription accounts instantly 111 ★

README

Agentic Guardrails

Reusable workflow templates that keep AI coding agents from shipping sloppy code.

These are markdown-based instructions that any AI coding agent can follow — [Cursor](https://cursor.com), [Claude Code](https://docs.anthropic.com/en/docs/claude-code), [opencode](https://opencode.ai), [Aider](https://aider.chat), [Gemini CLI](https://github.com/google-gemini/gemini-cli), or anything else that reads markdown.

The Problem

AI coding agents are remarkably productive. They're also remarkably consistent at generating specific categories of bad code:

  • Unnecessary comments — # increment counter above counter += 1
  • Defensive over-engineering — try/except blocks catching exceptions that can't be raised
  • Gratuitous abstraction — AbstractFooFactory with one concrete implementation
  • Phantom error handling — catching TypeError, ValueError, KeyError when only KeyError is possible
  • Docstring regurgitation — restating the function name and parameter types without adding insight
  • Over-parameterization — do_logging=True, validate=True, use_cache=True flag soup
  • Type assertion hacks — cast(Any, ...) and # type: ignore to paper over type issues
  • Dead code — commented-out blocks, unused imports, unreachable branches
  • Duplicate functions — re-inventing helpers that already exist in the codebase, session after session
  • Inconsistent style — new code that doesn't match the patterns of the surrounding file

These aren't bugs. They pass tests. They pass linters. But they accumulate into a codebase that's harder to read, harder to maintain, and increasingly full of noise. Every session with an AI agent leaves a little residue.

**Agentic Guardrails** is a set of four workflow files that catch these problems before they hit your commit history.

The Workflows

Four markdown files, designed to be run in sequence. Each focuses on exactly one concern.

| Workflow | Focus | Key Action | |----------|------