padosoft-rn-screen-scaffoldinglisted

Use this skill when adding a new screen, component or data-fetching hook to a React Native / Expo app — "make me a screen for X", "add a component that shows Y", "I need the hook for this endpoint" — and whenever something added earlier is half-wired: a screen whose title shows the raw key, a route that exists in one app of the monorepo but not the other, a component not exported from its barrel. It lists every file a new piece touches, in order, so nothing is left half-registered. Do not use it to review existing code (padosoft-react-native-conventions) or for native modules and build configuration.
padosoft/skills · ★ 1 · Web & Frontend · score 80

Install: claude install-skill padosoft/skills

# React Native screen scaffolding **What breaks is never the code, it is the registration.** A screen compiles and runs while its title shows `account.orders.title`, while it exists in one app of the monorepo and not the other, while its component is not exported from the barrel. Each of those is a file nobody opened. This skill is the list of files, in order. The conventions that the generated code must follow are in **`padosoft-react-native-conventions`**. --- ## 0. Ask first, in one batch Never scaffold on assumptions. Collect, in a single round: - **what it is**: screen, component, or query hook; - **name and placement**: app-specific or shared core? A screen belongs to an app unless it is used by more than one; a shared component belongs to core; - **which apps** of the monorepo it has to exist in — the answer is usually *all of them*, and that is the step that gets skipped; - **route params**, if any, and their types; - **the endpoint**, for a query hook: path, parameters, response shape, and whether it paginates. If the answer to "which apps" is not all, write down why. ## 1. New screen — the file list | # | File | Skipping it means | |---|---|---| | 1 | The screen component | — | | 2 | Its skeleton / loading state | A blank frame on a slow connection | | 3 | The components barrel of the folder | The screen imports from a deep path, or does not resolve | | 4 | The screen wrapper, if the project uses one | The cross-cutting HOCs are missing (see RN-NAV-003: