Development

Use when designing or revisiting a 12–18 month growth plan for a direct report. Trigger phrases include "build a growth plan for [report]", "what should [name]'s next year look like", "I want to architect [report]'s path to senior", "I'm prepping for promo cycle and [report] needs a plan", "let's think about [report]'s development". Distinct from one-on-one-prep and coaching-mode.

Use when preparing for a 1:1 — manager with a report, IC with their manager, or peer sync. Trigger phrases include "I have a 1:1 with X tomorrow", "help me prep for my 1:1", "what should I bring up in my next 1:1?". Builds a relationship-matched agenda; if the other person is a registered stakeholder, reads their reflection file first.

Use when moving outcomes without authority. Trigger phrases include "how do I get [team] to do X without going to their manager", "I need to convince [person] to support this", "I have to push back on [exec] without burning the relationship", "build the coalition", "I'm a TPM/staff eng/IC and I need [team] to prioritize this". Distinct from feedback-frameworks and coaching-mode.

Use when designing interview loops, writing interview questions or rubrics, calibrating panel feedback, running hiring debriefs, or making a hire/no-hire call. Trigger phrases include "design an interview loop for [role]", "write interview questions for [signal]", "help me run the debrief", "should we hire X", "I need a rubric for the system design round".

Use when the user is preparing to give feedback to a teammate, direct report, peer, or stakeholder — performance reviews, 1:1 prep, post-incident conversations, peer reviews, 360s, written async feedback, or any moment they're drafting "how do I tell them that…". Apply the COIN structure to compose the message and the SOLID checklist to pressure-test it before delivery.

Use for a quarterly/annual career retrospective across the haku memory; cited growth deltas vs. last retro, written to self/retros/. Trigger phrases include "run my career retro", "where am I in my career", "annual self-assessment", "how have I grown this year", "it's review season, take stock of everything". Distinct from wins-curate (audience-facing artifacts) and self-reflect (single entries).

Use when managing engineers who gravitate toward glue work (onboarding, documentation, unblocking) and need burnout protection, visibility, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how do I protect my glue person", "glue worker promotion", "coaching someone who's always helping others", "my engineer is drowning in non-promotable work".

Use when the user is navigating people/leadership situations as a PM — managing up to executives, managing down to a team, cross-functional conflict, 1:1s, performance reviews, post-mortems, incident response, roadmap negotiation, or stakeholder communication. Trigger when the question is about *how to handle a person or situation*, not about code or product mechanics.

Use for retrospective subtext reads on meetings, reviews, Slack threads, or 1:1s. Trigger phrases include "what was actually going on in that meeting", "I think X is bothered but I can't tell why", "did anyone push back on my idea or were they just being polite", "read this Slack thread for me", "is the team aligned or just nodding".

Use when the user needs a decision from executives and is preparing the meeting or memo that gets it — QBRs, roadmap reviews, headcount asks, investment pitches. Trigger phrases include "prep my exec readout", "I'm presenting to leadership", "I need sign-off from the VP", "help me get this decision approved". Distinct from demo-prep (performing a product) and the-status-crafter (recurring update rhythm).

This skill should be used when the user wants to talk to another LETS session of this repo - "ask the orchestrator", "ping the orchestrator", "what did the orchestrator say", "who is working", "message <name>", "tell <name>", "спитай у оркестратора", "запінгуй оркестратора", "що там оркестратор писав", "напиши в <name>", "хто ще працює". Resolves the peer, frames the message, sends only on the user's request, relays replies whole.

Mandatory pre-code gate and definition-of-done for ANY Odoo change (add field, override method, inherit view/xpath, wizard, cron, controller, report, security, bug fix, refactor, "optimize", "clean code", "stick to base"), Odoo 16-19. Run BEFORE brainstorming or planning: Odoo design questions are answered by tracing the real source into a Context Brief (file:line), not by open-ended Q&A. Resolves the Odoo version, loads the matching odoo-<major> pack, and closes with the i18n / security / hy...

Apply VueUse composables where appropriate to build concise, maintainable Vue.js / Nuxt features.

Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.

Vue 3 debugging and error handling for runtime errors, warnings, async failures, and SSR/hydration issues. Use when diagnosing or fixing Vue issues.

MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.

Core Regle form validation in Vue 3 — setup with `useRegle`, the reactive `r$` object, validation properties, displaying errors, and modifiers. Use when adding or editing Regle forms, binding `v-model` to `r$.$value`, or reading `$error`/`$errors`/`$invalid`/`$validate`/`$reset`. For validation rules see regle-rules; for advanced patterns see regle-advanced.

Pinia official Vue state management library, type-safe and extensible. Use when defining stores, working with state/getters/actions, or implementing store patterns in Vue apps.

Comark (Components in Markdown) parser: syntax, AST, Vue/React/Svelte/Angular renderers, plugins, and LLM streaming with auto-close.

Answer questions about ArkEnv and help implement environment variable validation. Use when developers: (1) Ask about environment variable validation or typesafety, (2) Want to setup ArkEnv in a project, (3) Need to define or update schemas using ArkType or Standard Schema, (4) Are integrating with Next.js, Nuxt, Vite, Bun, or Node.js runtimes. Triggers on: 'ArkEnv', 'env validation', 'typesafe env', 'createEnv', 'env.ts', 'arkenv'.

Translate strings in Xcode String Catalogs (.xcstrings files). Prefer to use the `xcode-skills:translation-coordinator` skill for task-coordination. Use this skill when translating individual strings or working with String Catalogs. Should only be activated when translating a single string or a small batch of known string keys. The `translation-coordinator` skill should be used for anything else.

Use when an app's layout must adapt to a window that changes size while the app runs, or when an app must support more than one window. That includes being asked to make an app resizable or support a resizable window, a layout that breaks or does not adapt as the window resizes, and preparing or optimizing an app for the foldable iPhone Duo, split-screen multitasking, or Stage Manager. Modernizes the app by replacing legacy shared-state APIs with context-appropriate alternatives: mainScreen, ...

Audits views for compliance with Apple's VoiceOver accessibility nutrition label. Checks that interactive elements have accessibility labels, labels are human-readable, accessibility traits are correct, images are properly configured, and custom controls are exposed to assistive technologies. Use when the user asks to check VoiceOver support, verify accessibility labels, audit the VoiceOver nutrition label, or review a view for screen reader compatibility.

Audits views for compliance with Apple's Sufficient Contrast accessibility nutrition label (WCAG 2.1 contrast ratios). Use when the user asks to check color contrast, audit contrast ratios, verify the Sufficient Contrast nutrition label, or review a view for accessibility.