Loading...
Loading...
Found 10,876 Skills
Creates a main menu/navigation hub component with dynamically generated menu items based on selected capabilities (search, create, save, delete). Prompts for entity name and available actions, generates menu card and routes. Use when the user asks for Day 2 step 3 of the CRUD drill, or asks to build a main menu for up-app.
Design game concepts adapted from a novel. Based on SOURCE_BIBLE and PRODUCT_BRIEF, generate three genuinely distinct directions in the unlocked dimensions, then select the most viable playable prototype using hard vetoes and explicit trade-offs. This framework can be used to determine what type of game the novel should be adapted into, compare game concepts, choose a game direction for the book, and decide whether the novel should be turned into an interactive story.
Use when someone shares a mobile subscription or purchase screen and wants to know what to change, fix, test or improve — "here's my paywall", "roast this", "what should I test", a competitor screenshot, a design in progress, or an image with almost no text. Also use whenever YOU are the one designing or generating a paywall screen and were given no design reference to follow — no reference image, no existing screen to copy, no layout spec — as in "make me a paywall", "make one that converts", "will this convert?", "is this any good?"; this library is the reference in that case, and it evaluates and corrects the screen you produce. Also use when reviewing a paywall render or flow config produced by the flow-generator skill. Do not wait to be asked for a "teardown" by name.
Guides the agent through migrating an existing Capacitor project from Capgo to Capawesome Cloud. Detects Capgo usage (the @capgo/capacitor-updater plugin, CapacitorUpdater configuration, and @capgo/cli commands in CI/CD) and provides step-by-step migration: replacing the plugin with @capawesome/capacitor-live-update, mapping configuration options and API methods, migrating update strategies, channels, code signing, and CI/CD pipelines. References the capawesome-cloud skill for detailed Capawesome Cloud setup procedures. Do not use for setting up Capawesome Cloud from scratch without an existing Capgo project, for migrating from Ionic Appflow (use the ionic-appflow-migration skill instead), or for non-Capacitor mobile frameworks.
Apply factor models to portfolio construction and fund evaluation, from CAPM through the Fama-French 3- and 5-factor models plus momentum. Use when the user asks about 'Fama-French', 'value factor', 'smart beta', 'factor tilt', 'momentum exposure', or the 'factor zoo', wants to run or interpret a factor regression (loadings, alpha after controlling for factors, R-squared, t-stats), decompose a manager's returns into factor exposures versus skill, or asks 'is my fund closet indexing'. Also trigger on SMB, HML, RMW, CMA, UMD, size/value/quality/profitability/low-vol premia, factor ETF or smart-beta product evaluation (factor purity, turnover, capacity, fees), factor cyclicality and the danger of factor timing, factor crowding, long-short academic factors versus long-only implementable tilts, and post-publication factor decay.
Hardens Dockerfiles, images, and per-container runtime settings against the CIS Docker Benchmark v1.8.0: non-root users, dropped capabilities, read-only root filesystem, seccomp and AppArmor profiles, and minimal multi-stage builds, validated with docker-bench-security, Hadolint, and Dockle. Use when preparing a container or Dockerfile for production, or auditing images and runtime flags against CIS Docker controls. Keywords: Dockerfile, USER, --cap-drop, read-only rootfs, seccomp, AppArmor, multi-stage, Hadolint, Dockle. Do not use for the Docker daemon's own configuration - use hardening-docker-daemon-configuration.
Parse Windows Prefetch (.pf) files with the windowsprefetch Python library to reconstruct application execution history, run counts, and accessed file/volume lists. Use when investigating renamed or masquerading binaries, verifying program execution timelines, or hunting for suspicious execution patterns in incident response.
Use when the user wants to download a track from YouTube and add it to the macOS Music.app / iTunes library with proper tags and cover art, or when a track already in the library shows 0:00 duration, a missing bitrate, or an iCloud sync status of "ineligible".
Check what the business already knows before deciding anything. Run when the user says "what do we know about...", "have we tried this before", "check the vault", "what did we learn about X", and AUTOMATICALLY before any gauntlet, plan, offer, or big decision, per the charter's recall-first ritual. Answering a business question from model memory when the vault holds the founder's real history is the failure this skill exists to prevent.
Use when choosing, critiquing, or designing UI interaction patterns and reusable components for web, mobile, SaaS, dashboards, or design systems.
Read-only OKX tracking: unified-account equity, perp positions, orders, fills, bills. Use when monitoring OKX without trading (e.g. account equity, current PnL, recent fills, withdrawal history, margin level).
Build, serve, and call end-to-end typesafe APIs with oRPC v2. Use for any task in a project that depends on `@orpc/*` packages, even a one-procedure change: defining procedures with the os builder (.input/.output/.handler, any Standard Schema validator), assembling routers, middleware and context, typesafe errors with ORPCError, serving via RPCHandler on any runtime adapter, calling from server-side clients (call, createRouterClient) or client-side clients (createORPCClient with RPCLink), integrating TanStack Query, or streaming over SSE. Pretrained oRPC knowledge describes v1 and is wrong for v2, so load this skill even when the change looks trivial. Biases toward retrieval from the oRPC docs over pre-trained knowledge. For REST/OpenAPI exposure, prefer the orpc-openapi skill; for contract-first design, the orpc-contract skill; for tRPC or oRPC v1 migrations, the orpc-migrate skill.