skill-library

Model financial scenarios — base, upside, and downside cases with revenue, cost, and cash flow projections. Produce scenario comparison tables with sensitivity analysis. Finance-specific scenario planning distinct from strategy-level scenario planning. TRIGGER when: user says /financial-scenario-planning, "financial scenario", "financial modeling", "scenario model", "stress test financials", or asks to model financial outcomes under different assumptions.

Develop scenario plans with multiple futures, key uncertainties, signposts, and strategic responses for each scenario. Structure scenario analysis for strategic decision-making. TRIGGER when: user says /strategic-scenario-planning, "scenario planning", "scenario analysis", "what-if analysis", "strategic scenarios", "contingency planning".

Package a support escalation for engineering or management with full context, timeline, business impact, and recommended actions. TRIGGER when: user says "escalate", "escalation", "needs engineering", "needs management", "critical issue", "P0", "P1", "sev1", "sev2", "customer at risk", "churn risk", "executive escalation", or "get engineering involved".

Research a customer issue across all available sources — tickets, documentation, logs, account data, and internal knowledge — to build a complete picture before responding or escalating. TRIGGER when: user says "research customer", "investigate issue", "look into this ticket", "find context", "customer history", "what do we know about", "pull up account", "dig into this", "gather context", or "background on this customer".

Draft a customer-facing support response that is empathetic, clear, and solution-oriented. Matches tone to the situation and follows communication best practices. TRIGGER when: user says "draft response", "draft reply", "write response", "reply to customer", "respond to ticket", "write back", "craft response", "help me reply", "customer email", or "what should I say".

Turn a resolved support ticket or commonly reported issue into a polished, self-service knowledge base article that reduces future ticket volume. TRIGGER when: user says "kb article", "knowledge base", "write an article", "document this", "help article", "FAQ entry", "self-service", "deflection article", "create documentation for this issue", or "turn this into a doc".

Triage and prioritize an incoming support ticket by classifying category, severity, urgency, and routing to the appropriate team or workflow. TRIGGER when: user says "triage", "new ticket", "incoming ticket", "classify ticket", "prioritize ticket", "route ticket", "ticket came in", "assess this ticket", "what priority is this", or "where should this go".

Comprehensive data visualization guidance covering best practices, chart selection, design principles, and accessibility. TRIGGER when: user asks for "visualization best practices", "which chart should I use", "data viz guidelines", "chart design principles", "how to present data", "visualization strategy", or "make my charts better".

Run a WCAG accessibility audit on a design, component, or page. TRIGGER when: user says "accessibility audit", "a11y review", "WCAG check", "is this accessible", or asks about color contrast, screen readers, keyboard navigation, or ARIA.

Get structured feedback on a design — UI, layout, visual hierarchy, interaction patterns, and usability. TRIGGER when: user says "critique this design", "review my design", "feedback on this UI", "what do you think of this layout", or shares a screenshot/mockup for review.

Generate developer handoff specs from a design file, screenshot, or Figma description. TRIGGER when: user says "handoff specs", "dev specs", "developer handoff", "generate specs from Figma", "implementation spec", or needs to translate design to code requirements.

Create, audit, or extend a design system — tokens, components, patterns, and documentation. TRIGGER when: user says "design system", "component library", "design tokens", "style guide", "create a component", or works on systematic design infrastructure.

Synthesize user research into actionable themes, insights, and recommendations. TRIGGER when: user says "synthesize research", "analyze interviews", "find patterns", "research themes", "insight mapping", or has raw research data to distill.

Plan, structure, and document user research — interview guides, survey design, usability test plans. TRIGGER when: user says "plan research", "interview guide", "survey questions", "usability test", "research plan", or needs to design a study.

Write UX copy for screens, flows, components, and micro-interactions. TRIGGER when: user says "UX copy", "microcopy", "write copy for", "button text", "error message", "empty state", "onboarding copy", or needs interface text.

