devendra-skill-package 1.0.2

package/.github/skills/code-test-coverage-analyzer/templates/test-case-row.md

@@ -0,0 +1,130 @@
+# Test Case Row Template
+
+Use this template for each test case entry in `04_TEST_CASE_COMPLIANCE.md`.
+
+---
+
+## Test Case Block Template
+
+```markdown
+### TC-{ID} — {Scenario Name}
+
+**Type**: Functional | Validation | Navigation | API | Business Logic | Edge Case | Negative
+**Related Story**: {US-ID or "None"}
+**Related BRD**: {BRD-ID or "None"}
+**Verdict**: PASS | PARTIAL_PASS | FAIL | NOT_IMPLEMENTED | BLOCKED | UNKNOWN
+**Confidence**: HIGH | MEDIUM | LOW
+
+#### Test Steps vs Implementation
+
+| # | Test Step | Expected Outcome | Actual Implementation | Step Status |
+|---|-----------|-----------------|----------------------|-------------|
+| 1 | {action from TC} | {expected from TC} | {what code actually does, with file ref} | PASS / FAIL |
+| 2 | | | | |
+...
+
+#### Evidence Files
+- `{file path}` — {why this file is evidence}
+- `{file path}` — {why this file is evidence}
+
+#### Verdict Reason
+{Specific reason for the verdict — must be precise, not vague.}
+
+#### Recommendation
+{What must change to make this test pass, or "No action required."}
+```
+
+---
+
+## Verdict Decision Rules
+
+### PASS
+ALL of the following are true:
+- Every test step can be traced to implementing code
+- The expected outcome matches what the code produces
+- No test step fails
+
+### PARTIAL_PASS
+- Most steps pass
+- At least one step fails (wrong message, wrong navigation, missing state)
+- The feature fundamentally exists but has gaps
+
+### FAIL
+- The feature exists but the implementation actively produces the wrong behavior
+- The expected result is demonstrably NOT what the code produces
+
+### NOT_IMPLEMENTED
+- A required screen, API endpoint, or core feature referenced in the test steps does not exist
+- The test cannot even start
+
+### BLOCKED
+- The test case itself is valid
+- It depends on another feature/screen/API that is MISSING
+- Name the blocker explicitly: "Blocked by: {missing feature, MISS-n}"
+
+### UNKNOWN
+- Searched extensively but cannot determine from static code analysis
+- Code is generated, obfuscated, or behind a runtime flag
+- State explicitly what was searched and why conclusion is not possible
+
+---
+
+## "Actual Implementation" Column Rules
+
+Write what the CODE DOES, not what the file is named.
+
+Wrong: "LoginScreen.tsx exists"
+Correct: "LoginScreen.tsx — handleSubmit() calls POST /auth/login with {mobile, pin} payload, stores JWT in AsyncStorage, navigates to Dashboard on 200 response"
+
+Wrong: "Validation file exists"
+Correct: "LoginSchema.ts — validates mobile as required + 10-digit numeric; validates pin as required, no length or format check implemented"
+
+---
+
+## Example Test Case Blocks
+
+```markdown
+### TC-005 — Login with valid mobile and PIN
+
+**Type**: Functional
+**Related Story**: US-003
+**Related BRD**: BRD-001, BRD-005
+**Verdict**: PARTIAL_PASS
+**Confidence**: HIGH
+
+#### Test Steps vs Implementation
+
+| # | Test Step | Expected Outcome | Actual Implementation | Step Status |
+|---|-----------|-----------------|----------------------|-------------|
+| 1 | Enter valid 10-digit mobile number | Field accepts input, no error | TextInput accepts numeric input, maxLength=10 — `LoginScreen.tsx:45` | PASS |
+| 2 | Enter valid 6-digit PIN | Field accepts input as password | SecureTextEntry PIN field present — `LoginScreen.tsx:62` | PASS |
+| 3 | Tap Login button | Loading spinner shown | ActivityIndicator shown while `isLoading=true` — `LoginScreen.tsx:89` | PASS |
+| 4 | API returns 200 with token | Navigate to Dashboard | Navigates to HomeScreen, not DashboardScreen — `LoginScreen.tsx:105` | FAIL |
+| 5 | Token stored for subsequent calls | Token in secure storage | Stores in AsyncStorage (not SecureStore) — `AuthService.ts:34` | PARTIAL |
+
+#### Evidence Files
+- `src/screens/LoginScreen.tsx` — main login UI and submit handler
+- `src/services/AuthService.ts` — API call and token storage
+
+#### Verdict Reason
+Steps 1–3 pass. Step 4 fails: navigation target is HomeScreen but requirement specifies DashboardScreen.
+Step 5 partial: token stored but in AsyncStorage (unencrypted) rather than SecureStore.
+
+#### Recommendation
+1. Change navigation in LoginScreen.tsx:105 to navigate to 'Dashboard' not 'Home'.
+2. Replace AsyncStorage with SecureStore for token storage in AuthService.ts:34.
+```
+
+---
+
+## Sorting Order in Report
+
+Sort test cases in this order within the report:
+1. FAIL — shown first (most critical)
+2. NOT_IMPLEMENTED — shown second
+3. BLOCKED — shown third
+4. PARTIAL_PASS — shown fourth
+5. UNKNOWN — shown fifth
+6. PASS — shown last
+
+Within each group, sort by TC-ID numerically.

