All authors
Claude Skills by cyber93de
github.com/cyber93de12 skills0 installs8 views
- Api DesignDesigning and reviewing service interfaces — REST (versioning, resource modelling, status codes, pagination, idempotency, errors, OpenAPI, .http files), SOAP/WSDL when it is genuinely required and how to migrate off it, GraphQL and gRPC trade-offs, and API authentication/authorisation. Invoke when creating or changing any endpoint, contract, WSDL, OpenAPI/Swagger spec or client, when deciding between REST/SOAP/GraphQL/gRPC, or on explicit request — "API", "REST", "endpoint", "SOAP", "WSDL", "...Votes: 0GitHub stars: 3
- Cloud NativePackaging and running services in the cloud — container images, Docker Compose, Kubernetes manifests and Helm, EC2/VM deployments, microservice boundaries versus a modular monolith, 12-factor configuration, health probes, autoscaling, zero-downtime rollout, and the observability and cost consequences. Invoke when a change touches a Dockerfile, compose file, K8s/Helm manifest, Terraform, or a deployment pipeline, when service decomposition is being discussed, or on explicit request — "Docker",...Votes: 0GitHub stars: 3
- Data StorageChoosing and using the right store — relational SQL (PostgreSQL and friends), NoSQL (document, key-value, wide-column, graph), embedded/in-app databases (SQLite, Room, Drift, Realm), Redis as cache and in-memory store, and Elasticsearch/OpenSearch as a search and read-load layer in front of the database. Covers when each is justified, cache invalidation, indexing, migrations and the polyglot-persistence trade-off. Invoke when a change adds or touches a datastore, a cache, a search index, or a...Votes: 0GitHub stars: 3
- Memory SetupPersistent project memory setup and the context-routing stack for this project — what lives in .claude/memory/ vs Beads vs graphify vs cocoindex-code vs context7, when to write a memory file, learning intensity, Ollama/router wiring, and shared team preferences. Invoke when deciding whether/what to save to memory, when context-routing is unclear (which source to hit first), when Ollama/claude-code-router or team-prefs come up, or on explicit request — "memory setup", "what should I remember",...Votes: 0GitHub stars: 3
- Messaging EventsAsynchronous integration — when a message queue or event stream is the right answer instead of a synchronous call, choosing between Kafka, RabbitMQ, NATS, SQS/SNS and a database-backed queue, and the patterns that make it survive production — delivery semantics, idempotent consumers, the transactional outbox, ordering and partitioning, schema evolution, dead-letter handling, sagas. Invoke when a change introduces or touches a queue, topic, broker, event, or background job, when synchronous co...Votes: 0GitHub stars: 3
- PonytailYAGNI decision ladder for any code-writing task — before adding new code, checks whether it needs to exist at all, already exists in the codebase, is available in the language's stdlib, is a native platform feature, is already an installed dependency, or can be a one-liner, and only then writes the minimum viable new code. Complements AGENTS.md §3a design principles (YAGNI, KISS, no premature abstraction) with an explicit, ordered checklist applied to every new function/class/dependency/abstr...Votes: 0GitHub stars: 3
- SecurityOperational security checklist for building and reviewing code — OWASP Top 10 and ASVS as the review raster, IAM done properly (least privilege, roles over per-user grants, short-lived credentials, rotation), API authentication and authorisation, input validation and injection defence, secrets handling, cryptography choices, and supply-chain safety (pinned dependencies, no curl-pipe-sh, image scanning). Invoke when a change touches authentication, authorisation, sessions, tokens, credentials,...Votes: 0GitHub stars: 3
- Seo OptimizationSearch-engine optimization for any web-facing project — plain HTML, GitHub Pages, static and documentation sites, landing pages, blogs, Next.js, Astro, Hugo, Jekyll, React, Vue, Svelte, Angular or any other web framework. Covers on-page HTML (title, meta description, canonical, robots, lang, viewport, headings, semantic HTML, alt text, internal linking), Open Graph, Twitter Cards, JSON-LD/schema.org structured data, technical SEO (robots.txt, sitemap.xml, redirects, broken links, Core Web Vit...Votes: 0GitHub stars: 3
- Stack BackendArchitecture, quality and test checklist for server-side services in any stack — Spring/Spring Boot, Quarkus, Jakarta EE on Tomcat, .NET, Rust (Axum/Actix), Node/NestJS, Go, Python (FastAPI/Django). Covers hexagonal layering with DAO/DTO, transactions and consistency, configuration and secrets, resilience (timeouts, retries, circuit breakers), observability, the FOSS-preferred stack, and the backend test pyramid. Invoke when the project contains a server-side application or service, or on exp...Votes: 0GitHub stars: 3
- Stack EmbeddedArchitecture, quality and test checklist for embedded/firmware work in C or C++ — MCU and RTOS targets, HAL/driver separation, deterministic memory and timing, cross-compilation and flashing, on-host unit tests with a mocked HAL, and the failure modes that only bite on real hardware. Invoke when the project targets a microcontroller, an RTOS (FreeRTOS/Zephyr/RIOT), bare metal, or a Linux embedded board, when the build uses a cross-toolchain (arm-none-eabi, riscv, Xtensa), or on explicit reque...Votes: 0GitHub stars: 3
- Stack MobileArchitecture, quality and test checklist for mobile apps — cross-platform with Dart/Flutter, and native with Kotlin on Android or Swift/Objective-C on iOS. Covers layering and state management, the platform lifecycle, offline/sync and on-device storage, permissions and secure credential storage, store-release constraints, and the mobile-specific test pyramid. Invoke when the project contains a Flutter/Dart app, an Android module (Gradle, Jetpack Compose, Kotlin), or an iOS target (Xcode, Swif...Votes: 0GitHub stars: 3
- Stack Web FrontendArchitecture, quality and test checklist for browser front-ends built with Angular, React, or Vue (incl. Next/Nuxt/SvelteKit-style meta-frameworks) — feature-sliced structure, state management, the API/DTO boundary, forms and validation, XSS and auth-token handling in the browser, bundle/Core-Web-Vitals budgets, i18n and accessibility, and the front-end test pyramid. Invoke when the project has an Angular, React, or Vue application, or on explicit request — "frontend", "Angular", "React", "Vu...Votes: 0GitHub stars: 3