kikin81

Use when starting or finishing a beads (bd) task in this repo. Handles claiming an issue, creating a Conventional-Commit-prefixed branch with the bd id embedded, and opening a PR with a `Closes:` footer. Trigger on phrases like "start nubecita-xxx", "pick up <bd-id>", "open a PR for this", or "finish this task".

Promote an already-built AAB from the Play internal track to one or more downstream tracks — closed testing (alpha), open testing (beta), and/or production — by dispatching the "Promote to Production" GitHub Action, then guiding the gated approval. Use when the user wants to ship the latest internal build to production or testing tracks, advance a staged rollout, or set an in-app-update priority.

Run a read-only weekly app-health checkup for the nubecita Bluesky client — pulling GA4 (analytics-mcp), Firebase Crashlytics (firebase MCP), and RevenueCat (revenuecat MCP), computing 7-day week-over-week deltas, flagging regressions, and writing a LOCAL (uncommitted) markdown report plus a terminal summary. Use this whenever the user asks how the app is doing / app health / "health check" / "checkup", wants to see login or sign-in error rates, feed or engagement numbers, how many users see the paywall or upgrade to Pro, conversion / MRR / churn, crash-free rate, ANRs, or "what crashes should we fix" — even if they don't say the word "health". Also trigger on "how are our analytics / metrics looking", "any crashes to fix this week", or a request to review Crashlytics/GA4/RevenueCat together.

Use when running the :benchmark macrobench in this repo to capture or compare startup TTID numbers — phrases like "run the startup bench", "measure profile impact", "compare bench results", "is cold start faster", "regenerate the baseline profile". Project-specific to nubecita's bench workflow on a real device.

Use when translating this repo's Android `strings.xml` resources into another language (es-419, pt-BR, etc.) — adding a brand-new locale, or backfilling the strings the `MissingTranslation` lint guard flags after new keys land. Repo-owned translations (NOT Play Console cloud auto-translate), so the app is genuinely localized and the marketing screenshots can render real translated UI. Trigger on "/translate-strings <locale>", "translate the app strings to <lang>", "add a <locale> locale", or "lint says MissingTranslation".

Use when starting a beads task in this repo with worktree isolation — phrases like "kick off a worktree for nubecita-X", "start worktree for X", "create worktree for X". Thin wrapper around `bd worktree create` with the project-local sibling-path convention.

Use this skill to generate well-branded interfaces and assets for Nubecita, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping a Material 3 Expressive Android Bluesky client with adaptive layouts for phone, tablet, and foldables.

Use this skill when integrating AT Protocol OAuth 2.0 login into an Android app consuming the kikin81/atproto-kotlin library. Covers hosting the client-metadata JSON, configuring the Android intent filter for the redirect URI, implementing an encrypted OAuthSessionStore, constructing the AtOAuth flow orchestrator, and driving beginLogin / completeLogin / createClient / logout. DPoP proof-of-possession and token refresh are handled transparently by the library. Use this skill after atproto-setup and before any atproto-read or atproto-write-records work.

Use this skill when reading data from the AT Protocol (Bluesky timeline, author feeds, profiles, notifications, search) using the kikin81/atproto-kotlin library. Covers three related techniques: calling a generated *Service query method, paginating cursor-based endpoints with the generated *PageFlow() extensions, and dispatching over open unions (feed reasons, post embeds, quoted records) safely including the *Unknown fallback arm. Use after atproto-oauth (you need an authenticated XrpcClient).

Use this skill when setting up a new Kotlin, Android, or KMP project to consume the kikin81/atproto-kotlin library. Covers Maven Central coordinates, the three published artifacts (runtime, models, oauth), Ktor engine selection, and minimum JDK/Android SDK requirements. Use this skill before any of the atproto-oauth, atproto-read, or atproto-write-records skills.

Use this skill for the cross-cutting type rules that apply across every ATProto operation in the kikin81/atproto-kotlin library. Covers AtField<T> three-state optionality for mutation payloads, the runtime value classes (Did, Handle, AtUri, Cid, Datetime, Nsid, RecordKey, AtIdentifier) and when to use each, and a consolidated list of cross-skill pitfalls. Load this once per session alongside whichever task-specific skill you're using.

Use this skill when writing records to the AT Protocol via the kikin81/atproto-kotlin library — creating posts, likes, reposts, follows, blocks, or deleting any of those. Every record write goes through com.atproto.repo.createRecord (or deleteRecord), using the encodeRecord() helper to wrap a typed record with its $type discriminator. Use after atproto-oauth (you need an authenticated XrpcClient) and atproto-read (for reading the records you want to act on).

Guides writing, reviewing, and reasoning about modern Android UI code using Jetpack Compose. Covers best practices for state management, side effects, recomposition, navigation, Material 3 design, accessibility, and performance. Use when reading, writing, or reviewing any Jetpack Compose project.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.