Babysitter code-generation

Minimal, pattern-matching code output. Write the least code that satisfies requirements. Match existing project patterns. Use Write/Edit tools only.

install

source · Clone the upstream repo

git clone https://github.com/a5c-ai/babysitter

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/cc10x/skills/code-generation" ~/.claude/skills/a5c-ai-babysitter-code-generation && rm -rf "$T"

manifest: library/methodologies/cc10x/skills/code-generation/SKILL.md

Code Generation

Overview

Guides code output to be minimal and pattern-matching. Write the least amount of code that satisfies the requirements while following existing project conventions.

Principles

Minimal: Write the least code that makes tests pass
Pattern-matching: Follow existing project conventions (check patterns.md)
Tool discipline: Use Write/Edit for files, Bash only for runners and linters
No gold plating: Do not add features beyond what is required
No premature optimization: Optimize only when performance tests demand it

Code Quality Checks

Follow project naming conventions
Match existing file structure and organization
Use established error handling patterns
Maintain consistent import ordering
Follow TypeScript strictness (no
```
any
```
, proper narrowing)

When to Use

During TDD GREEN phase (minimal implementation)
During TDD REFACTOR phase (pattern alignment)
When implementing fixes in DEBUG workflow

Agents Used

```
component-builder
```
(primary consumer)
```
bug-investigator
```
(fix implementation)