backend-patterns
vmain
io.github.affaan-m/ECC/backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
“github” 共 3,983 个结果
vmain
io.github.affaan-m/ECC/backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
vmain
io.github.affaan-m/ECC/security-review
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
vmain
io.github.affaan-m/ECC/code-tour
Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.
vmain
io.github.Archive228/loopkit/sql-review
Review SQL and ORM queries for correctness, safety, and performance before they ship.
vmaster
io.github.JetBrains/intellij-community/testing-internals
Internals of tests.cmd execution flow, test discovery, and troubleshooting. Use when debugging test discovery issues or understanding the test runner.
vmaster
io.github.JetBrains/intellij-community/testing-internals
Internals of tests.cmd execution flow, test discovery, and troubleshooting. Use when debugging test discovery issues or understanding the test runner.
vmain
io.github.microsoft/hve-core/prompt-refactor
Refactor existing prompt artifacts against explicit requirements through the full prompt-builder loop.
vmain
io.github.markus-global/markus/cursor-agent
Use the Cursor CLI agent mode for IDE-integrated coding with project rules and repo-aware edits
vmain
io.github.code-yeongyu/lazycodex/writing-design-plans
Use when you have a design brief or strategy and need to break implementation into reviewable chunks — creates step-by-step plans with verification criteria for each task
vmain
io.github.vudovn/ag-kit/frontend-architecture
How to organize frontend code — separation of concerns (UI / logic / data / type), file responsibility, state tiers, API services, schema validation, and framework conventions for React/Next and Vue. Structural rules, not visual design.
vmain
io.github.vudovn/ag-kit/design-spec
How to author a DESIGN.md file — the machine-readable design-token + human-rationale format that must exist before any UI is built. YAML front-matter token schema (colors, typography, spacing, rounded, components), type system, token references, and canonical section order.
vmain
io.github.sickn33/antigravity-awesome-skills/browser-testing-with-devtools
Test browser apps with Chrome DevTools MCP by inspecting live DOM, console logs, network traffic, screenshots, accessibility, and performance traces.
vmain
io.github.sickn33/antigravity-awesome-skills/frontend-lighthouse
Add a portable Lighthouse CI gate for production frontend builds with Core Web Vitals budgets, category floors, median runs, and CI artifacts.
vmain
io.github.Klotzkette/claude-fuer-deutsches-recht/writing-dokumente-intake
Dokumentenintake: sortiert Dokumente, erkennt Lücken, ordnet Beweiswert und formuliert gezielte Rückfragen.
vmain
io.github.greenpau/caddy-security/testing-and-ci
caddy-security repository testing and CI workflow guidance, including Go test command selection, Makefile report targets, Caddyfile parser/adapt fixture tests, runtime resolution fixtures, coverage artifacts, and GitHub Actions build/release/CLA behavior. Use when choosing or running tests, adding or updating test coverage, interpreting CI failures, reproducing GitHub Actions locally, or documenting validation for this Go/Caddy module.
vmain
io.github.hypnguyen1209/offensive-claude/mobile-pentest
Use when pentesting an Android/iOS app — Frida 17 instrumentation, SSL-pinning & root/jailbreak bypass, Android 14/15 CA injection, exported-component/content-provider abuse, deep-link/WebView chains, biometric bypass, Flutter/React-Native RE
vmain
io.github.seaworld008/Commonly-used-high-value-skills/kubernetes-specialist
Use when managing Kubernetes clusters, debugging Pods and workloads, designing Helm charts, reviewing manifests, or improving deployment, scaling, and observability practices.
vdev
io.github.plaited/plaited/css-schemas
Refresh or drift-check the generated CSS property schemas from @webref/css via the plaited CLI. Covers when to regenerate, review discipline, drift checking, and failure modes.
vmaster
io.github.SRombauts/SQLiteCpp/sqlitecpp-ci-workflows
SQLiteCpp CI workflow patterns. Use for GitHub Actions, AppVeyor, Travis, matrices, or test steps.
vmain
io.github.echoVic/boss-skill/testing-guide
后端测试编写指南,包括单元测试、集成测试和E2E测试的编写方法和最佳实践
vmain
io.github.JMBeresford/retrom/docker-via-wsl
Use when YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command. Docker Desktop runs on the WSL2 engine, so commands must be re-issued INSIDE WSL via wsl.exe -- running them from the Windows shell on a network/SMB drive (Z:, UNC) corrupts bind-mount paths. Does NOT apply if your shell is already inside WSL. Triggers on: docker, docker compose, docker-compose, container, bind mount, volume, 'is a directory', mount source wrong, Windows + Docker Desktop, WSL.
vmain
io.github.JMBeresford/retrom/docker-development
Use when working with ANY Docker task: writing Dockerfiles, configuring docker-compose/compose.yml, multi-stage builds, docker-bake.hcl, container security audits, .dockerignore optimization, or CI/CD container testing. Triggers on: Dockerfile, docker-compose, container, image build, multi-stage, docker bake, compose.
vmain
io.github.bmad-code-org/BMAD-METHOD/bmad-code-review
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
vmain
io.github.mohitagw15856/pm-claude-skills/sql-optimizer
Diagnose a slow SQL query and produce a concrete optimization plan. Use when asked to optimize SQL, speed up a slow query, reduce a query's cost/scan, fix a timeout, or review a query plan. Produces an analysis — the likely bottleneck, what the plan is doing wrong (full scans, bad joins, spills), the specific rewrite and index/partition changes, and the expected impact, with the optimized query.