start-flutter-craft

To ensure your Flutter development workflow starts with proper skill discovery, use a guided skill invocation process that mandatorily identifies and triggers applicable Flutter craft skills before providing any response. This enforces standardized tool usage at the outset of your interaction.

The best way to route Flutter feature planning requests accurately is to enforce a mandatory skill invocation workflow before replying. This standardized discovery process aligns Flutter capabilities and supports early clarification within a Clean Architecture mindset.

You standardize Flutter project setup and debugging conversations by directing every interaction to formally discover and invoke Flutter craft skills prior to any answer. This workflow includes announcing the invoked skill and tracking tasks throughout the discussion.

This guided Flutter workflow requires no specific external dependencies or components. It functions as an intermediate-level mechanism that enforces the Skill tool invocation internally, requiring only your Flutter-related queries to operate effectively.

You should not use a mandatory skill invocation workflow for Flutter tasks when you need immediate, direct answers without formal skill discovery and task tracking. This approach enforces a structured routing process that may add overhead to simple inquiries.