rhonda-rodododo

Use when adding encryption for a new data type, implementing envelope encryption, working with HPKE key wrapping, managing crypto labels, or handling multi-recipient decryption. Also use when the user mentions "encrypt", "E2EE", "envelope", "HPKE", "forward secrecy", "crypto label", "admin envelope", "content key", or needs to understand how data is encrypted at rest.

Guide JSON Schema and protocol changes through the multi-platform codegen pipeline in the Llamenos monorepo. Use this skill when modifying files in packages/protocol/schemas/, changing crypto-labels.json, updating wire formats, adding new message types, or when the user mentions "schema change", "protocol update", "codegen", "wire format", "new message type", "crypto label", "domain separation", "add a field", "new field", "envelope format", or "shared types". Also use when the user describes adding or modifying data structures that need to work across all platforms (desktop, iOS, Android, worker) — this implies a protocol change. If a change touches encrypted payload formats or cross-platform type definitions, this skill applies. Schema changes have blast radius across every platform — this skill ensures nothing is missed.

Process security audit findings into dependency-ordered implementation epics for the Llamenos monorepo. Use this skill when conducting a security audit, reviewing security findings, processing vulnerability reports, creating security fix epics, or when the user mentions "security audit", "vulnerability", "findings", "security review", "pen test results", "audit round", "security issue", "security bug", "exploit", "insecure", "hardening", or "timing-unsafe". Also use when the user describes specific security problems inline — like missing auth checks, unsafe crypto operations, or data exposure — even without using the word "audit" or "vulnerability". If the user pastes or describes 2+ security issues that need triage and remediation, this skill applies. Covers all platforms: Worker backend, desktop (Tauri), iOS (SwiftUI), Android (Kotlin/Compose), crypto (Rust), CI/CD, and infrastructure.

Guide BDD test writing for the Llamenos monorepo. Use this skill when writing Gherkin feature files, creating backend or desktop step definitions, debugging test failures, or when the user mentions "BDD", "feature file", "Gherkin", "step definition", "backend BDD", "test:backend:bdd", "behavioral test", "write tests first", "add test coverage", "tests broke", "fix tests", or "E2E testing". This skill supplements superpowers brainstorming and plan execution — it does not replace them. Use it for BDD-specific implementation detail, not as a workflow entry point.

Guide porting features across Desktop (Tauri/React), iOS (SwiftUI), and Android (Kotlin/Compose) in the Llamenos monorepo. Use this skill when implementing a feature that exists on one platform and needs to work on another, when the user mentions "port to iOS", "Android version", "feature parity", "cross-platform", "implement on all platforms", "build the iOS/Android/mobile version", "same thing on Swift/Kotlin/native side", or describes a feature that "doesn't exist on [platform] yet". Also use when the user says "the desktop version works, now build it for mobile", asks to "replicate" or "mirror" a feature across platforms, or when creating epics for mobile feature parity. If a user describes building a screen or feature and mentions a specific target platform while referencing an existing implementation on another platform, this skill applies. It ensures consistent architecture, shared types, proper crypto integration, and correct i18n string handling on each platform.

iOS build, test, and debugging workflows for the Llamenos project. Covers SSH to Mac M4, xcodebuild commands, simulator selection, XCFramework rebuilds, and UniFFI binding sync. Use when building iOS, running XCUITests, debugging crypto FFI issues, or troubleshooting Xcode/SPM problems.

Use when deploying the application, bumping versions, cutting releases, configuring CI/CD, managing Docker/Helm/Ansible deployments, or troubleshooting deployment issues. Also use when the user mentions "deploy", "release", "version bump", "Docker Compose", "Helm", "CI/CD", "wrangler", or needs to understand the deployment topology and release process.

Use when adding new Tauri IPC commands, modifying desktop crypto operations, updating the Rust CryptoState, or fixing Playwright test failures related to missing IPC mocks. Also use when the user mentions "IPC command", "platform.ts", "CryptoState", "tauri invoke", "generate_handler", or needs to understand the 4-layer IPC chain from Rust to test mocks.

Use when adding log statements, editing files that log, debugging log output, or reviewing PRs/code that touches logging. Enforces scoped structured logging (no console.*, no PII in logs, namespaces, createLogger/createDebugLog). Also use this when reviewing diffs — check for console.* usage, PII leaks in log extras, wrong logger primitive, or missing namespace conventions.

Orchestrate and run tests across all four suites (unit, integration, API E2E, UI E2E) with automatic service management, orphan process cleanup, worktree port tracking, and env validation. Use this skill whenever the user asks to run tests, check test health, verify changes work, or when you've completed implementation and need to validate. Also use proactively after any code change to verify it passes. Triggers on: "run tests", "check tests", "does this pass", "verify", "make sure tests pass", or after completing implementation steps.

Guide full-stack feature development with zod-validated schemas and OpenAPI-documented endpoints. Use this skill for ANY feature work that touches API endpoints, data types, or encrypted fields — including frontend components that consume API data. Trigger when adding new API endpoints, modifying route handlers, creating React Query hooks, building forms that submit to the API, working with encrypted fields (hub-key or envelope), creating or editing zod schemas, converting routes to @hono/zod-openapi, or adding new resource entities. Also trigger when the user mentions API validation, OpenAPI, Scalar docs, zod schemas, request/response types, shared types, or type duplication. This skill enforces the schema-first, single-source-of-truth pattern where all types are derived from zod schemas in @shared/schemas/ and used by both backend and frontend — no duplicate type definitions.

Write tests for the Llamenos project following established patterns, principles, and project conventions. Covers all four suites: unit, integration, API E2E, and UI E2E. Use this skill whenever writing new tests, adding test coverage, implementing features that need tests (all of them), or following TDD. Complements test-runner (which handles execution) and test-driven-development (which handles the red-green-refactor cycle). Triggers on: "write tests", "add tests for", "test coverage", "TDD", implementing any new feature or fix, or when a test file needs to be created or modified.