Skill Claude CodeCodex
Reviews URLSession networking code for iOS/macOS. Covers async/await patterns, request building, error handling, caching, and background sessions. Use when reviewing code that uses URLSession, URLRequest, URLCache, or URLError, or any iOS networking path.
Skill Claude CodeCodex
Reviews watchOS code for app lifecycle, complications (ClockKit/WidgetKit), WatchConnectivity, and performance constraints. Use when reviewing code with import WatchKit, WKExtension, WKApplicationDelegate, WCSession, or watchOS-specific patterns.
Skill Claude CodeCodex
Reviews WidgetKit code for timeline management, view composition, configurable intents, and performance. Use when reviewing code with import WidgetKit, TimelineProvider, Widget protocol, or @main struct Widget.
Skill Claude Code
Rewrite developer text so a sentence states a fact about this project, not a feeling. Use when docs, docstrings, commits, PRs, or comments are inflated, filler, or hard to act on. NOT FOR a README that drifted from the code (do-readme-update, if installed).
Skill Claude CodeCodex
Skill for building with the Astro web framework. Helps create Astro components and pages, configure SSR adapters, set up content collections, deploy static sites, and manage project structure and CLI commands. Use when the user needs to work with Astro, mentions .astro files, asks about static site generation (SSG)…
Skill Claude Code
Creates original editorial illustrations where a recurring mascot character performs the idea — one caught scene by default, a hand-built explainer diagram (labeled stages, a fan-out, timeline, loop, or stack) when the structure itself is the point, or a transparent character cutout (pose-only compositing asset, no…
Skill Claude CodeCodex
Teach the user a new skill or concept, within this workspace.
Skill Claude CodeCodex
Build an evidence-backed marketing system from product code and authorized analytics — positioning, discovery, launches, conversion, and retention. Use for marketing audits, go-to-market work, SEO, GEO and AI-search discoverability, measurement reviews, or synchronized reports, decks, and videos without inventing…
Skill Claude CodeCodex
Use when checking project status. Defaults to the current project; covers every active project on request. Surfaces work that is active, blocked, or stalled, grouped by project, then phase, then task, and always writes a dated markdown archive. Triggers include "regroup", "all projects", "just this project", "only…
Skill Claude CodeCodex
Make a repository legible to coding agents. Use when writing, creating, or improving AGENTS.md, writing agent instructions, onboarding an agent to a codebase, making a repo agent-first or agent-friendly, improving agent legibility, harness engineering, a Codex workflow, a docs tree for agents, CLAUDE.md routing, or…
Skill Claude CodeCodex
Authors Agent Skills: the vocabulary and principles that make a skill predictable, distillation of a blog post, article, documentation, GitHub repo, video transcript, book, or paper into a reusable skill, and review of PRs that add or modify Agent Skills for structural validity, design quality, and marketplace…
Skill Claude CodeCodex
Author or improve one Diataxis page, or write one short learning when a verified fix's reasoning is not in the code, tests, or docs. Use when writing a tutorial, how-to, reference, or explanation, when asked to improve an existing doc, or when a hard-won fix would be lost if only the diff remained. NOT FOR a README…
Skill Claude CodeCodex
Bring a repository's README back in line with the code. Use when a README is stale or wrong, after adding, removing, or renaming commands, scripts, flags, packages, config, env vars, or install steps, or when asked to update, refresh, sync, or fix a README.
Skill Claude CodeCodex
Backend engineering for Effect (TypeScript), Go, Python, and Rust - write, design, and review Effect services and code, and review Go, Python, and Rust changes. Use when working with Effect, Effect-TS, Effect v4, Effect.gen, Layer, Context.Service, Schema, Config, Schedule/retry, Stream, Fiber/fork, Cause/defects…
Skill Claude CodeCodex
Correct-by-construction TypeScript standards. Use for TypeScript engineering, or when another skill needs the user's coding standards.
Skill Claude CodeCodex
Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
Skill Claude CodeCodex
The full measure → fix → report loop for Electron and web apps via Playwright and Chromium CDP: measure the real production build, find the cause, fix it, re-measure the same way, and write an HTML report from harness JSON, with Blink style-invalidation traces and a React commit probe that name causes at file:line…
Skill Claude CodeCodex
Attack an idea, judge one named option against the evidence, or develop competing alternatives and synthesize a choice. Use when the user wants a red team, a devil's advocate, a stress test, the strongest objection, a verdict on a named candidate, or a choice that needs alternatives built out first. NOT FOR code diffs…
Skill Claude CodeCodex
Write a pointer-first session handoff, or resume from a source the user names. Use when work must continue without this session's history, or the user says handoff, hand off, or resume a handoff. Do NOT use to keep working in the current session, and do NOT use for a status check (do-regroup, if installed).
Skill Claude CodeCodex
Manage tasks through the tuxedo CLI - a todo.txt per project repo, plus a global /todo.txt of personal tasks and routes to each project's list - add, list, complete, prioritize, archive, dependencies, ready tasks, and end-of-turn upkeep so do-regroup can reach every project. Use for todo.txt, tuxedo, todos…
Skill Claude CodeCodex
Requirements dialogue for what to build, not how. Use when the user wants to brainstorm or scope an idea, or has no idea yet and needs a short options pass first. NOT FOR attacking an idea (do-redteam), implementation planning (do-plan), executing (do-work), PRD or spec prose (do-tech-writing), or UX flow trees…
Skill Claude CodeCodex
Reproduce a failure, confirm the root cause, then fix, diagnose, or rethink. Use when asked to debug or fix failing or slow behavior. NOT FOR implementing a named plan (do-work) or redesigning before a cause is known (do-brainstorm).
Skill Claude CodeCodex
One review pass over a requirements or plan doc: gaps, contradictions, unverifiable steps, and scope creep, fixed in place. Use when asked to review a requirements file or a plan before anyone builds from it. NOT FOR attacking the idea (do-redteam), writing the plan (do-plan), executing (do-work), PRD or spec prose…
Skill Claude CodeCodex
LFG runner. Let's go: take an explicit end-to-end ask from request to done with no menus. Use when the user invokes do-it, says LFG, or says let's go on autonomous end-to-end work. A feature runs do-plan, do-work, then do-commit cpp. A bug starts at do-debug's fix path. /do-it commit stops at a local commit. Do NOT…
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: