analyze-rust-ffi-crate-surface
Determine which parts of the C codebase use Rust-defined C symbols. Use this when you want to understand which C code files may be impacted by changes to a Rust FFI crate.
build
Compile the project to verify changes build successfully. Use this to verify your changes build properly together with the complete project and dependencies, and make sure to use it before running end to end tests.
check-rust-coverage
Check which Rust lines are not covered by Rust tests. Use this when you developed new Rust code and want to ensure it is tested.
jj-fix-conflicts
Fix merge conflicts in a jj change and its ancestors, starting from the oldest conflict. Use this when a jj change or its ancestors have conflicts that need resolving.
jj-split-changeset
Split a jj (Jujutsu) changeset into smaller, focused changesets. Use when asked to break up a large changeset, split commits, reorganize changes across revisions, or create stacked PRs from a single changeset. Covers safe duplication-based workflows, file-path and hunk-level splitting without interactive commands.
lint
Check code quality and formatting before committing changes. Use this to verify your changes meet our coding standards.
minimize-rust-ffi-crate-surface
Remove Rust-defined C symbols that are either unused or only used in C/C++ unit tests. Use this when you are refactoring a Rust FFI crate and want to remove unused symbols.
port-c-module
Guide for porting a C module to Rust. Use this when starting to port a C module to Rust.
read-unmodified-c-module
Read the source of the C module we are working on, before we made any changes.
review-rust-docs
Review the documentation of a Rust crate to ensure it meets our requirements and standards. Use this when you have done changes to Rust code.
run-python-tests
Run end-to-end Python tests after making changes to verify correctness. Use this when you want to verify your changes from an end-to-end perspective, after ensuring the build and Rust tests pass.
run-rust-benchmarks
Run Rust benchmarks and compare performance with the C implementation. Use this when you work on migrating C code to Rust and want to ensure performance is not regressed.
run-rust-tests
Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.
rust-docs-guidelines
Guidelines for writing Rust documentation. Use this when you want to write Rust documentation.
rust-review
Review Rust code changes for unsafe correctness, documentation quality, and C-to-Rust porting fidelity. Use this when you want to review Rust changes before merging.
rust-tests-guidelines
Guidelines for writing Rust tests. Use this when you want to write Rust tests.
verify
Run full verification before committing or creating a PR. Use this when you want to create a PR.
write-rust-tests
Write Rust tests to verify correctness of Rust code. Use this when you want to write Rust tests.
flex-grid-flow
Framework-agnostic design philosophy for fluid, responsive interfaces. Covers layout thinking, fluid typography/spacing math, adaptive colors, and hard rules. Equal coverage for SCSS and Tailwind.
supastarter-nextjs-skill
Guides development with supastarter for Next.js only (not Vue/Nuxt): tech stack, setup, configuration, database (Prisma), API (Hono/oRPC), auth (Better Auth), organizations, payments (Stripe), AI, customization, storage, mailing, i18n, SEO, deployment, background tasks, analytics, monitoring, E2E. Use when building or modifying supastarter Next.js apps, adding features, or when the user mentions supastarter Next.js, Prisma, oRPC, Better Auth, or related Next.js stack topics.
code-quality
Automated code quality detection — duplication, complexity, unused functions. Invoke when analyzing or refactoring Elixir code.
deployment-gotchas
MANDATORY for deployment and release configuration. Invoke before modifying config/, rel/, or Dockerfile.
ecto-changeset-patterns
MANDATORY for ALL changeset work beyond basic CRUD. Invoke before writing multiple changesets, cast_assoc, or conditional validation.
ecto-essentials
MANDATORY for ALL database work. Invoke before modifying schemas, queries, or migrations.
ecto-nested-associations
MANDATORY for ALL nested association and multi-table work. Invoke before writing cast_assoc, cast_embed, Ecto.Multi, or cascade operations.
elixir-essentials
MANDATORY for ALL Elixir code changes. Invoke before writing any .ex or .exs file.
oban-essentials
MANDATORY for ALL Oban work. Invoke before writing workers or enqueuing jobs.
otp-essentials
MANDATORY for ALL OTP work. Invoke before writing GenServer, Supervisor, Task, or Agent modules.
phoenix-auth-customization
MANDATORY when extending phx.gen.auth with custom fields. Invoke before adding usernames, profiles, or custom registration fields.
phoenix-authorization-patterns
MANDATORY for ALL authorization and access control work. Invoke before writing permission checks, policy modules, or role-based access.
phoenix-channels-essentials
MANDATORY for ALL Phoenix Channels work. Invoke before writing socket, channel, or Presence modules.
phoenix-json-api
MANDATORY for ALL JSON API work. Invoke before writing API controllers, pipelines, or JSON responses.
phoenix-liveview-auth
MANDATORY for ALL LiveView authentication work. Invoke before writing on_mount hooks, auth plugs for LiveViews, or session handling in LiveView modules.
phoenix-liveview-essentials
MANDATORY for ALL LiveView work. Invoke before writing LiveView modules or .heex templates.
phoenix-pubsub-patterns
MANDATORY for ALL PubSub and real-time broadcast work. Invoke before writing PubSub.subscribe, broadcast, or handle_info for real-time updates.
phoenix-uploads
MANDATORY for file upload features. Invoke before implementing upload or file serving functionality.
security-essentials
MANDATORY for ALL security-sensitive code. Invoke before writing auth, token handling, redirects, or user input processing.
telemetry-essentials
MANDATORY for ALL telemetry, logging, and observability work. Invoke before writing telemetry handlers, Logger calls, or metrics code.
testing-essentials
MANDATORY for ALL test files. Invoke before writing any _test.exs file.
ai-sdk-core
|
ai-sdk-ui
|
ai-sdk-agents
|
aws-architecture
Architect AWS infrastructure and application integrations with production-grade service selection, boundaries, rollout thinking, and verification. Use when the user asks for AWS architecture, infra design, service selection, or AWS-backed implementation planning. Do not use for repo-specific Nova guidance unless the active repo adapter calls into it.
browser-workbench-setup
Set up browser automation and UI QA for a new repository using playwright-interactive as the primary interactive tool and agent-browser as the secondary CLI smoke-check tool. Use when a user wants to bootstrap browser testing, screenshots, auth-state reuse, or local UI debugging conventions in a fresh repo.
bun-audit
Shared Bun audit/remediation router. Use when auditing a repo for Bun-first correctness, explaining Bun audit findings, listing Bun audit rules, planning safe Bun fixes, applying low-risk remediations, or validating Bun-related changes. This skill delegates to the shared engine in bun-dev/scripts.
bun-dev
Definitive, rule-first Bun development/build/runtime guidance + automation. Use when adopting Bun, migrating a repo from Node.js, auditing/fixing Bun package management (bun.lockb, bun install), optimizing scripts/monorepos (bun run --parallel/--sequential, --workspaces/--filter), configuring Bun + TypeScript, using bun test/build, tuning performance, or deploying Bun workloads/Vercel Functions with the Bun runtime (bunVersion, limitations, Next.js ISR scripts).
codex-sdk
>-
commit
Stage and commit changes in semantic groups. Use when the user wants to commit, organize commits, or clean up a branch before pushing.
context7-research
Deep library, dependency, framework, and API documentation research using Context7 MCP tools only. Use when you need up-to-date docs, version-specific API reference, migration guidance, or to verify code against official documentation. Triggers on requests like “look up docs”, “API reference”, “how do I use X”, “latest/current”, “deprecated”, “breaking changes”, “best practices”, or whenever correctness depends on primary documentation.
convex-audit
Audit a Convex-backed codebase for schema quality, security, runtime boundaries, migrations, and function-surface risks. Use when the user asks for a Convex review, backend audit, contract analysis, or remediation plan. Do not use for green-field feature-spec generation; use convex-feature-spec for that.
Page 142 of 1445 · 72243 results