base

Enforce coding constraints and TDD workflow with atomic todos.

1|Updated Jan 10, 2026

Search Tags:#testing #tdd #architecture #patterns #code-quality #todos

Ready to run

npx skills add https://github.com/artofrawr/claude-control --skill base-artofrawr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: base
Source: https://github.com/artofrawr/claude-control/tree/main/skills/base
Command: npx skills add https://github.com/artofrawr/claude-control --skill base-artofrawr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Universal coding patterns, constraints, and a disciplined TDD workflow to keep code maintainable and scalable.

Core Features & Use Cases

Enforces function-level and file-level limits to reduce complexity and improve readability.
Guides teams through a structured TDD workflow with atomic todos for precise work units.
Supports consistent architectural patterns and clear boundaries for modules and responsibilities.

Quick Start

Apply universal coding patterns and TDD discipline across your project to enforce constraints and guide atomic todos.

Frequently Asked Questions about base

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce function length and file size limits to improve code quality?▼

To enforce code quality limits, apply universal coding patterns that restrict function length to 20 lines, file size to 200 lines, and parameter counts to 3. These constraints reduce complexity and maintain readability across software projects.

What is the best way to structure a test-driven development workflow with atomic todos?▼

A test-driven development workflow with atomic todos is structured by guiding engineers through precise work units. This approach enforces rigorous TDD discipline and supports consistent architectural patterns across codebases.

Can I use these coding patterns and constraints for software projects of any scale?▼

Yes, these coding patterns and constraints target software projects of varying sizes. By enforcing flat module structures, one export focus per file, and a maximum nesting depth of 2, the rules keep code maintainable and scalable.

How do I maintain flat module structures and clear boundaries in my codebase?▼

To maintain flat module structures and clear boundaries, enforce architectural patterns that limit nesting depth to 2 and require one export focus per file. This establishes clear module responsibilities and improves overall code architecture.

Why does limiting nesting depth and parameter counts improve code maintainability?▼

Limiting nesting depth to 2 and parameter counts to 3 improves code maintainability by reducing cognitive load and function complexity. These explicit constraints enforce cleaner, more readable code that scales better across teams.