Expo Data Fetching
Applies Expo-recommended data fetching patterns for remote APIs, caching, and mobile networking constraints.
Skills for coding agent.
192 skills · 61–80
Applies Expo-recommended data fetching patterns for remote APIs, caching, and mobile networking constraints.
Guides native-feeling Expo/React Native UI—semantic colors, controls, icons, media, and visual polish.
Routes Expo and EAS work to the right official Expo skill and shared setup rules before coding or deploying.
Implements Expo Router file-based navigation—stacks, tabs, modals, sheets, links, and headers—correctly.
Builds native interfaces with @expo/ui, using SwiftUI on iOS and Jetpack Compose on Android.
Migrates an existing web/React app (Next.js, Vite, CRA) to a native iOS/Android Expo app.
Official Figma skill for turning selected designs into code with MCP design context and screenshots.
Builds or updates full-page Figma screens from code/descriptions using design-system search and assembly.
Builds or updates a professional design system in Figma from a codebase.
Translates Figma designs into production UI code with 1:1 visual fidelity via Figma MCP context.
Official Figma MCP skill for reading and editing Figma files via the Figma MCP server.
Finds bugs, security issues, and quality problems in local branch changes using Sentry engineering review habits.
Helps discover and install agent skills from the open ecosystem when you ask “is there a skill for X?”.
Finishes a development branch after tests pass—merge, PR, or cleanup with a clear integrate decision.
Pushes agents toward distinctive, intentional UI aesthetics instead of generic AI-looking layouts.
Enforces complete LLM code output by banning placeholders and truncated file generation.
Validates gcloud CLI operations and constructs commands with Google Cloud safety checks.
Adds Claude Code hooks that block dangerous Git commands before execution.
Runs a relentless interview to sharpen a plan or design before you build.
Grills a plan or design while grounding questions in your existing docs and specs.
An agent skill is a portable pack of instructions that gives an agent specialized know-how for a task. In the open Agent Skills format (from Anthropic, now widely adopted), that pack is a folder with a SKILL.md file and optional scripts or references the agent can load when needed.
SKILL.md is the required main file in a skill folder. It starts with simple metadata (name and description) plus the instructions. Agents use the metadata to decide when a skill applies, then read the full file — and any linked files — only when the task needs them.
Open the listing and follow the source link — usually a GitHub SKILL.md. Install with your agent’s skill flow, or add the repo the way that product documents. When this site shows the skill text, Copy is on the page.
A prompt is paste-in text for one chat turn (or a short thread). A skill is a reusable file pack an agent can discover and load across a task, sometimes with code attached. Prompts live in the prompt directory; skills usually live on GitHub and we link out.
Each skill uses one sitewide category — the same set as the rest of the directory (Coding agent, Marketing, Document intelligence, and so on). Hops filter to categories that already have skills.
Yes. Submit with a public GitHub SKILL.md URL, or attach a skill as part of a method on a use case. An editor reviews it before it appears here.