create-screen

create-screen is a skill for Claude Code from FouadMagdy01/RNCopilot. It costs 18 tokens per session (1,286 once invoked), scanned A, original, MIT.

A workflow for adding a new screen or tab to a React Native app using its existing navigation and translation patterns. Routing determines how users reach each screen, and i18n means supporting multiple languages.

In plain words
What is it for?
Use it to create tab, stack, modal, or authentication screens, decide whether they require login, and identify when backing data should be built first.
Why use it?
It reduces the chance that a new screen is placed in the wrong navigation group, lacks translations, or ignores the app's established structure.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to create tab, stack, modal, or authentication screens, decide whether they require login, and identify when backing data should be built first.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fouadmagdy01/rncopilot/create-screen
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add FouadMagdy01/RNCopilot --skill create-screen
Clone the repo
git clone --depth 1 https://github.com/FouadMagdy01/RNCopilot

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-screen

README.md
[![agentmods](https://agentmods.dev/badge/skills/fouadmagdy01/rncopilot/create-screen.svg)](https://agentmods.dev/skills/fouadmagdy01/rncopilot/create-screen)
Your own site
<a href="https://agentmods.dev/skills/fouadmagdy01/rncopilot/create-screen"><img src="https://agentmods.dev/badge/skills/fouadmagdy01/rncopilot/create-screen.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,286 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.01286
Opus 5 $0.00009 $0.00643
Sonnet 5 $0.00004 $0.00257
Haiku 4.5 $0.00002 $0.00129

Measured 8d ago against content hash 7fa03098f327, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

create-screen scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/create-screen/SKILL.md · 192 lines

How it starts

The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Screen / Tab

Add a new screen or tab following expo-router conventions and project patterns.

Gather Information

Ask the user for:

  1. Screen name (e.g., "products", "order-details", "profile")
  2. Type: tab screen, stack screen, or modal
  3. Location in routing:
    • Tab: app/(main)/(tabs)/<name>.tsx
    • Stack within main: app/(main)/<name>.tsx
    • Auth screen: app/(auth)/<name>.tsx
  4. Protected? Does it require authentication?
  5. Needs backing data? If yes, suggest running /create-feature first

Steps

1. Create the Screen File

Screen files use lowercase with hyphens and default exports.

// app/(main)/(tabs)/<name>.tsx  OR  app/(main)/<name>.tsx
import { useTranslation } from 'react-i18next';
import { StyleSheet } from 'react-native-unistyles';
import { ScreenContainer } from '@/common/components/ScreenContainer';
import { Text } from '@/common/components/Text';
import { ErrorBoundary } from '@/common/components/ErrorBoundary';

export default function <Name>Screen() {
  const { t } = useTranslation();

  return (
    <ScreenContainer scrollable padded>
      <ErrorBoundary>
        <Text variant="h1">{t('<name>.title')}</Text>
      </ErrorBoundary>
    </ScreenContainer>
  );
}

const styles = StyleSheet.create((theme) => ({
  // Add styles as needed
}));

If protected (requires auth):

import { useProtectedRoute } from '@/hooks/useProtectedRoute';

export default function <Name>Screen() {
  useProtectedRoute(); // Redirects to /(auth)/login if not authenticated
  const { t } = useTranslation();
  // ... rest of screen
}

2. Register as Tab (if tab screen)

Edit app/(main)/(tabs)/_layout.tsx to add the new tab:

<Tabs.Screen
  name="<name>"
  options={{
    title: t('tabs.<name>'),
    tabBarIcon: ({ color, size }) => (
      <Icon name="<icon-name>-outline" color={color} size={size} />
    ),
  }}
/>

The Icon component uses Ionicons names. Choose an appropriate icon from the Ionicons set.

Read the full file on GitHub · 192 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 192 lines · 18 tokens per session scan A 7fa03098f327

Subscribe to this mod's changes

create-screen is a skill published in the GitHub repository FouadMagdy01/RNCopilot (41 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 1,286 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

flutter-setup-localization

Add flutterlocalizations and intl dependencies, enable "generate true" in pubspec.yaml, and create an l10n.yaml configuration file. Use when initializing localization support for a new Flutter project.

flutter/agent-plugins · 52 tokens

asc-localize-metadata

Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.

rorkai/app-store-connect-cli-skills · 60 tokens

asc-metadata-sync

Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.

rorkai/app-store-connect-cli-skills · 39 tokens

ios-marketing-capture

Use when the user wants to automate capture of marketing screenshots for a SwiftUI iOS app across multiple locales, devices, or appearances. Covers full-screen shots, isolated element renders (carousel cards, widgets), and reproducible output naming. Triggers on marketing screenshots, locale screenshots, widget…

ParthJadhav/ios-marketing-capture · 78 tokens

localization-l10n

Implement localization (l10n) best practices to adapt applications for specific regions, languages, and cultural preferences.

Mindrally/skills · 28 tokens

maui-localization-theming

Implement MAUI localization and theming. USE FOR: RESX/AppResources, runtime culture switching, RTL/FlowDirection, platform language metadata, AppThemeBinding, DynamicResource, light/dark/system themes, UserAppTheme. DO NOT USE FOR: general layout, accessibility audits, icon/splash assets.

dotnet/maui-labs · 73 tokens