All authors
Claude Skills by claude-dev-suite
github.com/claude-dev-suite740 skills14 installs1,174 views
- Spring SchedulingSpring Scheduling and Async for Spring Boot 3.x. Covers @Scheduled, @Async, cron expressions, ThreadPoolTaskExecutor, task monitoring, distributed scheduling with ShedLock, and error handling. USE WHEN: user mentions "@Scheduled", "@Async", "cron expression Spring", "background jobs Spring", "async Spring Boot", "ThreadPoolTaskExecutor", "ShedLock" DO NOT USE FOR: complex batch jobs - use `spring-batch` skill, workflow orchestration - consider Temporal or Camunda, message-driven - use messa...Votes: 0GitHub stars: 31
- Spring SecuritySpring Security JWT authentication for Spring Boot 3. Covers SecurityFilterChain, JWT filter, authentication, authorization, CORS, rate limiting, and security headers. USE WHEN: user mentions "security", "JWT", "authentication", "authorization", asks about "login", "token", "CORS", "roles", "permissions", "@PreAuthorize" DO NOT USE FOR: Spring Boot basics (use `spring-boot`), OAuth2 details (use OAuth2 skill if available), general encryption (use security-expert)Votes: 0GitHub stars: 31
- Spring SessionSpring Session for distributed session management with Redis, JDBC, or Hazelcast. Covers session configuration, security integration, and session events. USE WHEN: user mentions "spring session", "distributed session", "session Redis", "session JDBC", "session cluster", "session management", "@SessionScope" DO NOT USE FOR: stateless JWT auth - use `jwt` skill, OAuth2 tokens - use `oauth2` skillVotes: 0GitHub stars: 31
- Spring ShellSpring Shell for building interactive CLI applications. Covers @ShellComponent, @ShellMethod, input validation, tables, and command groups. USE WHEN: user mentions "spring shell", "@ShellComponent", "@ShellMethod", "CLI application Spring", "interactive shell", "command line tool Spring" DO NOT USE FOR: simple scripts - use regular main method, batch processing - use `spring-batch` skill, web endpoints - use `spring-rest` skillVotes: 0GitHub stars: 31
- Spring StatemachineSpring Statemachine for building finite state machine applications. Covers states, transitions, guards, actions, persistence, and hierarchical states. USE WHEN: user mentions "spring statemachine", "state machine Spring", "workflow Spring", "finite state machine", "order state", "document lifecycle", "guards actions transitions" DO NOT USE FOR: simple status flags - use enum fields, complex workflow orchestration - use `spring-integration` or Camunda, business rules engine - use DroolsVotes: 0GitHub stars: 31
- Spring ValidationBean Validation (JSR-380) with Spring Boot. Covers request validation, custom validators, validation groups, and error handling. USE WHEN: user mentions "spring validation", "@Valid", "@NotNull", "@NotBlank", "bean validation", "request validation", "custom validator", "validation groups", "ConstraintValidator", "@Pattern" DO NOT USE FOR: business rule validation - use service layer, security validation - use `spring-security` skillVotes: 0GitHub stars: 31
- Spring WebSpring Web MVC advanced for Spring Boot 3.x. Covers RestClient (Spring 6.1+), WebClient, ResponseEntity patterns, interceptors, content negotiation, file upload/download, streaming responses, and custom argument resolvers. USE WHEN: user mentions "spring web", "RestClient", "WebClient", "ResponseEntity", "HTTP client Spring", "file upload", "file download", "streaming response", "HandlerInterceptor", "content negotiation", "argument resolver" DO NOT USE FOR: reactive web stack - use `spring...Votes: 0GitHub stars: 31
- Spring WebfluxSpring WebFlux for reactive programming in Spring Boot 3.x. Covers Mono/Flux, reactive operators, WebClient, functional endpoints, R2DBC integration, reactive error handling, and testing. Use for non-blocking high-concurrency apps. USE WHEN: user mentions "spring webflux", "reactive Spring", "Mono", "Flux", "WebClient reactive", "functional endpoints", "R2DBC", "non-blocking", "StepVerifier", "reactive streams" DO NOT USE FOR: traditional blocking MVC - use `spring-web` skill, simple REST A...Votes: 0GitHub stars: 31
- Spring WebsocketSpring WebSocket for real-time communication in Spring Boot 3.x. Covers STOMP over WebSocket, SockJS fallback, message brokers (simple and RabbitMQ/Redis), security, session handling, and testing. Use for chat, live notifications, and real-time updates. USE WHEN: user mentions "spring websocket", "STOMP", "SockJS", "real-time Spring", "@MessageMapping", "@SendTo", "WebSocket security", "message broker Spring", "chat application Spring", "live notifications" DO NOT USE FOR: REST APIs - use `...Votes: 0GitHub stars: 31
- StreamlitStreamlit Python web application framework. Covers session state, caching, layouts, widgets, multipage apps, and deployment. Use when building interactive Python data apps or dashboards. USE WHEN: user mentions "streamlit", "st.session_state", "st.cache_data", "streamlit app", "python dashboard", "python web app", "streamlit deploy", "streamlit form", "streamlit component" DO NOT USE FOR: FastAPI/Flask REST APIs, Django web apps, Jupyter notebooksVotes: 0GitHub stars: 31
- ThymeleafThymeleaf template engine for Java/Spring. Covers HTML templates, expressions, fragments, i18n, and email templates. USE WHEN: user mentions "thymeleaf", "spring template", "HTML template Spring", "email template Java", "th:text", "th:each", "th:if", "fragments", "layout" DO NOT USE FOR: REST API JSON - use `spring-rest` skill, SPA frontend - use React/Vue/Angular skills, PDF generation - use JasperReports or iTextVotes: 0GitHub stars: 31
- WarpWarp Rust web framework using filters. Covers routing, filters, rejection, WebSocket, and TLS. Use for composable, type-safe Rust APIs. USE WHEN: user mentions "warp", "rust filters", "composable rust api", asks about "warp filters", "warp rejection", "filter composition rust", "rust hyper warp", "warp websocket" DO NOT USE FOR: Axum projects - use `axum` instead, Actix-web projects - use `actix-web` instead, Rocket projects - use `rocket` instead, non-Rust backendsVotes: 0GitHub stars: 31
- BiomeBiome linter and formatter for JavaScript/TypeScript. Covers configuration, rules, and integration patterns. Replaces ESLint + Prettier for faster development experience. USE WHEN: user mentions "biome", "linting", "formatting", "code style", "biome.json", asks about "setup linter", "format code", "migrate from ESLint", "migrate from Prettier", "biome rules", "biome configuration" DO NOT USE FOR: ESLint configuration - Biome is an ESLint replacement, Prettier configuration - Biome is a Pret...Votes: 0GitHub stars: 31
- Caching StrategiesApplication caching patterns. Redis caching, in-memory caches, HTTP caching, cache invalidation strategies, cache-aside, write-through, and CDN caching. USE WHEN: user mentions "caching", "cache invalidation", "Redis cache", "HTTP cache", "CDN caching", "cache-aside", "write-through", "TTL", "stale-while-revalidate" DO NOT USE FOR: Redis as database/queue - use `redis` or `job-queues`; browser storage - use frontend skillsVotes: 0GitHub stars: 31
- Clean CodeClean code principles. Covers naming, functions, and readability. Use when writing or reviewing code for quality. USE WHEN: user mentions "code quality", "readability", "refactor", "clean up code", "naming", "magic numbers", asks about "how to write better code", "code smells", "DRY", "KISS", "YAGNI", "single responsibility" DO NOT USE FOR: SOLID principles - use `solid-principles` instead, Git workflow - use `git-workflow` instead, Performance optimization - use `performance` insteadVotes: 0GitHub stars: 31
- Error HandlingError handling patterns across languages and frameworks. Custom error classes, global exception handlers, Problem Details (RFC 9457), error boundaries (React), Result types, and structured error responses. USE WHEN: user mentions "error handling", "exception handler", "error boundary", "custom error", "Problem Details", "error response", "global error handler" DO NOT USE FOR: logging errors - use logging skills; error tracking services - use `error-tracking`Votes: 0GitHub stars: 31
- Event DrivenEvent-driven architecture patterns and best practices. Covers Saga, Outbox, CQRS, Event Sourcing, and messaging patterns for distributed systems. USE WHEN: user mentions "event-driven", "Saga", "Outbox pattern", "CQRS", "Event Sourcing", "distributed transactions", "eventual consistency", "message broker", "event bus", asks about "microservices communication", "async patterns", "compensating transactions" DO NOT USE FOR: Simple pub/sub - use messaging framework skills (Kafka, RabbitMQ), RES...Votes: 0GitHub stars: 31
- Feature FlagsFeature flag management. LaunchDarkly, Unleash, Flagsmith, and custom implementations. Gradual rollouts, A/B testing, kill switches, and flag lifecycle management. USE WHEN: user mentions "feature flag", "feature toggle", "LaunchDarkly", "Unleash", "Flagsmith", "gradual rollout", "A/B test", "canary release", "kill switch" DO NOT USE FOR: CI/CD deployment strategies - use `github-actions`; environment config - use environment variable patternsVotes: 0GitHub stars: 31
- Git WorkflowGit workflow best practices. Covers branching, commits, and collaboration. Use for version control guidance. USE WHEN: user mentions "git", "commit", "branch", "pull request", "PR", "merge", "rebase", "version control", asks about "commit message", "branching strategy", "git best practices", "conventional commits", "how to write PR description" DO NOT USE FOR: Git commands syntax - use git documentation, GitHub Actions CI/CD - use ci-cd skills, Code review quality - use `code-reviewer` agentVotes: 0GitHub stars: 31
- Open SourceOpen source readiness best practices. Covers licensing, documentation, community health, CI/CD, compliance, legal, and packaging. USE WHEN: user mentions "open source", "license", "LICENSE", "CONTRIBUTING", "CODE_OF_CONDUCT", "CHANGELOG", "open source readiness", "community health", "OSS compliance", "SPDX", "CLA", "DCO", "OpenSSF", "SBOM", "release automation", "npm publish", "make project open source", "prepare for open source" DO NOT USE FOR: Git workflow and branching - use git-workflow...Votes: 0GitHub stars: 31
- PerformanceWeb performance optimization. Covers frontend, backend, and database optimization. Use for performance reviews. USE WHEN: user mentions "performance", "slow", "optimization", "Core Web Vitals", "LCP", "INP", "CLS", "bundle size", "lazy load", "caching", "N+1 query", "memory leak", asks about "how to speed up", "improve performance", "reduce load time", "database optimization" DO NOT USE FOR: Algorithm complexity - use computer science fundamentals, Code quality/readability - use `clean-code...Votes: 0GitHub stars: 31
- Python QualityPython static analysis with ruff, mypy, pyright. Type checking and linting best practices. USE WHEN: "type checking", "mypy", "pyright", "ruff", "linting", "static analysis", "type error", "type hints", "pylint", "flake8", "black", "isort", "code quality" DO NOT USE FOR: Basic type hint syntax - use languages/python skill DO NOT USE FOR: Runtime validation - use PydanticVotes: 0GitHub stars: 31
- Resilience PatternsApplication resilience patterns. Circuit breakers, retries with backoff, bulkheads, timeouts, fallbacks, and health checks. Polly (.NET), resilience4j (Java), cockatiel (Node.js). USE WHEN: user mentions "circuit breaker", "retry", "backoff", "bulkhead", "resilience", "fault tolerance", "Polly", "resilience4j", "fallback" DO NOT USE FOR: error handling basics - use language skills; monitoring - use `opentelemetry`Votes: 0GitHub stars: 31
- RuffRuff Python linter and formatter. Covers configuration in pyproject.toml, rule selection, auto-fix, and integration with editors and CI. Use when configuring or troubleshooting Python code quality tooling. USE WHEN: user mentions "ruff", "ruff check", "ruff format", "python linting", "pyproject.toml linting", "isort alternative", "black alternative", "flake8 replacement", "python formatter" DO NOT USE FOR: ESLint/Prettier (JavaScript), mypy type checkingVotes: 0GitHub stars: 31
- Solid PrinciplesSOLID design principles. Covers SRP, OCP, LSP, ISP, DIP. Use when designing classes and modules. USE WHEN: user mentions "SOLID", "single responsibility", "open closed", "Liskov", "interface segregation", "dependency inversion", "dependency injection", asks about "class design", "OOP principles", "extensibility", "abstraction", "how to design classes" DO NOT USE FOR: General code quality - use `clean-code` instead, Specific patterns - use design patterns skills, Language-specific OOP - use ...Votes: 0GitHub stars: 31
- Token OptimizationToken optimization best practices for MCP server and tool interactions. Minimizes token consumption while maintaining effectiveness. USE WHEN: user mentions "token usage", "optimize tokens", "reduce API calls", "MCP efficiency", asks about "how to use less tokens", "MCP best practices", "limit output size", "efficient queries" DO NOT USE FOR: Code optimization - use `performance` instead, Text compression - this is about API usage patterns, Cost optimization (infrastructure) - use cloud/Dev...Votes: 0GitHub stars: 31
- Descriptors WalletBitcoin Core descriptors wallet: createwallet, importdescriptors, multipath, ranges, watch-only, signing wallets, multisig coordination. Replaces legacy BDB wallet. USE WHEN: setting up Bitcoin Core wallet, watching xpubs, building signing pipelines via Core.Votes: 0GitHub stars: 31
- IndexesBitcoin Core indexes: txindex, blockfilterindex (BIP157/158), coinstatsindex, txospenderindex. Disk costs, rebuild times, when each is needed. USE WHEN: choosing which indexes to enable, troubleshooting "txid not found", integrating with electrs / fulcrum / LN nodes.Votes: 0GitHub stars: 31
- KnotsBitcoin Knots: Luke Dashjr's Bitcoin Core fork with stricter mempool policy and additional configuration. Since the 2026 BIP-110 and BLAKE2b hardforks it is also a separate consensus network, not only a policy downstream. Differences vs Core, when to consider, compatibility. USE WHEN: evaluating Knots for stricter mempool policy, reviewing a node deployment that uses Knots, understanding policy and consensus divergence between Core and Knots.Votes: 0GitHub stars: 31
- OperationsRunning Bitcoin Core in production: bitcoin.conf reference, sections, pruning, signet, dbcache, mempool tuning, network bind, Tor, IBD considerations, debug.log analysis. USE WHEN: deploying a node, tuning performance, debugging IBD issues, configuring multi-network nodes.Votes: 0GitHub stars: 31
- Release EngineeringBitcoin Core release engineering: Guix reproducible builds, signed release tarballs, deterministic outputs, code-signing keys, the release process, security disclosure. USE WHEN: building Bitcoin Core from source for verification, understanding release security, contributing to consensus-critical code.Votes: 0GitHub stars: 31
- Rest ApiBitcoin Core REST interface: read-only HTTP endpoints for blocks, txs, UTXOs, headers, mempool. No auth, no rate limit. Useful for high-throughput read services. USE WHEN: building read-only services that don't need RPC auth, fetching tx/block data efficiently, integrating with explorers.Votes: 0GitHub stars: 31
- RpcBitcoin Core JSON-RPC interface: authentication (cookie, rpcauth), wallet vs node RPCs, common verbs (getblockchaininfo, getrawtransaction, scantxoutset, importdescriptors, walletprocesspsbt, submitpackage, testmempoolaccept), error handling. USE WHEN: scripting bitcoind, integrating a service, debugging RPC errors.Votes: 0GitHub stars: 31
- ZmqZeroMQ notifications from Bitcoin Core: rawblock, rawtx, hashblock, hashtx, sequence. Subscribe over TCP/IPC, integration patterns for Electrs, BTCPay, Lightning nodes. USE WHEN: building real-time integrations with bitcoind, monitoring mempool sequence, integrating LN nodes.Votes: 0GitHub stars: 31
- Adaptor SigsAdaptor signatures: pre-signature paired with a "secret" such that publishing a valid signature reveals the secret, and vice versa. Foundational for atomic swaps, scriptless scripts, DLCs, Submarine Swaps trustless variants, PTLCs (Point Time-Locked Contracts). USE WHEN: designing atomic swaps, evaluating PTLCs vs HTLCs, building DLCs, understanding scriptless scripts.Votes: 0GitHub stars: 31
- Bip32BIP32 hierarchical deterministic key derivation: master key from seed, hardened vs unhardened derivation, xpub/xprv encoding, fingerprints, child-key chaining, key origin paths. USE WHEN: building HD wallets, deriving addresses, parsing xpubs, validating descriptors with key origin.Votes: 0GitHub stars: 31
- DlcsDiscreet Log Contracts: smart contracts on Bitcoin via oracle attestations + adaptor signatures. Oracle publishes nonces upfront, reveals signed outcomes; CETs (Contract Execution Transactions) enforce payouts. No on-chain footprint of the contract logic. USE WHEN: building betting / prediction markets, parametric insurance, derivatives, oracle-driven settlements on Bitcoin.Votes: 0GitHub stars: 31
- EcdsaECDSA signatures over secp256k1: sign/verify, deterministic-k (RFC6979), low-s (BIP146), DER encoding, malleability, recoverable signatures. USE WHEN: signing legacy/SegWit-v0 inputs, verifying legacy signatures, debugging "non-canonical signature" errors.Votes: 0GitHub stars: 31
- FrostFROST (Flexible Round-Optimised Schnorr Threshold): t-of-n threshold signing on secp256k1. n participants share a key via Distributed Key Generation (DKG) or trusted dealer; any t can produce a Schnorr signature. Differs from MuSig2 (which is n-of-n). USE WHEN: t-of-n threshold custody (e.g., 3-of-5 board signatures) with single-sig appearance on chain, federated services, multi-sig with availability.Votes: 0GitHub stars: 31
- Musig2MuSig2 (BIP327): two-round Schnorr key aggregation for n-of-n multisig. Aggregates n public keys into a single 32-byte x-only pubkey indistinguishable from a single-sig. Used in Taproot cooperative spends. Quick refs: protocol round-trip, key aggregation math, common attacks. USE WHEN: implementing n-of-n cooperative Taproot signing, designing Lightning Taproot channels, joint custody.Votes: 0GitHub stars: 31
- SchnorrBIP340 Schnorr signatures over secp256k1: sign/verify, x-only pubkeys, tagged hashes, batch verification, key tweaking. Building block for Taproot, MuSig2, FROST, adaptor signatures, DLCs. Quick refs: signing pseudocode, batch verification, common mistakes. USE WHEN: signing/verifying Taproot key-path or Tapscript spends, designing aggregation protocols, reading BIP340.Votes: 0GitHub stars: 31
- Secp256k1secp256k1 elliptic curve: parameters, group law, key encoding, point serialization, library bindings (libsecp256k1 in C, Rust, Python). USE WHEN: low-level key/point operations, debugging signature failures, understanding why Bitcoin uses this curve specifically.Votes: 0GitHub stars: 31
- Bitbox02BitBox02 and BitBox02 Nova (Shift Crypto, Switzerland): Multi Edition (BTC + altcoins), Bitcoin-Only Edition. BitBoxApp, dual-chip secure element, USB-C; Nova adds an EAL6+ secure chip and Bluetooth LE for iPhone/iPad. USE WHEN: integrating with BitBox02, evaluating European HW options.Votes: 0GitHub stars: 31
- ColdcardColdcard hardware wallets (Coinkite): Mk4, Mk5, Q. Bitcoin-only firmware, airgap support via SD card / NFC / QR, BIP85, MuSig2 (Edge firmware), Trick PINs, and the July 2026 seed-entropy advisory. USE WHEN: integrating with Coldcard, supporting Mk4 / Mk5 / Q, designing airgap signing flows, assessing whether a seed was generated by affected firmware.Votes: 0GitHub stars: 31
- HwiHWI (Hardware Wallet Interface): standardized Python API across HW vendors (Trezor, Ledger, Coldcard, BitBox02, Jade, etc.). Used by Bitcoin Core, Sparrow, Specter for cross-vendor signing. USE WHEN: integrating multi-vendor HW signing, building wallets that support several HW.Votes: 0GitHub stars: 31
- JadeBlockstream Jade: open-source HW wallet. Optional offline mode via QR, or SD / USB on Jade Plus. Liquid + Bitcoin support, "Pinserver" online mode for blind signing. USE WHEN: integrating with Jade, supporting Liquid + Bitcoin signing.Votes: 0GitHub stars: 31
- KeystoneKeystone 3 Pro: airgap HW wallet with QR + microSD, color touchscreen, multi-currency support, fingerprint auth. USE WHEN: integrating Keystone, evaluating mid-priced HW options.Votes: 0GitHub stars: 31
- KruxKrux: DIY airgap signer running on Sipeed M5StickV / Maix Amigo. Open-source, multi-language, stateless. USE WHEN: integrating Krux, evaluating M5StickV-based signers.Votes: 0GitHub stars: 31
- LedgerLedger hardware wallets: Stax, Flex, Nano Gen5, Nano X, Nano S Plus. BOLOS app architecture, Ledger Wallet (formerly Ledger Live), secure element, anti-klepto. USE WHEN: integrating with Ledger, supporting Ledger in app, debugging PSBT signing or HW Recovery service issues.Votes: 0GitHub stars: 31
- Multi Vendor MultisigMulti-vendor multisig: combining HW wallets from different vendors (Trezor + Ledger + Coldcard) for diversification. Coordinator-mediated setup, descriptor sharing, threat model. USE WHEN: designing multi-vendor custody, implementing 2-of-3 multisig with diverse hardware.Votes: 0GitHub stars: 31