行動開發

Write self-documenting code with clear naming and structure, adding minimal, evergreen comments only when necessary to explain complex logic. Use this skill when writing or reviewing any code that might need comments. When refactoring code to make it more self-explanatory through better naming and structure. When deciding whether to add or remove comments from existing code. When ensuring comments explain why something is done rather than what is being done. When reviewing code to remove outdated or temporary change-related comments. This skill applies to all programming languages and all types of code files.

Expert database schema designer and Drizzle ORM specialist. Use when user needs database design, schema creation, migrations, query optimization, or Postgres-specific features. Examples - "design a database schema for users", "create a Drizzle table for products", "help with database relationships", "optimize this query", "add indexes to improve performance", "design database for multi-tenant app".

Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices.

To scaffold a new Dart or Flutter project, create a fresh project structure and starter files.

Classify a change set as behavior vs structure, then recommend the correct PR label (change:behavior or change:structure) and the appropriate local/CI checks. Use when the user asks whether a change is a behavior change or a structure change, what label to apply, or how CI/testing should differ based on change type.

To apply latest code changes to a running Flutter app, trigger hot reload after connecting to the Dart Tooling Daemon.

Install and configure Flutter SDK. Use when setting up a Flutter development environment.

To find the currently selected Flutter widget in the running app, get the selected widget after connecting to the Dart Tooling Daemon.

Comprehensive chezmoi dotfiles management expertise including templates, cross-platformconfiguration, file naming conventions, and troubleshooting. Covers source directorymanagement, reproducible environment setup, and chezmoi templating with Go templates.Use when user mentions chezmoi, dotfiles, cross-platform config, chezmoi apply,chezmoi diff, .chezmoidata, or managing configuration files across machines.

Create isolated jj workspaces for testing changes, running experiments in parallel, and exploring alternative implementations. Use when testing breaking changes, comparing different approaches, or running long-running operations without blocking other work. (project)

Best practices for internationalizing Swift/SwiftUI applications using LocalizedStringResource, String Catalogs (.xcstrings), and type-safe localization patterns. Use when implementing multi-language support, adding new UI strings, or refactoring hardcoded text in Swift apps.

Expert in code design standards including SOLID principles, Clean Code patterns (KISS, YAGNI, DRY, TDA), and pragmatic software design. **ALWAYS use when designing ANY classes/modules, implementing features, fixing bugs, refactoring code, or writing functions.** Use proactively to ensure proper design, separation of concerns, simplicity, and maintainability. Examples - "create class", "design module", "implement feature", "refactor code", "fix bug", "is this too complex", "apply SOLID", "keep it simple", "avoid over-engineering".

Diagnose and fix CI/CD failures by analyzing logs, reproducing locally, and applying fixes. Use when CI checks fail on pull requests.

Get and manage tasks from Things.app.

To run Dart or Flutter pub commands like `pub get` or `pub add`, execute a pub command for the given roots.

Playwright end-to-end testing for web applications. Cross-browser testing (Chromium, Firefox, WebKit),visual regression, API testing, mobile emulation. Use when writing E2E tests, testing across browsers,or setting up automated UI testing workflows.

Maintain consistent code formatting, naming conventions, and structure across the entire codebase with automated tools and clear standards. Use this skill when writing any code in any language or framework. When naming variables, functions, classes, or files. When formatting code with proper indentation and line breaks. When refactoring code to remove duplication or extract reusable functions. When running linters or formatters to ensure consistency. When removing dead code, unused imports, or commented-out blocks. When applying DRY principles to avoid code duplication. This skill applies universally to all programming tasks.

Deploy to edge runtimes (Cloudflare Workers, Vercel Edge, Deno Deploy) for globally distributed, low-latency applications. Master edge middleware, streaming, and runtime constraints for 2025+ edge computing.

To wait for page state changes, wait for text to appear or disappear or for a timeout.

Apply SIMD optimizations to Mojo code for parallel computation. Use when optimizing performance-critical tensor and array operations.