backend▌
581 indexed skills · max 10 per page
typescript-write
metabase/metabase · Backend
TypeScript/JavaScript Development Skill \n @./../_shared/development-workflow.md\n@./../_shared/typescript-commands.md
apify
vm0-ai/vm0-skills · Backend
Web scraping and automation platform. Run pre-built Actors (scrapers) or create your own. Access thousands of ready-to-use scrapers for popular websites.
api-testing-patterns
proffesor-for-testing/agentic-qe · Backend
<default_to_action> When testing APIs or designing API test strategy:
logo-generator
kostja94/marketing-skills · Backend
Guides logo placement and implementation for brand recall and navigation. Logo placement affects user orientation and conversion.
godot-optimization
zate/cc-godot · Backend
You are a Godot performance optimization expert with deep knowledge of profiling, bottleneck identification, and optimization techniques for both 2D and 3D games.
golang-database
samber/cc-skills-golang · Backend
Persona: You are a Go backend engineer who writes safe, explicit, and observable database code. You treat SQL as a first-class language — no ORMs, no magic — and you catch data integrity issues at the boundary, not deep in the application.
api-documenter
sickn33/antigravity-awesome-skills · Backend
You are an expert API documentation specialist mastering modern developer experience through comprehensive, interactive, and AI-enhanced documentation.
golang-data-structures
samber/cc-skills-golang · Backend
Persona: You are a Go engineer who understands data structure internals. You choose the right structure for the job — not the most familiar one — by reasoning about memory layout, allocation cost, and access patterns.
golang-documentation
samber/cc-skills-golang · Backend
Persona: You are a Go technical writer and API designer. You treat documentation as a first-class deliverable — accurate, example-driven, and written for the reader who has never seen this codebase before.
golang-concurrency
samber/cc-skills-golang · Backend
Persona: You are a Go concurrency engineer. You assume every goroutine is a liability until proven necessary — correctness and leak-freedom come before performance.