Loading...
Loading...
Found 1,213 Skills
Use when decisions could affect groups differently and need to anticipate harms/benefits, assess fairness and safety concerns, identify vulnerable populations, propose risk mitigations, define monitoring metrics, or when user mentions ethical review, impact assessment, differential harm, safety analysis, vulnerable groups, bias audit, or responsible AI/tech.
Guide a user through Stanford Biodesign's needs-finding process to define, scope, and refine a rigorous health-app need statement without jumping prematurely to solutions.
oRPC (v1.12+) typesafe API layer for TypeScript. Covers contract-first development, procedure definition, middleware, routers, context, error handling, Hono integration, TanStack Query, event iterators, plugins, file uploads, WebSocket adapter, and best practices. Use when building or modifying API procedures, data fetching hooks, server handlers, or real-time features. Triggers on tasks involving oRPC, typesafe APIs, RPC procedures, or server route handlers.
Guided Perses dashboard creation: gather requirements (metrics, datasource, layout), generate CUE definition or JSON spec, validate with percli lint, deploy with percli apply or MCP perses_create_dashboard. Use when user wants to create a new Perses dashboard, build a monitoring dashboard, or generate dashboard definitions. Use for "create perses dashboard", "new dashboard", "perses new dashboard", "build dashboard". Do NOT use for Grafana migration (use perses-grafana-migrate) or plugin development (use perses-plugin-create).
Gold-standard code review for SAP CC Go repositories against the project's lead review standards. Dispatches 10 domain-specialist agents in parallel — each loads domain-specific references and scans ALL packages for violations in their assigned domain. Produces a prioritized report with REJECTED/CORRECT code examples. Optional --fix mode applies corrections on a worktree branch. This is the definitive "would this code pass lead review?" assessment.
Build generative UI apps with OpenUI and OpenUI Lang — the token-efficient open standard for LLM-generated interfaces. Use when mentioning OpenUI, @openuidev, generative UI, streaming UI from LLMs, component libraries for AI, or replacing json-render/A2UI. Covers scaffolding, defineComponent, system prompts, the Renderer, and debugging OpenUI Lang output.
A library of creative mechanics — the structural patterns that define how an ad constructs meaning between its hook, visuals, and narrative. Use this whenever designing ad concepts, briefing creative, or trying to explain why a specific ad works beyond just its hook or format. Trigger when a user describes an ad they saw and wants to understand or replicate what made it work, when building a creative concept from a messaging angle, or when execution needs more than a hook and a format — it needs a structural idea. Creative mechanics sit between hooks and visual formats in the Creative Strategy Engine: hooks say what, formats show how, mechanics define the cognitive or emotional mechanism that makes the concept land. Always pair with Hook Writing for opening line execution and Hook Tactics for tactic classification.
Strategic framework for mapping pain/persona intersections and messaging angles. Defines the structure for organizing creative strategy, not the tactics for execution. Use this when planning an organizational or systematic approach to creative strategy, or when a user provides a product and wants to define messaging angles, write strategic hooks, or execute ads in visual formats defined by awareness and decision stages.
Generate an ethos/ folder that captures a project's vision, principles, personas, and non-goals — the 50k-foot "why behind the what." Use when the user wants to establish project philosophy, define guiding principles, document who the product is for, or create foundational context that agents and humans can reference for decision-making. Triggers: "create an ethos", "define project principles", "document our vision", "set up project philosophy", "who is this product for."
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.
Apply when working with GraphQL schema files in graphql/ or implementing resolvers in node/resolvers/ for VTEX IO apps. Covers schema.graphql definitions, @cacheControl and @auth directives, custom type definitions, and resolver registration in the Service class. Use for exposing data through GraphQL queries and mutations with proper cache control and authentication enforcement.
Expert knowledge for Azure Blueprints development including troubleshooting, architecture & design patterns, security, configuration, and integrations & coding patterns. Use when defining Azure Blueprints, mapping built-in compliance sets, automating via CLI/PowerShell/REST, or fixing assignment errors, and other Azure Blueprints related development tasks. Not for Azure Policy (use azure-policy), Azure Resource Manager (use azure-resource-manager), Azure Managed Applications (use azure-managed-applications), Azure Deployment Environments (use azure-deployment-environments).