Explore skills
Showing 18541–18570 of 77104 skills
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.
laguagu/claude-code-nextjs-skills
Stars: 74Claude CodeCodexTriage open pull request review comments with an Opus sub-agent, apply the accepted changes, and reply to every thread with the decision. Trigger on /address-pr-comments, address review comments, fix PR comments, or handle review feedback.
ShipfoxHQ/shipfox
Stars: 89Claude CodeCodexALWAYS use this skill when committing changes. Applies Shipfox agent sequencing for branch checks, scoped validation, and commit creation. Trigger on commit, commit changes, save changes, make a commit, or create commit.
ShipfoxHQ/shipfox
Stars: 89Claude CodeCodexDiagnose and fix failing CI checks on a pull request, then commit and push the fix. Trigger on /fix-ci, fix CI, CI is red, checks are failing, or fix the failing build on a PR.
ShipfoxHQ/shipfox
Stars: 89Claude CodeCodexGenerate a Changeset file for the current branch using Shipfox agent automation. Trigger when the user asks to add a Changeset, document a change for release, bump versions, or prepare a PR that touches published packages.
ShipfoxHQ/shipfox
Stars: 89Claude CodeCodexALWAYS use this skill when creating pull requests. Applies Shipfox agent sequencing for GitHub CLI review preparation and pull-request creation. Trigger on create PR, open PR, submit PR, make PR, push and create PR, or prepare changes for review.
ShipfoxHQ/shipfox
Stars: 89Claude CodeCodexShip a Linear issue end to end: implement it, open the pull request, then loop on merge conflicts, CI failures, and review comments until the pull request is green and every review thread is handled, and keep it rebased on main until it merges. Trigger on /ship, ship ENG-123, or take an issue all the way to a reviewed pull request.
ShipfoxHQ/shipfox
Stars: 89Claude CodeCodexMeasure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower. Use for any question about CI duration, a slow job, or when CI got slow.
wado-lang/wado
Stars: 120Claude CodeCodexInvestigate and improve code coverage for the wado-compiler crate. Use for any question about what the tests do and do not reach, dead code included.
wado-lang/wado
Stars: 120Claude CodeCodexUse rust-gdb to inspect variables and step through code without modifying it. Prefer it over print debugging for any investigation into what the compiler is actually doing (lldb is unavailable on Claude Code Web).
wado-lang/wado
Stars: 120Claude CodeCodexCut the branch down to what the code cannot say: reuse what exists, remove duplication, dead code, and wasted work, turn invariants into asserts, and delete the comments the code already speaks. Run it after answering review feedback too — a fix written to satisfy a reviewer is the least distilled code on the branch.
wado-lang/wado
Stars: 120Claude CodeCodexReview the branch with Eddy, the repository's own review bot (`package-eddy/`), then answer its findings with /code-review-response. Invoke ONLY when the user asks for it by name — never on your own initiative: a review calls a paid API.
wado-lang/wado
Stars: 120Claude CodeCodexThe only way to merge origin/main into a branch, conflicts or not. Use it every time main comes in — a PR reported conflicting or DIRTY, a branch behind origin/main, a CI failure to reproduce on the merged tree. Never run `git merge origin/main` or `git pull origin main` by hand.
wado-lang/wado
Stars: 120Claude CodeCodexTranspile Wado Wasm components to JS with jco, then run, debug, and benchmark them on Node. Use for anything that involves jco, Node, or a browser as the host.
wado-lang/wado
Stars: 120Claude CodeCodexTask-completion flow: `/cr` (a `/code-review` answered with `/code-review-response`, which ends with `/distill`), update docs (spec/cheatsheet/compiler/optimizer), then run `mise run on-task-done` (build, clippy-fix, golden + format fixtures, doc-stdlib, format, tests; the longest task there is) and commit its generated changes. Invoke ONLY when the user asks for it by name or explicitly asks to run the completion flow — never on your own initiative, and not because a task looks finished.
wado-lang/wado
Stars: 120Claude CodeCodexDebug the Wado optimizer with the WADO_TRACE, WADO_DUMP_PASS_BEFORE/AFTER, WADO_LIST_PASSES, and WADO_SKIP_PASS env vars. Use whenever a NIR/WIR pass is in question — wrong code, a WIR pipeline ICE, or just to see what a pass did to the IR. For guest-side slowness see wado-performance.
wado-lang/wado
Stars: 120Claude CodeCodexProfile the native Rust `wado` binary (compile/serve/run) for host-side bottlenecks — wall time per phase with the span trace, CPU with a sampling profiler (samply, or perf where samply cannot run), memory with the span trace's RSS and valgrind DHAT. Use for native CPU or memory profiling, not guest wasm (see wado-performance for that).
wado-lang/wado
Stars: 120Claude CodeCodexThe rules for opening a PR you must read before creating or editing any pull request.
wado-lang/wado
Stars: 120Claude CodeCodexRename a Rust symbol across the workspace (an item, a method, a field, a module, a local variable) with `wado-dev-tools rust-rename`, which edits where rust-analyzer resolves the name rather than where the text matches. Read before any Rust rename.
wado-lang/wado
Stars: 120Claude CodeCodexLocate and sync the reference specs and runtimes vendored under vendor/ — the Wasm, WASI P3, and Component Model specs, and the wasm-tools and wasmtime sources. Use whenever an answer should come from one of those sources rather than memory, and whenever vendor/ is missing or stale.
wado-lang/wado
Stars: 120Claude CodeCodexHow to drive the `wado` command — compile, run, test, serve, format, and publish a Wado program, target a Wasm world, pick an allocator, grant directories, and inspect the compiler with dump and query. Read before invoking the `wado` binary.
wado-lang/wado
Stars: 120Claude CodeCodexAnalyze and improve the runtime speed of a Wado program's compiled guest Wasm — profile hot functions, read the generated WIR for allocations and copies, reason about the WasmGC cost model, and A/B-measure a fix. Use for any guest-side speed question, whatever the program does. For host-side native compiler profiling see profiling-wado-compiler; for wrong code out of an optimizer pass see optimizer-debug.
wado-lang/wado
Stars: 120Claude CodeCodexRun binaryen's wasm-opt over the core Wasm that Wado generates, and read what it changes. Use for any question about wasm-opt or binaryen, or to find where Wado's codegen leaves size or speed on the table.
wado-lang/wado
Stars: 120Claude CodeCodexOne file, one job, and short enough to hold in your head. Covers the size policy (hard-split over 300 lines, split 200 to 300 at a seam, aim for 150), what a natural seam is and where to cut, the exemptions, the dependency rules that decide where the split lands, and the signals that a file is already two files. Use before adding to a file that is already long, when naming a new file, when a function has nowhere obvious to live, or when a review says a file is doing too much. Triggers - "this file is too long", "where should this go", "split this file", "is this file too big", "one responsibility".
kromatv/kroma
Stars: 81Claude CodeCodexWhat things get called. A file is named after its export in the project's case convention, a suffix is a resolution instruction rather than decoration, an index file only re-exports, and some symbol names are always wrong (utils, helpers, V2, Enhanced, New). Covers learning a tree's local vocabulary before adding to it, test and platform-variant naming, and the per-language conventions. Use when creating a file or directory, naming a test file, adding a platform variant, or when a name has to change. Triggers - "what should I call this file", "where does this file go", "naming convention", "kebab or camel", "name this test".
kromatv/kroma
Stars: 81Claude CodeCodexWrite a short release note people finish reading. Picks the few changes a user will notice from the pull requests since the last release, names each by what the reader can now do, keeps to a length budget, writes every language from the intent instead of translating, and traces every line to a PR. Use when cutting a release, or filling a GitHub Release body, a store "what's new", a package changelog or an in-app what's new screen. Triggers - "write the release notes", "release notes for 0.4.0", "what's new", "changelog for this release", "notes de version".
kromatv/kroma
Stars: 81Claude CodeCodexWrite cargo tests. A test name is a sentence, the body is setup, mock, test and verify blocks separated by blank lines with no comments, and shared setup lives in a named test-support module rather than in each test. Covers naming, the block shape, where a test file goes, async and time, workspaces, and running one crate or one filter. Use when adding or changing any #[test] or #[tokio::test], or when Rust coverage has to come up. Triggers - "write a rust test", "cargo test", "test this crate", "cover this handler".
kromatv/kroma
Stars: 81Claude CodeCodexDrive a PR to a green quality gate and keep it there. Loops on SonarCloud for the project's targets, no new issues, no duplication on new code, and coverage on new logic as close to 100% as the code allows, then watches the PR checks until every one passes. Use when a quality gate blocks a merge, when coverage or duplication has to come up, or before asking for review. Triggers - "fix the sonar issues", "quality gate", "get coverage up", "zero duplication", "loop until CI is green", "watch the checks".
kromatv/kroma
Stars: 81Claude CodeCodexWrite and change a product spec. Covers what belongs in the spec rather than in architecture, the status vocabulary, requirement IDs and how to keep them stable, and how to size a requirement so it becomes one story. Use when adding or editing a spec chapter, when a PR changes behaviour and the spec has to move with it, or when asked what the product should do. Triggers - "write the spec", "add a requirement", "spec this out", "update the spec", "what should this do".
kromatv/kroma
Stars: 81Claude CodeCodexWrite GitHub issues and PR descriptions. Covers the epic and sub-issue structure, linking a requirement instead of copying spec text, reading the project's label set and templates rather than guessing them, title format, and what a reviewer needs in a PR body. Use when opening an issue, turning a spec requirement into work, filing a bug, or writing a PR description. Triggers - "open an issue", "write a ticket", "file a bug", "turn this into work", "write the PR description".
kromatv/kroma
Stars: 81Claude CodeCodex