
Create or update a DESIGN.md design system specification for websites, apps, prototypes, or product designs. Use when the user asks to generate a DESIGN.md, design system spec, UI specification, frontend design source of truth, Stitch/Google Design.md-style document, or agent-ready design tokens and component guidelines from images, descriptions, screenshots, mockups, brand notes, or raw product requirements.
--- name: expo-ios-agent-device description: Drive the Kotoba Expo iOS simulator effectively with agent-device. Use when verifying iOS UI behavior, testing Expo dev-client flows, seeding simulator app state, diagnosing accessibility selectors, or automating simulator QA for this repo. --- # Expo iOS Agent Device Use this skill when automating Kotoba on the iOS simulator with `agent-device`. ## Preflight Run these before planning commands: ```sh agent-device --version agent-device help workf
Compact the current conversation into a handoff document for another agent to pick up.
Transform technical documents, outlines, or raw notes into engaging, human-sounding blog posts. Use when asked to write a blog post, draft a post, turn this into a blog, or write up some content.
Curate and catalog agent skills from GitHub repositories or URLs. You MUST use this skill whenever the user asks you to add a skill, curate skills, catalog an agent tool, or update a central catalog/README with a list of skills.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Initialize or update a repository so coding agents can work in it effectively. Use this skill whenever the user asks to bootstrap a new project, make a repo coding-agent friendly, create or update AGENTS.md, set project rules, add documentation conventions, initialize docs structure, or refresh package-manager/project-command guidance.
Parses a design document to extract User Stories and creates corresponding GitHub Issues. It can optionally link them to a GitHub Milestone. This skill acts as a setup phase for GitHub-native issue tracking. Make sure to use this skill whenever the user asks to "send the design doc to GitHub", "create issues from the design doc", "setup the milestone", or mentions turning requirements into actionable GitHub issues.
Implement one specific user story or task from a GitHub Issue backlog, usually identified by a story ID such as USERST-001 or an issue number. Assigns the issue, implements the acceptance criteria, verifies the change, commits, pushes, and creates a PR. You MUST use this skill when asked to "implement USERST-001", "implement a user story", "run one iteration", "do the next task", or "complete a task from the backlog".
Add, configure, set up, install, repair, or verify gluestack-ui for an existing Expo or React Native project only when the user explicitly asks for gluestack setup/configuration/installation/repair/verification, directly names expo-gluestack-setup, or a new-project scaffold workflow invokes it for a gluestack handoff. Do not use this skill for general gluestack questions, error explanations, code review, postmortems, design advice, or unrelated Expo/NativeWind work unless the user explicitly requests this skill or asks to configure/setup/repair gluestack in the existing project.
Orchestrate the complete delivery workflow for one GitHub user story: implement it with the user-story-implementer skill, review the resulting PR with the user-story-reviewer skill, address reviewer feedback, and repeat until the PR is approved, merged, or blocked. You MUST use this skill when asked to "implement and review a user story", "run the full user story workflow", "deliver USERST-001", "complete USERST-001 end to end", or "run implementation and review together".
Create, bootstrap, initialize, or scaffold a brand-new React Native Expo app or Expo-centered monorepo with Expo Router, Expo SDK 55 by default, expo-dev-client, NativeWind, official gluestack setup via expo-gluestack-setup, starter gluestack components, EAS Build, and EAS Update. Use this skill only when the user is starting a new project/starter/scaffold or explicitly asks to use expo-scaffold. Do not use it for general Expo questions, code review, debugging, verification, postmortems, or existing-project changes unless the user explicitly requests a new scaffold or directly names this skill. For existing Expo apps, use a narrower skill only when the user explicitly asks to configure, set up, install, repair, or verify that specific system.
Review an implemented user story or task (via GitHub Pull Request) for completeness, test coverage, and code quality. Use this when asked to QA, review a PR, verify implementation, review a user story like USERST-001, or as a follow-up to the user-story-implementer skill.
Performs a comprehensive final audit of an implemented design document or feature. Reconciles the design doc's user stories against GitHub Issues and PRs, verifies acceptance-criteria evidence, checks design drift, audits documentation, runs appropriate verification commands, creates follow-up issues for unresolved gaps, and reports release readiness. Use this when asked to "do a final review of the design doc", "verify completion", "check if the feature is ready for release", "audit the implementation", or "run a post-implementation review".
Use the Kore CLI to search, browse, save, and synthesize the user's personal memory bank
Instructs the agent on how to efficiently browse public GitHub repositories using a local shallow clone. You MUST use this skill whenever the user asks you to scan, examine, clone, or extract information from a public Git repository, or whenever they provide a GitHub URL to explore.
Synthesize design discussions into a complete design document with agent-ready user stories. Use when asked to write a design doc, produce a design document, create a PRD, plan a feature, or turn a discussion into a spec.
One-time, read-only critique of a design doc, spec, PRD, or requirements for completeness, implementability, and user story readiness. Produces a structured review artifact with gaps, score, and next steps; does not edit or mark Revised. Use design-doc-review-loop when the user wants revisions, repeated review, or feature-delivery readiness.
Orchestrate end-to-end delivery of a complete feature from a revised design document: sync user stories to GitHub Issues with design-to-issues, deliver each story one at a time with user-story-delivery, and finish with post-implementation-reviewer. You MUST use this skill when asked to "deliver this design doc", "implement this feature from the design", "run the full feature delivery workflow", "turn this design into issues and ship it", or coordinate multiple user stories from a design document through implementation, review, and final audit.
Run the review-revision loop for an existing design doc: call design-doc-reviewer, address Critical Gaps and Minor Issues, repeat until clean, then mark the doc Revised for feature-delivery. Use when asked to review and revise, repeat until no gaps remain, prepare a design doc for feature delivery, or start a reviewer subagent and address feedback. Use design-doc-reviewer for one-time read-only critique.