Optimize Reduce waste and improve efficiency. Only optimize after you have real users and real problems — premature optimization is the most common waste of founder time. This skill is for making existing things faster and leaner. For building features, use build . For fixing bugs, use debug . For monitoring performance in production, use monitor . For database schema design, use database . Workflow When to Optimize (and When NOT To) Don't optimize when: - Building your MVP - Fewer than 100 active users - Everything works fine - You haven't measured the problem Optimize when: - Users complain…