feature-expansion

Expand an MVP into Phase 2 with screens, components, navigation, and Supabase migrations.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/fosejary/simple-todo --skill feature-expansion-fosejary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-expansion
Source: https://github.com/fosejary/simple-todo/tree/main/.claude/skills/feature-expansion
Command: npx skills add https://github.com/fosejary/simple-todo --skill feature-expansion-fosejary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the need to turn Phase 2 roadmap and new user requirements into a coherent set of app changes—screens, components, navigation, and Supabase database updates—without breaking existing MVP behavior.

Core Features & Use Cases

  • Phase 2 feature selection & mini-design: Re-evaluates Phase 2 items from an audit report, prioritizes high-value and integration-friendly work, and produces per-feature mini design plans (UI, components, data model, navigation, dependencies).
  • Supabase data model expansion with safety: Adds or modifies tables/columns via non-destructive migrations, includes required RLS policies, and keeps TypeScript types in sync.
  • App UI implementation & integration: Adds Expo Router screens under app/, builds feature components, introduces fetching hooks and stores when needed, and integrates links/navigation while minimizing impact to existing screens.
  • Team handoff for quality: After implementation, requests follow-up from production, performance, and growth agents for error handling/security, UI/performance optimization, and analytics event tracking.

Quick Start

Use the feature-expansion skill to design and implement the MVP Phase 2 functionality by updating screens, components, Supabase migrations (including RLS), and navigation, and then saving the results to the feature report.

Frequently Asked Questions about feature-expansion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add new UI screens to an Expo Router app without breaking existing navigation?

To add new Expo Router screens without breaking existing navigation, integrate new feature modules under the `app/` directory and build feature components with fetching hooks. This approach minimizes impact on current screens while safely expanding app workflows.

What is the safest way to expand a Supabase schema with row level security policies during an MVP update?

The safest way to expand a Supabase schema with row level security policies is through non-destructive SQL migrations. This approach adds required RLS policies, modifies tables or columns, and keeps TypeScript types synchronized without breaking existing MVP behavior.

How do I plan Phase 2 app features from a roadmap for implementation?

To plan Phase 2 app features, re-evaluate items from an audit report and prioritize high-value, integration-friendly work. This generates per-feature mini design plans covering UI, components, data models, and navigation dependencies for codebase-aligned implementation.

Can I use TypeScript strict mode when adding Supabase data models and Expo Router screens?

Yes, you can use TypeScript strictness when adding Supabase data models and Expo Router screens. Feature expansion requires deterministic, codebase-aligned implementation that keeps TypeScript types synchronized with safe non-destructive SQL migrations.

What should I do after implementing new feature modules and Supabase migrations?

After implementing new feature modules and Supabase migrations, you should request follow-up from production, performance, and growth agents. This team handoff ensures coordinated error handling, security checks, UI performance optimization, and analytics event tracking.