Showing 39301–39330 of 77205 skills
Only the most important rules for writing basic Trigger.dev tasks
om-network/betayum
Configure your Trigger.dev project with a trigger.config.ts file
om-network/betayum
How to use realtime in your Trigger.dev tasks and your frontend
om-network/betayum
Use when building or editing frontend UI components, layouts, styling, design system usage, colors, dark mode, or icons.
om-network/betayum
MUST run after writing or modifying code — reviews changed files for verbose patterns, inconsistencies, and readability issues before considering work done
om-network/betayum
Use when writing TypeScript/React code - covers type safety, component patterns, and file organization
om-network/betayum
How to write and manage Cursor rules - invoke with @cursor-usage
om-network/betayum
Use when implementing data fetching, API calls, server/client components, or SWR hooks
om-network/betayum
Use when building forms - covers React Hook Form, Zod validation, and form patterns
om-network/betayum
Use when working with packages, dependencies, monorepo structure, or build configuration
om-network/betayum
Use when starting a new feature, Linear ticket, or bugfix in this repo — establishes the branch + worktree + env + DB + dev-server conventions so the work is immediately ready to code without fighting infra. Triggers on "start a new feature", "spin up a worktree", "begin ticket", "new branch".
om-network/betayum
Prompt engineering best practices - invoke with @prompt-engineering
om-network/betayum
Use when cleaning up old git worktrees, removing worktrees whose branches have merged or been abandoned, or dropping orphaned compdev_* Postgres databases. Triggers on "clean up worktrees", "delete stale worktrees", "worktrees piling up", "orphaned databases", "remove unused worktree".
om-network/betayum
Comprehensive rules to help you write advanced Trigger.dev tasks
om-network/betayum
Only the most important rules for writing basic Trigger.dev tasks
om-network/betayum
Configure your Trigger.dev project with a trigger.config.ts file
om-network/betayum
How to use realtime in your Trigger.dev tasks and your frontend
om-network/betayum
Use when building or editing frontend UI components, layouts, styling, design system usage, colors, dark mode, or icons.
om-network/betayum
Add a new addressing mode to Turnfleet - implement Planner and Renderer, golden tests, an e2e case and an ADR. Use when a new way of assigning relay addresses or port ranges is needed.
Hazmi35/turnfleet
Change the TURNPool API types safely - edit types and markers, regenerate, update webhooks, tests and docs. Use whenever a field is added, removed or re-marked in api/v1alpha1.
Hazmi35/turnfleet
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Hazmi35/turnfleet
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Hazmi35/turnfleet
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Hazmi35/turnfleet
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
Hazmi35/turnfleet
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
Hazmi35/turnfleet
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Hazmi35/turnfleet
Use when a conversation begins with a CesiumJS development request - maps the 14 domain skills on offer and explains how passive activation selects between them
CesiumGS/cesiumjs-skills
Implement a specification in code.
gentleeduck/duck-mc
Conduct a retrospective on a coding session.
gentleeduck/duck-mc
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
modem-dev/ossrules