Catalog of 16 shared Ruby development skills covering TDD, refactoring, code review, security review, DDD, YARD documentation, and common design patterns (service objects, calculators, API clients)...
This repository serves as the central library of framework-agnostic Ruby skills and process-discipline skills for the AI agent ecosystem.
| Skill | Category | Description |
|---|---|---|
| define-domain-language | DDD | Extracting ubiquitous language or glossary definitions. |
| review-domain-boundaries | DDD | Auditing context boundaries and language leakage. |
| model-domain | DDD | Tactical DDD design (aggregates, entities, value objects, domain services). |
| write-yard-docs | Documentation | Writing or reviewing inline YARD documentation for public Ruby APIs. |
| create-service-object | Patterns | Creating a service object (PORO .call pattern). |
| implement-calculator-pattern | Patterns | Implementing polymorphic variant-based calculators (Strategy + Factory). |
| integrate-api-client | Patterns | Designing HTTP integrations (layered client/fetcher/builder pattern). |
| triage-bug | Testing | Investigating a bug, reproducing via failing test, and creating a repair plan. |
| respond-to-review | Code Quality | Receiving code review feedback and addressing comments. |
| skill-router | Orchestration | Triaging and decomposing complex Ruby requests into ordered sub-tasks. |
| generate-tdd-tasks | Planning | Breaking features into TDD quadruplet task lists with docs and review tasks. |
| tdd-process | Process | General engineering loop: Red-Green-Refactor process gates and checkpoints. |
| refactor-process | Process | Safely refactoring code while preserving behavior under characterization tests. |
| review-process | Process | Reviewing changesets (severity taxonomies, structured findings, re-review). |
| security-review-process | Process | Reviewing code for general Ruby security flaws (secrets, injections). |
| test-planning-process | Process | Choosing test boundaries (unit vs integration) and test scenarios. |
Process-discipline skills encode universal software engineering principles. They contain zero framework-specific details and are meant to be referenced by framework orchestrators to enforce engineering gates.
Planning skills bridge requirements and implementation by breaking features into actionable task lists. They compose process-discipline and atomic skills into ordered workflows.
Atomic skills focus on concrete Ruby programming patterns, design patterns, and domain analysis techniques.