package/.github/skills/code-test-coverage-analyzer/templates/user-story-compliance-row.md

@@ -0,0 +1,170 @@
+# User Story Compliance Row Template
+
+Use this template for each user story section in `03_USER_STORY_COMPLIANCE.md`.
+
+---
+
+## User Story Block Template
+
+```markdown
+---
+
+## Story {US-ID} — {Story Title}
+
+**As a** {role}
+**I want to** {goal}
+**So that** {value}
+
+**Related BRD**: {BRD-ID list or "None identified"}
+**Overall Status**: FULLY_SATISFIED | PARTIALLY_SATISFIED | NOT_SATISFIED | NOT_VERIFIABLE
+
+---
+
+### Acceptance Criteria
+
+| AC-ID | Criterion | Status | Evidence | Issues |
+|-------|-----------|--------|----------|--------|
+| {US-ID}-AC-01 | {exact AC text from document} | SATISFIED | {file + function} | {gap or "-"} |
+| {US-ID}-AC-02 | | | | |
+
+---
+
+### Business Flow Verification
+
+| Aspect | Required (from Story) | Implemented | Status | Evidence |
+|--------|-----------------------|-------------|--------|----------|
+| Entry Screen | {screen name} | {YES/NO/PARTIAL + file} | MATCH/MISMATCH/MISSING | {file path} |
+| Primary API | {method + endpoint} | {implemented endpoint} | | {file path} |
+| Core Validation | {validation rule} | {implemented rule} | | {file path} |
+| Success Navigation | {target screen} | {actual target} | | {file path} |
+| Error Handling | {expected error behavior} | {actual behavior} | | {file path} |
+| Loading State | {required/not required} | {YES/NO} | | {file path} |
+| Empty State | {required/not required} | {YES/NO} | | {file path} |
+
+---
+
+### Validation Detail
+
+| Field | Required Rule | Required Message | Implemented Rule | Implemented Message | Match |
+|-------|--------------|-----------------|-----------------|---------------------|-------|
+| {fieldName} | {e.g., required, min:6} | {exact message} | {found rule} | {found message} | EXACT/SIMILAR/MISMATCH/MISSING |
+
+---
+
+### Missing Elements
+
+{Bullet list of what is missing. If nothing is missing, write: "None — story is fully implemented."}
+
+- [ ] {Specific missing element with BRD-ID reference}
+- [ ] {Another missing element}
+
+---
+
+### Recommendation
+
+{Specific, actionable guidance. If nothing to do: "No action required."}
+
+---
+```
+
+---
+
+## Overall Status Determination Rules
+
+### FULLY_SATISFIED
+ALL acceptance criteria are SATISFIED.
+Business flow verification shows all aspects matched.
+
+### PARTIALLY_SATISFIED
+At least one AC is SATISFIED but not all ACs are SATISFIED.
+OR: All ACs satisfied but business flow has gaps (loading state missing, error handling incomplete).
+
+### NOT_SATISFIED
+Zero ACs are SATISFIED (all are NOT_SATISFIED or NOT_VERIFIABLE).
+OR: The core feature does not exist.
+
+### NOT_VERIFIABLE
+Cannot determine satisfaction from source code alone.
+AC describes a UX behavior, performance metric, or user emotion that cannot be read from code.
+
+---
+
+## Evidence Format Rules
+
+**Good evidence**:
+```
+src/features/loan/LoanApplicationScreen.tsx → submitApplication() — calls POST /loan/apply
+```
+
+**Bad evidence** (too vague):
+```
+LoanApplicationScreen exists
+```
+
+**Good AC evidence**:
+```
+src/validation/loanSchema.ts → loanSchema — has Yup required() + min(5000) on amount field
+```
+
+**Bad AC evidence**:
+```
+Validation exists in the project
+```
+
+---
+
+## Example Story Block
+
+```markdown
+---
+
+## Story US-007 — Apply for Personal Loan
+
+**As a** registered customer
+**I want to** apply for a personal loan online
+**So that** I can get funds without visiting a branch
+
+**Related BRD**: BRD-012, BRD-013, BRD-014
+**Overall Status**: PARTIALLY_SATISFIED
+
+---
+
+### Acceptance Criteria
+
+| AC-ID | Criterion | Status | Evidence | Issues |
+|-------|-----------|--------|----------|--------|
+| US-007-AC-01 | User can enter loan amount between 5,000 and 5,00,000 | SATISFIED | `LoanApplicationScreen.tsx:78` → amountInput with min/max Yup validation | - |
+| US-007-AC-02 | User can select loan tenure from 12 to 60 months | SATISFIED | `LoanApplicationScreen.tsx:95` → TenureDropdown with options 12,24,36,48,60 | - |
+| US-007-AC-03 | EMI is calculated and shown before submission | PARTIALLY_SATISFIED | `LoanCalculationService.ts:23` → calculateEMI() — formula implemented but not shown on screen until Submit tapped | EMI display is post-submit, not real-time |
+| US-007-AC-04 | System shows confirmation screen after successful application | NOT_SATISFIED | `LoanApplicationScreen.tsx:112` → navigates to HomeScreen, not LoanConfirmationScreen | LoanConfirmationScreen not found in codebase |
+
+---
+
+### Business Flow Verification
+
+| Aspect | Required | Implemented | Status | Evidence |
+|--------|----------|-------------|--------|----------|
+| Entry Screen | LoanApplicationScreen | YES | MATCH | `src/screens/loan/LoanApplicationScreen.tsx` |
+| Primary API | POST /loan/apply | POST /loan/apply | MATCH | `src/services/LoanService.ts:45` |
+| Core Validation | Amount 5000–500000 | YES | MATCH | `src/validation/loanSchema.ts:12` |
+| Success Navigation | LoanConfirmationScreen | HomeScreen (WRONG) | MISMATCH | `LoanApplicationScreen.tsx:112` |
+| Error Handling | Show API error message | Partial — 400 handled, 500 not | PARTIAL | `LoanApplicationScreen.tsx:125` |
+| Loading State | Required | YES — ActivityIndicator | MATCH | `LoanApplicationScreen.tsx:88` |
+| Empty State | Not required | N/A | N/A | - |
+
+---
+
+### Missing Elements
+
+- [ ] LoanConfirmationScreen not implemented (BRD-014 — confirmation after loan approval)
+- [ ] Real-time EMI calculation on screen (AC-03 gap)
+- [ ] HTTP 500 error handling in loan application flow
+
+---
+
+### Recommendation
+
+1. Create LoanConfirmationScreen and update navigation in LoanApplicationScreen.tsx:112.
+2. Wire calculateEMI() to amount and tenure inputs via onChange for real-time display.
+3. Add HTTP 500 catch block in LoanApplicationScreen.tsx:125.
+```

