メニュー
Add a new screen to the mobile app (apps/mobile). Use when creating a new route/screen in the Expo Router app.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | new-mobile-screen |
| description | Add a new screen to the mobile app (apps/mobile). Use when creating a new route/screen in the Expo Router app. |
The mobile app uses Expo Router (file-based routing) with React Native, Tamagui UI, and a custom useTranslation hook for i18n.
apps/mobile/app/
(tabs)/ ← tab navigator screens
(tv)/ ← TV-specific screens
<screen>.tsx ← top-level screen
<domain>/
[id].tsx ← dynamic route
_layout.tsx ← nested layout
Create the screen file at the appropriate path under apps/mobile/app/:
export default function <Name>Screen() (Expo Router requires default export)(tabs)/Use i18n with the useTranslation hook:
import { useTranslation } from '@/lib/i18n';
const { t } = useTranslation();
// t('some.key')
Use shared UI components from @arcadeum/ui (imported via workspace alias):
import { Button, Card, YStack, XStack, Text } from '@arcadeum/ui';
Navigation — use expo-router hooks:
import { useRouter, useLocalSearchParams } from 'expo-router';
Add translations to apps/mobile/lib/i18n/messages/ for all locales.
Register in tab bar (if adding a tab): update apps/mobile/app/(tabs)/_layout.tsx
<SafeAreaView> or the project's screen wrapperuseSessionTokens() store and redirect to auth if unauthenticateduseColorScheme() from @/hooks/useColorScheme for theme-aware stylingImplement a feature from docs/ROADMAP.md end-to-end: branch, code, test, commit, push, open PR, fix CI. Use when user says "implement feature X from roadmap" or "start with feature X".
Deterministic LLM-first SEO audits for websites, blog posts, and GitHub repositories. Use this when the user asks to "perform SEO analysis", "run SEO audit", "analyze SEO", "check technical SEO", "review schema", "Core Web Vitals", "E-E-A-T", "hreflang", "GEO", "AEO", or GitHub repository SEO optimization. For full/page/repo audits, run bundled scripts for evidence and return prioritized, confidence-labeled fixes.
Use when implementing or reviewing accessibility (a11y) — ARIA attributes, keyboard navigation, focus management, color contrast, screen reader support, semantic HTML, form labels, error handling, or any WCAG compliance task. Trigger on keywords like a11y, accessibility, ARIA, keyboard, focus, screen reader, WCAG, contrast, VoiceOver, NVDA.
Use when implementing or reviewing frontend performance — bundle optimization, lazy loading, image optimization, caching, Core Web Vitals (LCP, FID/INP, CLS), code splitting, rendering strategies, or any speed/performance task. Trigger on keywords like performance, speed, bundle size, lazy load, Web Vitals, LCP, CLS, INP, cache, optimize, lighthouse, Core Web Vitals.
Check existing @arcadeum/ui components before implementing any new UI. Use before writing any component — reuse what exists, add to packages/ui if missing.
Create a git commit following the project's Conventional Commits convention with ARC ticket reference. Use when committing changes.