Flutter feature analysis

Skill Desquared/agents-rules-skills/skills/flutter-feature-analysis

Use when assessing feasibility or complexity of a new Flutter feature before implementation. Especially when evaluating API requirements, state management approach, UI component availability, native dependencies, or effort estimation.From its SKILL.md

Install

npx -y skills add Desquared/agents-rules-skills --skill flutter-feature-analysis

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, as published. Nobody here has run it

Feature Analysis Skill

Analysis Framework

1. Discovery

grep -r "<similar_feature>" lib/features/    # Find patterns
grep "<package>" pubspec.yaml                # Check dependencies
find lib -path "*/domain/models/*.dart"      # Review models

2. Complexity Assessment

Simple:

Single API call, straightforward UI, minimal state
Example: Display static model details
State Management: Simple solution (Cubit, ChangeNotifier, GetxController)

Complex:

Multiple API calls, state orchestration, complex business rules
Example: Multi-step flow
State Management: Robust solution (Bloc with events, StateNotifier, complex GetX)

3. Technical Checklist

API endpoint exists?
DTO/Model mapping needed?
Repository pattern required?
State management approach? (Check existing patterns in project)
UI components available in design system?
Native platform features needed?
Accessibility considerations?
Performance implications?

4. Dependencies

Check pubspec.yaml for existing vs new packages
Check native side: plugin/ios/, plugin/android/

5. Output Format

# Feature Analysis: [Name]

## Feasibility: ✅ / ⚠️ / ❌

##State Management**: [Based on project patterns: Bloc/Provider/GetX/Riverpod]
**Rationale**: [Why this approach fits]

## Technical Requirements
- API: [endpoint]
- New Models: [list]
- UI Components: [available/needed]
- Native Features: [yes/no]
- State Management: [Match existing patternse/needed]
- Native Features: [yes/no]

## Dependencies
- Existing: [packages]
- New: [packages]

## Risks
1. [Risk]
2. [Risk]

## Estimated Effort
- Development: X hours
- Testing: Y hours