Skip to content

feedback: used iceCoder to execute a ROADMAP on a Flutter project #43

Description

@Guo-Zhang

Task

We asked iceCoder to execute the ROADMAP of a Flutter game project (qtgame-war). The ROADMAP had 3 items: refactor game module (rename campaign-specific field names, wire effectiveMoveRange to campaign.moveMod), clean up dead code, and update docs/tests.

Result

17 files changed, +178 -337, all 42 Flutter tests passed.

Commit: quanttide/qtgame-war@c07b235

Quality assessment

Dimension Grade Notes
Consistency A Cross-file rename covered all 17 files without miss
Backward compat A JSON schema key kept as initial_huaye_power, only Dart field renamed
Safety A effectiveMoveRange uses clamp(1, 99) to prevent negative values
Tests A All 42 tests updated and passing
Docs A Clean the docs with better results

Pain points

1. .iceCoder/ and data/ directory pollution

iceCoder created .iceCoder/ (mcp.json, memory.md) and data/ (config, sessions, telemetry, etc.) in the working directory. These are runtime artifacts that must be manually cleaned up before committing. In a project with src/, docs/, tests/, these auto-created directories add noise.

Suggestion: respect ICE_DATA_DIR / ~/.iceCoder/ even when running in dev mode. Currently it only uses ~/.iceCoder/ when detected as packaged CLI entry. If a user is running from a project directory, the default should still be ~/.iceCoder/ (or at least a .gitignore-friendly name).

2. Prerequisites for getting it to work

We needed two patches to make iceCoder functional:

These may be specific to our setup (npm link, DeepSeek API via env var), but worth noting for improving first-run experience.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions