VeryGoodOpenSource / VeryGoodOpenSource/vgv-ai-flutter-plugin

feat: sync and reference Very Good Engineering content

Open
#158 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

external dependency feature
Dominant language
Shell
Stars
162
Forks
23
Avg merge
2d 22h
Merged PRs (30d)
4

Description

What

Pull the latest published Very Good Engineering standards at session start, and have skills read them instead of restating standards inline.

Why

Skills here restate VGE standards in their own words. layered-architecture opens with a Core Standards list covering the four layers and dependency direction, which is the VGE Layered Architecture page rewritten. Those copies drift the moment VGE changes, and shipping a plugin release for every standards edit does not scale. Plugins are also not updated reliably on local machines, so the content has to reach them without a release.

How

  • A SessionStart hook runs a sync script before any work begins.
  • The script compares the locally cached VGE version against the published one.
  • Minor difference: download and overwrite the cache.
  • Major difference: keep the cached copy and wait for a plugin release, since a new or rewritten section may need skills rewired.
  • The cache lives outside the plugin directory so it survives reinstalls.
  • Skills read the cache rather than restating standards.

Sync must fail open. A network failure, a slow response, or an offline machine cannot block the session or the hook's time budget.

Sections

Development and Architecture.

Tasks

  • Add the sync script and wire it to SessionStart
  • Pin the VGE version this plugin was built against
  • Hold on a major difference, sync on a minor one
  • Fail open on any network or parse error
  • Point skills and review agents at the cache instead of restating standards

Blocked

Waiting on work in Very Good Engineering to publish versioned, downloadable bundles. Nothing here is implementable until that lands.

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.

Research direction

Start by inspecting the existing SessionStart hook wiring, sync entry point, cache handling, and skill definitions. The issue is blocked until Very Good Engineering publishes versioned downloadable bundles. Done means the hook and skills use the versioned cache, major updates are held, minor updates sync, and failures do not block a session.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.