MVP Slimdown Procedure (TrustFlow)
- •Create a working branch:
git switch -c chore/mvp-slimdown - •List unused/redundant components and modals
- •Move unnecessary files to archive/
- •Remove all imports and usage references
- •Skip/simplify flows outside MVP (e.g., BiometricModal)
- •Clean up props and dummy/mock data
- •Update documentation to match current state
- •Commit at each logical milestone
Tips:
- •Archived files can be restored from archive/
- •Make small, frequent commits
- •Centralize rules in copilot-instructions.md
Last updated: 2026-02-10# Skill: MVP Slimdown Procedure
Purpose
Standardize the process for reducing a project to its Minimum Viable Product (MVP) core, ensuring maintainability and clarity.
When to Use
- •When you want to minimize project features and structure
- •When you need to temporarily archive unused components or visual effects
- •When preparing for an MVP release and need to clean up
Steps
- •Create a working branch
- •
git switch -c chore/mvp-slimdown
- •
- •List up unused/redundant components and modals
- •Create an archive/ directory and move unnecessary files there
- •Remove all imports and usage references
- •Skip or simplify flows outside MVP (e.g., BiometricModal)
- •Clean up props and dummy/mock data
- •Update documentation to match the current state
- •Commit at each logical milestone
Tips
- •Archived files can be restored from archive/ at any time
- •Make small, frequent commits
- •Centralize rules and guidelines in copilot-instructions.md