Skip to content
Agentmart
Submit a tool

ftk-refactor-legacy

Migrate an existing Flutter project toward FTK standards (feature-first, Riverpod, dio) one feature at a time, behind characterization tests.

Skill by adiwirya

IndexedMIT
Write a review

Chalk Labs

Need help deploying ftk-refactor-legacy?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/adiwirya-ftk-refactor-legacy

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Migrate an existing Flutter project toward FTK standards (feature-first, Riverpod, dio) one feature at a time, behind characterization tests. Use on legacy codebases — never for greenfield.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/ftk-refactor-legacy

What's inside

Skill name
ftk-refactor-legacy
Description
Migrate an existing Flutter project toward FTK standards (feature-first, Riverpod, dio) one feature at a time, behind characterization tests. Use on legacy codebases — never for greenfield.
License
MIT
Instructions
26 lines in SKILL.md · view on GitHub

Before installing

  • Instructions read files in your home folder (~/.ssh, ~/.aws…)

Files (1)

  • SKILL.md

SKILL.md (first lines)

Incremental migration. The app must run after EVERY stage; big-bang rewrites are forbidden.

Resolve the toolkit root from `toolkitPath` in `~/.config/flutter-tools-kit/ftk-settings.json`, then read `knowledge/architecture.md` and `knowledge/riverpod-patterns.md` from it.

## 1. Map (first run only)

Dispatch `ftk-codebase-researcher` to map current conventions: state management in use, folder layout, HTTP client, DI, test coverage. Present the map plus a migration order proposal (leaf features with fewest dependents first). Agree the scope: ONE feature per run.

## 2. Safety net

Before touching the feature: characterization tests that pin its CURRENT observable behavior (repository outputs, notifier/bloc state transitions, key widget rendering). These tests define "still works" — write them against behavior, not implementation.

## 3. Migrate in stages (verify after each: analyze clean, tests green, app boots)

1. **Structure:** move the feature's files into `lib/features/<feature>/{data,domain,presentation}` — imports only, no logic changes.
2. **State:** re-implement the feature's state in Riverpod per `knowledge/riverpod-patterns.md`. Old and new state solutions may coexist ACROSS features (adapter at the boundary), never within one.
3. **Network:** route the feature's HTTP through a repository backed by the shared `dioProvider` (create `core/network/` if this is the first feature).
4. Delete the dead old code the same run — do not leave both paths alive within the migrated feature.

## 4. Finish

Run the FULL suite plus the characterization tests, then re-run the app through the feature's main flow. Report: what moved, adapters introduced (and when they can die), conventions found that deviate from FTK (recorded, not silently "fixed"), and the recommended next feature.

Out of scope, always: refactoring features not in the agreed scope; upgrading packages (that is ftk-update-deps); visual changes.

From adiwirya/flutter-tools-kit, MIT.

More from adiwirya/flutter-tools-kit

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jul 10, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from adiwirya

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get ftk-refactor-legacy running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying ftk-refactor-legacy?

CallGet help
Cite this page

ftk-refactor-legacy skill. Agent Mart. https://agentmart.dev/skills/adiwirya-ftk-refactor-legacy (last updated 2026-10-24)