ai-flow-dev 2.1.3 → 2.1.5

package/prompts/mobile/flow-build-phase-5.md

@@ -3,9 +3,7 @@
 **Duration:** 15-20 minutes
 **Questions:** ~10 questions
 **Output:** docs/code-standards.md, parts of ai-instructions.md
-
----
-
+---
 ## 🎯 Objective
 
 Define coding conventions and standards for your mobile app:
@@ -15,9 +13,7 @@ Define coding conventions and standards for your mobile app:
 3. Import organization
 4. Commit message standards
 5. Mobile-specific best practices
-
----
-
+---
 ## 📋 Questions
 
 ### Question 5.1: File Naming Convention
@@ -25,6 +21,7 @@ Define coding conventions and standards for your mobile app:
 **How will you name your files?**
 
 **If React Native:**
+
 - A) ⭐ **PascalCase for components** (Recommended)
   - Components: `UserProfile.tsx`, `Button.tsx`
   - Screens: `HomeScreen.tsx`, `ProfileScreen.tsx`
@@ -35,36 +32,40 @@ Define coding conventions and standards for your mobile app:
   - Components: `user-profile.tsx`, `button.tsx`
 
 **If Flutter:**
+
 - A) ⭐ **snake_case** (Dart convention)
   - Files: `user_profile.dart`, `home_screen.dart`
   - Classes: `UserProfile`, `HomeScreen`
 
 **If Native iOS:**
+
 - A) ⭐ **PascalCase** (Swift convention)
   - Files: `UserProfile.swift`, `HomeViewController.swift`
 
 **If Native Android:**
+
 - A) ⭐ **PascalCase for classes, camelCase for files** (Kotlin convention)
   - Files: `UserProfile.kt`, `HomeActivity.kt`
 
 **Your answer:**
-
----
-
+---
 ### Question 5.2: Component/Screen Naming Convention
 
 **How will you name components and screens?**
 
 **If React Native:**
+
 - A) ⭐ **PascalCase** (Recommended)
   - Components: `<UserProfile />`, `<Button />`
   - Screens: `<HomeScreen />`, `<ProfileScreen />`
 
 **If Flutter:**
+
 - A) ⭐ **PascalCase for widgets**
   - Widgets: `UserProfile`, `HomeScreen`
 
 **If Native:**
+
 - A) ⭐ **PascalCase for classes**
   - iOS: `UserProfileViewController`
   - Android: `UserProfileActivity`
@@ -74,7 +75,9 @@ Define coding conventions and standards for your mobile app:
 **Named exports vs default exports?**
 
 **If React Native:**
+
 - A) ⭐ **Named exports** (Recommended)
+
   ```typescript
   export const Button = () => { ... }
   // Usage: import { Button } from './Button'
@@ -86,14 +89,13 @@ Define coding conventions and standards for your mobile app:
   ```
 
 **Your answer:**
-
----
-
+---
 ### Question 5.3: Linting & Formatting
 
 **What linting/formatting tools will you use?**
 
 **If React Native:**
+
 - A) ⭐ **ESLint + Prettier** (Recommended)
   - ESLint: Code quality rules
   - Prettier: Code formatting
@@ -101,31 +103,34 @@ Define coding conventions and standards for your mobile app:
 - B) **Biome** (All-in-one, faster)
 
 **If Flutter:**
+
 - A) ⭐ **dart format** (Built-in)
 - B) **dart analyze** (Linting)
 
 **If Native iOS:**
+
 - A) ⭐ **SwiftLint** (Recommended)
 - B) **SwiftFormat**
 
 **If Native Android:**
+
 - A) ⭐ **ktlint** (Recommended)
 - B) **Detekt**
 
 **Your answer:**
 
 **ESLint config (if React Native):**
+
 - A) ⭐ **@react-native-community/eslint-config**
 - B) **eslint-config-airbnb**
 - C) **Custom config**
-
----
-
+---
 ### Question 5.4: Import Organization
 
 **How will you organize imports?**
 
 **If React Native:**
+
 ```typescript
 // 1. External libraries
 import React from 'react';
@@ -143,6 +148,7 @@ import type { User } from '@/types';
 ```
 
 **If Flutter:**
+
 ```dart
 // 1. Dart SDK
 import 'dart:async';
@@ -159,18 +165,19 @@ import 'package:myapp/services/auth_service.dart';
 **Your answer:**
 
 **Import alias for src/?**
+
 - `@/` (React Native)
 - `~/` (Alternative)
 - No alias (relative paths only)
-
----
-
+---
 ### Question 5.5: TypeScript/Dart Strictness
 
 **How strict should TypeScript/Dart be?**
 
 **If React Native (TypeScript):**
+
 - A) ⭐ **Strict mode** (Recommended)
+
   ```json
   {
     "strict": true,
@@ -182,6 +189,7 @@ import 'package:myapp/services/auth_service.dart';
 - C) **Lenient**
 
 **If Flutter (Dart):**
