Total 56,302 skills, Backend Development has 4435 skills
Showing 12 of 4435 skills
Use these skills when you need to explore the database schema, identify objects like views and triggers, and execute custom SQL queries to interact with your data.
WeChat Pay Medical Insurance Payment (Mobile Medical Insurance Payment 2.0) Access Solution, covering the full link of medical insurance and self-payment mixed order placement, order query, medical insurance refund notification, and medical insurance payment callback. It provides five capabilities: product selection/sample code/business quick reference/quality assessment/troubleshooting. Use when user mentions "Medical Insurance Payment", "Mobile Medical Insurance Payment 2.0", "Medical Insurance and Self-payment Mixed", "Medical Insurance Electronic Certificate", "Medical Insurance Mixed Payment Collection", "Medical Insurance Refund Notification", "Medical Insurance Registration", "Medical Insurance In-clinic Payment", "Medical Insurance Inpatient Settlement", "Medical Insurance Pharmacy Purchase", "Internet Hospital Medical Insurance", "Medical Insurance Designated Institution", or asks to "access medical insurance payment", "request sample code for medical insurance order placement interface", "troubleshoot medical insurance payment issues".
Use when the user wants to extract, generate, refine, or harden an OpenAPI or Swagger specification from an existing API application, service, project, repo, routes, controllers, handlers, or codebase. Select this skill for any request whose intent is to derive, extract, generate, reverse-engineer, infer, document, or harden an OpenAPI or Swagger contract from an existing application or source code. This includes generic prompts about producing an API spec/docs/schema/contract for an existing app, project, service, repo, endpoints, routes, or controllers. Prefer this skill over extraction-only skills when the prompt is about an existing application or codebase and the expected outcome is an accurate extracted contract plus post-extraction refinement.
Use when asked to identify and fix errors in an OpenAPI specification that are preventing it from running as mock or test
Audits optimizer table statistics for staleness, missing coverage, and data quality issues using SHOW STATISTICS. Use when diagnosing poor query performance, unexpected plan changes, or after bulk data changes to identify stale statistics requiring refresh via CREATE STATISTICS.
Build and configure a GraphQL API backed by Neo4j using @neo4j/graphql v7 (current) or v5 (LTS). Covers Neo4jGraphQL constructor, getSchema(), assertIndexesAndConstraints(), type definitions with @node, @relationship (IN/OUT/UNDIRECTED), @cypher for custom resolvers, @authorization/@authentication for JWT/JWKS security, auto-generated queries/mutations, OGM programmatic access, subscriptions via CDC, and Apollo Federation. Use when writing typeDefs, securing fields, or wiring Neo4j to Apollo Server. Does NOT handle raw Cypher outside resolvers — use neo4j-cypher-skill. Does NOT cover Spring Data Neo4j entity mapping — use neo4j-spring-data-skill.
Use when creating, modifying, or removing API endpoints on a Datex Studio branch. Covers the full lifecycle: requirements, prerequisite creation (datasources, flows), endpoint wiring, and verification. Trigger for: "create an endpoint", "expose this flow as an API", "add an API for X", "modify endpoint", "remove endpoint", "change endpoint alias", "create an API that does X".
gRPC service development in .NET for high-performance inter-service communication
Configure Redis for caching and data storage. Set up clustering, persistence, and Sentinel. Use when implementing Redis caching or queues.
General performance optimization techniques for Motoko. Reducing allocations, efficient Text building, fixed-width arithmetic, block processing, async patterns, and more. Load when you need to improve hot paths or reduce overhead without changing behavior.
Analyze a user's codebase to verify it can use Runway's public API (server-side requirement)
Design complete API contracts in OpenAPI 3.0/3.1 YAML with endpoints, schemas, security, pagination, error handling, and RFC 7807 problem details. Use when asking to design an API, create an OpenAPI spec, define API endpoints, write API contracts, or generate a Swagger specification.