Mobile

WHEN: Kotlin Multiplatform (KMP) project review, expect/actual patterns, shared module structure, iOS interopWHAT: Module structure analysis + expect/actual validation + platform separation + iOS/Android interop + dependency managementWHEN NOT: Android UI → kotlin-android-reviewer, Server → kotlin-spring-reviewer

Make well-calibrated probability estimates using superforecasting methodology. Use when user asks about probability, likelihood, chance, odds, "will X happen", "when will X happen", "how much will X cost", "what could go wrong", failure modes, risk assessment, forecasting, or any question involving uncertainty and estimation.

Deploys applications globally on Fly.io edge infrastructure with Firecracker VMs, multi-region deployment, and usage-based pricing. Use when deploying to multiple regions, running containers at the edge, or needing fast cold starts.

Playwright E2E testing patterns for TaxHelper. Use for auth redirects, insights drill-down, mobile viewport checks, and PWA verification.

Use when implementing iOS 26 features (Liquid Glass, new SwiftUI APIs, WebView, Chart3D), deploying iOS 26+ apps, or supporting backward compatibility with iOS 17/18.

Sanitizing and validating user input to prevent XSS, injection attacks, and security vulnerabilities in TypeScript applications

Discover all resources in your Amplify sandbox (DynamoDB tables, Lambda functions, data models, auth config) by reading amplify_outputs.json and querying AppSync.

Defines the standard 8-category taxonomy for classifying project files: Config, Tests, Docs, Scripts, Source Code, Data, AI Tooling, and Other. REFERENCE THIS SKILL whenever categorizing files, auditing project structure, or answering 'what types of files are here.' Apply these categories and patterns whether using the bundled script or manual analysis.

Brief description of what this skill does and when to use it. Be specific with trigger keywords so Claude knows when to apply this skill.

This skill should be used when the user asks to "implement with TDD", "write tests first", "do test-driven development", or as Phase 3 of the /dev workflow. Enforces RED-GREEN-REFACTOR cycle with mandatory test-first approach.

Professional network graph analyst identifying Gladwellian superconnectors, mavens, and influence brokers using betweenness centrality, structural holes theory, and multi-source network reconstruction. Activate on 'superconnectors', 'network analysis', 'who knows who', 'professional network', 'influence mapping', 'betweenness centrality'. NOT for surveillance, discrimination, stalking, privacy violation, or speculation without data.

Use when implementing route changes, view transitions, modal opens/closes, or navigation animation in web and mobile applications.

Orchestre cycle de vie modules (planification, exécution, finalisation), génère rapports professionnels, met à jour RAPPORT_GENERAL

**UNIVERSAL TRIGGER**: Use when user wants to GET/FETCH/RETRIEVE any data FROM Bugsnag.Common patterns:- "get/show/list/display [something] from bugsnag"- "получить/показать/вывести [что-то] из bugsnag"- "bugsnag [organizations/projects/errors/details/events/comments/stats]"- "what [data] in bugsnag", "check bugsnag [resource]"Specific data types supported:📊 **Organizations & Projects**:- "list bugsnag organizations/orgs", "show organizations"- "list bugsnag projects", "available projects", "проекты bugsnag"🐛 **Errors (viewing)**:- "show/list bugsnag errors", "что в bugsnag", "check bugsnag"- "open errors", "error list", "ошибки bugsnag", "открытые ошибки"- "errors with severity error/warning", "filter bugsnag errors"🔍 **Error Details**:- "bugsnag details for <id>", "error details", "детали ошибки"- "show stack trace", "error context", "what happened in error"- "events for error", "error timeline", "события ошибки"💬 **Comments**:- "show comments for error", "error comments", "коммента

Write and format Rust documentation correctly. Apply proactively when writing code with rustdoc comments (//! or ///). Covers structure (inverted pyramid), intra-doc links (crate:: paths, reference-style), constant conventions (binary/byte literal/decimal), and formatting (cargo rustdoc-fmt). Also use retroactively via /fix-intradoc-links, /fix-comments, or /fix-md-tables commands.

Apply Go idioms from “Effective Go” when writing, reviewing, or refactoring Go code so results remain idiomatic, maintainable, and performant.

10 ready-to-use themes with colors and fonts for consistent styling.Use when: applying visual themes to pages, components, or design systems.Triggers: "theme", "color palette", "color scheme", "fonts", "branding","visual identity", "design system colors".

Storage management for Bazzite. Automounting drives (BTRFS/EXT4, Framework, SteamOS),BTRFS deduplication, rmlint disk trimming, and snapper snapshots. Use when usersneed to configure disk and partition management.

AI-powered Telemetry Validator Agent that verifies instrumentation works in sandbox environments. Use when: (1) Validating OTel spans are emitted correctly, (2) Verifying correlation headers in Kafka messages, (3) Confirming OpenLineage events for data pipelines, (4) Generating validation evidence for merge approval. Triggers: "validate telemetry", "verify instrumentation", "check OTel spans", "validate correlation headers".

Deconstructs complex problems using the 'Polymath Investor' framework with a 5-step cognitive chain (First Principles → Modular Isolation → Pareto Filtering → Cross-Domain Mapping → Dynamic Zooming). Use when analyzing systems, architectures, businesses, or learning challenges; when seeking high-leverage insights or 'Alpha'; when applying first principles thinking; or when needing cross-disciplinary perspectives to reveal blind spots. Transforms overwhelming complexity into actionable levers.