
Use when you have a spec or requirements for a multi-step task, before touching code
Use when implementing MVVM, clean architecture, dependency injection with Hilt, or structuring Android app layers.
Convert Figma specs into Flutter widgets. Use when implementing new UI from Figma and the project has an existing design system.
Use when building Android UIs with Jetpack Compose, managing state with remember/mutableStateOf, or implementing declarative UI patterns.
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.
Enforce ultra-safe refactoring rules to prevent architecture changes, over-engineering, or unintended side effects.
Analyze and improve test code quality using Kent Beck's Test Desiderata framework. Use when analyzing test files, reviewing test code, identifying test quality issues, suggesting test improvements, or when asked to evaluate tests against best practices. Applies to unit tests, integration tests, and any automated test code.
Prepare Android release notes, risks, and QA checklist for Play Store submission and internal release.
Summarize a Bitbucket pull request and produce a QA checklist and risk list. Use when preparing PR description, reviewer notes, or release notes.
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.
Simplifies and refines code for clarity, readability, and maintainability. Reduces complexity without changing behavior. Use when simplifying, cleaning up, or reducing complexity in code.
Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Automate Flutter app builds and deployments to both the App Store and Google Play using Fastlane with this step-by-step guide.
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
This post provides a handy collection of Flutter commands and scripts for web development, package creation, troubleshooting, testing, and more, streamlining your Flutter workflow.
Use when kotlin's null safety system including nullable types, safe calls, Elvis operator, smart casts, and patterns for eliminating NullPointerExceptions while maintaining code expressiveness and clarity.
Use when executing implementation plans with independent tasks in the current session
Applies Kent Beck's Thinkies—pattern-based thinking habits that generate ideas. Use when stuck, exploring alternatives, or reframing decisions.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Finds weak or missing tests by analyzing if code changes would be caught. Use when verifying test effectiveness, strengthening test suites, or validating TDD workflows.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Reviews technical proposals against 30 complexity dimensions. Questions necessity of scale, consistency, and resilience. Use when proposing technologies (Kafka, microservices, event sourcing) or designing systems. Pushes for simplest viable approach.
Automate your Flutter app releases to beta or production with this handy shell script that handles version bumping, formatting, cleaning, rebuilding, and deployment via Fastlane.
Use when kotlin coroutines for structured concurrency including suspend functions, coroutine builders, Flow, channels, and patterns for building efficient asynchronous code with cancellation and exception handling.
Android and Flutter CI/release readiness workflow for branch validation, failure triage, QA checklist creation, and release-note risk review. Use when preparing mobile PRs for merge, fixing broken CI, validating a release candidate, or deciding go/no-go for internal or store release.
Mobile tech-lead operating mode for Android and Flutter delivery. Use when making architecture decisions, reviewing team PRs, guiding junior engineers, gating merges/releases, or balancing speed vs stability with token-efficient communication.
Mobile release and publish gate for Android and Flutter applications, including Play Store readiness. Use when preparing release candidates, approving go/no-go decisions, validating store metadata and versioning, or minimizing rollout risk before publish.
Detects stories that are too big and applies splitting heuristics. Identifies linguistic red flags (and, or, manage, handle, including) and suggests concrete splitting strategies. Use when breaking down requirements or splitting large work.
Modern clean architecture workflow for Android (Kotlin, Compose/XML, coroutines) and Flutter (Dart, widget/state architecture). Use when designing new features, refactoring legacy modules, auditing code quality, or upgrading architecture and async patterns with low-risk, incremental changes.
Mobile pull request review and merge gate for Android and Flutter codebases. Use when reviewing junior or peer code, deciding whether a PR is safe to merge, classifying findings severity, or preparing final merge notes with explicit block/approve decisions.
--- name: small-safe-steps description: Small Safe Steps (S3): breaks work into 1-3h increments with zero downtime. Use when asking "how do I implement/migrate/refactor", "what steps to do X", "plan safe migration", or handling risky DB/API changes. Applies expand-contract pattern for migrations, refactorings, schema changes. allowed-tools: - Read - AskUserQuestion --- STARTER_CHARACTER = 🪜⚡ # Small Safe Steps ## Mission Help you divide **ANY work** into the smallest, safest, most valua
Use when implementing any feature or bugfix, before writing implementation code
Harden Android Kotlin API DTO/mapping (Retrofit/Moshi/Gson) for nullability and contract safety. Use when fixing 4xx/5xx parsing, NPEs, or mismatched fields.
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
End-to-end Flutter feature delivery workflow for Dart apps using clean boundaries, small safe slices, and explicit state management. Use when implementing screens/features from requirement/design to verifiable patch.
Slices features into vertical deliverable pieces using the Hamburger Method. Generates 4-5 implementation options per layer and composes minimal end-to-end slices. Use when slicing work, breaking down features into layers, or delivering incrementally.
Deep Kotlin logic workflow for use-cases, repositories, ViewModels, Flow/coroutine orchestration, and compact architecture-safe refactors. Use when implementing non-trivial business rules, fixing coroutine race/cancellation issues, reducing logic complexity, or enforcing clean layered boundaries in Android Kotlin code.
CI/CD optimization workflow for existing mobile pipelines (Android and Flutter) across Bitbucket, GitHub Actions, GitLab, Jenkins, and Fastlane. Use when auditing current CI/CD setup, reducing build time/flakiness, improving release safety, or planning incremental pipeline upgrades without destabilizing delivery.
Safe merge-conflict resolution workflow for Android and Flutter repositories. Use when resolving git conflicts from teammate branches, rebases, or release branches, and you need minimal behavior change, verification evidence, and merge-safe outcomes.
Token-efficient workflow for Android and Flutter development that compresses task context without losing correctness. Use when conversations get long, context windows are tight, tasks span many files, or you need concise updates while preserving evidence and engineering quality.
Top-level orchestration skill for Android/Flutter delivery from feature implementation to review, conflict resolution, merge, release, and CI/CD improvement. Use when you want one lead workflow that routes tasks safely, keeps responses token-efficient, and protects production stability.
Mobile UI slicing workflow for Android Compose, Android XML, and Flutter widgets. Use when implementing new screens/components, splitting large UI tasks into safe incremental slices, fixing layout/state coupling, or converting design specs into maintainable UI without logic leakage.
Mobile dependency and platform update advisor for Android and Flutter projects. Use when mapping project structure, evaluating SDK/dependency updates, prioritizing technical debt, identifying architecture hotspots, or creating a safe improvement roadmap.
Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to official OpenAI domains.
Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
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; evidence before assertions always
Learn how to import `dart:html` and `dart:io` in the same Flutter project to create cross-platform plugins that work seamlessly on mobile and web.
Deploy your Flutter app to the App Store and Google Play with ease using this step-by-step guide covering installation, project setup, Fastlane integration, and automated deployments with Automator.
End-to-end Android feature delivery workflow for Kotlin + Compose + XML (when mixed stacks exist). Use for implementing a new feature from requirement/design to verifiable patch in small safe steps with clean architecture boundaries.
Analyze Android Logcat/crash traces to find the true root cause and propose a minimal Kotlin fix. Use when debugging crashes, ANRs, or runtime exceptions.
Fix Flutter UI issues based on QA screenshots (padding, spacing, alignment, dividers). Use when asked to match UI precisely without refactoring unrelated code.