Loading...
Loading...
Found 3,962 Skills
Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows.
Use when designing Xiaohongshu post thumbnails or first images, creating eye-catching cover images, improving click-through rates, or A/B testing cover designs
Use when repurposing Xiaohongshu content, recycling existing posts, adapting content for different formats, maximizing content value, or creating content variations from core material
Use when someone asks to write, rewrite, review, or improve text that appears inside a product or interface. Examples: "review the UX copy", "is there a better way to phrase this", "rewrite this error message", "write copy for this screen/flow/page", reviewing button labels, improving CLI output messages, writing onboarding copy, settings descriptions, or confirmation dialogs. Trigger whenever the request involves wording shown to end users inside software — apps, web, CLI, email notifications, modals, tooltips, empty states, or alerts. Also trigger for vague requests like "review the UX" where interface copy review is implied. Do NOT trigger for content marketing, blog posts, app store listings, API docs, brand guides, cover letters, or interview questions — this is a technical writing skill for interface language.
Write copy that gets a "yes" using Joanna Wiebe's research-first, Voice of Customer methodology Use when: **Writing landing pages, emails, or sales pages** that need measurable conversion results; **Starting a new copy project** and need a systematic process to follow; **Struggling with what to write** and staring at a blank page; **Wanting to prove ROI** to clients with data-backed decisions; **Improving existing copy** through validation and testing
Autonomous development agent that picks tasks from a project board (Jira, ClickUp, GitHub Issues), explores the codebase, implements the solution, opens a PR, and notifies the team. Configurable per-project via project files in ~/.config/delivering-tickets/projects/. Use this skill when the user asks to "work on a ticket", "pick up a task", "implement issue X", "work autonomously on the board", "take the next task", or any variation of autonomous task execution from a project board. Also triggers when the user mentions delivering-tickets, project configuration, or wants to set up autonomous development workflows for their team. Available commands: /delivering-tickets (start), /delivering-tickets:check (check replies), /delivering-tickets:status (workflow status), /delivering-tickets:setup (verify environment), /delivering-tickets:project (manage projects). Do NOT use for general coding without a ticket, standalone code reviews, project setup without a board configured, or questions unrelated to task execution from a project board.
Applicable when followers are unfollowing, engagement rates are declining, or you need strategies to maintain long-term follower engagement and reduce churn
Email marketing automation for HubSpot/Klaviyo/Mailchimp (and similar ESPs): design trigger-based lifecycle workflows (welcome, onboarding, nurture, win-back, cart abandonment), define segmentation + suppression/frequency policies, troubleshoot deliverability (SPF/DKIM/DMARC, one-click unsubscribe, list hygiene), and measure incrementality/ROI (holdouts, RPE, retention economics).
Enforce Vertical Slice Architecture (VSA) when building applications in any language (Go, .NET/C#, Java, Kotlin, TypeScript, Python, etc.) and any type (web API, mobile backend, CLI, event-driven). Organize code by feature/use-case instead of technical layers. Each feature is a self-contained vertical slice with a single entry point that receives the router/framework handle and its dependencies. Use when the user says "vertical slice architecture", "VSA", "organizar por feature", "feature-based architecture", "slice architecture", or when building a new app or feature and the project already follows VSA conventions. Also use when reviewing or refactoring code to align with VSA principles.
Configures .NET CI/CD pipelines (GitHub Actions with setup-dotnet, NuGet cache, reusable workflows; Azure DevOps with DotNetCoreCLI, templates, multi-stage), containerization (multi-stage Dockerfiles, Compose, rootless), packaging (NuGet authoring, source generators, MSIX signing), release management (NBGV, SemVer, changelogs, GitHub Releases), and observability (OpenTelemetry, health checks, structured logging, PII). Spans 18 topic areas. Do not use for application-layer API or UI implementation patterns.
Netflix Eureka for service discovery in Spring Cloud microservices. Covers Eureka Server, Eureka Client, registration, and health checks. USE WHEN: user mentions "eureka", "service discovery", "service registry", "@EnableEurekaServer", "@EnableDiscoveryClient", "eureka dashboard" DO NOT USE FOR: Kubernetes service discovery - use native K8s, Consul - use Consul-specific patterns
GraphQL Code Generator for TypeScript. Generates typed operations, hooks, and document nodes from GraphQL schemas. Use for type-safe GraphQL in frontend. USE WHEN: user mentions "GraphQL Codegen", "generate GraphQL types", "GraphQL TypeScript", "typed GraphQL", "client preset", "React Query GraphQL", asks about "GraphQL code generation", "type-safe GraphQL client", "fragment masking" DO NOT USE FOR: REST API types - use `openapi-codegen` instead; tRPC - use `trpc` instead; GraphQL schema design - use `graphql` instead; Manual GraphQL queries without codegen