kienbui1995
232 verified skills
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
development
accessibility-audit
Use when auditing WCAG compliance, testing with assistive technologies, or fixing accessibility issues
testing
accessibility-compliance
Use when implementing or reviewing accessibility - WCAG compliance, screen reader support, keyboard navigation, a11y testing
testing
add-analytics-instrumentation
End-to-end instrumentation workflow orchestrating diff-intake → discover-event-surfaces → instrument-events. Uses mcp__Amplitude__get_event_properties, mcp__Amplitude__get_project_context.
tools
ado-api-cli
Use when automating Azure DevOps operations — az devops CLI, REST API calls, PAT management, service principal automation, webhooks, and scripting repeatable ADO administrative tasks.
tools
ado-container-deployments
Use when implementing container CI/CD on Azure DevOps — Docker image builds with caching, pushing to Azure Container Registry, deploying to AKS with Helm or kubectl, and image promotion across environments.
development
ado-pipeline-design
Use when designing Azure Pipelines YAML — multi-stage pipelines, reusable templates, conditions and expressions, matrix strategies, triggers, and pipeline dependencies for complex CI/CD workflows.
testing
ado-pipeline-optimization
Use when improving Azure Pipelines performance — caching dependencies, parallel job strategies, artifact management between stages, test result publishing, code coverage gates, and reducing pipeline runtime.
development
ado-work-tracking
Use when configuring Azure DevOps work tracking — boards setup, backlog configuration, sprint management, work item type customization, process templates, queries, and team area/iteration paths.
development
agentic-ai-patterns
Use when designing AI agents - tool use, multi-agent orchestration, state management, planning loops, error recovery, and agent evaluation
tools
agentic-eval
Use when evaluating AI agent systems — trajectory evaluation, pass@k testing, tool call correctness, non-deterministic behavior testing, and building eval infrastructure specific to multi-step agentic workflows.
tools
ai-product-validation
Use when deciding whether to build an AI product — rapid problem validation, market discovery, early user interviews, and demand signals BEFORE writing any code. Prevents the
development
ai-safety-guardrails
Use when adding safety layers to AI features - output validation, hallucination detection, content filtering, PII redaction, input sanitization
testing
analytics-reporting
Use when building marketing dashboards, attribution models, or reporting on campaign performance
development
analyze-experiment
Comprehensive A/B test analysis with statistical validity, segment breakdown, and SHIP/ITERATE/ABANDON recommendation. Uses mcp__Amplitude__query_experiment, mcp__Amplitude__get_experiments.
tools
analyze-feedback
Synthesize customer feedback into themes, pain points, and prioritized product roadmap recommendations. Uses mcp__Amplitude__get_feedback_insights, mcp__Amplitude__get_feedback_comments, mcp__Amplitude__get_feedback_trends.
tools
api-design
Use when designing REST or GraphQL APIs - endpoint naming, versioning, error handling, pagination, authentication patterns
development
azure-monitor
Use when setting up Azure observability with Log Analytics, configuring metric and log alerts, integrating Application Insights for APM, routing diagnostic logs, or studying for AZ-400 or AZ-305.
devops
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
development
brand-voice
Use when defining tone of voice guidelines, ensuring messaging consistency, or onboarding writers to your brand
documentation
skills/cloud/gcp/bigquery-optimization
--- name: bigquery-optimization description: Use when designing BigQuery schemas, optimizing queries, managing partitioning/clustering, controlling costs, or studying for GCP Professional Data Engineer (GCP-PDE). Covers domains: Design data processing systems (~22%) and Store the data (~15-20%). --- # BigQuery Optimization ## When to Use - Designing tables for an analytics use case on GCP - Queries are slow or unexpectedly expensive - Planning partitioning/clustering strategy - Preparing for G
devops
blockchain-audit
Use when reviewing smart contracts for security vulnerabilities, auditing web3 patterns, or preparing for a formal audit
development
chrome-store-publishing
Publish and maintain Chrome extensions on the Chrome Web Store — packaging, store listing, screenshots, review process, and update management.
tools
ci-cd-pipeline
Use when setting up or improving CI/CD pipelines - GitHub Actions, automated testing, deployment, release automation
tools
claude-mcp-setup
Use when connecting Claude Code to external services via MCP (Model Context Protocol) — configuring MCP servers for databases, APIs, file systems, and custom tools, and designing effective tool descriptions for Claude.
tools
claude-md-authoring
Use when writing or improving CLAUDE.md files — project context that Claude Code reads every session, global vs project rules, what to include for maximum AI effectiveness, and memory-aware documentation patterns.
development
skills/cloud/gcp/cloud-build-deploy
--- name: cloud-build-deploy description: Use when building CI/CD pipelines on GCP with Cloud Build, Cloud Deploy, or Artifact Registry. Covers GCP Cloud Developer domain: Building and testing (~26%) and Deploying (~19%). Also covers DevOps Engineer domain: CI/CD pipelines (~25%). --- # Cloud Build & Cloud Deploy ## When to Use - Setting up CI/CD pipelines on GCP - Configuring build triggers, test steps, and artifact management - Implementing progressive delivery (canary, blue/green) - Prepari
development
skills/cloud/gcp/cloud-run-functions
--- name: cloud-run-functions description: Use when choosing between Cloud Run and Cloud Functions, designing serverless compute on GCP, configuring concurrency/scaling, or building event-driven architectures. Covers GCP Cloud Developer domain: Designing apps (~36%). --- # Cloud Run & Cloud Functions ## When to Use - Deciding between Cloud Run, Cloud Functions, and App Engine - Configuring autoscaling, concurrency, and cold start behavior - Building event-driven serverless architectures - Prep
development
skills/cloud/gcp/cloud-storage
--- name: cloud-storage description: Use when designing Cloud Storage buckets, choosing storage classes, setting lifecycle rules, controlling access, or using GCS as a data lake. Covers GCP-PDE domain: Store the data (~15-20%). --- # Cloud Storage ## When to Use - Designing data lake or file storage on GCP - Setting up lifecycle management to control costs - Configuring access control for sensitive data - Preparing for GCP Professional Data Engineer exam ## Core Jobs ### 1. Storage Class Sel
devops
codepipeline-cicd
Use when building AWS CI/CD pipelines with CodePipeline/CodeBuild/CodeDeploy, choosing deployment strategies, configuring buildspec.yml, or setting up artifact management with CodeArtifact. Covers AWS DOP-C02 and DVA-C02 CI/CD domains.
development
content-scripts
Build content scripts for DOM manipulation, page interaction, and messaging between extension and web pages.
tools
daily-brief
Morning analytics briefing covering the last 1-2 days — surfaces anomalies, trends, risks, and wins. Uses mcp__Amplitude__query_amplitude_data, mcp__Amplitude__get_charts, mcp__Amplitude__get_context.
tools
database-optimization
Use when reviewing database schemas, slow queries, missing indexes, or planning migrations
data-ai
dataflow-gen2
Use when building no-code/low-code data transformations in Microsoft Fabric with Dataflow Gen2, configuring Power Query transformations, setting up incremental refresh, or studying for DP-700 (Microsoft Fabric Data Engineer Associate).
development
skills/cloud/gcp/dataflow-pipeline
--- name: dataflow-pipeline description: Use when building Apache Beam pipelines on Google Cloud Dataflow — batch ETL, streaming, windowing, triggers, or Dataflow vs Dataproc decisions. Covers GCP-PDE domain: Ingest and process data (~25-30%). --- # Dataflow Pipeline ## When to Use - Building ETL pipelines (batch or streaming) on GCP - Choosing between Dataflow and Dataproc for a workload - Designing windowing or late-data handling for streaming - Preparing for GCP Professional Data Engineer e
development
data-modeling
Use when designing analytics schemas, choosing between star schema and OBT, or modeling entities for a data warehouse
data-ai
data-pipeline-design
Use when designing ETL/ELT pipelines, choosing between streaming vs batch, or architecting data flow between systems
devops
skills/cloud/gcp/data-quality-validation
--- name: data-quality-validation description: Use when designing data quality checks, validating pipeline outputs, setting up schema validation, or using Dataform/Dataplex/Cloud DQ. Covers GCP-PDE domain: Prepare and use data for analysis (~10-15%). --- # Data Quality Validation ## When to Use - Designing data quality checks for a pipeline - Schema validation after ingestion - Setting up monitoring for data freshness and completeness - Preparing for GCP Professional Data Engineer exam ## Cor
testing
deal-strategy
Use when navigating complex enterprise deals, multi-stakeholder sales, or competitive displacement situations
business
design-handoff
Use when preparing designs for developer implementation, writing specs, or managing the design-to-code workflow
development
design-system-audit
Use when reviewing component consistency, design token coverage, or the health of a design system
testing
design-with-pencil
Use when creating UI designs with Pencil — the MCP-native canvas that lives in your repo. Requires Pencil extension installed in your IDE.
tools
design-with-stitch
Use when creating UI designs, mockups, or prototypes - integrates Google Stitch SDK for visual design generation
development
diff-intake
Transform code diffs (PRs, branches, files) into structured YAML briefs for analytics instrumentation planning. Minimal MCP usage — primarily code analysis.
tools
discover-analytics-patterns
Map existing analytics SDK implementations in a codebase to understand naming conventions and instrumentation patterns. Uses mcp__Amplitude__get_event_properties.
tools
discovery-call
Use when running discovery calls, qualifying opportunities, or applying MEDDIC/SPIN selling frameworks
development
eks-kubernetes
Use when designing EKS clusters, choosing node types (managed/Fargate), implementing IRSA for pod IAM access, scaling with Karpenter, or troubleshooting EKS networking. Covers AWS DOP-C02 and SAP-C02 container orchestration domains.
devops
environment-setup
Use when bootstrapping new projects, setting up dev environments, writing onboarding docs, or configuring local development tooling
tools
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
testing
experiment-tracking
Use when designing A/B tests, managing experiment hypotheses, analyzing results, or building an experimentation culture
development
extension-apis
Use Chrome/WebExtension APIs correctly — storage, tabs, alarms, notifications, contextMenus, identity, and cross-browser compatibility.
tools
fabric-monitoring
Use when monitoring Microsoft Fabric capacity usage, pipeline run failures, notebook performance, semantic model refresh errors, or managing Fabric capacity with the Capacity Metrics app. Covers DP-700 monitoring and optimization domain.
testing
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
development
game-audio
Use when writing a sound design brief, planning music direction, or building the audio systems specification for a game
development
skills/cloud/aws/glue-etl
--- name: glue-etl description: Use when building ETL pipelines with AWS Glue, managing the Glue Data Catalog, designing crawler strategies, or choosing between Glue and EMR. Covers AWS DEA-C01 domain: Data Ingestion and Transformation. --- # AWS Glue ETL ## When to Use - Building serverless ETL pipelines on AWS without managing infrastructure - Deciding between AWS Glue and Amazon EMR for a transformation workload - Designing Glue Data Catalog schema and crawler strategies - Using Glue Studio
development
hr-people-ops
Use when designing hiring processes, writing job descriptions, running performance reviews, or documenting culture and values
documentation
infrastructure-review
Use when reviewing deployments, CI/CD, monitoring, scaling, or incident response configurations
testing
instrument-events
Step 3 of instrumentation workflow — transform event candidates into concrete tracking specifications with exact code locations and property definitions. Uses mcp__Amplitude__get_event_properties, mcp__Amplitude__get_project_context.
tools
knowledge-transfer
Use when handing off a system, preparing someone to own a codebase, or ensuring knowledge doesn't live in one person's head
development
lake-formation-governance
Use when implementing fine-grained access control for S3 data lakes, setting up column-level or row-level security, sharing data across accounts, or governing the Glue Data Catalog with Lake Formation. Covers AWS DEA-C01 data governance domain.
development
lambda-serverless
Use when building Lambda functions, designing serverless architectures, configuring event sources, managing concurrency and cold starts, or setting up Lambda@Edge. Covers AWS DVA-C02 and SAP-C02 serverless domains.
development
level-design
Use when designing game levels, planning pacing and challenge curves, or documenting spatial layouts
testing
llm-cost-optimization
Use when reducing AI API costs — prompt caching, token reduction, batch processing, cost accounting for multi-step workflows, and building a cost optimization strategy for LLM-powered applications.
development
llm-evaluation
Use when measuring AI output quality - eval frameworks, golden datasets, regression testing, benchmarking, human-in-the-loop evaluation
development
llm-observability
Use when monitoring AI systems in production - cost tracking, latency, token usage, error rates, quality drift, and LLMOps dashboards
testing
manifest-v3
Design and configure Manifest V3 browser extensions — service workers, permissions, declarative rules, and migration from MV2.
tools
microsoft-sentinel
Use when implementing Microsoft Sentinel as SIEM/SOAR, configuring data connectors, building analytics rules, managing incidents, automating response with playbooks, or studying for SC-500 (Cloud and AI Security Engineer) or AZ-500.
development
monitor-ai-quality
Proactive health monitoring of AI/LLM features covering quality, cost, performance, and error metrics. Uses mcp__Amplitude__query_amplitude_data, mcp__Amplitude__get_charts, mcp__Amplitude__get_agent_results.
tools
performance-testing
Use when load testing APIs, profiling bottlenecks, or validating performance SLAs before release
development
pipeline-management
Use when reviewing deal stages, maintaining CRM hygiene, building forecasts, or analyzing pipeline health
development
product-strategy
Use when making product decisions, prioritizing features, planning launches, writing PRDs, or defining what to build next
development
prompt-engineering
Use when designing, testing, or versioning LLM prompts - covers few-shot, chain-of-thought, structured output, prompt templates, and systematic testing
testing
proposal-writing
Use when writing sales proposals, structuring pricing presentations, or articulating value propositions
testing
pr-workflow
Use when creating pull requests - PR structure, description templates, review checklist, merge strategies, branch naming
testing
qc-automation
Use when designing or implementing test automation — choosing the right automation framework (Playwright, pytest, JUnit), Page Object Model, selector strategies, test isolation, managing flaky tests, and CI integration.
tools
qc-defect-management
Use when managing defects — writing effective bug reports, applying severity/priority matrix, tracking defect lifecycle, conducting root cause analysis, and measuring defect metrics for process improvement.
business
qc-metrics
Use when measuring and reporting QA quality — defect escape rate, test coverage analysis, flaky test rate, mean time to detect, shift-left metrics, and building quality dashboards for stakeholders.
development
refactoring
Use when improving code structure without changing behavior - extract methods, simplify conditionals, reduce duplication, improve naming
development
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
development
skills/cloud/gcp/security-command-center
--- name: security-command-center description: Use when configuring Security Command Center, reviewing security findings, setting up threat detection, or managing compliance posture on GCP. Covers GCP Security Engineer domain: Managing operations (~16-22%). --- # Security Command Center ## When to Use - Reviewing security posture across GCP projects - Setting up threat detection for cloud resources - Responding to security findings - Preparing for GCP Professional Cloud Security Engineer exam
testing
security-review
Use when reviewing code for security vulnerabilities, auth issues, data exposure, or before deploying to production
development
seo-optimization
Use when improving organic search rankings, conducting keyword research, or fixing technical SEO issues
research
social-media-planning
Use when building a social media strategy, scheduling content, or adapting messaging per platform
development
session-lifecycle
Use when starting or ending a Claude Code working session — load context from memory, output a session brief, save decisions and progress at session end, and ensure work is resumable next session.
development
stakeholder-communication
Use when writing exec updates, status reports, or communicating product decisions to non-technical stakeholders
testing
solo-founder-gtm
Use when building go-to-market as a solo founder — distribution playbook for <5 hours/week, AI-powered personalized outreach, community leverage (Twitter/Reddit/ProductHunt/IndieHackers), and sales-led loops for early traction.
development
sprint-retrospective
Use when facilitating sprint retrospectives, choosing retro formats, or driving actionable outcomes from team reflection
development
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
development
support-playbook
Use when building a support triage process, writing escalation paths, or creating templates for common support issues
development
taxonomy
Create, validate, audit, and govern Amplitude event taxonomy across a product. Uses mcp__Amplitude__get_event_properties, mcp__Amplitude__get_project_context, mcp__Amplitude__query_amplitude_data.
tools
team-onboarding
Use when onboarding a new engineer, setting up their dev environment, introducing the codebase, or planning their first PR
development
tech-debt-triage
Use when prioritizing technical debt, deciding what to fix vs live with, or allocating time for debt reduction
testing
training-pipeline
Use when building reproducible ML training workflows, orchestrating training jobs, or versioning training artifacts
development
user-research
Use when planning user interviews, writing discussion guides, running usability tests, or synthesizing research findings
testing
ux-audit
Use when conducting a heuristic evaluation of an existing interface, identifying usability problems, or prioritizing UX improvements
testing
vpc-networking
Use when designing VPC architectures, configuring subnets and routing, setting up hybrid connectivity (VPN/Direct Connect/Transit Gateway), or choosing between load balancer types. Covers AWS ANS-C01 and SAP-C02 networking domains.
devops
workflow-templates
Use when executing a structured workflow — select and run a feature, bugfix, refactor, research, or incident template with correct agent and model assignments per phase.
development
xr-interface-design
Use when designing for XR (AR/VR/MR), choosing interaction modes, or adapting 2D UI patterns for spatial computing
content-media
visionos-patterns
Use when designing for Apple visionOS, applying spatial design conventions, or building for the Apple Vision Pro platform
development
model-monitoring
Use when setting up drift detection, retraining triggers, or production model health dashboards
data-ai
extension-testing
Test browser extensions with Playwright, unit test background workers and storage, and set up CI for extension projects.
tools
ado-release-management
Use when implementing release management on Azure DevOps — deployment gates (quality gates), pre/post-deployment approvals, deployment rings, rollback strategies, deployment freeze windows, and multi-environment promotion.
development
ado-pipelines-ops
Use when managing Azure DevOps pipeline infrastructure — self-hosted agent pools, service connections, variable groups, secure files, environments, approvals, and pipeline resource governance.
development
ado-security-policies
Use when configuring Azure DevOps security — security groups and permissions, branch policies, PR policies, audit log review, and org/project-level security governance.
development
ai-product-positioning
Use when defining how an AI product stands out — defensibility assessment, outcome-based messaging, feature vs product decision, competitive moat design, and positioning for a specific niche.
testing
create-chart
Build Amplitude charts from natural language descriptions. Uses mcp__Amplitude__get_event_properties, mcp__Amplitude__get_context, mcp__Amplitude__get_charts.
tools
compare-user-journeys
Identify behavioral differences between two user groups combining session replays with quantitative metrics. Uses mcp__Amplitude__get_session_replays, mcp__Amplitude__query_amplitude_data.
tools
discover-event-surfaces
Step 2 of instrumentation workflow — identify candidate analytics events from code change briefs. Uses mcp__Amplitude__get_event_properties, mcp__Amplitude__get_context.
tools
api-contract-testing
Use when validating API schemas, detecting breaking changes, or setting up consumer-driven contract testing
development
azure-functions
Use when building serverless event-driven applications with Azure Functions, designing Durable Functions orchestration workflows, choosing hosting plans, or studying for Azure AI Cloud Developer Associate (AI-200/AZ-204).
development
skills/cloud/gcp/gke-kubernetes
--- name: gke-kubernetes description: Use when designing GKE clusters, choosing Autopilot vs Standard, configuring workloads, setting up Workload Identity, or managing node pools. Covers GCP Cloud Developer domain: Deploying (~19%) and DevOps domain: CI/CD (~25%). --- # GKE Kubernetes ## When to Use - Designing or troubleshooting Kubernetes workloads on GCP - Choosing between GKE Autopilot and Standard - Configuring autoscaling, node pools, and resource limits - Preparing for GCP Professional
development
cost-aware-routing
Use when deciding which model or agent to use for a task - guides cost-optimized model selection based on task complexity
testing
ado-pipeline-security
Use when hardening Azure Pipelines security — YAML pipeline permissions, fork build security, resource authorization, secret scanning, protected resources, and preventing pipeline-based attacks.
development
dependency-management
Use when updating packages, auditing vulnerabilities, managing version pinning, or evaluating new dependencies
testing
incident-response
Use when handling production incidents - outage triage, root cause analysis, communication, postmortem writing
testing
agentic-security
Use when securing AI agent systems — defending against prompt injection, sandboxing tool execution, preventing indirect attacks through retrieved data, designing minimal-permission tool architectures, and security testing agents.
tools
ai-product-retention
Use when designing AI products for long-term retention — stickiness patterns, daily engagement hooks, workflow integration depth, habit loops specific to AI, and measuring whether users actually keep using your AI feature.
testing
adr-writing
Use when documenting architecture decisions, capturing the context and trade-offs behind technical choices
testing
agentic-reliability
Use when designing reliable AI agent systems — retry strategies, circuit breakers, fallbacks, graceful degradation, timeout management, and handling compound failures in multi-step agent workflows.
testing
agentic-memory
Use when designing memory systems for AI agents — tiered memory architecture (in-context, session, long-term, episodic), context window management, memory compression, and retrieval strategies for persistent agent state.
data-ai
discover-opportunities
Cross-reference analytics, experiments, session replays, and feedback to surface highest-impact product improvements. Uses mcp__Amplitude__query_amplitude_data, mcp__Amplitude__get_session_replays, mcp__Amplitude__get_feedback_insights.
tools
analyze-chart
Deep-dive investigation of Amplitude charts to identify trends, anomalies, and root causes. Uses mcp__Amplitude__query_chart, mcp__Amplitude__render_chart, mcp__Amplitude__get_event_properties.
tools
replay-ux-audit
Synthesize multiple session replays into a UX friction map identifying systemic usability issues. Uses mcp__Amplitude__list_session_replays, mcp__Amplitude__get_session_replay_events, mcp__Amplitude__get_session_replays.
tools
debug-replay
Transform bug reports into actionable reproduction steps using session replay data. Uses mcp__Amplitude__list_session_replays, mcp__Amplitude__get_session_replay_events, mcp__Amplitude__get_session_replays.
tools
analyze-dashboard
Synthesize an Amplitude dashboard into executive narrative with key findings, trends, and risks. Uses mcp__Amplitude__get_dashboard, mcp__Amplitude__query_charts.
tools
what-would-lenny-do
Applies Lenny Rachitsky's product wisdom to your specific situation by searching his newsletter archive. Uses mcp__Amplitude__search.
tools
authentication-patterns
Use when implementing auth - OAuth 2.0, JWT, session management, API keys, RBAC, or reviewing auth security
development
extension-security
Secure browser extensions — CSP configuration, minimal permissions, content script XSS prevention, and handling sensitive data safely.
tools
caching-strategy
Use when implementing caching - Redis, CDN, HTTP cache headers, application-level memoization, or cache invalidation patterns
databases
extension-ui
Build extension UI — popup, options page, side panel, and devtools panel — with React/Vue or vanilla JS.
tools
chaos-engineering
Use when designing resilience tests, planning chaos experiments, or validating failure recovery
testing
cloud-cost-review
Use when auditing cloud spend, rightsizing instances, reviewing reserved instance coverage, or finding cost optimization opportunities
testing
claude-memory
Use when leveraging Claude Code's auto-memory system — understanding what Claude saves to memory, writing good memory entries manually, structuring the memory directory, and using memory for project continuity across sessions.
development
skills/cloud/gcp/cloud-networking
--- name: cloud-networking description: Use when designing VPC networks, configuring subnets/routes/firewall rules, setting up VPC Peering or Shared VPC, or designing hybrid connectivity. Covers GCP Network Engineer domains: VPC Design (~20-25%) and VPC Implementation (~20-25%). --- # Cloud Networking ## When to Use - Designing VPC architecture for a GCP deployment - Configuring firewall rules, routes, or NAT - Planning hybrid connectivity (VPN or Interconnect) - Preparing for GCP Professional
devops
claude-project-settings
Use when configuring Claude Code for a project — .claude/settings.json structure, permission modes, model selection, tool allowlists/denylists, and team vs personal settings.
tools
iam-security
Use when designing IAM policies, troubleshooting access denied errors, implementing SCPs, permission boundaries, cross-account roles, or using IAM Access Analyzer. Covers AWS SCS-C02, SAP-C02, and DVA-C02 identity domains.
testing
azure-networking
Use when designing Azure VNet architecture, configuring NSGs, selecting load balancers, planning hybrid connectivity (VPN/ExpressRoute), implementing Private Link, or studying for Azure Network Engineer Associate (AZ-700) or AZ-305.
testing
guardduty-security
Use when setting up AWS GuardDuty threat detection, managing findings, automating incident response, configuring multi-account setups, or understanding GuardDuty vs Inspector vs Security Hub. Covers AWS SCS-C02 detection and response domain.
testing
s3-best-practices
Use when designing S3 data lakes, selecting storage classes, configuring lifecycle policies, implementing access control and encryption, or optimizing S3 performance. Covers AWS DEA-C01 and SAP-C02 storage domains.
testing
fabric-pipelines
Use when building data pipeline orchestration in Microsoft Fabric, configuring Copy Data activities, scheduling data movement, implementing control flow logic, or studying for DP-700 (Microsoft Fabric Data Engineer Associate).
development
aks-kubernetes
Use when designing Azure Kubernetes Service (AKS) clusters, configuring node pools, integrating Azure AD/Entra ID RBAC, implementing Workload Identity, planning scaling strategies, or studying for AZ-400 or AZ-305.
devops
azure-openai
Use when integrating Azure OpenAI Service, deploying GPT/embedding models, building RAG applications with Azure AI Search, implementing prompt engineering patterns, or studying for Azure AI Engineer Associate (AI-102) or AI-200.
development
skills/cloud/gcp/cloud-iam
--- name: cloud-iam description: Use when configuring GCP IAM roles, service accounts, org policies, Workload Identity Federation, or least-privilege access. Covers GCP Security Engineer domain: Configuring access (~22-28%) and DevOps domain: Org management (~20%). --- # Cloud IAM ## When to Use - Designing access control for GCP resources - Configuring service accounts and Workload Identity Federation - Setting org policies for compliance - Preparing for GCP Professional Cloud Security or Dev
development
competitive-analysis
Use when researching competitors, positioning features, or preparing for a market entry
research
docker-containerization
Use when creating Dockerfiles, docker-compose configs, optimizing container images, or setting up containerized development environments
development
skills/cloud/gcp/cloud-monitoring
--- name: cloud-monitoring description: Use when setting up Cloud Monitoring dashboards, alerting policies, log-based metrics, distributed tracing, or building SLO/SLI frameworks. Covers GCP DevOps Engineer domain: Troubleshooting (~25%) and Optimizing performance (~12%). --- # Cloud Monitoring ## When to Use - Setting up observability for GCP services - Designing SLO/SLI framework and error budgets - Troubleshooting production issues with logs and traces - Preparing for GCP Professional Cloud
development
feature-engineering
Use when selecting, transforming, or creating features for ML models
data-ai
fabric-lakehouse
Use when designing Microsoft Fabric Lakehouse architecture, working with Delta tables, OneLake storage, Spark notebooks, or studying for DP-700 (Microsoft Fabric Data Engineer Associate). Covers Fabric architecture, Delta Lake, OneLake shortcuts, and medallion patterns.
testing
financial-modeling
Use when building unit economics models, financial projections, or analyzing the business viability of a feature or product
development
email-marketing
Use when designing email campaigns, building drip sequences, segmenting lists, or improving deliverability
development
incident-postmortem
Use when writing a blameless postmortem after an incident, identifying root causes, and building follow-up action items
development
feedback-synthesis
Use when processing user interviews, support tickets, NPS comments, or survey responses into actionable insights
documentation
launch-planning
Use when planning a product or feature launch, building a GTM strategy, or coordinating a cross-functional release
development
rag-architecture
Use when building RAG pipelines - document ingestion, chunking, embedding, vector search, retrieval, reranking, and generation with context
development
performance-benchmarking
Use when establishing performance baselines, comparing before/after changes, or validating performance SLAs
tools
model-selection-guide
Use when choosing between Claude models for a task — decision tree for Haiku/Sonnet/Opus based on task type, cost estimates, escalation triggers, and cascade patterns.
testing
model-routing
Use when selecting AI models for different tasks, designing cost-aware routing (cheap→expensive cascade), implementing model fallbacks, and optimizing the capability/cost/latency tradeoff across model tiers.
data-ai
ml-experiment-tracking
Use when managing ML experiments, ensuring reproducibility, or comparing model runs
testing
narrative-design
Use when designing game story structure, writing branching dialogue, building lore, or planning narrative delivery
development
on-call-runbook
Use when writing runbooks for on-call engineers, documenting incident response steps, or creating operational playbooks
testing
qa-process-design
Use when designing quality assurance processes — defining quality standards, integrating QA checkpoints into SDLC, creating process documentation, onboarding teams to quality practices, and building a quality-first engineering culture.
development
qa-audit
Use when conducting quality audits — reviewing process compliance, identifying gaps between defined process and actual practice, conducting structured inspections (code review audits, test quality reviews), and producing audit reports with remediation plans.
development
qc-uat-facilitation
Use when facilitating User Acceptance Testing — planning UAT sessions with business stakeholders, designing business-scenario test cases (not technical), coordinating UAT execution, managing UAT defects, and obtaining formal sign-off.
testing
product-metrics
Use when defining KPIs, building dashboards, or measuring whether a feature or product is healthy
development
receiving-code-review
Use when receiving code review feedback, before implementing suggestions - requires technical rigor and verification, not performative agreement
development
qc-test-data
Use when managing test data — designing test data strategies, using factories and builders, creating fixtures, generating synthetic data, masking PII for testing, and managing test database state.
development
roadmap-planning
Use when building quarterly roadmaps, prioritizing the backlog, or communicating what's coming and why
development
quality-gates
Use when defining definition of done, setting release criteria, or building automated quality checks into the CI/CD pipeline
development
technical-art
Use when writing shader briefs, defining performance budgets, creating LOD strategies, or bridging art and engineering
tools
sprint-planning
Use when facilitating sprint planning, refining the backlog, calculating team capacity, or setting sprint goals
development
spec-driven-development
Use when starting any non-trivial feature — enforces requirements → design → tasks workflow with explicit approval gates before writing code. Prevents wasted implementation effort.
development
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
development
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
development
user-story-writing
Use when writing user stories, acceptance criteria, or breaking epics into shippable slices
tools
test-strategy
Use when building a test coverage plan, choosing what to test at each layer, or applying risk-based testing to focus effort
development
using-magic-powers
Use when starting any conversation - establishes how to find and use skills, model routing, and cost-aware development
development
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans
tools
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
testing
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims
data-ai
open-source-project
Use when setting up, maintaining, or growing an open source project — covers docs, community, licensing, and launch
documentation
performance-optimization
Use when diagnosing slow code, optimizing queries, reducing latency, or profiling application performance
development
mvp-rapid-development
Use when building MVPs fast with a small team - lean startup for AI products, feature prioritization, ship-fast patterns, iteration cycles
development
qa-risk-management
Use when managing quality risk — identifying quality risks in a product or release, applying risk-based testing prioritization, creating risk mitigation plans, and communicating quality risk to stakeholders for go/no-go decisions.
development
qc-security-testing
Use when testing security from a QC perspective — OWASP Top 10 test cases, authentication and authorization testing, input validation testing, security regression testing, and integrating security checks into the QC process.
testing
qc-test-design
Use when designing test cases — applying boundary value analysis, equivalence partitioning, decision tables, pairwise testing, and exploratory testing techniques to maximize defect detection with minimal test cases.
testing
sales-coaching
Use when running call reviews, building rep onboarding plans, handling objection training, or improving sales team performance
development
technical-writing
Use when writing documentation, READMEs, API docs, changelogs, ADRs, or user guides — ensures clarity, structure, and project consistency
development
technical-documentation
Use when writing API docs, runbooks, user guides, architecture docs, or internal wikis
development
vibe-coding
Use when rapidly prototyping AI products — going from idea to working demo in 4-8 hours using AI-assisted development tools (Cursor, Bolt, v0, Lovable), knowing when to vibe vs spec, and transitioning prototypes to production.
tools
spatial-ux
Use when designing 3D layouts, applying depth cues, planning spatial hierarchies, or ensuring user comfort in spatial experiences
content-media
slo-sli-design
Use when defining service level objectives, SLIs, or error budgets for reliability engineering
content-media
solutions-architecture
Use when designing pre-sales architectures, creating technical proposals, or helping customers integrate your platform
business
qc-mobile-testing
Use when testing mobile applications — device matrix strategy, iOS and Android testing tools (XCUITest, Espresso, Appium), gesture and interaction testing, network condition testing, app lifecycle testing, and mobile-specific quality concerns.
tools
model-evaluation
Use when selecting evaluation metrics, detecting bias, or validating model readiness for production
data-ai
mlops-deployment
Use when deploying ML models to production, setting up canary releases, or designing the serving infrastructure
devops
legal-compliance
Use when reviewing code, docs, or features for legal and regulatory requirements (GDPR, CCPA, SOC2, HIPAA, etc.)
development
growth-hacking
Use when designing viral loops, improving activation rates, running retention experiments, or building growth models
development
game-design-doc
Use when writing a Game Design Document (GDD), defining core mechanics, or planning player loops
documentation
developer-advocacy
Use when writing API documentation, creating developer tutorials, building devrel content, or engaging the developer community
development
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
testing
skills/cloud/gcp/vpc-service-controls
--- name: vpc-service-controls description: Use when configuring VPC Service Controls perimeters to protect GCP services from data exfiltration, or designing access levels for conditional access. Covers GCP Security Engineer domain: Securing communications and boundary protection (~18-24%) and Ensuring data protection (~23%). --- # VPC Service Controls ## When to Use - Preventing data exfiltration from BigQuery, GCS, or other GCP services - Designing security perimeters for sensitive data - Co
testing
data-quality
Use when validating data pipelines, writing data tests, or investigating data anomalies
testing
content-strategy
Use when building a content calendar, defining target audiences for content, or choosing content formats and distribution channels
development
skills/cloud/gcp/vertex-ai-mlops
--- name: vertex-ai-mlops description: Use when building ML pipelines on Vertex AI, managing model lifecycle, setting up feature stores, or deploying models for serving. Covers GCP-PDE domain: Maintain and automate data workloads (~10-15%) and GCP ML Engineer domain: MLOps (~30-35%). --- # Vertex AI MLOps ## When to Use - Designing ML training or serving infrastructure on GCP - Setting up model monitoring or retraining pipelines - Choosing between AutoML and custom training - Preparing for GCP
development
skills/cloud/gcp/pubsub-messaging
--- name: pubsub-messaging description: Use when designing Pub/Sub topics/subscriptions, choosing push vs pull, handling message ordering, dead letters, or integrating Pub/Sub with Dataflow/BigQuery. Covers GCP-PDE domain: Ingest and process data (~25-30%). --- # Pub/Sub Messaging ## When to Use - Designing event-driven or streaming ingestion on GCP - Choosing between Pub/Sub and Pub/Sub Lite - Troubleshooting message delivery, ordering, or acknowledgement issues - Preparing for GCP Profession
devops
azure-devops-pipelines
Use when building Azure Pipelines CI/CD workflows, configuring YAML pipelines, setting up deployment environments with approvals, choosing agent types, or studying for Azure DevOps Engineer Expert (AZ-400).
development
eventstreams
Use when building real-time streaming pipelines in Microsoft Fabric with Eventstreams, connecting Event Hubs or IoT Hub sources, processing streams with windowed aggregations, or routing to Eventhouse/Lakehouse destinations. Covers DP-700 real-time intelligence domain.
development
fabric-governance
Use when configuring Microsoft Fabric workspace security, sensitivity labels, item-level permissions, endorsement, domain management, or row-level security in semantic models. Covers DP-700 governance and security domain.
development
redshift-optimization
Use when designing Amazon Redshift schemas, optimizing query performance, choosing distribution and sort keys, planning RA3 clusters, or comparing Redshift vs Athena. Covers AWS DEA-C01 data warehousing domain.
devops
azure-ad-entra
Use when configuring Microsoft Entra ID (Azure AD), managing app registrations, setting up Conditional Access policies, implementing PIM for privileged access, or studying for AZ-500, SC-500, or AZ-305.
testing
kinesis-streaming
Use when designing real-time streaming architectures with Amazon Kinesis, choosing between Kinesis services, managing shards, or comparing Kinesis vs MSK. Covers AWS DEA-C01 and DVA-C02 streaming domains.
devops
sagemaker-mlops
Use when building ML training/serving pipelines on AWS SageMaker, implementing MLOps with SageMaker Pipelines and Model Registry, monitoring models in production, or optimizing training costs with Spot instances. Covers AWS MLA-C01 exam domains.
development
dynamodb-design
Use when designing DynamoDB schemas, choosing partition and sort keys, planning GSI/LSI indexes, selecting capacity modes, or implementing DynamoDB Streams and DAX. Covers AWS DEA-C01 and DVA-C02 NoSQL design domains.
testing
cloudwatch-monitoring
Use when setting up AWS observability with CloudWatch metrics, logs, alarms, dashboards, X-Ray tracing, or CloudWatch Synthetics canaries. Covers monitoring domains across DEA-C01, DVA-C02, and DOP-C02 exams.
testing
capacity-planning
Use when projecting infrastructure needs, planning for traffic growth, or making scaling decisions
testing
claude-hooks
Use when automating Claude Code workflows with hooks — PreToolUse (validate/block actions), PostToolUse (react to completions), Stop (enforce standards before finishing), and SessionStart (load context). Configure in .claude/settings.json.
tools
firefox-publishing
Publish Firefox browser extensions to Mozilla Add-ons (AMO) — packaging, review process, source code submission, and Firefox-specific requirements.
tools
cross-browser-compat
Build browser extensions that work across Chrome, Firefox, Safari, and Edge — API differences, polyfills, and browser-specific manifest requirements.
tools
review-agent-insights
Retrieve and synthesize AI agent analysis findings ranked by business impact. Uses mcp__Amplitude__get_agent_results, mcp__Amplitude__get_feedback_insights.
tools
weekly-brief
Weekly analytics briefing synthesizing 7 days of data with week-over-week momentum analysis. Uses mcp__Amplitude__query_amplitude_data, mcp__Amplitude__get_charts.
tools
monitor-reliability
Proactive reliability health check using auto-captured error and network failure data. Uses mcp__Amplitude__query_amplitude_data, mcp__Amplitude__get_charts, mcp__Amplitude__get_context.
tools
investigate-ai-session
Deep-dive into a specific AI agent session to identify failure root cause and improvement opportunities. Uses mcp__Amplitude__get_session_replay_events, mcp__Amplitude__query_amplitude_data.
tools
diagnose-errors
Triage and investigate application errors using Amplitude's auto-captured error events. Uses mcp__Amplitude__query_amplitude_data, mcp__Amplitude__get_session_replays, mcp__Amplitude__get_charts.
tools
create-dashboard
Build Amplitude dashboards from requirements by discovering existing charts and organizing them into logical sections. Uses mcp__Amplitude__create_dashboard, mcp__Amplitude__get_charts, mcp__Amplitude__query_charts.
tools
ai-product-design
Use when productizing AI features for end users — UX patterns for AI, streaming, loading states, error handling, fallback design, reliability, and responsible AI disclosure.
data-ai
analyze-ai-topics
Analyze user inquiries to AI agents, identify topic coverage gaps, and prioritize improvements. Uses mcp__Amplitude__query_amplitude_data, mcp__Amplitude__get_feedback_insights, mcp__Amplitude__get_feedback_mentions.
tools
analyze-account-health
B2B account health assessment covering usage patterns, expansion risk, and growth opportunities. Uses mcp__Amplitude__get_users, mcp__Amplitude__query_amplitude_data.
tools
ai-harness
Use when building evaluation infrastructure for AI systems — test harnesses, CI pipelines for AI, automated regression detection, golden datasets, and continuous quality measurement.
development
ai-product-monetization
Use when pricing an AI product — choosing between usage-based/hybrid/outcome pricing, calculating unit economics, protecting margins against LLM cost, and setting prices that reflect value without losing customers.
testing
ai-data-moat
Use when building defensibility into an AI product — designing data collection strategies that compound over time, domain-specific dataset building, proprietary data as competitive moat vs base models, and when data beats prompt engineering.
development
ado-artifacts
Use when managing Azure Artifacts — feed creation and permissions, upstream sources, retention policies, package promotion across views, and connecting build pipelines to artifact feeds.
development
ado-organization
Use when setting up or managing Azure DevOps organizations and projects — project creation, team structure, user management, billing, extensions, and org-level settings.
tools