implement-widget

Enforce reusable Flutter widget architecture with StatelessWidget and StatefulWidget guidelines.

Updated Apr 1, 2026

Search Tags:#architecture #i18n #widget #flutter #stateful #stateless #dispose

Ready to run

npx skills add https://github.com/andrelucassvt/CleanMacForDevsWeb --skill implement-widget

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-widget
Source: https://github.com/andrelucassvt/CleanMacForDevsWeb/tree/main/.agents/skills/implement-widget
Command: npx skills add https://github.com/andrelucassvt/CleanMacForDevsWeb --skill implement-widget

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flutter developers often waste time rewriting similar widget blocks instead of focusing on business logic. This skill codifies architecture and best practices to create reusable widgets that stay clean, testable, and consistent across features.

Core Features & Use Cases

Enforces when to use StatelessWidget vs StatefulWidget based on internal state.
Encourages passing an entire Entity as a parameter for flexibility and reusability.
Highlights i18n, proper disposal, and cubit access separation for safer code.
Guides widget organization and accessibility across presentation layers.

Quick Start

Create a reusable Flutter widget following the architecture guidance for the target feature.

Frequently Asked Questions about implement-widget

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

FAQPage Schema

When should I use StatelessWidget vs StatefulWidget in Flutter?▼

Passing a whole entity as a widget parameter increases reusability and flexibility. This architecture lets widgets adapt to entity changes without modifying parameter signatures across multiple presentation layers.

How do I structure reusable Flutter widgets for consistency?▼

Structure reusable Flutter widgets by enforcing project organization, frontmatter naming, and template guidelines. This ensures consistency, testability, and maintainability across all presentation layers in your application.

Do I need to handle disposal and i18n for every Flutter widget?▼

You must handle disposal and i18n for Flutter widgets to ensure safe code. Proper disposal prevents memory leaks, while i18n integration guarantees widgets support multiple languages across different features.

What is the best way to separate Cubit access in Flutter widgets?▼

The best way to separate Cubit access is isolating it within specific presentation layers. This safe usage pattern prevents tight coupling, keeping business logic separate from reusable widget architecture.