Updated 2mo ago
by korallis
skills-collection
Working collection of agent skills for planning, implementation, review, and delivery.
20 GitHub stars (20)
+2 in 30 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | +1 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | 0 |
| Oct 15 | 0 |
| Oct 16 | 0 |
| Oct 17 | 0 |
| Oct 18 | 0 |
| Oct 19 | 0 |
| Oct 20 | 0 |
| Oct 21 | 0 |
| Oct 22 | 0 |
| Oct 23 | 0 |
| Oct 24 | 0 |
| Oct 25 | 0 |
| Oct 26 | 0 |
| Oct 27 | 0 |
| Oct 28 | 0 |
| Oct 29 | 0 |
| Oct 30 | 0 |
| Oct 31 | 0 |
| Nov 1 | 0 |
| Nov 2 | 0 |
| Nov 3 | 0 |
| Nov 4 | +2 |
- 30 skills (30 skills found in its SKILL.md files)
- 1 forks (1 forks)
- 2mo ago last update (Last updated 2mo ago)
Install
Skills CLI
npx skills add korallis/skills-collection
Asks which skills and agents to install. Just one: npx skills add korallis/skills-collection --skill architect — add -g for every project.
Claude Code
git clone https://github.com/korallis/skills-collectioncp -r "skills-collection/architect" ~/.claude/skills/
Copies the architect skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add korallis/skills-collection
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
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, and repository evidence before implementation.
architect/SKILL.md on GitHub (opens in a new tab) -
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 verify the strongest result without cloud agents.
arena/SKILL.md on GitHub (opens in a new tab) -
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 versus still risky.
blast-radius/SKILL.md on GitHub (opens in a new tab) -
bootstrap-ios
Bootstrap agents for iOS, iPadOS, macOS, Swift, SwiftUI, SwiftData/Core Data, Swift Testing, Xcode build/test/debug, Simulator, App Intents, or XcodeBuildMCP work. Use before building, fixing, refactoring, QAing, or setting up Apple-platform repos, and when asked to load/install Ray's iOS skills or bootstrap iOS.
bootstrap-ios/SKILL.md on GitHub (opens in a new tab) -
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-architecture/SKILL.md on GitHub (opens in a new tab) -
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, or clean code.
clean-code/SKILL.md on GitHub (opens in a new tab) -
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 in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to…
code-review/SKILL.md on GitHub (opens in a new tab) -
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
codebase-design/SKILL.md on GitHub (opens in a new tab) -
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
diagnosing-bugs/SKILL.md on GitHub (opens in a new tab) -
domain-modeling
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
domain-modeling/SKILL.md on GitHub (opens in a new tab) -
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, and repository merge policy.
github-delivery/SKILL.md on GitHub (opens in a new tab) -
grill-with-docs
A relentless interview that sharpens a plan or design and records the decisions as ADRs and glossary entries. Use when the user says grill this plan, stress-test this design and write it up, or wants an architecture decision documented as it is made.
grill-with-docs/SKILL.md on GitHub (opens in a new tab) -
grilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
grilling/SKILL.md on GitHub (opens in a new tab) -
handoff
Compact the current conversation into a handoff document another agent can pick up. Use when the user says handoff, hand this off, continue in a new session, compact for another agent, or a session is ending with work unfinished.
handoff/SKILL.md on GitHub (opens in a new tab) -
improve-codebase-architecture
Identifies weak module boundaries and concrete deepening opportunities in a codebase, with a visual report to choose from. Use when the user asks where the architecture is weak, wants module boundaries improved, says improve the architecture, or asks what to refactor next.
improve-codebase-architecture/SKILL.md on GitHub (opens in a new tab) -
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 judgment without pretending model diversity.
interrogate/SKILL.md on GitHub (opens in a new tab) -
lee-engineering
Global TypeScript-first engineering router. Use whenever planning, designing, building, implementing, refactoring, debugging, reviewing, or documenting software. Selects the smallest relevant specialist skills, routes work across whatever models this account can actually reach, verifies against the real artifact, and delivers through GitHub.
lee-engineering/SKILL.md on GitHub (opens in a new tab) -
prototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
prototype/SKILL.md on GitHub (opens in a new tab) -
research
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, library or vendor behaviour confirmed, or reading legwork delegated to a background agent.
research/SKILL.md on GitHub (opens in a new tab) -
resolving-merge-conflicts
Resolves an in-progress git merge or rebase conflict. Use when the user hits merge conflicts, says resolve this conflict, rebase failed, or git status shows unmerged paths.
resolving-merge-conflicts/SKILL.md on GitHub (opens in a new tab) -
running-bug-review-board
Runs real-user QA, manual test plans, UX bug hunts, build sign-off, bug filing, and bug triage for web or iOS/iPadOS apps. Use when asked "QA this", "is this ready to ship?", or similar. Produces P0/P1/P2 bug reports, YES/NO phase sign-off, tracker sync guidance, and an HTML QA dashboard; keeps Interactive BRB triage in a separate session.
running-bug-review-board/SKILL.md on GitHub (opens in a new tab) -
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.
scaffolding/SKILL.md on GitHub (opens in a new tab) -
setup-lee-engineering
Set up the agent skills collection for whatever harness you are in. Links the skills into every harness from one copy, scans which models the account can actually reach, assigns them to engineering roles, writes the harness's own routing config, and confirms the assignment with the user role by role. Use for /setup-lee-engineering, "set up lee-engineering", "which models do I have", "scan my rout…
setup-lee-engineering/SKILL.md on GitHub (opens in a new tab) -
swiftui-animation-match
Match UI/UX interaction needs to proven SwiftUI animation patterns from curated open-source catalogs. Use when planning or building iOS/macOS screens where an interaction should feel alive - loaders, likes, toggles, card decks, reveals, shaders - or when asked which animation fits a moment. Recommends system-first restraint before custom motion.
swiftui-animation-match/SKILL.md on GitHub (opens in a new tab) -
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
tdd/SKILL.md on GitHub (opens in a new tab) -
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
technical-writing/SKILL.md on GitHub (opens in a new tab) -
to-tickets
Break a plan, spec, or the current conversation into tracer-bullet tickets with explicit blocking edges, published to the configured tracker. Use when the user says turn this into tickets, break this down into issues, create the work items, or wants a plan converted into independently verifiable units.
to-tickets/SKILL.md on GitHub (opens in a new tab) -
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
typescript-best-practices/SKILL.md on GitHub (opens in a new tab) -
waves
WAVES - Workers, Aggregate, Verify, Extend - wave-based orchestration. Decompose a big goal into independent slices, verify coverage, spawn workers in parallel as a bounded wave, collect evidence-backed handoffs, verify important claims, synthesize one deliverable, and extend into another wave only when warranted. Bounded by design to avoid runaway token loops; invoke deliberately. Formerly waves…
waves/SKILL.md on GitHub (opens in a new tab) -
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
writing-for-agents/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.