Plan and execute mobile app releases to Google Play Store and Apple App Store — store listing optimization, review guidelines compliance, staged rollouts, release checklists, and post-release monitoring. TRIGGER when: user says /app-store-release, asks about publishing to Play Store or App Store, needs to prepare a store listing, or wants a release checklist.

Design, review, or troubleshoot CI/CD pipelines for mobile apps — build automation, code signing, test automation, artifact distribution, and release management across Flutter, Android, and iOS. Covers Fastlane, Codemagic, Bitrise, and GitHub Actions. TRIGGER when: user says /mobile-ci-cd, asks about mobile build automation, needs to set up code signing in CI, or wants to automate mobile app releases.

Generate or update API documentation from code — endpoints, request/response schemas, authentication, error codes, and usage examples. TRIGGER when: user says /api-docs, asks to document an API, needs endpoint documentation, or wants OpenAPI/Swagger specs.

Generate text-based architecture diagrams from code or descriptions. Uses Mermaid syntax for system diagrams, sequence diagrams, and flowcharts. TRIGGER when: user says /architecture-diagram, wants a system diagram, asks to visualize architecture, or needs a sequence diagram.

Generate a changelog entry from commits, PRs, or a description of changes. Follows Keep a Changelog format with clear, user-facing language. TRIGGER when: user says /changelog, needs release notes, wants to summarize recent changes, or is preparing a release.

Create or review a documentation style guide — writing conventions, formatting standards, terminology, and tone guidelines for a project. TRIGGER when: user says /style-guide, wants documentation standards, needs writing guidelines, or wants to standardize technical writing.

Implement accessibility — ARIA patterns, keyboard navigation, screen reader support, semantic HTML, focus management, and testing strategies. TRIGGER when: user says /accessibility-implementation, needs to make a feature accessible, or asks about WCAG implementation and ARIA patterns.

Write architecture decision records (ADRs), evaluate technical tradeoffs, and document system architecture choices with structured reasoning. TRIGGER when: user says /architecture, asks to write an ADR, evaluate architecture tradeoffs, compare technical approaches, or document a system design decision.

Design and review backend application architecture — layering, API patterns, persistence, messaging, and deployment topology across Spring Boot (Java/Kotlin), Node.js (Express/NestJS), Django/FastAPI (Python), and Go. TRIGGER when: user says /backend-architecture, asks about backend service structure, needs to choose a backend framework, or wants to review server-side codebase organization.

Review code or pull requests for security vulnerabilities, correctness, performance, and style. Provide actionable, categorized feedback. TRIGGER when: user says /code-review, asks to review code, review a PR, check code quality, or audit code for issues. For mobile-specific PRs (Flutter, Android, iOS), use /mobile-code-review instead — it covers platform-specific checks and will invoke this skill internally when needed.

Estimate engineering effort — work breakdown, estimation techniques (T-shirt, story points, hours), risk buffers, and stakeholder communication. TRIGGER when: user says /cost-estimation, needs to estimate engineering work, or asks about project sizing, effort estimation, or timeline planning.

Evaluate and choose a mobile development strategy — Flutter vs. native (Kotlin/Swift) vs. Kotlin Multiplatform (KMP) vs. React Native vs. .NET MAUI. Decision framework covering team skills, platform API access, performance, long-term maintenance, and cost. TRIGGER when: user says /cross-platform-strategy, asks whether to use Flutter or native, needs to choose a mobile framework, or wants to evaluate cross-platform vs. native tradeoffs.

Design event-driven systems — event schemas, message broker selection, ordering guarantees, dead letter queues, saga patterns, and idempotency. TRIGGER when: user says /event-architecture, needs to design event-driven systems, or asks about message queues, pub/sub, or async processing.

Plan internationalization — string extraction, locale management, RTL support, date/number formatting, pluralization, and translation workflows. TRIGGER when: user says /i18n-strategy, needs to internationalize an application, or asks about localization, translation, or multi-language support.

Assess legacy codebases — code health metrics, dependency mapping, risk areas, technical debt quantification, and modernization roadmap. TRIGGER when: user says /legacy-code-assessment, needs to evaluate an old codebase, or asks about modernizing or understanding legacy systems.