package/.github/skills/custom-font-integrator/SKILL.md

@@ -0,0 +1,373 @@
+---
+name: custom-font-integrator
+description: Set up and integrate custom .ttf fonts into React Native projects for both iOS and Android. Use this skill whenever a user provides .ttf font files and wants to use them in their Bare React Native app. Trigger when the user mentions custom fonts, .ttf files, adding fonts to React Native, font integration, or wants to use specific font families in their project. This skill handles file placement, configuration, and code examples for both platforms.
+compatibility: Requires a Bare React Native project (not Expo)
+---
+
+# React Native Custom Fonts Setup
+
+Integrate custom .ttf fonts into your Bare React Native project for both iOS and Android with proper configuration and usage examples.
+
+## Overview
+
+Custom fonts in React Native require platform-specific setup:
+- **iOS**: Add fonts to `Info.plist` and link them via Xcode
+- **Android**: Place fonts in `android/app/src/main/assets/fonts/`
+
+This skill handles the complete setup process and provides code examples for using your fonts.
+
+## Prerequisites
+
+- Bare React Native project (initialized with `npx react-native init`)
+- `.ttf` font files ready to integrate
+- Access to project files on both iOS and Android sides
+
+## Font Path Resolution (MANDATORY — before any setup step)
+
+Before running any step, resolve `<fontsPath>` using this priority order:
+
+1. **User-provided path** — if the user explicitly states a folder (e.g. `src/assets/fonts`, `assets/fonts`, `resources/fonts`), use that value as `<fontsPath>`.
+2. **Codebase scan** — if no path is provided, scan the project root for `.ttf` / `.otf` files recursively. Use the directory of the first match as `<fontsPath>`.
+3. **Default fallback** — if no font files are found on disk, use `assets/fonts` as `<fontsPath>` and create the folder.
+
+Emit one line before proceeding:
+```
+INFO: fontsPath resolved to '<fontsPath>' (source: user-provided | codebase-scan | default-fallback)
+```
+
+All commands, config snippets, and file references below use `<fontsPath>` as a placeholder. Replace it with the resolved value before applying.
+
+---
+
+## Already-Configured Check (MANDATORY — run after Font Path Resolution, before Setup)
+
+Before executing any setup step, build a **per-font status table** by checking each font file individually across both platforms. Only fonts that are missing from a platform are configured — already-present fonts are skipped entirely.
+
+### Step A — Enumerate fonts to integrate
+
+Collect the list of `.ttf` / `.otf` files from `<fontsPath>`. Each file is one font entry.
+
+Example input:
+```
+<fontsPath>/
+  Poppins-Regular.ttf
+  Poppins-Bold.ttf
+  Roboto-Regular.ttf
+```
+
+### Step B — Per-font status check
+
+For each font file `<FontFile>.ttf`, check three locations independently:
+
+| Location | PASS condition |
+|----------|----------------|
+| **Android** — `android/app/src/main/assets/fonts/<FontFile>.ttf` | File exists |
+| **iOS copy** — `ios/<AppName>/<FontFile>.ttf` | File exists |
+| **Info.plist** — `ios/<AppName>/Info.plist` (or `ios/<AppName>/<AppName>/Info.plist`) | `<string><FontFile>.ttf</string>` entry present inside `<key>UIAppFonts</key>` array |
+
+Build a status table before proceeding:
+
+```
+Font                   | Android | iOS copy | Info.plist | Action
+-----------------------|---------|----------|------------|-------
+Poppins-Regular.ttf    | PASS    | PASS     | PASS       | SKIP
+Poppins-Bold.ttf       | FAIL    | PASS     | PASS       | Android only
+Roboto-Regular.ttf     | FAIL    | FAIL     | FAIL       | Full setup
+```
+
+### Step C — Decision per font
+
+For each font entry in the table:
+
+- **All 3 PASS** → skip this font entirely; emit:
+  ```
+  INFO: Poppins-Regular.ttf already configured on all platforms. Skipping.
+  ```
+- **Android FAIL only** → copy file to `android/app/src/main/assets/fonts/` only
+- **iOS copy FAIL only** → copy file to `ios/<AppName>/` only
+- **Info.plist FAIL only** → add `<string><FontFile>.ttf</string>` entry to `UIAppFonts` only
+- **Multiple FAILs** → run only the failing sub-steps for that font
+- **All 3 FAIL** → run full setup for that font
+
+After the table, emit a summary:
+
+```
+INFO: 1 font(s) fully configured — skipped.
+INFO: 1 font(s) need Android copy only.
+INFO: 1 font(s) need full setup.
+```
+
+> **Rule**: Never copy or modify configuration for a font that already passes all 3 checks. Only act on the specific platform(s) where the check failed.
+
+---
+
+## Setup Process
+
+### Step 1: Organize Your Font Files
+
+Create a fonts directory in your project if it does not already exist:
+
+```bash
+mkdir -p <fontsPath>
+# Place your .ttf files here
+```
+
+Your project structure should look like:
+```
+MyApp/
+├── <fontsPath>/
+│   ├── MyFont-Regular.ttf
+│   ├── MyFont-Bold.ttf
+│   └── MyFont-Italic.ttf
+├── android/
+├── ios/
+├── App.js
+└── package.json
+```
+
+### Step 2: Android Setup
+
+#### Recommended: Link fonts via react-native.config.js (auto-copies to both platforms)
+
+Add an `assets` array to `react-native.config.js` in your project root (create the file if it doesn't exist):
+
+```javascript
+// react-native.config.js
+module.exports = {
+  assets: ['./<fontsPath>'],  // replace <fontsPath> with the resolved path, e.g. 'assets/fonts' or 'src/assets/fonts'
+};
+```
+
+> The skill fills in the exact resolved `<fontsPath>` value here — it is never hardcoded to `assets/fonts`.
+
+Then run:
+
+```bash
+npx react-native-asset
+```
+
+This automatically:
+- Copies fonts to `android/app/src/main/assets/fonts/`
+- Copies fonts to `ios/<AppName>/` and updates `Info.plist` UIAppFonts
+
+> **Re-run `npx react-native-asset` every time you add or remove a font file.**
+
+#### Manual fallback: Copy fonts to Android assets
+
+```bash
+mkdir -p android/app/src/main/assets/fonts
+cp <fontsPath>/*.ttf android/app/src/main/assets/fonts/
+```
+
+Android automatically recognizes fonts in this directory. No additional configuration needed!
+
+**Font naming for Android**: Use the exact filename (without .ttf extension) as the `fontFamily` in your StyleSheet.
+
+### Step 3: iOS Setup
+
+#### 1. Copy fonts to iOS project
+
+> Skip this step if you used `react-native-asset` above — it handles iOS automatically.
+
+```bash
+mkdir -p ios/<AppName>
+cp <fontsPath>/*.ttf ios/<AppName>/
+```
+
+Replace `<AppName>` with your actual Xcode target folder name (the folder containing `AppDelegate.swift` / `AppDelegate.m`). Using `ios/Fonts/` is **not** recommended — fonts must sit inside the app target bundle.
+
+#### 2. Add fonts to Xcode (Important!)
+
+1. Open `ios/YourProject.xcworkspace` in Xcode
+2. Select your project in the navigator
+3. Select your app target
+4. Go to **Build Phases** → **Copy Bundle Resources**
+5. Click the **+** button
+6. Select all `.ttf` files from the `ios/<AppName>` folder
+7. Ensure "Copy items if needed" is checked and files are added to your target
+
+#### 3. Update Info.plist
+
+Open `ios/YourProject/Info.plist` and add the following array (before the closing `</dict>`):
+
+```xml
+<key>UIAppFonts</key>
+<array>
+    <string>MyFont-Regular.ttf</string>
+    <string>MyFont-Bold.ttf</string>
+    <string>MyFont-Italic.ttf</string>
+</array>
+```
+
+**Important**: Use only the filename (with .ttf extension), not the full path.
+
+## Using Custom Fonts in Your Code
+
+Once setup is complete, use your fonts in StyleSheet:
+
+```javascript
+import React from 'react';
+import { View, Text, StyleSheet } from 'react-native';
+
+const styles = StyleSheet.create({
+  regularText: {
+    fontFamily: 'MyFont-Regular',
+    fontSize: 16,
+  },
+  boldText: {
+    fontFamily: 'MyFont-Bold',
+    fontSize: 18,
+    fontWeight: 'bold',
+  },
+  italicText: {
+    fontFamily: 'MyFont-Italic',
+    fontSize: 16,
+    fontStyle: 'italic',
+  },
+});
+
+export default function App() {
+  return (
+    <View>
+      <Text style={styles.regularText}>Regular Font</Text>
+      <Text style={styles.boldText}>Bold Font</Text>
+      <Text style={styles.italicText}>Italic Font</Text>
+    </View>
+  );
+}
+```
+
+## Font Naming Conventions
+
+### Android
+- Use the **exact filename** (without `.ttf`)
+- Example: `MyFont-Regular.ttf` → `fontFamily: 'MyFont-Regular'`
+
+### iOS
+- Use the **PostScript name** or **filename**
+- For most standard fonts, filename works fine
+- To check PostScript name: Double-click the `.ttf` file on Mac, look at the "PostScript name" field
+- Example: `fontFamily: 'MyFont-Regular'`
+
+## Troubleshooting
+
+### Font not appearing on Android
+- ✅ Check font file is in `android/app/src/main/assets/fonts/`
+- ✅ Verify `fontFamily` name matches filename exactly (case-sensitive)
+- ✅ Rebuild: `npx react-native run-android`
+
+### Font not appearing on iOS
+- ✅ Verify font file is in `ios/YourProject/` directory
+- ✅ Check font is added to "Copy Bundle Resources" in Build Phases
+- ✅ Verify `Info.plist` includes the font filename with `.ttf` extension
+- ✅ Try PostScript name if filename doesn't work
+- ✅ Clean build folder: `Cmd + Shift + K` in Xcode, then rebuild
+
+### Fallback fonts
+If a font isn't found, React Native falls back to the system default font. Always test on both platforms.
+
+## Quick Reference
+
+| Task | Command |
+|------|---------|
+| Create fonts directory | `mkdir -p <fontsPath> android/app/src/main/assets/fonts` |
+| Link fonts (recommended) | `npx react-native-asset` |
+| Copy fonts to Android (manual) | `cp <fontsPath>/*.ttf android/app/src/main/assets/fonts/` |
+| Copy fonts to iOS (manual) | `cp <fontsPath>/*.ttf ios/<AppName>/` |
+| Rebuild Android | `npx react-native run-android` |
+| Rebuild iOS | `npx react-native run-ios` |
+
+## Testing Your Fonts
+
+Create a test component to verify fonts are loaded:
+
+```javascript
+import React from 'react';
+import { View, Text, ScrollView, StyleSheet } from 'react-native';
+
+const TestFonts = ({ fonts }) => (
+  <ScrollView style={styles.container}>
+    {fonts.map((font) => (
+      <Text key={font} style={[styles.testText, { fontFamily: font }]}>
+        Testing: {font}
+      </Text>
+    ))}
+  </ScrollView>
+);
+
+const styles = StyleSheet.create({
+  container: { padding: 20, backgroundColor: '#fff' },
+  testText: { fontSize: 18, marginVertical: 10 },
+});
+
+export default TestFonts;
+```
+
+## Advanced: Font Weight and Style Fallback
+
+React Native allows you to use `fontWeight` and `fontStyle` properties to automatically select different font files:
+
+```javascript
+const styles = StyleSheet.create({
+  text: {
+    fontFamily: 'Montserrat',
+    fontSize: 16,
+    fontWeight: '600',  // Will attempt to load Montserrat-SemiBold if configured
+  },
+});
+```
+
+For this to work, you need to set up font matching in `react-native.config.js` (advanced):
+
+```javascript
+module.exports = {
+  project: {
+    ios: {},
+    android: {},
+  },
+  dependency: {
+    platforms: {
+      ios: {},
+      android: {},
+    },
+  },
+};
+```
+
+**Note**: React Native's automatic weight/style matching is limited. It's best to explicitly use different font family names for different weights.
+
+## Monospace Fonts
+
+If using monospace fonts (e.g., for code display):
+
+```javascript
+const styles = StyleSheet.create({
+  codeText: {
+    fontFamily: 'Courier-Regular',
+    fontSize: 12,
+  },
+});
+```
+
+Monospace fonts should work the same as regular fonts once properly configured.
+
+## Common Font File Naming Patterns
+
+| Pattern | Android fontFamily | iOS fontFamily |
+|---------|-------------------|----------------|
+| `Font-Regular.ttf` | `Font-Regular` | `Font-Regular` |
+| `Font-Bold.ttf` | `Font-Bold` | `Font-Bold` |
+| `Font.ttf` | `Font` | `Font` |
+| `FontRegular.ttf` | `FontRegular` | `FontRegular` |
+| `font_regular.ttf` | `font_regular` | `font_regular` |
+
+---
+
+**Next Steps**:
+1. Resolve `<fontsPath>` from user input, codebase scan, or default (see **Font Path Resolution** above)
+2. Place your `.ttf` files in `<fontsPath>/`
+3. Add `assets: ['./<fontsPath>']` to `react-native.config.js` and run `npx react-native-asset` (recommended), OR follow the manual Android and iOS setup steps above
+4. If using manual iOS setup: update `Info.plist` with font names
+5. Use the fonts in your StyleSheet by `fontFamily` name
+6. Rebuild and test both platforms
+7. Use the test component to verify all fonts load correctly