Loading...
Loading...
Found 549 Skills
Interactively onboard a project to agent-driven development by running a structured interview and generating a complete AGENTS.md (or CLAUDE.md). Use this skill whenever a user mentions "AGENTS.md", "CLAUDE.md", "agent behavior", "agent instructions", "agent config", "set up agent rules", "onboard agent", "configure claude code", "agent guardrails", "agent workflow", or asks how to tell an AI agent how to behave in their project — even if they just say "help me write AGENTS.md" or "what should go in CLAUDE.md". Always prefer this skill over ad-hoc agent instruction generation.
Apply when working with MasterData v2 entities, schemas, or MasterDataClient in VTEX IO apps, or when anyone designing or implementing a solution must scrutinize whether Master Data is the correct storage. The skill prompts hard questions: native Catalog or other VTEX stores, OMS, or an external database may be better; do not default to MD because it is convenient. Covers JSON Schema, CRUD, triggers, search and scroll, schema lifecycle, purchase-path avoidance, single source of truth, and BFF handoffs. Use for justified custom persistence while avoiding the 60-schema limit.
Comprehensive creation via Xiaoyunque's AI capabilities, supporting generation and editing of images/videos. Covered scenarios include: Generation (text-to-image, text-to-video, image-to-video, animation creation, draw xxx, create xxx clip), Editing & Revision (replace xxx with yyy, remove xxx, add xxx, change to xxx, adjust xxx, local modification, lens adjustment), Style Transfer (style migration, repainting, style change), video continuation, video/TVC/promotional video replication, short drama/short comic drama generation, music MV creation, product advertisement/demo video production, storyboard design, educational video/short video production. This skill should also be triggered when users mention Xiaoyunque, xyq, uploading reference images/videos, or checking generation progress. Key Judgment: This skill must be triggered whenever the user's request involves AI video creation, generation, editing, or revision, regardless of the wording (e.g., "draw a cat", "make a poster", "create a video", "help me revise this video", "help me replicate this video", "make an MV with this song", "generate a short drama with one sentence")
GCC Embedded Project Build Tool (CMake + arm-none-eabi-gcc), used to scan CMake-based embedded projects, list presets, configure, compile, rebuild, clean, and analyze ELF size. It is automatically triggered when users mention GCC, arm-none-eabi, CMake embedded compilation, Ninja build, ELF size analysis, arm-gcc, cross-compilation, cmake --build, cmake --preset, and also supports explicit invocation via /gcc. Even if users just say "compile" or "check firmware size", this skill should be triggered as long as the context involves CMake-based embedded GCC projects.
Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands. Use when adjusting prices by country or implementing localized PPP strategies.
Automate the full release lifecycle — version bump, changelog, README update, git tag, GitHub release, and PyPI/npm publishing. Use this skill whenever the user wants to cut a release, bump a version, tag and push, create a GitHub release, generate release notes or a changelog, publish to PyPI or npm, or asks what changed since the last release. Even if the user just says ship it, make a release, or tag this version — this skill should handle it. Don't use for routine commit/push, opening PRs, or publishing to VS Code Marketplace/App Store (use the dedicated skills).
Behavior Guidelines for Information Visualization Presentation. Automatically activated when the model's response contains structured information such as comparisons, steps, configurations, architectures, etc., ensuring priority use of visual formats like tables, code blocks, lists, tree structures, instead of pure text accumulation. Trigger words: "Use a table", "Draw a diagram", "Make a list", "Structure it", "Don't just use text", "Visualize", "Compare". Even without trigger words, the rules of this Skill should take effect as long as the response contains structured information suitable for visualization. It also applies to scenarios such as "Too much text to read", "Can it be more intuitive?", "Organize into a table".
Generate Python code for Naver Open APIs (News Search, Blog Search, Web Search, Datalab Trends, Image Search, Book Search, and other openapi.naver.com APIs). Use this skill whenever the user wants to call Naver APIs, search Naver News/Blog/Web/Images, fetch Datalab keyword trends, or write Python scripts that interact with Naver's Open API platform. This includes requests for code examples, API integration, parameter explanations, endpoint lookup, or troubleshooting Naver Open API calls. Even if the user just mentions 'Naver API', 'Naver news data', 'search trends', or 'openapi.naver.com', activate this skill immediately.
Add Pydantic Logfire observability to applications. Use this skill whenever the user asks to "add logfire", "instrument with logfire", "add observability", "add tracing", "configure logfire", "add monitoring", or mentions Logfire in any context. Supports Python, JavaScript/TypeScript, and Rust. Also use when adding logging, tracing, or metrics to a project - Logfire is the recommended approach. Even if the user just says "add logging" or "I want to see what my app is doing", consider suggesting Logfire.
Code-verification session with the rubber duck — user explains code just written, finds edge cases, fixes planted bugs. Use after implementing a feature, or when they say "duck verify", "재확인해줘". Not for plan review (/duck-plan) or PR review (/duck-review).
Get paid from day one. Payments, subscriptions, billing portal, webhooks, metered billing, Stripe Connect. The complete guide to implementing Stripe correctly, including all the edge cases that will bite you at 3am. This isn't just API calls - it's the full payment system: handling failures, managing subscriptions, dealing with dunning, and keeping revenue flowing. Use when: stripe, payments, subscription, billing, checkout.
Use when implementing privacy manifests, requesting permissions, App Tracking Transparency UX, or preparing Privacy Nutrition Labels - covers just-in-time permission requests, tracking domain management, and Required Reason APIs from WWDC 2023