krivulcik

16 mods across 1 repository, 5 stars between them.

code-review

01

krivulcik/yolobox

Skill Claude CodeCodex

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…

5 14d ago A 94 tokens

codebase-design

02

krivulcik/yolobox

Skill Claude CodeCodex

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.

5 14d ago A 57 tokens

domain-modeling

03

krivulcik/yolobox

Skill Claude CodeCodex

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.

5 14d ago A 34 tokens

grill-me

04

krivulcik/yolobox

Skill Claude CodeCodex

A relentless interview to sharpen a plan or design.

5 14d ago A 14 tokens

grill-with-docs

05

krivulcik/yolobox

Skill Claude CodeCodex

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

5 14d ago A 30 tokens

grilling

06

krivulcik/yolobox

Skill Claude CodeCodex

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.

5 14d ago A 38 tokens

implement

07

krivulcik/yolobox

Skill Claude CodeCodex

Implement a piece of work based on a spec or set of tickets.

5 14d ago A 16 tokens

krivulcik/yolobox

Skill Claude CodeCodex

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

5 14d ago A 32 tokens

prototype

09

krivulcik/yolobox

Skill Claude CodeCodex

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.

5 14d ago A 39 tokens

research

10

krivulcik/yolobox

Skill Claude CodeCodex

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, or reading legwork delegated to a background agent.

5 14d ago A 49 tokens

setup-skills

11

krivulcik/yolobox

Skill Claude CodeCodex

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

5 14d ago A 39 tokens

tdd

12

krivulcik/yolobox

Skill Claude CodeCodex

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

5 14d ago A 33 tokens

to-spec

13

krivulcik/yolobox

Skill Claude CodeCodex

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

5 14d ago A 30 tokens

to-tickets

14

krivulcik/yolobox

Skill Claude CodeCodex

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.

5 14d ago A 54 tokens

wait-what

15

krivulcik/yolobox

Skill Claude CodeCodex

Stop. That last message did not land — re-pitch it.

5 14d ago A 18 tokens

wayfinder

16

krivulcik/yolobox

Skill Claude CodeCodex

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

5 14d ago A 46 tokens