All authors
Claude Skills by claude-dev-suite
github.com/claude-dev-suite740 skills14 installs1,174 views
- Decision Model CalibrationTurning a model's class probabilities into numbers you can set a threshold on: building the labelled corpus, measuring accuracy and calibration honestly (ECE with a noise floor, Brier, risk–coverage), fitting temperature/Platt, removing option-order bias, conformal prediction sets, and choosing per-action thresholds. Applies to Jev and any typed classifier with probabilities, and says which LLM providers expose logprobs at all. USE WHEN: user asks whether a confidence/probability can be trus...Votes: 0GitHub stars: 40
- Typed Decision ModelsReplacing an LLM used as a classifier with a model that returns typed decisions and probabilities instead of prose — TypeSafe's Jev and the wider pattern. Covers the three primitives, the decomposition that makes them work, what `confidence` does and does not mean, and the independently measured evidence on where the vendor's claims hold. USE WHEN: user mentions "Jev", "TypeSafe AI", "System One model", "typed decision model", "decision model", "calibrated probabilities", "classifier instead...Votes: 0GitHub stars: 40
- Typesafe JevBuilding against TypeSafe's Jev: the /v1/systemone HTTP API, the Python (`typesafe-sdk`) and JS (`@typesafe-ai/sdk`) SDKs, Noul/Choice/Score request and answer shapes, model ids and pinning, limits, pricing, retries, errors, gateways, and the framework integrations (Pydantic AI `TypeSafeModel`, LangChain `TypeSafeClassifier`, Vercel AI SDK, OpenRouter, LiteLLM, DSPy). USE WHEN: code imports `typesafe_sdk`, `@typesafe-ai/sdk`, `langchain_typesafe`, `@ai-sdk/typesafe-ai`, or uses `typesafe:jev...Votes: 0GitHub stars: 40
- ISSUE TEMPLATEName, and a link to its official docs.Votes: 0GitHub stars: 33
- Core DaoCore (Core DAO): EVM sidechain whose Satoshi Plus consensus elects validators from delegated Bitcoin hash power, delegated CORE stake and non-custodial CLTV-timelocked BTC stake. Chain ID 1116, 3s blocks, 24h election rounds. Latest client v1.0.26 (2 Sept 2026); CoreRewardFix hard fork activated 3 Sept 2026. USE WHEN: building on Core, implementing non-custodial BTC staking or hash-power delegation, evaluating BTCFi yield venues.Votes: 0GitHub stars: 33
- Fractal BitcoinFractal Bitcoin: a Bitcoin Core-derived scaling chain with ~30s blocks and Cadence Mining (part merge-mined with Bitcoin, part permissionless, part Index Mining since FIP-101). Mainnet 9 Sept 2024. FIP-102 / fractald v0.4.0 hard-forked at block 2,100,000, combining the first and second FB halvings; the chain passed that height before 15 September 2026. USE WHEN: building on Fractal, indexing BRC-20 on Fractal, reasoning about merge-mined Bitcoin-derived chains.Votes: 0GitHub stars: 33
- LombardLombard: LBTC, a cross-chain yield-bearing wrapped BTC issued by a 10-of-14 institutional notary consortium running a Cosmos appchain (the Lombard Ledger), with HSM key custody (CubeSigner) and an independent Bascule verification layer. LBTC yield moved OFF Babylon staking to a Bitwise covered-call strategy in 2026. USE WHEN: integrating LBTC, threat-modelling consortium-issued wrapped BTC, evaluating BTC "liquid staking" yield claims.Votes: 0GitHub stars: 33
- MezoMezo: Thesis's Bitcoin-first Cosmos SDK / CometBFT chain with EVM (Evmos fork), BTC for gas, tBTC bridging and a Proof-of-Authority validator set. Mainnet 28 May 2025. MUSD is its Bitcoin-backed CDP stablecoin, a Threshold USD / Liquity fork with a 110% minimum collateral ratio. Chain TVL ~$71.7M on 15 September 2026. USE WHEN: building on Mezo, integrating MUSD, evaluating a major downstream consumer of tBTC.Votes: 0GitHub stars: 33
- SolvSolv Protocol: SolvBTC / xSolvBTC tokenized Bitcoin distributed across many chains, custody behind Safe multisigs with a Vault Guardian and FROST signing partners. Migrated bridging from LayerZero to Chainlink CCIP on 7 May 2026. BRO Vault incident, 5 March 2026: 38.0474 SolvBTC (~$2.7M), fully compensated. USE WHEN: integrating SolvBTC, threat-modelling multi-chain wrapped BTC, reviewing BTCFi custody incidents.Votes: 0GitHub stars: 33
- Bitcoin Kernellibbitcoinkernel: Bitcoin Core's experimental C library exposing the validation engine (block/header validation, block index traversal, block + undo reads, script verification), and the `bitcoinkernel` Rust bindings over `libbitcoinkernel-sys`. USE WHEN: embedding Core's exact consensus semantics in a non-C++ process - indexers, explorers, validation tooling, fuzzing harnesses.Votes: 0GitHub stars: 33
- Corepccorepc: the rust-bitcoin org's Bitcoin Core JSON-RPC stack. `corepc-types` (per-Core-version response types + version-agnostic `model` types), `corepc-client` (blocking/async test client), `bitcoind` (spin up regtest nodes for integration tests). USE WHEN: talking to bitcoind from Rust, or integration-testing Rust code against a real Bitcoin Core binary.Votes: 0GitHub stars: 33
- TestnetPublic mined test networks: testnet3 (deprecated), testnet4 (BIP94) and the testnet5 draft (BIP95). Chain selection, the 20-minute difficulty exception, block storms, and when to prefer signet. USE WHEN: picking a public test network, debugging testnet4 block behaviour, or tracking the testnet5 migration.Votes: 0GitHub stars: 33
- Axe Coreaxe-core - accessibility testing engine for automated WCAG compliance checks. USE WHEN: user mentions "axe", "automated accessibility testing", "a11y tests", asks about "integrating accessibility checks", "CI/CD accessibility", "Playwright accessibility", "Jest accessibility", "Vitest axe" DO NOT USE FOR: manual accessibility audits - use `wcag` skill insteadVotes: 0GitHub stars: 31
- WcagWCAG 2.2 Web Content Accessibility Guidelines. Covers conformance levels A/AA/AAA, success criteria, testing with axe-core, and common accessibility patterns. USE WHEN: user mentions "accessibility", "a11y", "WCAG", "screen reader", "ARIA", asks about "color contrast", "keyboard navigation", "accessible forms", "compliance", "ADA", "Section 508" DO NOT USE FOR: automated testing implementation - use `axe-core` insteadVotes: 0GitHub stars: 31
- Anthropic PythonAnthropic Python SDK for Claude API integration. Covers messages API, streaming, tool use, vision, error handling, and best practices. Use when building Python applications that call the Claude API. USE WHEN: user mentions "anthropic", "claude api", "anthropic sdk", "anthropic.Anthropic()", "client.messages.create", "claude-opus", "claude-sonnet", "tool_use", "streaming claude", "claude python" DO NOT USE FOR: OpenAI API, other LLM providers, JavaScript/TypeScript Anthropic SDKVotes: 0GitHub stars: 31
- LangchainLangChain framework for LLM application development. Covers chains, agents, tools, RAG pipelines, vector stores, memory, and LangChain Expression Language (LCEL). Python and TypeScript/JavaScript. USE WHEN: user mentions "langchain", "LLM chain", "AI agent", "LCEL", "retrieval chain", "LangChain tools", "LangSmith", "LangGraph" DO NOT USE FOR: direct API calls without framework - use Claude/OpenAI SDK; vector database specifics - use `vector-databases`; RAG architecture patterns - use `rag-...Votes: 0GitHub stars: 31
- Rag PatternsRetrieval-Augmented Generation architecture patterns. Chunking strategies, retrieval pipelines, re-ranking, hybrid search, evaluation, and production RAG system design. USE WHEN: user mentions "RAG", "retrieval augmented generation", "document Q&A", "knowledge base chatbot", "semantic search pipeline", "chunking strategy" DO NOT USE FOR: vector database specifics - use `vector-databases`; LangChain implementation - use `langchain`; direct LLM API calls - use Claude/OpenAI SDK skillsVotes: 0GitHub stars: 31
- Vector DatabasesVector database integration for embeddings and similarity search. Pinecone, Weaviate, Qdrant, ChromaDB, pgvector. Index management, metadata filtering, hybrid search, and production optimization. USE WHEN: user mentions "vector database", "embeddings", "similarity search", "Pinecone", "Weaviate", "Qdrant", "ChromaDB", "pgvector", "HNSW", "ANN" DO NOT USE FOR: LangChain integration - use `langchain`; RAG architecture - use `rag-patterns`; traditional databases - use database skillsVotes: 0GitHub stars: 31
- Agentic ArchitectureArchitecture of LLM agent systems: orchestration topologies (single agent, supervisor/sub-agents, pipelines, networks), memory/context strategy, the tool layer, and human-in-the-loop/control. Architect-level system design, not prompt wording. USE WHEN: designing agentic/LLM-agent systems, "agent orchestration", "multi-agent", "supervisor", "sub-agents", "tool use", "agent memory", "human-in-the-loop", workflow vs autonomous agent, agent topology/control. DO NOT USE FOR: single prompt/RAG re...Votes: 0GitHub stars: 31
- Ai Hardware SelectionSelecting accelerators for AI workloads: GPU vs TPU vs NPU vs FPGA vs CPU, and the metrics that actually decide it — memory capacity & bandwidth, TOPS/ FLOPS, interconnect, and cost/Watt. Architect-level hardware-fit reasoning. USE WHEN: choosing AI hardware/accelerators, "which GPU", "TPU vs GPU", "NPU", "FPGA", "HBM/memory bandwidth", "TOPS", "cost per token", VRAM sizing for a model, training vs inference hardware, accelerator interconnect. DO NOT USE FOR: serving software topology (use ...Votes: 0GitHub stars: 31
- Edge InferenceEdge / on-device AI inference architecture: running models on MCUs, NPUs, mobile, and mini-PCs; quantization for edge, TOPS/memory/energy budgets, TinyML, and the latency case for on-device vs cloud. Architect-level. USE WHEN: designing on-device/edge AI, "edge inference", "on-device", "NPU", "TinyML", "quantization", "Jetson", "Coral", "Hailo", local LLM on small hardware, offline/low-latency inference, energy-constrained ML. DO NOT USE FOR: cloud GPU serving (use `inference-serving-topolo...Votes: 0GitHub stars: 31
- Hybrid Edge CloudHybrid edge-cloud AI architecture: local-first inference with cloud escalation, model cascading, and splitting the workload across device and datacenter to balance latency, cost, privacy, and quality. Architect-level topology. USE WHEN: designing systems that combine on-device and cloud AI, "local-first", "cloud fallback", "model cascade", "escalation", "hybrid inference", routing by confidence/complexity, edge+cloud trade-offs. DO NOT USE FOR: pure on-device (use `edge-inference`); pure cl...Votes: 0GitHub stars: 31
- Inference Serving TopologyLLM/model inference serving architecture: the engine → serving → orchestration layering (vLLM/SGLang/TensorRT-LLM, Triton, KServe/Ray Serve), KV-cache & continuous batching, prefill-decode disaggregation, and scaling. Architect-level topology, not model training. USE WHEN: designing model/LLM serving infra, "vLLM", "SGLang", "TensorRT-LLM", "Triton", "KServe", "Ray Serve", "continuous batching", "KV cache", "prefill decode", "TTFT", multi-GPU/multi-model serving, inference autoscaling. DO N...Votes: 0GitHub stars: 31
- Model Gateway RoutingModel gateway / LLM router architecture: a control point in front of multiple models/providers for routing (cost/quality/latency), fallback, rate limiting, caching, observability, and governance. Architect-level, multi-provider. USE WHEN: designing an LLM gateway/router, "model router", "LLM gateway", "multi-provider", "fallback", "cost routing", "LiteLLM", "Envoy AI Gateway", semantic cache, central key/quota/observability for LLM calls. DO NOT USE FOR: single-engine serving (use `inferenc...Votes: 0GitHub stars: 31
- Framer MotionFramer Motion animation library for React. Declarative, physics-based and gesture-aware: variants and orchestration, AnimatePresence, FLIP layout animation, scroll-linked motion, spring configuration and gestures. USE WHEN: user mentions "Framer Motion", "motion.div", "AnimatePresence", "variants", "layout animation", "spring animation", asks about animating a React component, exit animations, drag or gesture handling DO NOT USE FOR: timeline-based or non-React animation (use `gsap`), SVG-s...Votes: 0GitHub stars: 31
- GsapGSAP (GreenSock Animation Platform) — high-performance JavaScript animation engine with a plugin ecosystem. Covers tweens, easing, timelines, ScrollTrigger and the useGSAP React hook. USE WHEN: user mentions "GSAP", "GreenSock", "ScrollTrigger", "useGSAP", "timeline animation", "tween", asks about scroll-driven sequences or complex animation choreography DO NOT USE FOR: React-idiomatic declarative animation (use `framer-motion`), SVG path morphing basics (use `svg-animation`), 3D scenes (us...Votes: 0GitHub stars: 31
- GraphqlGraphQL API design. Covers schema, queries, mutations, and resolvers. Use when building or consuming GraphQL APIs. USE WHEN: user mentions "GraphQL", "schema definition", "resolvers", "mutations", "queries", "DataLoader", "N+1 problem", asks about "how to design GraphQL API", "GraphQL schema", "GraphQL authentication", "GraphQL pagination", "Apollo Server" DO NOT USE FOR: REST APIs - use `rest-api` instead; tRPC - use `trpc` instead; GraphQL code generation - use `graphql-codegen` insteadVotes: 0GitHub stars: 31
- GrpcgRPC service development. Protocol Buffers (protobuf), service definitions, streaming (unary, server, client, bidirectional), interceptors, and code generation for Node.js, Go, Java, and Python. USE WHEN: user mentions "gRPC", "protobuf", "Protocol Buffers", ".proto", "grpc-js", "tonic", "grpc-java", "service mesh RPC" DO NOT USE FOR: REST APIs - use `rest-api`; GraphQL - use `graphql`; WebSocket - use real-time skillsVotes: 0GitHub stars: 31
- OpenapiOpenAPI/Swagger specification. Covers schema definition, paths, and documentation. Use for API documentation. USE WHEN: user mentions "OpenAPI", "Swagger", "API spec", "API documentation", "schema definition", "OpenAPI 3.0", "Swagger UI", asks about "how to write OpenAPI spec", "document REST API", "API contract", "schema validation" DO NOT USE FOR: GraphQL schemas - use `graphql` instead; tRPC - use `trpc` instead; Generating clients from OpenAPI - use `openapi-codegen` instead; Spring Boo...Votes: 0GitHub stars: 31
- PaginationAPI pagination patterns. Offset-based, cursor-based, keyset pagination. Filtering, sorting, and page metadata. REST and GraphQL pagination implementations. USE WHEN: user mentions "pagination", "paginate", "cursor", "offset", "page size", "next page", "infinite scroll API", "list endpoint" DO NOT USE FOR: frontend infinite scroll UI - use frontend framework skills; database query optimization - use database skillsVotes: 0GitHub stars: 31
- Rest ApiREST API design principles. Covers resources, methods, and status codes. Use when designing or reviewing REST APIs. USE WHEN: user mentions "REST API", "RESTful", "HTTP methods", "status codes", "resource naming", "API endpoints", "pagination", "versioning", asks about "how to design REST API", "REST best practices", "API documentation", "HTTP verbs" DO NOT USE FOR: GraphQL APIs - use `graphql` instead; tRPC - use `trpc` instead; OpenAPI specs - use `openapi` instead; Spring Boot REST - com...Votes: 0GitHub stars: 31
- Springdoc OpenapiSpringdoc OpenAPI for API documentation in Spring Boot. Covers Swagger UI configuration, annotations, schema customization, and security documentation. Based on production patterns from castellino and gestionale-presenze projects. USE WHEN: user mentions "Springdoc", "Spring Boot OpenAPI", "Swagger in Spring", "@Operation", "@Schema", "Swagger UI Spring", asks about "Spring Boot API documentation", "Spring REST documentation", "OpenAPI in Java" DO NOT USE FOR: General OpenAPI specs - use `o...Votes: 0GitHub stars: 31
- Swagger DotnetSwashbuckle and NSwag for ASP.NET Core API documentation. Covers XML comments, operation filters, and OpenAPI customization. USE WHEN: user mentions "Swagger", "Swashbuckle", "NSwag", ".NET OpenAPI", "API documentation", "Swagger UI", ".NET API docs" DO NOT USE FOR: Springdoc OpenAPI - use `springdoc-openapi`, generic OpenAPI spec - use `openapi`Votes: 0GitHub stars: 31
- TrpctRPC for type-safe APIs. Covers routers, procedures, and React Query integration. Use for end-to-end type-safe APIs. USE WHEN: user mentions "tRPC", "type-safe API", "end-to-end types", "procedures", "tRPC router", "tRPC React Query", asks about "how to build type-safe API", "tRPC with Next.js", "tRPC middleware", "tRPC context" DO NOT USE FOR: REST APIs - use `rest-api` instead; GraphQL - use `graphql` instead; OpenAPI specs - use `openapi` instead; Non-TypeScript projectsVotes: 0GitHub stars: 31
- WebhooksWebhook patterns for sending and receiving. Signature verification, retry logic, idempotency, payload design, and webhook infrastructure. Covers Stripe, GitHub, Slack webhook consumption and custom webhook dispatch. USE WHEN: user mentions "webhook", "webhook endpoint", "webhook signature", "event callback", "HTTP callback", "webhook retry", "webhook dispatch" DO NOT USE FOR: WebSocket real-time - use `socket-io` or `sse`; message queues - use messaging skillsVotes: 0GitHub stars: 31
- AxiosAxios - promise-based HTTP client for browser and Node.js USE WHEN: user mentions "Axios", "HTTP requests", "API calls", "interceptors", "Axios instance", asks about "how to make HTTP calls", "configure Axios", "add auth header", "handle HTTP errors" DO NOT USE FOR: Fetch API - use `http-clients` instead; ky/ofetch - use `http-clients` instead; GraphQL clients - use `graphql-codegen` instead; tRPC - use `trpc` insteadVotes: 0GitHub stars: 31
- Graphql CodegenGraphQL Code Generator for TypeScript. Generates typed operations, hooks, and document nodes from GraphQL schemas. Use for type-safe GraphQL in frontend. USE WHEN: user mentions "GraphQL Codegen", "generate GraphQL types", "GraphQL TypeScript", "typed GraphQL", "client preset", "React Query GraphQL", asks about "GraphQL code generation", "type-safe GraphQL client", "fragment masking" DO NOT USE FOR: REST API types - use `openapi-codegen` instead; tRPC - use `trpc` instead; GraphQL schema de...Votes: 0GitHub stars: 31
- Http ClientsHTTP clients for frontend and Node.js. Covers Axios, Fetch API, ky, and ofetch. Includes interceptors, error handling, retry logic, and auth token management. Use for configuring API clients and HTTP communication. USE WHEN: user mentions "HTTP client", "Fetch API", "ky", "ofetch", "HTTP wrapper", "retry logic", "token refresh", asks about "which HTTP client to use", "HTTP request library", "API client setup", "request interceptors" DO NOT USE FOR: Axios-specific questions - use `axios` ins...Votes: 0GitHub stars: 31
- Openapi CodegenOpenAPI client code generation. Covers openapi-typescript, openapi-generator-cli, swagger-typescript-api, and trpc-openapi. Use for generating type-safe API clients. USE WHEN: user mentions "OpenAPI codegen", "generate API client", "openapi-typescript", "swagger-typescript-api", "openapi-generator", asks about "generate types from OpenAPI", "type-safe API client", "OpenAPI client generation" DO NOT USE FOR: Writing OpenAPI specs - use `openapi` instead; GraphQL codegen - use `graphql-codege...Votes: 0GitHub stars: 31
- Openapi GeneratorOpenAPI Generator - generate clients and servers from OpenAPI specs USE WHEN: user mentions "OpenAPI Generator CLI", "generate Java client", "generate Spring server", "openapi-generator-cli", "openapi-generator-maven-plugin", asks about "generate server from OpenAPI", "OpenAPI Generator templates" DO NOT USE FOR: TypeScript-only generation - use `openapi-codegen` instead; Writing OpenAPI specs - use `openapi` instead; GraphQL - use `graphql-codegen` insteadVotes: 0GitHub stars: 31
- Type Safe ApiEnd-to-end type safety patterns for API development. Covers Zod-to-OpenAPI, ts-rest, Zodios, and contract testing. Use for ensuring type consistency between backend and frontend. USE WHEN: user mentions "type-safe API", "end-to-end types", "Zod to OpenAPI", "ts-rest", "Zodios", "contract testing", asks about "share types between frontend and backend", "type safety across API", "API contract", "Pact testing" DO NOT USE FOR: tRPC (use `trpc` instead); GraphQL (use `graphql` instead); Simple O...Votes: 0GitHub stars: 31
- DddDomain-Driven Design patterns. Bounded contexts, aggregates, entities, value objects, domain events, repositories, and application services. Strategic and tactical DDD for complex business domains. USE WHEN: user mentions "DDD", "Domain-Driven Design", "bounded context", "aggregate", "value object", "domain event", "ubiquitous language", "aggregate root", "domain service" DO NOT USE FOR: database schema design - use database skills; CQRS/Event Sourcing specifics - use `event-sourcing-cqrs`Votes: 0GitHub stars: 31
- Event Sourcing CqrsEvent Sourcing and CQRS patterns. Event stores, projections, snapshots, command handlers, query models, and eventual consistency. Covers EventStoreDB, Axon Framework, and custom implementations. USE WHEN: user mentions "event sourcing", "CQRS", "event store", "projection", "command handler", "read model", "write model", "EventStoreDB", "Axon" DO NOT USE FOR: simple event-driven architecture - use `event-driven`; message brokers - use messaging skills; DDD basics - use `ddd`Votes: 0GitHub stars: 31
- MultitenancyMulti-tenant architecture patterns. Database-per-tenant, schema-per-tenant, shared-schema with tenant ID, row-level security, tenant resolution, and data isolation. USE WHEN: user mentions "multi-tenant", "multitenancy", "SaaS architecture", "tenant isolation", "row-level security", "tenant ID", "subdomain routing" DO NOT USE FOR: general database design - use database skills; authentication - use auth skillsVotes: 0GitHub stars: 31
- JwtJSON Web Tokens for authentication. Covers token structure, signing, and validation. Use for stateless authentication. USE WHEN: user mentions "JWT", "token authentication", "access token", "refresh token", asks about "stateless auth", "token signing", "token validation" DO NOT USE FOR: session-based auth (use session management), OAuth flows (use oauth2 skill), NextAuth.js (use nextauth skill)Votes: 0GitHub stars: 31
- NextauthNextAuth.js authentication for Next.js. Covers providers, sessions, and callbacks. Use for Next.js authentication. USE WHEN: user mentions "NextAuth", "Next.js auth", "Auth.js", asks about "Next.js authentication", "App Router auth", "next-auth", "authentication providers" DO NOT USE FOR: generic OAuth (use oauth2 skill), JWT implementation (use jwt skill), non-Next.js projects, Express/Fastify authVotes: 0GitHub stars: 31
- Oauth2OAuth 2.0 authorization framework. Covers flows, tokens, and provider integration. Use for third-party authentication. USE WHEN: user mentions "OAuth", "Google login", "GitHub auth", "social login", "authorization code flow", "PKCE", asks about "third-party auth", "provider integration" DO NOT USE FOR: JWT tokens (use jwt skill), NextAuth.js (use nextauth skill), API keys, simple password authVotes: 0GitHub stars: 31
- WebauthnWebAuthn/FIDO2 passwordless authentication. Passkeys, registration and authentication ceremonies, SimpleWebAuthn library, resident credentials, and platform/cross-platform authenticators. USE WHEN: user mentions "WebAuthn", "FIDO2", "passkey", "passwordless", "biometric login", "security key", "fingerprint login", "SimpleWebAuthn" DO NOT USE FOR: password-based auth - use `jwt` or `oauth2`; magic links - different flow; OAuth social login - use `oauth2`Votes: 0GitHub stars: 31
- Actix WebActix-web Rust web framework. Covers routing, extractors, middleware, state management, and WebSocket. Use for high-performance Rust APIs. USE WHEN: user mentions "actix-web", "actix", "rust web framework", "rust api", asks about "rust async web", "actix middleware", "actix extractors", "rust websocket", "high performance rust api" DO NOT USE FOR: Axum projects - use `axum` instead, Rocket projects - use `rocket` instead, Warp projects - use `warp` instead, non-Rust backendsVotes: 0GitHub stars: 31
- Aspnet BlazorBlazor Server, WebAssembly, and United (Auto) with components, interop, and render modes. Covers .NET 8+ Blazor patterns. USE WHEN: user mentions "Blazor", "Blazor Server", "Blazor WASM", "Blazor WebAssembly", "Blazor components", "render modes", "Blazor interop" DO NOT USE FOR: Angular components - use `angular`, React components - use `react`, Svelte - use `svelte`Votes: 0GitHub stars: 31