Loading...
Loading...
Found 920 Skills
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 implementing fulfillment, invoice, or tracking logic for VTEX marketplace seller connectors. Covers the Order Invoice Notification API, invoice payload structure, tracking updates, partial invoicing for split shipments, and the authorize fulfillment flow. Use for building seller-side order fulfillment that integrates with VTEX marketplace order management including the 2.5s simulation timeout.
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 deciding, designing, or implementing client-side state with FastStore SDK hooks like useCart, useSession, or useSearch. Covers cart manipulation, session handling, faceted search, and analytics event tracking from @faststore/sdk. Use for any interactive ecommerce feature that relies on FastStore's built-in state management.
Creator workflow — generate platform-ready content packages. Triggers on: "创作", "写公众号", "小红书", "口播", "creator", "content workflow", "帮我写一篇", "生成内容", "write an article", "create content".
Automatically detect GPU vendor, find appropriate PyTorch container image, launch with correct mounts, and validate GPU functionality. Supports NVIDIA, Ascend, Metax, Iluvatar, and AMD/ROCm. Use when user says "setup container", "start pytorch container", or invokes /gpu-container-setup.
Generate concise task summaries from One Horizon data. Use when asked to "summarize my work", "write a status report", "create a weekly summary", or "brief my manager". Includes initiatives and blockers when provided. Requires One Horizon MCP.
Guide users through defining their pricing strategy for an AI product or SaaS. Covers billing model selection (usage-based, subscription, hybrid), subscription tier pricing, credit/overage costs, real-time vs invoice billing trade-offs, existing PSP integration, custom currency vs fiat, and pricing dimensions. Ends with a personalised pricing strategy summary, MRR projection, visual output (HTML or PDF), and tool recommendations. Use when a user wants to define their pricing, figure out how to charge for their AI product, decide between billing models, understand the real-time vs invoice billing trade-off, or evaluate what tools to use for monetisation.
Pipeline orchestrator that classifies incoming coding tasks and routes them through the correct combination of skills in the right order at the right depth. Auto-activates on any coding task. Centralizes the decision logic for which skills to use, how deep each goes, and how artifacts pass between them. Handles three pipeline variants: standard (plan-interview, intent-framed-agent, context-surfing, simplify-and-harden, self-improvement), team-based (agent-teams-simplify-and-harden), and CI (simplify-and-harden-ci, self-improvement-ci). Use this skill whenever starting any coding work — it determines the appropriate pipeline depth and variant automatically. Does not replace individual skills; dispatches to them.
Use this skill when the user wants to transform an existing image into a new generated result, such as replacing models, changing poses, swapping backgrounds, generating scenes, expanding image edges, removing backgrounds, or creating virtual try-on images. Use it for image-editing and image-generation tasks where a source image and text instructions need to be turned into one or more final images.
Reads documented bugs from bugs.md, analyzes root causes, implements fixes with regression tests, and validates the full test suite. Prioritizes fixes by severity (high to low). Updates bugs.md with correction status and generates a final bugfix report. Use when the user asks to fix bugs, resolve issues, or run the bugfix workflow for a feature. Do not use for new feature implementation, code review, or QA testing.
Use when the user says "silly sausage", "silly-sausage", invokes /silly-sausage, or expresses lighthearted exasperation at a mistake the agent made. Also triggers on the phrase appearing anywhere in user input — no slash required.