ltatarev
User💝 Claude Code plugin for React Native development
Categories
Indexed Skills (17)
implement-ticket
Implement a ticket end-to-end as a frontend engineer — fetch it from whichever tracker the repo uses (Linear, Notion, or in-repo docs/tickets), implement following the codebase's existing structure and conventions, write tests, verify no regressions, move the ticket to In Review, and offer a commit. Use when the user asks to implement, work on, or pick up a ticket (e.g. "/implement-ticket ABC-123", "implement ticket 007", "pick up the sync bug ticket").
add-feature
Scaffolds a new feature module under src/modules/ or extends an existing one in a package-by-feature React Native codebase. Use when the user asks to add a feature, screen, module, setting, Redux slice, selector, or thunk; wire a new route into React Navigation; register a reducer in the store; or extend an existing module. Also use when deciding where new code belongs (module vs utils vs theme) or when a change crosses module boundaries.
bootsplash
Set up and debug the launch screen / splash in a React Native app using react-native-bootsplash, including light and dark variants without the paid license key. Use when the user asks about the splash screen, launch screen, bootsplash, app startup flash, a logo that is wrong or stale on launch, or a splash that stays light in dark mode; when regenerating splash assets; or before touching BootSplash.storyboard, values-night/, drawable-night-*/, or the bootsplash asset catalogs.
build-ui
Builds screens, components, modals, and sheets to the house React Native UI standard. Use when the user asks to build or add a screen, component, modal, sheet, button, or any JSX; when doing styling, theming, animation, or gesture work; or before writing any StyleSheet, translation key, or accessibility prop in a React Native project. Covers Unistyles v3 patterns, composing from the shared UI kit instead of raw RN primitives, the i18n + a11y procedure, and worklet rules.
commit-changes
Split the current working tree into a sequence of small, meaningful commits. Use when the user asks to commit their current changes, split a mixed diff, clean up a working tree before a PR, or create reviewable commits.
gitmoji
Gitmoji commit message format for git commits. Use when the user asks to commit changes, push code, create a commit message, or invokes /git-commit, /git-commit-push, or /git-commit-push-pr.
ios-widget
Build and wire an iOS home-screen widget (WidgetKit) into a React Native app — the App Group snapshot architecture, adding the extension target to project.pbxproj by script, the Swift native module bridge, rendering the widget's image offscreen with Skia, dark mode, freshness, and the build verification traps. Use when the user asks to add, change, or debug a widget, a WidgetKit extension, an App Group, a home-screen widget, or a lock-screen widget; when a widget renders blank, stale, or light-only; or before touching anything under an ios/*Widget/ directory.
maintain-skills
Meta-skill for keeping a skill library correct as the codebase evolves — both the shared adora-skills plugin and a project's own .claude/skills/. Use when the user asks to update, refresh, audit, or re-sync skills, says a skill taught something wrong or is out of date, after a big refactor / rename / module move, after CONTEXT.md or an ADR changes, when adding a new domain that needs a skill, or when deciding whether to update an existing skill, write a new one, or delete one.
ticket-shaping
Turn a UX/design-level description of a feature or change into an implementation-ready ticket in whichever tracker the repo uses (Linear, Notion, or in-repo docs/tickets) — UX spec plus a concrete, file-level recommended implementation plan the user challenges before it is written down. The user describes how something should behave and look, NOT the technical approach; this skill interviews them one question at a time, drafts the plan, hands it to `grill-plan`, then writes the ticket(s). Trigger when the user says "shape this", "write a ticket", "let's spec", "I want the app to…", "it should feel like…", "turn this idea into a task", or describes desired behavior/looks and asks to capture it for later implementation. NOT for stress-testing an already-written plan (that's `grill-plan` on its own) and NOT for actually building the feature.
truesheet-usage
Consumer-side guide for integrating @lodev09/react-native-true-sheet into a React Native app. Use this skill whenever the user wants to add, configure, control, or debug a bottom sheet using TrueSheet — including ref-based sheets, named global sheets, web support with TrueSheetProvider/useTrueSheet, React Navigation or Expo Router sheet flows, Reanimated-driven animations, scrolling content, stacking, headers/footers, detents, side sheets, keyboard handling, dimming, liquid glass, and Jest testing. Also use when the user is migrating from v2 to v3, troubleshooting layout or gesture issues, or asking about any TrueSheet prop, event, or method — even if they don't mention "TrueSheet" by name but describe a bottom sheet in a React Native context.
unistyles
Style React Native components with react-native-unistyles (StyleSheet.create, theme tokens, variants, breakpoints, runtime). Use whenever writing or editing styles in this codebase, or when asked about Unistyles APIs, theming, or migration behavior.
validate-change
Validation and handoff procedure for React Native changes. Use when finishing any code change, before committing or handing off, when the user says "run the checks", "is this ready", "validate", or asks whether tests/lint/types pass. Covers which checks match which change scope, how to establish a baseline so pre-existing issues are not blamed on new work, and the handoff report format.
verify
Build, launch and drive a React Native app on the iOS simulator to observe a change end-to-end. Use when verifying a code change actually works at runtime and not just in tests, when the user asks to run the app, take a screenshot, or check something on device, or when a bug can only be confirmed by driving the UI. Covers idb-based tapping, why synthetic clicks fail, where console output actually goes, and simulator gotchas.
write-tests
Writes Jest unit tests the house way in a React Native repo. Use when the user asks to add or write tests, says "test this", or after changing merge logic, persist transforms, sync, eligibility rules, verification, ordering, or utility logic. Covers detecting the repo's unit Jest config, what its setup file mocks, the fixture-builder test style, how to run one focused file, and what does or does not deserve a test.
xcode-cloud
Set up, debug and maintain Xcode Cloud CI for a React Native iOS app — the ci_post_clone.sh / ci_pre_xcodebuild.sh scripts that install node, pods and the RN prebuilt tarballs, the workflow settings, and the App Store Connect prerequisites for TestFlight. Use when the user asks to set up Xcode Cloud, add CI to an iOS app, get builds into TestFlight, or fix a failing cloud build; when an archive fails with "Unable to load contents of file list", "node: command not found", a curl error inside pod install, a bigdecimal or bundler failure, or a bare exit 65; when a green archive never reaches TestFlight; or before touching anything under ios/ci_scripts/, .xcode.env, Podfile, or Gemfile. Also use to record a newly diagnosed cloud build failure so it is not re-derived next time.
domain-model
Build and sharpen a project's domain model — the `CONTEXT.md` glossary of terms and the `docs/adr/` record of architectural decisions. Use when the user wants to pin down terminology or a ubiquitous language, asks "what should we call this", says the glossary is wrong or missing a term, wants to record or revisit an architectural decision ("write an ADR", "record why we did this"), or when another skill needs the model changed rather than merely read. Also use mid-design, the moment a term or a hard-to-reverse decision crystallises. NOT for reading `CONTEXT.md` for vocabulary — that is a habit every skill has, not a reason to load this one.
grill-plan
Relentlessly interview the user about a plan, design, or decision until you both reach the same understanding — one question per turn, each with your recommended answer, facts looked up rather than asked. Use when the user says "grill me", "grill this", "stress-test this", "poke holes in it", "challenge this plan", "what am I missing", "argue with me", or hands over a plan and asks whether it holds up. Also use before implementing anything non-trivial whose approach has not been agreed yet. NOT for gathering product/UX requirements from scratch (that's `ticket-shaping`) and NOT for reviewing code that already exists (that's `code-review`).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.