agentleFS
Sign inStart free
wolulabswolulabs/hermes-founder-os/skills/build-system/SKILL.md

build-system

Skill18 starsChanged 6 months agoMITView on GitHub

Specialist skill for implementation planning, coding execution guidance, test planning, refactor recommendations, and anti-overengineering discipline for MVP builds. Use with PRD.md and TASKS.md to implement scoped phases safely.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. immacualate/claude-forge★ 5same name
    2. Geruyang/skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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. Distinctive:

    Use this skill when the product scope is defined and the user needs implementation planning, coding guidance, test strategy, debugging …

    line 8
  2. Very specific:

    Read PRD.md, TASKS.md, and relevant code.

    line 40
  3. Distinctive:

    Add or update focused tests based on risk.

    line 44
  4. Distinctive:

    Run verification commands when available.

    line 45
  5. Distinctive:

    Do not add features outside MVP scope.

    line 50
  6. Distinctive:

    Prefer existing code patterns.

    line 51
  7. Distinctive:

    Keep changes small and reviewable.

    line 52
  8. Distinctive:

    Avoid new dependencies unless clearly justified.

    line 53
  9. Distinctive:

    Prefer boring, maintainable solutions.

    line 55

≈ “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

Build System

Use this skill when the product scope is defined and the user needs implementation planning, coding guidance, test strategy, debugging discipline, or refactor recommendations.

Build System is execution-focused. It should preserve MVP scope, avoid speculative abstractions, and convert product requirements into small, verifiable engineering steps.

Primary Outputs

  • Implementation plan.
  • Code task sequence.
  • Test checklist.
  • Refactor recommendations.
  • Risk notes.

Use This Skill For

  • Implementing a scoped phase.
  • Breaking PRD/TASKS into coding steps.
  • Debugging.
  • Test planning.
  • Refactor review.
  • Avoiding overengineering.
  • Reviewing implementation readiness.

Do Not Use This Skill For

  • Market validation.
  • Writing PRDs.
  • Landing page strategy.
  • Launch planning.
  • High-level architecture review before product scope exists.

Default Workflow

  1. Read PRD.md, TASKS.md, and relevant code.
  2. Confirm phase boundary.
  3. Identify dependencies and risky files.
  4. Implement only the requested scope.
  5. Add or update focused tests based on risk.
  6. Run verification commands when available.
  7. Summarize changes, tests, and remaining risks.

Scope Discipline

  • Do not add features outside MVP scope.
  • Prefer existing code patterns.
  • Keep changes small and reviewable.
  • Avoid new dependencies unless clearly justified.
  • Refactor only when it directly supports the task.
  • Prefer boring, maintainable solutions.
  • For mobile apps, do not implement Stripe, PayPal, Midtrans, Xendit, or external web checkout for in-app digital goods, premium features, credits, paid AI usage, or subscriptions unless the PRD and architecture review document a platform-policy exception. Use Apple IAP / Google Play Billing, often via RevenueCat.

References

  • references/engineering-principles.md for execution philosophy.
  • references/implementation-workflow.md for step-by-step build flow.
  • references/testing-checklist.md for verification.
  • references/refactor-rules.md for refactor boundaries.

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