VeryGoodOpenSource / VeryGoodOpenSource/vgv-ai-flutter-plugin

perf: reduce token usage

Open
#81 0 comments 0 reactions 1 assignee View on GitHub

@ryzizub is already working on this.

Since Apr 15, 2026.

p2 performance
Dominant language
Shell
Stars
162
Forks
23
Avg merge
2d 22h
Merged PRs (30d)
4

Description

Problem

One quick analysis on layered-architecture skill showed up that nearly 150 lines can be reduced, layered-architecture/SKILL.md shows inline code that is nearly identical to what's already in its own reference files.

UserApiClient — shown in SKILL.md:146-171 AND worked-example.md:78-117
// Both files show UserApiClient with constructor-injected http.Client,
// getUser method, statusCode != 200 check, UserResponse.fromJson

User domain model — shown in SKILL.md:193-208 AND worked-example.md:222-242

UserRepository — shown in SKILL.md:212-231 AND worked-example.md:262-288

ProfileBloc _onLoadRequested — shown in SKILL.md:286-299 AND worked-example.md:373-386

main_development.dart bootstrap — shown in SKILL.md:308-345 AND worked-example.md:469-489

pubspec.yaml dependency graph — shown in SKILL.md:240-270 AND pubspec.md:1-104 (same patterns, different domain names:
user vs weather). Then worked-example.md shows them a third time.

The SKILL.md already links to these references, but then shows 80-90% of the same code inline.

Solution

Run analysis on skills to try to apply some best practices:

  • duplicate reference files,
  • near identical instructions,
  • repeated patterns,
  • bash heavy sections → scripts
  • prose tightening
    It would be good to run same analysis over other skills

Trim inline examples in SKILL.md to short signature-level snippets (3-5 lines showing the key pattern) and rely on the existing reference links for full implementations. This would cut ~120-150 lines from layered-architecture/SKILL.md without losing any content — it's all still available in the reference files.

Requirements
  • All CI/CD checks are passing.
  • There is no drop in the test coverage percentage.
Additional Context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.