Break monoliths into services — domain boundaries, communication patterns, data ownership, strangler fig migration, and operational readiness. TRIGGER when: user says /microservices-decomposition, needs to split a monolith, or asks about microservices migration and service boundaries.

Implement and audit mobile app accessibility — screen readers (TalkBack, VoiceOver), semantic labels, focus management, dynamic type, color contrast, touch targets, and platform-specific a11y APIs across Flutter, Android (Kotlin/Java), and iOS (Swift/ObjC). TRIGGER when: user says /mobile-accessibility, asks about making a mobile app accessible, needs to fix accessibility issues, or wants to audit a11y compliance.

Implement mobile analytics and crash reporting — event tracking strategy, Firebase Analytics, Mixpanel, Amplitude, Crashlytics, Sentry, user properties, funnel tracking, privacy-compliant tracking (ATT, consent), and A/B testing across Flutter, Android (Kotlin/Java), and iOS (Swift/ObjC). TRIGGER when: user says /mobile-analytics, asks about tracking events in a mobile app, needs to set up crash reporting, or wants to design an analytics strategy.

Design and review mobile application architecture — patterns (MVVM, MVI, Clean Architecture, TCA), navigation, dependency injection, modularization, and offline-first strategies across Flutter, Android (Kotlin), and iOS (Swift). TRIGGER when: user says /mobile-architecture, asks about mobile app structure, needs to choose an architecture pattern for a mobile app, or wants to review mobile codebase organization.

Review mobile pull requests with platform-specific checklists — code quality, architecture compliance, performance, accessibility, security, and testing standards across Flutter (Dart), Android (Kotlin/Java), and iOS (Swift/ObjC). TRIGGER when: user says /mobile-code-review, asks to review a mobile PR, needs a mobile-specific code review checklist, or wants PR review guidelines. DO NOT TRIGGER for generic/backend code reviews — use /code-review instead.

Choose, design, and review local data storage in mobile apps — key-value stores, SQL databases, NoSQL, file storage, secure storage, and sync strategies across Flutter (Hive, Isar, Drift, SharedPreferences), Android (Room, DataStore, SharedPreferences), and iOS (Core Data, SwiftData, UserDefaults, Keychain). TRIGGER when: user says /mobile-data-persistence, asks about local storage in a mobile app, needs to choose a persistence solution, or wants to review data layer design.

Understand, compare, and implement mobile design patterns — MVC, MVP, MVVM, MVI, Clean Architecture, VIPER, TCA, and BLoC. Covers rationale, data flow, testability, and platform-specific implementations across Flutter, Android (Java/Kotlin), and iOS (ObjC/Swift). TRIGGER when: user says /mobile-design-patterns, asks about MVC vs MVVM vs MVI, needs to understand or choose a mobile architecture pattern, or wants to migrate between patterns.

Design and implement mobile networking layers — HTTP clients, interceptors, authentication token management, caching, offline queues, GraphQL, WebSockets, and response parsing across Flutter (Dio/http), Android (Retrofit/OkHttp/Ktor), and iOS (URLSession/Alamofire). TRIGGER when: user says /mobile-networking, asks about API integration in mobile, needs to set up networking, implement token refresh, or optimize API calls.

Profile, diagnose, and optimize mobile app performance — startup time, UI jank, memory leaks, battery drain, network efficiency, and app size across Flutter, Android, and iOS. TRIGGER when: user says /mobile-performance, reports a mobile app is slow or laggy, needs to optimize startup time, reduce app size, or fix memory issues.

Implement push notifications in mobile apps — FCM, APNs, local notifications, rich media, notification channels, deep linking from notifications, silent push, token management, and notification strategies across Flutter, Android (Kotlin/Java), and iOS (Swift/ObjC). TRIGGER when: user says /mobile-push-notifications, asks about push notifications, needs to implement FCM/APNs, or wants to design a notification strategy.