Bump container image tags in Prow job YAMLs under prow-jobs/ while keeping the tag variant suffix (e.g. -dind, -alpine). Use when asked to update or refresh Prow job images, or to bump container/initContainer tags to a newer version without changing variants.
USE WHEN: planning complex multi-step tasks, organizing work with dependencies, identifying parallelization opportunities, breaking down large features into atomic tasks. DO NOT USE WHEN: single simple tasks, tasks without dependencies, or when user just wants immediate execution without planning. For complex orchestration, trigger deep thinking with "think harder" or "ultrathink" to map comprehensive dependency graphs.
Strategies for developing apps that work across multiple Apple platforms, including adaptive layouts and multi-view implementations.
For (1) finding solutions, patterns, and workarounds to issues when encountering unexpected behavior, or when stuck after trying initial approaches; (2) saving solutions, patterns, and workarounds discovered during development; (3) paring down useful-discoveries, keeping only the most valuable.
USE WHEN: analyzing existing architectures, evaluating architectural decisions, identifying technical debt, planning refactoring, assessing whether patterns are justified, onboarding to complex codebases, reviewing PRs with architectural changes. DO NOT USE WHEN: simple code questions, bug fixes, feature implementation, or tasks not requiring architectural analysis. For complex architectural analysis, trigger deep thinking with "think harder" or "ultrathink" to enable thorough first-principles reasoning.
For understanding what each mode does, which mode is best (most appropriate mode) for a given situation, and establishing a pattern for choosing when and how a mode delegates or passes operation to another mode
Use when setting up background jobs, caching, or WebSockets - SolidQueue, SolidCache, SolidCable (TEAM RULE
Building robust R packages with modern tidyverse patterns. Use this skill when creating or maintaining R packages, designing APIs, choosing dependencies, implementing input validation, writing error messages, or deciding between internal and exported functions. Covers dependency strategy, tidyverse API design patterns, validation approaches, error handling with cli/rlang, testing levels, and documentation priorities.
Use when designing Rails models - ActiveRecord patterns, validations, callbacks, scopes, associations, concerns, query objects, form objects
Finds insights that eliminate multiple components; "if this is true, we don't need X, Y, or Z". Used when implementing the same concept multiple ways, accumulating special cases, or complexity is spiraling. Otherwise known as "Simplification Cascades"
Object-oriented programming in R: S7, S3, S4, and vctrs class design. Use this skill when designing classes for R projects, choosing between OOP systems, building class hierarchies with inheritance, or migrating between systems. Covers S7 class definitions and methods, the decision matrix for choosing S7 vs S3 vs S4 vs vctrs, practical guidelines for each system, and migration strategies.
Any time an external api needs to be understood or queried
Use when building Rails controllers - RESTful actions, nested resources, skinny controllers, concerns, strong parameters
Scaffolds a new Kirby page type (blueprint + template, optional controller/model) using project roots, index tools, and Panel field/section references. Use when creating a new page type or extending an existing blueprint/template.
Builds Kirby listings, pagination, search, filtering/sorting/grouping, and navigation menus. Use when implementing collection logic in templates/controllers/snippets.
Implements custom Kirby routes and content representations (.json/.xml/.rss), including redirects, sitemap endpoints, and URL pattern filtering. Use when building endpoints, redirects, or representation templates that change how URLs resolve.
Implements frontend forms and actions in Kirby (contact forms, file uploads, email with attachments, creating pages from frontend). Use when handling user input or building submission flows.
Use when styling Rails views - Tailwind CSS utility-first framework and DaisyUI component library with theming
Use when building Rails view structure - partials, helpers, forms, nested forms, accessibility (WCAG 2.1 AA)
Builds or extends Kirby plugins using hooks, extensions, blocks, KirbyTags, and shared templates/controllers. Use when creating reusable features or integrating Panel customizations.
Exposes Kirby content to headless clients using the API, KQL, and JSON representations. Use when building API endpoints, KQL queries, or headless frontends.
Use when sending emails - ActionMailer with async delivery via SolidQueue, templates, previews, and testing
