Explore skills
Showing 26491–26520 of 77079 skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexBundle TypeScript and JavaScript libraries with blazing-fast speed powered by Rolldown. Use when building libraries, generating type declarations, bundling for multiple formats, or migrating from tsup.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexTurborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexMaster TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexReact composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexGuide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexVite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexThis skill should be used only when the user explicitly asks to use `$ralph-specum-feedback`, or explicitly asks Ralph Specum in Codex to draft or submit feedback.
tzachbon/smart-ralph
Stars: 566Claude CodeCodexThis skill should be used only when the user explicitly asks to use `$ralph-specum-index`, or explicitly asks Ralph Specum in Codex to generate or refresh index artifacts.
tzachbon/smart-ralph
Stars: 566Claude CodeCodexIndex of the Convex Architecture Documents (CADs), the normative specifications for Convex. Use to find which CAD governs a subsystem before changing protocol, encoding, consensus or economic behaviour.
Convex-Dev/convex
Stars: 119Claude CodeCodexCAD3 encoding format — cells, embedded vs branch references, value IDs, validity rules. Use when working on encoders, decoders, serialisation, hashing or anything that reads or writes cell encodings.
Convex-Dev/convex
Stars: 119Claude CodeCodexOrientation in the Convex ecosystem — what lives in which repository, where the specs and docs are, and which client libraries exist. Use when you need context that is not in this repository.
Convex-Dev/convex
Stars: 119Claude CodeCodexTriage the open Convex issues against a fixed rubric — close what is done or superseded, give each a type label, and collect everything that needs a maintainer decision into one review sheet. Use when asked to review or triage all open issues.
Convex-Dev/convex
Stars: 119Claude CodeCodexStages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexTurns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexSynthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexStress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexWatches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexOpens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexRebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexPerform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexCreate a feature branch with sequential or timestamp numbering
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexValidate current branch follows feature branch naming conventions
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexRun the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously. Stops before extract; run that manually.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexRun the speckit implementation phase chunk-by-chunk in clean-context subagents, then review, then produce a final report. Picks up from an existing tasks.md.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexRun the speckit preparation phases end-to-end — specify, plan, critique, tasks — making all decisions autonomously. Stops before implementation.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexProduce a manual QA checklist that walks a human tester through verifying the just-implemented feature, written next to spec.md / plan.md in the active feature directory.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexRun a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodexProduce a flow-level summary of the current Claude Code session — executive summary, chronological timeline, and outcomes — written into the active feature directory next to spec.md / plan.md.
opsmill/nornir-infrahub
Stars: 12Claude CodeCodex