Skill for generating randomization schemes for experiments
Use when the user wants feedback on how randomness, RNG, luck, dice, loot drops, or procedural elements are used in a game design…
Ranger Finance SDK for building perpetual futures trading applications on Solana.
This skill should be used when the user asks to "track rankings", "check keyword positions", "ranking changes", "monitor SERP positions"…
Use only when the user explicitly mentions "rapids-first" or "RAPIDS first", to prefer the RAPIDS GPU stack (cudf, cuml, cupy, cupyx) and…
Use when deciding which revacc-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a…
Implement sophisticated rate limiting with sliding windows, token buckets,
Guide for creating or updating skills that extend Manus via specialized knowledge, workflows, or tool integrations.
Laravel Cashier (Stripe) - Subscription billing and payment processing
Scalable data processing for ML workloads.
Distributed training orchestration across clusters.
Randomized benchmarking skill for gate fidelity characterization
Offload cargo/gcc/bun builds to remote workers.
Next.js and React performance. Use when writing or reviewing React and Next code for waterfalls, bundle size, RSC boundaries, and…
Provides comprehensive React 19 patterns for Server Components, Server Actions, useOptimistic, useActionState, useTransition, concurrent…
Guidance for frontend HTTP and data-fetching code — keep raw HTTP calls out of UI components, route them through hooks/query layers and…
Guidance for implementing or refactoring React components — keep components focused on rendering, props, and events, and extract API…
High-quality React component authoring focused on single responsibility, low coupling, and English-only code and comments.
Build interactive React dashboards in Treasure Work using render_react.
Use when building React 18+ applications in .jsx or .tsx files, Next.js App Router projects, or create-react-app setups.
Guidance for structuring frontend feature code as vertical feature-first slices (src/features/<feature>/...) instead of global technical…