+
 - A) ⭐ **Strict analysis** (Recommended)
   ```yaml
   analyzer:
@@ -192,44 +200,43 @@ import 'package:myapp/services/auth_service.dart';
 **Your answer:**
 
 **`any` type policy (TypeScript):**
+
 - A) ❌ Never allow `any`
 - B) ⚠️ Allow with warning
 - C) ✅ Allow freely (not recommended)
-
----
-
+---
 ### Question 5.6: Code Comments
 
 **What's your commenting policy?**
 
 A) ⭐ **JSDoc for public APIs, inline for complex logic** (Recommended)
-   ```typescript
-   /**
-    * Fetches user data from the API
-    * @param userId - The user's unique identifier
-    * @returns User object or null if not found
-    */
-   export async function fetchUser(userId: string): Promise<User | null> {
-     // Check cache first
-     const cached = cache.get(userId);
-     if (cached) return cached;
-     return api.get(`/users/${userId}`);
-   }
-   ```
+
+```typescript
+/**
+ * Fetches user data from the API
+ * @param userId - The user's unique identifier
+ * @returns User object or null if not found
+ */
+export async function fetchUser(userId: string): Promise<User | null> {
+  // Check cache first
+  const cached = cache.get(userId);
+  if (cached) return cached;
+  return api.get(`/users/${userId}`);
+}
+```
 
 B) **JSDoc everywhere**
 C) **Minimal comments**
 D) **No comment policy**
 
 **Your answer:**
-
----
-
+---
 ### Question 5.7: Component/Screen Structure
 
 **How will you structure components and screens?**
 
 **If React Native:**
+
 ```
 screens/
 ├── HomeScreen/
@@ -240,6 +247,7 @@ screens/
 ```
 
 **If Flutter:**
+
 ```
 lib/
 ├── screens/
@@ -248,35 +256,35 @@ lib/
 ```
 
 **Your answer:**
-
----
-
+---
 ### Question 5.8: Error Handling Patterns
 
 **How will you handle errors?**
 
 **If React Native:**
+
 - A) ⭐ **Error Boundaries + Try-Catch**
   - Error Boundaries for render errors
   - Try-Catch for async errors
 
 **If Flutter:**
+
 - A) ⭐ **Try-Catch + Global Error Handler**
   - FlutterError.onError for global errors
 
 **If Native:**
+
 - A) ⭐ **Try-Catch + Crash Reporting**
   - Sentry, Firebase Crashlytics
 
 **Your answer:**
 
 **Error logging:**
+
 - Firebase Crashlytics
 - Sentry
 - Console only (development)
-
----
-
+---
 ### Question 5.9: Mobile-Specific Best Practices
 
 **What mobile-specific practices will you enforce?**
@@ -295,23 +303,23 @@ Select all that apply:
 - [ ] **Push Notifications:** Handle notification taps
 
 **Your answer:**
-
----
-
+---
 ### Question 5.10: Commit Message Convention
 
 **What commit message format will you use?**
 
 A) ⭐ **Conventional Commits** (Recommended)
-   ```
-   <type>(<scope>): <subject>
-   
-   <body>
-   
-   <footer>
-   ```
-   - Types: feat, fix, docs, style, refactor, test, chore
-   - Example: `feat(auth): add biometric login`
+
+```
+<type>(<scope>): <subject>
+
+<body>
+
+<footer>
+```
+
+- Types: feat, fix, docs, style, refactor, test, chore
+- Example: `feat(auth): add biometric login`
 
 B) **Simple descriptive**
 C) **No convention**
@@ -319,21 +327,19 @@ C) **No convention**
 **Your answer:**
 
 **Enforce with:**
+
 - commitlint (pre-commit hook)
 - Manual review
 - No enforcement
-
----
-
+---
 ## ✅ Phase 5 Completion
 
 After answering all questions, summarize:
 
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+---
 ✅ Phase 5 Complete: Code Standards
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
+---
 Selected Standards:
 - File Naming: PascalCase for components
 - Linting: ESLint + Prettier
@@ -344,24 +350,18 @@ Selected Standards:
 
 Proceed to Phase 6 (Testing Strategy)? (Y/n)
 ```
-
----
-
+---
 ## 📝 Generated Documents
 
 After Phase 5, generate/update:
 
 - `docs/code-standards.md` - Code standards and conventions
 - `ai-instructions.md` - Add code standards rules
-
----
-
+---
 **Next Phase:** Phase 6 - Testing Strategy
 
 Read: `.ai-flow/prompts/mobile/flow-build-phase-6-testing.md`
-
----
-
+---
 **Last Updated:** 2025-01-XX
 
 **Version:** 1.4.0