korallis/skills-collection

clean-architecture

Clean Architecture. Enforce the Dependency Rule. Use when adding a file, import, module, package, layer, dependency, framework, database, HTTP client, or use case, or when deciding where code belongs.

clean-code

Clean Code. Enforce Martin's naming, function, comment, error, test, and smell rules on every change. Use when writing, editing, reviewing, or refactoring any source file, or when the user mentions naming, functions, comments, duplication, Boy Scout, smells,…

lee-engineering

Global TypeScript-first engineering router for Lee's projects. Use whenever planning, designing, building, implementing, refactoring, debugging, reviewing, or documenting software. Selects the smallest relevant specialist skills, local multi-agent workflows,…

scaffolding

Scaffolding. Enforce Dune-style capability folders, public module contracts, one data owner, and mechanical boundaries. Use when creating an app, module, package, workspace, monorepo, or folder tree, or when deciding where a new capability lives.

architect

Architecture-first workflow for non-trivial or high-risk software changes. Use when a plan or implementation crosses modules, introduces domain concepts, changes contracts, or risks shallow layering. Grounds designs in callers, data structures, signatures,…

arena

Local multi-agent design or implementation competition. Use when several materially different solutions are plausible and selection quality matters. Creates isolated candidates, judges them against shared criteria, and lets the lead agent synthesize and…

blast-radius

Change-impact and completion audit for wide, risky, cross-cutting, or merge-critical work. Use before declaring such work complete to inspect callers and contracts beyond the diff, identify safety facts, exercise the real artifact, and report what is cleared…

code-review

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews…

github-delivery

GitHub-only delivery workflow for planning branches, worktrees, issues, pull requests, checks, reviews, and merges. Use whenever software work may affect Git or GitHub. Replaces Graphite and other stack managers with plain git, gh, GitHub Actions, Projects,…

improve-codebase-architecture

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

interrogate

Independent local multi-model review for contested, security-sensitive, high-risk, or merge-critical plans and changes. Use when one reviewer is insufficient. Gives reviewers the same intent and rubric, aggregates consensus and disagreements, and applies lead…

to-tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

waves-codex

WAVES - Workers, Aggregate, Verify, Extend - wave-based orchestration for Codex. Decompose a big goal into independent slices, verify coverage, spawn Codex subagents in parallel as a bounded wave, collect evidence-backed handoffs, verify important claims,…