Total 57,408 skills
Showing 12 of 57408 skills
Create basic Transformers model adapters for msModelSlim. Implements required interfaces and completes a four-step verification workflow: generate test model -> full fallback quantization -> weight verification -> quantization description validation. Use this skill when the user wants to: (1) create msModelSlim adapters for decoder-only LLM, (2) adapt understanding VLM text backbones for quantization, (3) implement W8A8/W4A16 quantization workflow for new models. Trigger: user mentions "msModelSlim", "adapter", "model adapter","quantization", "W8A8","W4A16", "transformers", "LLM", "VLM", "adapter creation", "适配器","模型适配", "量化", "模型适配器", "LLM量化"
Conduct a structured business-logic interview for a new feature, asking questions iteratively until shared understanding is reached, then save a clean spec doc to `docs/<feature-slug>-business-logic.md`. The skill always writes the spec to disk and always stops there — it never continues into implementation planning. Use during planning — before any code or file paths are discussed — whenever the user wants to add a feature, change a flow, or scope new behavior. Trigger on phrases like "I want to add X", "let's plan a new feature", "we need to support Y", "I'm thinking about a feature for Z", "scope out…", "let's figure out what should happen when…", or any time the user describes a new capability and the next move is clarifying *what* it should do (not *how* to build it). Triggers even if the user doesn't say "plan mode" or "business logic" — if a feature is being scoped, this is the right skill. Refuses to discuss code, file paths, schemas, libraries, or implementation; redirects back to user behavior and business rules. Output is a saved markdown spec; running the implementation-planning skill afterward is a separate, user-initiated step.
Break an implementation plan markdown file into a sequenced, dependency-annotated, checkbox-tracked task list saved as a sibling doc (e.g. `docs/<feature>-tasks.md`). Each task is annotated with the lower-numbered tasks it depends on (or marked dependency-free) and ordered topologically, so independent tasks can be implemented in parallel. The task list is the execution contract — each task is one logical commit that bundles the code change **and** the ticked checkbox together (never a separate "tick-only" commit). Use this whenever the user has an implementation plan (file like `docs/<thing>-plan.md`, an `## Implementation plan` section, or a freshly written design doc) and wants a step-by-step todo list to drive the build. Trigger on phrases like "break this plan into tasks", "make a task list", "generate the tasks doc", "turn this plan into checkboxes", "split this into steps I can implement one by one", or whenever a plan exists and the next move is execution — even if the user doesn't explicitly say "task list".
SQLx + PostgreSQL v17 database guide. Queries, migrations, ENUMs, JSONB, transactions.
Masters Reatom v1001 async flows. Use when implementing, documenting, or reviewing Reatom async queries, mutations, wrap usage, withAsync, withAsyncData, withAbort, abortVar, sampling, take, onEvent, race, framePromise, Suspense, retry, caching, or race-prone UI workflows.
Research trends deeply across social platforms and search engines, preserving source evidence and producing a cited, reproducible report. Use for multi-platform trend discovery, content intelligence, audience research, or long-running topic monitoring; not for private-data collection or engagement automation.
Reviews code, docs, examples, and agent-produced changes that use Reatom. Use when reviewing Reatom pull requests, examples, migrations, model files, async flows, routing, forms, persistence, or documentation that claims Reatom behavior.
Implements and documents @reatom/jsx — reactive native DOM JSX. Use when writing JSX components, mount/unmount, props (prop:/attr:/on:), css prop, models, refs, SVG, Bind, or TypeScript JSX typings with Reatom.
Implements and documents Reatom v1001 (@reatom/core) using project conventions. Use when writing or modifying Reatom models, actions, async flows, routing, forms, persistence, framework adapters, examples, or docs — or when answering Reatom API questions.
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow. Use only when asked to run the full deploy test suite or this workflow specifically from an internal vercel/next.js PR branch. Do not use for focused deployment-test sanity checks; run the relevant tests locally with pnpm test-deploy instead. Covers resolving the latest branch SHA, waiting for vercel-packages, preserving default workflow inputs, dispatching the workflow, and verifying the run.
Use this skill whenever a user specifically requests legal research or Westlaw Deep Research, asks for CoCounsel Legal or cocounsel legal support, or asks a question that requires explaining, analyzing, or synthesizing U.S. law.
Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue.