Total 57,977 skills
Showing 12 of 57977 skills
Use this skill to fix scroll jank, lost item state, and broken animateItem() animations in LazyColumn, LazyRow, LazyVerticalGrid, and LazyHorizontalGrid. Covers stable item keys, contentType for mixed-type feeds, Modifier.animateItem() requirements, hoisting modifier chains and painters out of the items lambda, and validating item composable stability. Use when the developer mentions LazyColumn jank, dropped frames while scrolling, items losing scroll state on insert/remove/reorder, mixed feeds of cards/headers/ads feeling sluggish, animateItem() not animating, RecyclerView view-type analog, key parameter, or contentType parameter. The prefetch-window tuning lives in a sibling skill.
Current shadcn/ui component guidance for projects generated with Radix UI or Base UI, including primitive-specific composition, Tailwind CSS v4 theming, accessibility, forms, tables, and state patterns. Inspect the checked-in component implementation before applying Radix asChild or Base UI render APIs.
Current Next.js 16 App Router guidance for caching, Cache Components, Server Components, routing, Server Actions, and next.config.js. Use for Next.js 16.x code. Generic React 19 patterns are covered by the react skill.
Analyze candidate models before adapter implementation. Determine model implementation source (transformers or model-local), structural features, layer-by-layer loading requirements, and MoE fused weight risks. Use this skill when the user wants to: (1) assess model adaptation feasibility before creating msModelSlim adapters, (2) analyze model structure and type classification, (3) evaluate MoE compatibility for quantization. Trigger: user mentions "model analysis", "msModelSlim", "adapter", "transformers", "MoE", "layer-by-layer", "model assessment", "feasibility", "模型分析", "适配可行性", "模型评估", "MoE分析"
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.
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.
Activate this skill when users fall into "analysis paralysis" (want to act but dare not take action) or "blind action" (act without summarization or improvement). Typical trigger signals: "I need to finish my research before starting", "I don't know if I understand this industry well enough to start a business", "We've been doing things but have no methodology". Scenarios where it is not called: Scenarios where mature methodologies are already in effective operation, pure theoretical learning needs. Difference from "Seeking Truth from Facts Information Processing Method": This skill focuses on the complete cognitive cycle (practice - cognition - re-practice), while the latter focuses on specific techniques of information processing in a single cycle.
Game audio engineer using Web Audio API for procedural music and sound effects in browser games. Zero dependencies. Use when adding music or SFX to a game.
Orchestration mode: the fleet-manager only plans, dispatches, supervises, and reviews — all code changes are delegated to fleet-workers (matching the fleet-manager's harness, model, and effort by default) in visible herdr tabs, each in its own git worktree. Use when the user runs /fleet, says "fleet mode", or asks to orchestrate work across delegated agents. "fleet off" deactivates.
Recover blocked/paywalled/WAF'd pages via fallbacks.