sdlc-ai-workflow

SDK development, external developer communication, code samples, API client libraries, community engagement, and developer experience. Use when creating SDKs, writing external guides, creating code samples, or improving developer experience.

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

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

WCAG 2.1 AA compliance, keyboard navigation, screen reader testing, semantic HTML, ARIA labels, color contrast, assistive technology validation. Use when ensuring accessibility, conducting a11y audits, testing with screen readers, or designing inclusive interfaces.

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.

Hermetic builds, dependency management, build caching, reproducible builds, cross-compilation, build optimization. Use when optimizing build speed, ensuring reproducibility, or designing build infrastructure.

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.

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.

Incident response, postmortem facilitation, root cause analysis (RCA), blameless culture, incident timeline documentation, and incident classification. Use when responding to production incidents, writing incident reports, facilitating postmortems, or improving incident response processes.

Design docs, RFC (Request for Comments) process, ADR (Architecture Decision Records), code comments (WHY not WHAT), documentation structure, knowledge discovery and search, cross-team communication. Use when documenting decisions, writing design docs, or improving knowledge sharing.

Internationalization (i18n) and localization (l10n) strategy, string externalization, plural and gender handling, right-to-left text support, cultural adaptation, translation workflow, locale-specific testing. Use when adding multi-language support, managing translations, or expanding to new locales.

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.

Retrospectives (blameless, action items), team health metrics (sentiment, velocity), psychological safety and trust, mentoring and career growth, diversity and inclusion, on-call burden and burnout prevention, team dynamics. Use when facilitating retrospectives, planning team growth, or improving team health.

Release planning and scheduling, semantic versioning (semver), rollout strategies (canary, blue-green, gradual), changelog generation, rollback procedures, production validation. Use when planning releases, creating rollout strategies, or managing version bumps.

Tech debt inventory, paydown strategy, prioritization (Critical/High/Medium/Low), deprecation planning, communicating to stakeholders, refactoring initiatives. Use when managing technical debt, planning paydown, or assessing refactoring ROI.

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".

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".

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".

Use when the user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Ultra-compressed communication: 75% token reduction, full technical accuracy, no filler.

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 the user mentions keywords related to code-review.

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

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

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

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".

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

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.

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