Skip to content
Back to skills

Code Generation

ASecurity

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

  • 1,760 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 29, 2026
ai-agentstypescriptgobashperformance

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned May 29, 2026

npx -y skills add a5c-ai/babysitter --skill code-generation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Generation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Generation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/a5c-ai-code-generation/badge)](https://www.skillsdirectory.com/skills/a5c-ai-code-generation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-generation
description: Minimal, pattern-matching code output. Write the least code that satisfies requirements. Match existing project patterns. Use Write/Edit tools only.
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
---

# 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

1. **Minimal**: Write the least code that makes tests pass
2. **Pattern-matching**: Follow existing project conventions (check patterns.md)
3. **Tool discipline**: Use Write/Edit for files, Bash only for runners and linters
4. **No gold plating**: Do not add features beyond what is required
5. **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)

Files in this skill

  • README.md222 B
  • SKILL.md1.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…