Skill Claude CodeCodex
Generates C4 model architecture diagrams using Structurizr DSL (primary) or Mermaid C4 (fallback). Use when: user asks to "draw a diagram", "create a C4 diagram", "show architecture as a diagram", "generate architecture diagram", "document the system". DO NOT USE for code explanation or walkthroughs (use…
Skill Claude CodeCodex
Use when writing new code, naming modules/files/functions/variables, reviewing or refactoring for readability, reducing complexity, deciding whether an abstraction belongs, or reviewing with CUPID; also the constructive hacker ethos (curiosity, craftsmanship, open-source contribution, remove drudgery; never…
Skill Claude CodeCodex
Analyze a real communication artifact (Slack/Teams message, email, meeting transcript, pitch or presentation draft, CV, or resume) and coach it sharper using seven rhetoric + structure techniques: ethos/logos/pathos, reframing tough questions, centering the other person, the Pyramid Principle, pattern interrupt…
Skill Claude CodeCodex
Use this skill when the user wants to investigate a bug, defect, incident, or quality issue and find its root cause — including requests to run a "5 whys" analysis, write a postmortem, do a root-cause analysis (RCA), figure out why a bug reached production or slipped past code review/QA, set up a recurring…
Skill Claude CodeCodex
Explains code with C4 model diagrams, analogies, and step-by-step walkthroughs. Use when explaining how code works, teaching about a codebase, onboarding to architecture, or when the user asks "how does this work?", "explain this system", "walk me through this", "what does this code do?", "help me understand this"…
Skill Claude CodeCodex
Idiomatic Go — error handling, concurrency, web services, testing, and project structure. TRIGGER when: language (Go, Golang, .go files, go mod, go build, go run, go test, go fmt), concurrency (goroutine, channel, sync, context, select statement), errors (error interface, error wrapping, sentinel errors…
Skill Claude CodeCodex
Go concurrency — goroutines, channels, select, sync primitives, context, and data race prevention. TRIGGER when: user asks about goroutines, Go channels, Go select, sync.Mutex, sync.WaitGroup, sync.Once, Go context, context.WithCancel, context.WithTimeout, Go data race, race condition in Go, Go concurrency patterns…
Skill Claude CodeCodex
Go error handling — error interface, custom error types, wrapping, sentinel errors, errors.Is/As, panic/recover. TRIGGER when: user asks about Go error handling, if err != nil, custom errors, error wrapping, fmt.Errorf %w, errors.Is, errors.As, sentinel errors, panic recover, when to panic in Go, error types in Go, Go…
Skill Claude CodeCodex
Go modules and packages — go.mod, go.sum, versioning, proxies, internal packages, init functions. TRIGGER when: user asks about Go modules, go mod init, go mod tidy, go.mod, go.sum, Go package organization, Go imports, Go internal package, Go init function, Go module proxy, Go versioning, Go major version, Go replace…
Skill Claude CodeCodex
Go testing — table-driven tests, test helpers, benchmarks, fuzz testing, profiling, and testify. TRIGGER when: user asks about Go testing, go test, testing package, table-driven tests in Go, Go test helpers, t.Helper, t.Run, Go benchmarks, Go profiling, pprof, Go fuzz testing, Go test coverage, testify, Go mock, Go…
Skill Claude CodeCodex
Go type system — structs, interfaces, embedding, composition, generics, slices, maps, enums with iota. TRIGGER when: user asks about Go structs, Go interfaces, Go embedding, composition in Go, Go generics, type parameters, Go type constraints, Go slices, Go maps, Go iota, Go enum, Go bitmask, implicit interface…
Skill Claude CodeCodex
Go web development — HTTP server, handlers, middleware, routing, JSON encoding, XML, templates. TRIGGER when: user asks about Go HTTP server, net/http, Go handler, Go middleware, Go routing, Go JSON, encoding/json, json.Marshal, json.Unmarshal, Go XML, Go templates, html/template, Go REST API, Go web service…
Skill Claude CodeCodex
Kano Model feature triage: classify features as Must-be, One-dimensional, Attractive, Indifferent, or Reverse before building them. Empowers developers to refuse unnecessary work with a principled, evidence-based framework. TRIGGER when: user says Kano, "should we build this?", "is this feature worth it?", "feature…
Skill Claude CodeCodex
Maintains a rolling daily progress log (progress-daily.md) that captures Impact, Learnings, and Commits for each day of engineering work, sourced from git history. Author identity and log path are configurable per repo. TRIGGER when: user says "log today", "log my day", "any updates?", "what did I ship?", "update my…
Skill Claude CodeCodex
GitHub Flavored Markdown (GFM) syntax reference — tables, alerts, footnotes, task lists, links, images, mentions, anchors, escaping, and common pitfalls. TRIGGER when: user asks about GFM, github flavored markdown, markdown syntax, md syntax, github markdown formatting, markdown table, markdown heading, markdown link…
Skill Claude CodeCodex
Enforce and guide the Mikado Method for large, graph-driven refactors where a single naive change cascades into many failing call sites. The skill enforces the full Mikado loop: goal → naive attempt → map prerequisites → revert → implement leaves → commit → repeat. TRIGGER when: user mentions Mikado Method, dependency…
Skill Claude CodeCodex
Review and write OOP code in TypeScript/Node.js/NestJS: SOLID, GoF patterns, Tell Don't Ask, Object Calisthenics, class-shape smells. Use for code review, refactoring, or new class/service design. TRIGGER when: static-only class; single public method; setters required before valid; data-only class; getters used to…
Skill Claude CodeCodex
Write, review, debug, and explain OCaml code and dune projects. Use whenever the user mentions OCaml, .ml/.mli files, dune, dune-project, opam, Alcotest, qcheck, shrinking, counterexamples, property-based testing, mutation testing, katas or exercises written in OCaml, or asks to convert JS/TS/PHP logic into OCaml.…
Skill Claude CodeCodex
Detect code smells and apply in-place refactoring techniques (Extract Method/Class, Replace Conditional, Introduce Parameter Object, Rename, Move) to improve clarity, testability, and maintainability of a single function, class, or file. TRIGGER when: user mentions refactoring opportunities, code smell, long method…
Skill Claude CodeCodex
Write, review, debug, and explain ReScript code and rewatch projects. Use when the user mentions ReScript, .res/.resi files, rescript.json, bsconfig.json, rewatch, @rescript/core, @rescript/react, genType, uncurried functions, ReScript 11 to 12 migration, JS bindings, or pastes .res code with a compiler error. Explain…
Skill Claude CodeCodex
REST API design best practices — URI naming, HTTP verbs/status codes, pagination, filtering, error envelopes, versioning, security. Based on Octo's API design guide with modern updates. TRIGGER when: designing REST API, designing endpoint, API design review, URL design, resource naming, HTTP verb choice, status code…
Skill Claude CodeCodex
Reviews current branch and uncommitted changes: reads the actual diff, checks changed tests and CI first, reports risk and evidence with structured feedback (Blockers / Concerns / Nits), then applies approved fixes and asks before committing. TRIGGER when: user says "/review", "review this PR", "review my changes"…
Skill Claude CodeCodex
Write, review, and improve Ruby and Rails code — idiomatic style (duck typing, Enumerable, judicious metaprogramming), GoF design patterns applied the Ruby way (Strategy, Observer, Template Method, Decorator, Factory, Adapter, Composite, Command, Builder, DSLs), and testing (RSpec/Minitest structure, mocking…
Skill Claude CodeCodex
Presents requested code changes as unified diffs (diff -u format) with 3 lines of context where available. TRIGGER when: user explicitly asks for a code diff or patch — "show me the diff", "as a unified diff", "show the patch", or "/show-me-the-code" — including additions and deletions. DO NOT USE for code edits…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: