tamasbege
UserClaude Code plugin marketplace for the hard, production-critical parts of engineering — backend reliability (API contracts, idempotency, rate limiting, resilience, caching, auth), adversarial code review, and frontend motion/UX.
Categories
Indexed Skills (12)
api-response-normalizer
Design a normalized API response contract so every endpoint returns a predictable shape for success, errors, validation failures, and collections. Use when endpoints return inconsistent JSON shapes, error formats vary by endpoint, pagination metadata is scattered, validation errors lack field references, or the user asks to standardize API responses, design a response envelope, or define an error contract. Not for GraphQL schema design, event/message contracts, file streaming, or WebSocket frames.
auth-flow-architect
Design authentication and authorization architectures - OAuth2/OIDC flow selection, JWT vs opaque tokens, refresh token rotation with reuse detection, session management and revocation, token storage rules per client type (SPA, mobile, server, M2M), the BFF pattern, RBAC/scopes/permissions modeling, and multi-tenant claims. Use when building or reviewing login/auth for an app, choosing between sessions and JWTs, integrating an identity provider (Auth0, Keycloak, Entra ID, Cognito), securing an SPA or mobile app, designing API-to-API auth, fixing token expiry/refresh bugs, or when the user asks how to do auth properly.
blindspot-finder
Adversarial code review that finds the self-review blind spot by forcing four hostile perspective shifts before rendering a verdict. Use when reviewing a diff or PR before merge, when a review feels like it's about to be a rubber stamp, when Claude just said "looks good" and a second, harsher opinion is wanted, or after a long session where fatigue may be hiding bugs. Covers correctness/robustness, maintainability, security, and production operability (logging, alerting, rollback safety) — the last of which most adversarial reviewers skip.
caching-strategy-architect
Design caching architectures that are fast AND correct - cache placement (in-process, distributed, CDN), pattern selection (cache-aside, read-through, write-through, write-behind), TTL and invalidation strategy, stampede protection, and consistency guarantees. Use when database load is too high, latency needs cutting, the same data is fetched repeatedly, users see stale data after updates, cache and database disagree, a cache expiry causes load spikes (thundering herd), or the user asks where or how to add caching or fix cache invalidation.
cold-start-optimizer
Produce a tailored cold-start and first-load performance optimization plan for frontend apps (bundle size, FCP/LCP, code splitting, caching) and backend/serverless services (JVM startup, AWS Lambda / Azure Functions cold starts, container boot). Use when the user reports a slow first load, poor Lighthouse or Core Web Vitals scores, large JS bundles, serverless cold starts, slow Spring Boot startup, or asks how to make an app start or load faster.
event-pipeline-architect
Design production-grade event-driven pipelines with implementation-ready depth - event catalogs, payload schemas, producers and consumers with the outbox pattern, retries, DLQs, idempotency, schema evolution, scaling, observability, and infrastructure-as-code. Use when adding async processing between services, decoupling producers from consumers, migrating from synchronous to event-driven communication, designing Kafka / Azure Service Bus / AWS SQS-SNS / RabbitMQ / Pub-Sub topologies, or redesigning retry and failure handling for existing events.
expressive-motion-architect
Design bold, expressive interaction and motion systems for products — spring-physics choreography, shape morphing between states, dynamic color moments, and emphasized typography compositions — implemented across Compose, Flutter, and the web (where Material's own Expressive spec explicitly has no implementation). Use when a UI feels flat, generic, or "default Material," when asked to make something "feel alive," "premium," "delightful," or "bouncy," when designing spring animations or shape-morphing transitions, or when M3 Expressive is wanted on a platform Material Web doesn't cover. Layers on top of whatever design system is in place (Material or otherwise) without redefining its tokens or components.
idempotency-builder
Design and deliver a complete idempotency system so critical actions are safe to retry - key design, request fingerprinting, atomic locking, partial-failure recovery, payment provider coordination (Stripe, Adyen, PayPal), saga idempotency, and monitoring. Use when protecting payments, orders, or webhooks from duplicate execution, handling at-least-once message delivery, double-click or client-retry bugs, duplicate webhook processing, overlapping cron jobs, or when the user asks to make an endpoint idempotent or prevent duplicate charges and records.
rate-limiter-designer
Design and implement rate limiting and quota systems - algorithm selection (token bucket, sliding window, GCRA), distributed enforcement with Redis, per-tenant and per-endpoint limits, 429 response contracts with standard headers, and outbound limiting against third-party APIs. Use when an API needs throttling or quotas, endpoints are being hammered by clients or scrapers, one tenant is starving others (noisy neighbor), login or signup needs brute-force protection, or the system must respect a third-party provider's rate limits without getting banned.
resilience-strategist
Design failure-handling for service dependencies - timeout budgets, retries with backoff and jitter, retry budgets, circuit breakers, bulkheads, fallbacks, and load shedding. Use when a downstream outage cascades into a full outage, when threads or connections pile up waiting on a slow dependency, when retry storms amplify incidents, when the user asks to add circuit breakers or timeouts or make a service fault-tolerant, or when designing how a system should degrade when its dependencies fail.
ux-reviewer
Adversarial, persona-driven usability review of an existing UI or flow — a live URL, screenshots, a Figma link, or a described user flow — reviewed through four user archetypes plus Nielsen's usability heuristics to surface friction, confusion, and accessibility gaps before they ship. Use when reviewing a design or flow before dev handoff, auditing a shipped screen for usability problems, or asked to "review the UX," "critique this flow," or "find usability issues." This is a critique gate against a design that already exists — not generative user research (personas or journey maps built from real user data), which is discovery work outside this skill's scope.
blind-spot-breaker
Adversarial code review that breaks the self-review blind spot by forcing four hostile perspective shifts before rendering a verdict. Use when reviewing a diff or PR before merge, when a review feels like it's about to be a rubber stamp, when Claude just said "looks good" and a second, harsher opinion is wanted, or after a long session where fatigue may be hiding bugs. Covers correctness/robustness, maintainability, security, and production operability (logging, alerting, rollback safety) — the last of which most adversarial reviewers skip.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.