Step 2: Generate Features List with AI

The Features List transforms your product description into an actionable development plan that maximizes reuse of the boilerplate's 15 pre-built features and 69+ UI components.

Why This Step Matters

Instead of building everything from scratch, the AI will:

• ✅ Identify features you can REUSE as-is (~60-70% of features)
• 🎨 Flag features to CUSTOMIZE (adapt existing)
• 🆕 Isolate features to build NEW from scratch
• 🔗 Suggest ways to COMBINE existing features

Result: Save 4-8 weeks of development time by reusing existing infrastructure.

Prerequisites

The 4-Step Process

1. Read What's Available

IMPORTANT: Before running the prompt, read:

implemented_features.md

This file (in your project root) contains:

• 15 production-ready features (Auth, Onboarding, Paywall, Gamification, etc.)
• 69+ UI components (Button, Input, Modal, Card, etc.)
• 18+ infrastructure services (Storage, API, Sync, Analytics, etc.)

Spend 5-10 minutes scanning this to understand what you already have.

2. Copy the Boilerplate-Aware Prompt

Navigate to:

ai_rules/prompts/2_app_features_list_prompt.md

This enhanced prompt contains:

• Complete inventory of boilerplate features
• REUSE/CUSTOMIZE/NEW/COMBINE framework
• Feature mapping table generator
• Reuse percentage calculator

3. Run the Interactive Prompt

Paste the prompt into your AI assistant (ChatGPT o1/4o, Claude 3.5 Sonnet).

The AI will:

Step 0: Confirm boilerplate awareness

"I've reviewed the boilerplate's 15 features, 69+ components,
and offline-first architecture. My goal is to maximize reuse.
Are you ready to proceed?"

Step 1: Ask for your product_description.md

"Please paste the content of your product_description.md"

Step 2: Generate feature mapping table

| Product Feature      | Boilerplate Status | Action Required                    |
|----------------------|-------------------|------------------------------------|
| User Login           | REUSE             | Use existing auth feature          |
| Daily Challenges     | CUSTOMIZE         | Adapt Todos + Gamification         |
| Community Feed       | NEW               | Build from scratch                 |
| Meditation Timer     | COMBINE           | Merge Todos pattern + Notifications|

Step 3: Ask 5-10 clarifying questions (focused on NEW/CUSTOMIZE features only)

1. For Daily Challenges: What makes them different from regular todos?
2. For Community Feed: Do users need to be logged in?
3. For Meditation Timer: How does timing work? Background support needed?

AI-generated table identifying REUSE, CUSTOMIZE, and NEW features

Step 4: Generate comprehensive app_features_list.md

4. Save the Output

Save the generated content to:

ai_rules/app_approach/app_features_list.md

Or:

app_features_list.md (project root)

What the AI Generates

A comprehensive feature specification with:

📋 Feature Reuse Summary

**Total Features Needed**: 12
- ✅ REUSE (Use as-is): 5 features (~42% of development saved)
- 🎨 CUSTOMIZE (Adapt existing): 4 features (~33%)
- 🆕 NEW (Build from scratch): 2 features (~17%)
- 🔗 COMBINE (Merge existing): 1 feature (~8%)

**Estimated Development Time Saved**: 6-8 weeks thanks to boilerplate

2. Detailed Feature Breakdown

For each feature, you'll get:

Features to REUSE (No changes needed)

#### Authentication
- **Status**: ✅ REUSE
- **Boilerplate Location**: `src/features/auth/`
- **What's Included**: Apple/Google/Email login, Biometric auth
- **Configuration Needed**: Update Supabase keys, Firebase config
- **Estimated Setup Time**: 1-2 hours

Features to CUSTOMIZE (Adapt existing)

#### Onboarding
- **Status**: 🎨 CUSTOMIZE
- **Boilerplate Base**: `src/features/onboarding/`
- **Customization Needed**:
  - [ ] Update welcome screens (edit config/welcome-onboarding-config.ts)
  - [ ] Modify questionnaire questions
  - [ ] Adjust translations in src/locales/*.json
- **Estimated Time**: 2-3 days

Features to BUILD NEW

#### Meditation Timer
- **Status**: 🆕 NEW
- **Why New**: Unique audio player + background timer functionality
- **Reference Pattern**: Copy from `src/features/todos/` (offline-first)
- **UI Components to Reuse**: Button, Card, Progress, AnimatedModal
- **Estimated Time**: 1-2 weeks

3. Complete Development Plan

• Navigation structure
• Data architecture (Supabase tables + Redux slices)
• UI components strategy (which to reuse vs build)
• Monetization strategy (customize existing paywall)
• Analytics events (reuse existing + add custom)
• Development phases with realistic timelines

Example Output

3. Maximum Reuse Tips

1. Don't Reinvent the Wheel: If the AI suggests CUSTOMIZE, ask "Can I reuse X feature instead?"
2. Leverage UI Components: Always use the 69+ existing components before building custom UI
3. Follow Reference Patterns: For new features, copy architecture from src/features/todos/
4. Combine Smartly: Many "new" features are just combinations of existing ones

Visualizing the feature mapping process

Common Patterns

What's Next?

Once you have your app_features_list.md, proceed to:

Troubleshooting

Q: The AI isn't categorizing features as REUSE/CUSTOMIZE/NEW A: Make sure you pasted the entire prompt from 2_app_features_list_prompt.md. The enhanced version has this framework built-in.

Q: It says "80% of features are NEW" - that seems wrong A: Ask the AI: "Did you review implemented_features.md? Can any of these map to existing Auth, Onboarding, Settings, Paywall, or Gamification features?"

Q: Can I change categorization if I disagree? A: Yes! If the AI says NEW but you think you can CUSTOMIZE, ask it to reconsider with specific reasoning.

Q: The output is too long A: That's normal. app_features_list.md is comprehensive (often 500-800 lines). It's your complete development blueprint.