base

Codifies architectural patterns and TDD workflows to enforce consistent, maintainable code across projects.

Updated Apr 21, 2026

Search Tags:#testing #tdd #linting #quality-gates #software-architecture #coding-patterns #atomic-todos

Ready to run

npx skills add https://github.com/joshuakessell/cornerstone --skill base-joshuakessell

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Foundational guidelines to keep software simple, consistent, and maintainable by codifying patterns, constraints, TDD workflows, and atomic todos.

Core Features & Use Cases

Enforces simple functions, limited nesting, and single responsibility per file
Enforces TDD workflow with red/green/validate cycles and quality gates
Enables atomic todos and session management for resumable work and traceability

Quick Start

Apply universal coding patterns and a TDD workflow across a project to ensure simplicity, testability, and clear progress tracking.

Frequently Asked Questions about base

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

FAQPage Schema

How do I enforce TDD workflow cycles and quality gates during development?▼

Enforce a TDD workflow by applying strict red, green, and validate cycles with quality gates during development. This keeps software simple and maintainable through disciplined testing and clear module boundaries.

What are universal coding patterns for keeping software maintainable?▼

Universal coding patterns for maintainable software include simple functions, limited nesting, and single responsibility per file. Codifying these constraints guards against complexity and ensures reliable, testable architectures.

How do I manage atomic todos for resumable software development sessions?▼

Manage atomic todos to enable resumable work and traceability across development sessions. This practice tracks clear progress and ensures disciplined, incremental software implementation without losing context.

How do I define clear module boundaries to limit software complexity?▼

Define clear module boundaries by enforcing single responsibility per file and limiting nesting depth. These universal coding constraints prevent complexity growth and maintain strict architectural discipline across projects.