agentleFS
Sign inStart free
p10ns11yp10ns11y/skills/mvu-refactor-plan/SKILL.md

mvu-refactor-plan

Skill2 starsChanged 40 days agoMITView on GitHub

Plan and implement CMake + elomaxz MVU refactors in C codebases. Use when user references elomaxz, MVU, CMake refactor plan, or attached implementation plan.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the attached plan and existing CMakeLists.txt, model, and app entry points.

    line 16
  2. Distinctive:

    Run build; fix compiler errors before next step.

    line 19
  3. Distinctive:

    Update README/license only after core build passes.

    line 20
  4. Distinctive:

    Follow elomaxz naming and MVU boundaries from the plan — do not invent parallel architecture.

    line 24
  5. Distinctive:

    Prefer minimal diffs; avoid drive-by reformat of unrelated C files.

    line 25
  6. Distinctive:

    If ColumnLimit breaks signatures, fix layout in context — do not truncate identifiers.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MVU refactor (CMake + elomaxz)

When to use

  • User attaches or references an implementation plan for CMake + elomaxz MVU
  • Refactoring model/view/update structure in a C project
  • Integrating patterns from the elomaxz library

Steps

  1. Read the attached plan and existing CMakeLists.txt, model, and app entry points.
  2. Grep for symbols mentioned in the plan before moving files.
  3. Implement in small steps: CMake → headers → .c → build after each logical chunk.
  4. Run build; fix compiler errors before next step.
  5. Update README/license only after core build passes.

Constraints

  • Follow elomaxz naming and MVU boundaries from the plan — do not invent parallel architecture.
  • Prefer minimal diffs; avoid drive-by reformat of unrelated C files.
  • If ColumnLimit breaks signatures, fix layout in context — do not truncate identifiers.

Done when

Build succeeds and plan checklist items are addressed or explicitly deferred with reason.

Example provenance: premflow. Pair with explore-repo-readonly when structure is unknown.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free