Rapid Development

Code Patterns

Pattern 1: Mock with Early Return

The preferred pattern for mocked implementations. Real code stays commented out below the mock return.

async function getStockQuote(symbol: string) {
  // TODO: MVP - Replace mock data with Twelve Data API call
  return getMockQuote(symbol);

  // Real implementation (uncomment when ready):
  // const response = await fmpApi.quote(symbol);
  // if (!response.ok) {
  //   throw new Error(`Failed to fetch quote for ${symbol}`);
  // }
  // return response.data;
}

Pattern 2: Conditional Mock (for gradual rollout)

Use when you want to toggle between mock and real implementation:

async function getStockQuote(symbol: string) {
  // TODO: MVP - Remove mock condition when Twelve Data API ready
  const USE_MOCK = true; // Set to false to use real API

  if (USE_MOCK) {
    return getMockQuote(symbol);
  }

  const response = await fmpApi.quote(symbol);
  if (!response.ok) {
    throw new Error(`Failed to fetch quote for ${symbol}`);
  }
  return response.data;
}

Pattern 3: Partial Mock

When some data is real but other parts are mocked:

async function getStockAnalysis(symbol: string) {
  const profile = await getCompanyProfile(symbol); // Real API

  // TODO: MVP - Replace mock financials with Twelve Data API
  const financials = getMockFinancials(symbol);
  // Real implementation:
  // const financials = await fmpApi.financials(symbol);

  return { profile, financials };
}

Pattern 4: Placeholder Constants

For data that needs verification before production:

// ⚠️ PLACEHOLDER DATA - Needs verified sector benchmarks from industry research
export const SECTOR_GROWTH_BENCHMARKS: Record<Sector, number> = {
  Technology: 0.15,
  Healthcare: 0.12,
  Financials: 0.08,
  // ...
};

Mock Data Location

Mock file naming: {feature}.mock.ts or {feature}.mock.json

Finding TODO Markers

Search for all MVP-related markers in the codebase:

# Find all TODO: MVP markers
grep -r "TODO: MVP" --include="*.ts" --include="*.tsx"

# Find all TODO: FINALIZE markers
grep -r "TODO: FINALIZE" --include="*.ts" --include="*.tsx"

# Find all placeholder data markers
grep -r "PLACEHOLDER DATA" --include="*.ts"

Finalization Checklist

When finalizing a feature (removing mocks, going to production):

Step 1: Identify All Mocks

grep -r "TODO: MVP" apps/web/src/features/{feature-name}
grep -r "TODO: MVP" apps/api/src/integrations/{feature-name}

Step 2: For Each Mock

1. Delete the mock return line
2. Uncomment the real implementation
3. Remove the TODO: MVP comment
4. Test the real implementation
5. Add TODO: FINALIZE if needs review

Step 3: Clean Up

1. Remove unused mock data files
2. Update imports (remove mock imports)
3. Run tests to verify functionality
4. Update documentation if needed

Step 4: Final Review

1. Search for any remaining TODO: MVP in the feature
2. Verify no dead mock code remains
3. Mark feature as finalized in conversation

Finalization Communication

When the user says a feature is finalized:

1. User explicitly states: "This feature is finalized" or similar
2. Claude Code runs the finalization checklist above
3. Documentation is updated to mark the feature as production-ready
4. Any remaining TODO: MVP markers are addressed or flagged

When This Skill Becomes Obsolete

This skill should be deleted when:

1. StockFind exits MVP/POC phase
2. All TODO: MVP markers have been resolved
3. Real API integrations are complete (Twelve Data, Stripe production, etc.)
4. The project moves to maintenance/growth phase

To delete: Remove the .claude/skills/rapid-development/ directory and update the skill reference tables in CLAUDE.md files.