Loading...
Loading...
Found 5,940 Skills
Apply vertical (domain-first) codebase architecture to any project. Use this skill whenever a user asks where to put a file, how to structure a codebase, how to organize code by feature or domain, how to refactor a "horizontal" structure (components/, hooks/, utils/, types/), or asks about code colocation, monorepo boundaries, shared code, or module ownership. Also trigger when the user creates a new module and needs to decide where it belongs, or when reviewing a PR that touches file organization. Works for any language or framework (Python, TypeScript, Go, Rust, etc.) — not just React or frontend.
Use this skill when drawing shapes and graphics in Phaser 4. Covers the Graphics game object, lines, rectangles, circles, arcs, polygons, gradients, fill, stroke, and generated textures. Triggers on: Graphics, draw shape, fillRect, lineStyle, polygon, arc.
Use when the user explicitly requests security best practices guidance, a security review or report, or secure-by-default coding help for Python, JavaScript or TypeScript, or Go code.
Authors and consumes feature-level domain knowledge files in ai-context/features/. Reference guide for bounded-context business rules, invariants, integration points, and known gotchas.
Use when deploying a database to Zeabur. Use when user needs MySQL, PostgreSQL, MongoDB, or Redis. Use when user says "I need a database", "add database", "deploy postgres", "set up MySQL", "add Redis", "add MongoDB", or "connect to database". Also use when user mentions data persistence issues like "data lost after restart", "data not saved", "data disappears", "need persistent storage for data", or "how to persist data". Also use when integrating a database with an existing service.
Monitors email deliverability via Mailgun Optimize (InboxReady) API. Use when the user wants to test inbox placement with seed lists, monitor IP or domain blocklists, track spam traps, check email health scores, review DMARC reports, or pull Google Postmaster or Microsoft SNDS data. Also use when emails are going to spam, sender reputation is dropping, inbox rate is declining, a domain needs warmup monitoring, an IP needs blocklist removal, or the user wants to set up email deliverability monitoring.
Upgrade any Pulumi provider to a newer version and reconcile the resulting diff. Use when users want to upgrade or update a provider (including editing package.json, requirements.txt, pyproject.toml, go.mod, or Pulumi.yaml to bump a provider SDK), check for breaking changes before or during an upgrade, fix resources that broke after a provider upgrade, or resolve unexpected replacements, creates, or deletes in a post-upgrade preview. Applies to all providers (aws, azure-native, gcp, kubernetes, aws-native, cloudflare, datadog, etc.) — not just Tier 1. Do NOT use for querying which stacks use what package versions; use skill `package-usage` for cross-stack audits. Do NOT use for general infrastructure tasks.
Work with the DatoCMS CLI tool (datocms) for command-line migrations, schema type generation, direct one-off CMA calls, typed one-off TypeScript CMA scripts, environment operations, deployment workflows, and multi-project profile syncing. Use when users ask for datocms CLI commands or scripts such as migrations:new, migrations:run, schema:generate, cma:call, cma:docs, cma:script (for ad-hoc typed TypeScript scripts with ambient client/Schema globals), migration scaffolding for models/fields/blocks, CLI setup with datocms.config.json and profiles, OAuth authentication (login, logout, whoami), discovering accessible projects (projects:list), project linking (link, unlink), environment commands (list/fork/promote/rename/destroy), maintenance-mode toggling, CI/CD migration pipelines, blueprint/client project sync, imports from WordPress or Contentful (including assets/content), and CLI plugin management (plugins:install, plugins:add, plugins:available, plugins:link for local plugin development, plugins:remove, plugins:update, plugins:reset, plugins:inspect).
Color-code the Obsidian graph view by rewriting `.obsidian/graph.json` colorGroups. Use this skill when the user says "color my graph", "color code obsidian", "colorize the graph", "color the graph by tag", "color by category", "highlight visibility in graph", "make the graph colorful", "distinguish tags in graph", or wants nodes in Obsidian's graph view tinted by tag, folder, or visibility. Generates a `colorGroups` array from the vault's actual tags/categories and merges it into the existing graph.json without clobbering other graph settings. Always backs up first.
Sprout Social platform help — Publishing, Smart Inbox, Analytics, Social Listening (add-on), Influencer Marketing, Employee Advocacy, AI Assist, API, Salesforce/HubSpot/Zendesk integrations. Use when Sprout Social posts aren't publishing on schedule, Smart Inbox is overwhelming and hard to triage, analytics reports don't show the metrics you need, social listening queries return too much noise, influencer campaigns in Sprout lack visibility, employee advocacy adoption is low, AI Assist suggestions feel off, CRM sync keeps disconnecting, or you're deciding between Sprout Social and Hootsuite/Buffer/Agorapulse. Do NOT use for social listening strategy across tools (use /sales-social-listening), influencer marketing strategy (use /sales-influencer-marketing), social media management strategy (use /sales-social-media-management), or employee advocacy strategy (use /sales-employee-advocacy).
Online reputation management strategy — monitoring reviews across Google, Yelp, Facebook, and industry sites, responding to negative reviews, generating more reviews, managing business listings, Google Business Profile optimization, reputation recovery after a crisis. Covers multi-location reputation at scale. Use when Google reviews disappeared or got removed, negative review is hurting your business, not getting enough reviews, business listings show wrong information, unsure which reputation management tool to pick, or your star rating is dropping. Do NOT use for ecommerce product review apps (use /sales-customer-reviews), B2B software reviews on G2 (use /sales-g2), or social listening for brand mentions (use /sales-social-listening).
Offer a structured but non-clinical space for a PhD student or researcher to check in on their mental and emotional state, especially around imposter syndrome, guilt about rest, chronic over-promising, and burnout signals. Use this skill when the user expresses feelings of inadequacy, constant comparison to peers, fear of disappointing their advisor, guilt about taking time off, or exhaustion that isn't just physical. Trigger on phrases like "I feel behind", "everyone is smarter than me", "I can't rest", "I'm burned out", "imposter syndrome", "I'm not good enough", "I'm afraid of disappointing", "I should be working", or whenever the tone of the user's message suggests emotional strain rather than a technical question. Also trigger gently if these signals appear incidentally in a task-focused conversation.