Claude Skills by saitarrun

REST/gRPC API design, versioning strategies, error codes, request/response contracts, backward compatibility, rate limiting, OpenAPI specifications. Use when designing APIs, defining contracts, planning versioning, or ensuring API consistency.

This skill should be used when the user asks to "design a system", "architecture", "ADR", "system design", "tech stack", "choose between approaches", "coupling", "service granularity", "blueprint", "component design", "API contract", "schema design", "trade-offs", or discusses "monolith", "microservices", "fitness functions", or architectural decisions.

This skill should be used when the user mentions keywords related to cicd.

This skill should be used when the user mentions keywords related to cloud-infra.

This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.

This skill should be used when the user mentions keywords related to code-review.

This skill should be used when the user mentions keywords related to code-standards.

Deep structural codebase comprehension, AST dependency graph traversal, symbol caller/callee tracing, and monorepo navigation strategies for massive codebases.

Secrets management, environment-specific configs, safe defaults, feature flags, configuration-as-code, compliance and audit trails. Use when managing secrets, configuring deployments, or implementing feature flags.

Consumer-driven contract testing, OpenAPI spec drift validation, and breaking API change detection for microservices.

Version updates (major/minor/patch), security patch application, transitive dependency resolution, monorepo dependency management, deprecation tracking, license compliance. Use when updating dependencies, managing versions, or addressing CVEs.

This skill should be used when the user mentions keywords related to documentation.

Autonomous intent detection, dynamic agent spawning, capability-flag auto-resolution, and contextual skill injection based on task requirements.

Enterprise architecture patterns, multi-tenancy isolation, disaster recovery (RTO/RPO), data residency, and audit logging standards.

Comprehensive testing matrix spanning Unit, Integration, E2E (Playwright), Contract (Pact), Chaos/Fault-Injection, Mutation, Load/Stress (k6), and Security Fuzz testing.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me", "stress test", "poke holes", "challenge my plan".

Extract explicit and latent user goals, resolve ambiguous requests, detect unstated business constraints, and map natural language intents to concrete engineering execution paths.

Industrial legacy code modernization, strangler fig migration, monolith decoupling, schema evolution without downtime, and reverse-engineering undocumented codebases.

Architecture standards, evaluation metrics, cost budget controls, and security guardrails for LLM, RAG, and Agentic features.

Metrics, logging, distributed tracing, dashboards, alerting, SLO-driven observability, post-incident analysis. Use when designing monitoring, setting up dashboards, creating alert rules, or analyzing production data.

This skill should be used when the user mentions keywords related to ops-sre.

Profile systems, identify bottlenecks, optimize code and infrastructure for speed, throughput, and resource efficiency.

Browser automation and end-to-end testing with Playwright. Use when building/testing frontends, automating user workflows, taking screenshots, validating UI state, filling forms, testing across browsers, or mentions "playwright", "E2E test", "browser automation", "screenshot".

Comprehensive code review for pull requests using parallel multi-agent analysis. Audits CLAUDE.md compliance, checks for bugs, analyzes git history, reviews comments, and filters by confidence score. Use when reviewing a GitHub PR, mentions "code review", "review this PR", or "/code-review".

Self-diagnosing, self-correcting agent loop for Build phase. Defines DoD checking, inner/outer loop retry logic, circuit breakers, and sentinel health checks.

This skill should be used when the user asks to "write requirements", "create user stories", "define acceptance criteria", "decompose a feature", "analyze an issue", "write a PRD", "create user stories", "acceptance criteria", "roadmap", "feature spec", or discusses "INVEST" criteria, "ambiguity", or "story estimation".

Hyper-scale root cause analysis (RCA), bisection, call-tree backtracking, and automated surgical remediation across massive million-file enterprise repositories.

This skill should be used when the user mentions keywords related to security-audit.

Automated security vulnerability remediation, CVE patching, cryptographic hardening, Zero-Trust protocol implementation, and compliance upgrades.

End-to-end founder playbook, product-market fit (PMF) telemetry, SaaS monetization, churn analysis, growth loops, and investor-ready unit economics (CAC, LTV, MRR).

This skill should be used when the user mentions keywords related to testing.

This skill should be used when the user mentions keywords related to threat-modeling.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Token conservation economics, bounded context-window pruning, AST structural query optimization, and high-precision prompt budget discipline.

This skill should be used when the user mentions keywords related to ux-design.

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.