Loading...
Loading...
Found 3,960 Skills
Fetch and render Drupal content in Canvas components with JSON:API and SWR patterns. Use when building content lists, integrating with SWR, or querying related entities. Covers JsonApiClient, DrupalJsonApiParams, relationship handling, and filter patterns.
Optimize Claude Code permissions by finding safe Bash commands from session history and auto-applying them to settings.json. Can run from any coding agent but targets Claude Code specifically. Use when experiencing permission fatigue, too many permission prompts, wanting to optimize permissions, or needing to set up allowlists. Triggers on "optimize permissions", "reduce permission prompts", "allowlist commands", "too many permission prompts", "permission fatigue", "permission setup", or complaints about clicking approve too often.
Control which data each viewer sees in an embedded Domo dashboard/card via server-side programmatic filters and dataset switching. Covers the OAuth → embed token flow, standard filters, SQL filters (OR/BETWEEN/LIKE), per-dataset targeting, datasetRedirects for multi-tenant architectures, and token size limits. Use for any per-viewer, per-role, or per-tenant data restrictions at embed time. Not for client-side JS API filtering (use cap-de-jsapi-filters).
UX design interview → living doc UX Design section (flows, screens, states, components, a11y). Optional — UI features only. Triggers: 'design the UX,' 'what screens,' 'how should users interact,' post-define. Not for: technical design (architect), requirements (define). Skip for API-only, CLI, backend, or exact UI replicas.
Generate interactive prototypes from PRD documents. **This skill must be used when users need to generate interactive UI prototypes, multi-page jump demos, or quickly validate product designs based on PRD**. Trigger scenarios: Users say "generate prototype", "make a demo", "generate navigable prototype", "turn PRD into clickable pages".
Send text messages to specified contacts via the WeChat desktop client on macOS. Used when the user provides a contact name and message content, such as "Send a WeChat message to Zhang San: xxx", "Open WeChat to send a message to someone", "Send specified text via WeChat". The WeChat desktop client must be installed before running, and accessibility permissions must be granted to the current terminal or Codex. Only exact matching is performed during execution: first search for the contact, then verify that the current session title exactly matches the target; stop if the match fails to avoid sending messages by mistake.
React bindings for TanStack Start: createStart, StartClient, StartServer, React-specific imports, re-exports from @tanstack/react-router, full project setup with React, useServerFn hook.
Runs a structured brand intake interview and then conducts web research to build a comprehensive brand context document. Use this whenever the user says they're working on a new client, wants to build brand context, or says "run brand intake", "conduct brand research" or "build brand context for [brand]". Also trigger when the user starts a creative strategy workflow for a brand that doesn't yet have a context document in the project. This must run BEFORE any Creative Strategy Engine, Hook Writing, or other execution work — it is the prerequisite context layer for all downstream creative strategy.
Apply when deciding, designing, or implementing data fetching with FastStore GraphQL files in src/graphql/ or src/fragments/, or configuring faststore.config. Covers API extensions, GraphQL fragments, server-side and client-side data fetching, and custom resolver patterns. Use for integrating custom data sources or extending the FastStore GraphQL schema.
Apply when building backend service apps under node/ in a VTEX IO project or configuring service.json routes. Covers the Service class, middleware functions, ctx.clients pattern, JanusClient, ExternalClient, MasterDataClient, and IOClients registration. Use for implementing backend APIs, event handlers, or integrations that must use @vtex/api clients instead of raw HTTP libraries.
Apply when designing or modifying a BFF (Backend-for-Frontend) layer, middleware, or API proxy for a headless VTEX storefront. Covers BFF middleware architecture, public vs private API classification, VtexIdclientAutCookie management, API key protection, and secure request proxying. Use for any headless commerce project that must never expose VTEX_APP_KEY or call private VTEX APIs from the browser.
Apply when working with MasterData v2 entities, schemas, or MasterDataClient in VTEX IO apps. Covers data entities, JSON Schema definitions, CRUD operations, the masterdata builder, triggers, search and scroll operations, and schema lifecycle management. Use for storing, querying, and managing custom data in VTEX IO apps while avoiding the 60-schema limit through proper schema versioning.