agentleFS
wheeloswheelos/apollo-lite/.agents/skills/build/SKILL.md

build

Skill177 starsChanged 7 days agoApache-2.0View on GitHub

Apollo-Lite compile workflow. Use when building Apollo modules in the managed dev container or diagnosing a Bazel build failure.

169 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use backprop, finances and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • GerardoRdz96Skill

    finances

    Use when Gera talks about his money — logging an expense ("I spent X on Y"), checking where he stands this pay-period, closing a period, planning debt payoff, onboarding his financial picture, or asking for budgeting/finance opinions. Servy's financial brain. Triggers — "I spent", "log this expense", "where am I this period", "close the period", "how's my budget", "debt plan", "should I pay off", "finances onboard", "/finances".

    Also in 3 projects that use this

  • cpiprintSkill

    favicon

    Generate favicons from a source image

    Also in 3 projects that use this

  • madeehahassanSkill

    Go-Live

    Pre-launch checklist. Use before making any app public, sharing a link externally, or announcing a product launch. Adapts to Claude Code, claude.ai, and Cowork.

    Also in 3 projects that use this

  • TrevokeSkill

    define

    Use when a new feature request, bug report, or work request needs requirements defined before implementation

    Also in 3 projects that use this

  • HAR5HA-7663Skill

    shape

    Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 155 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this only for compiling Apollo source and diagnosing compile failures.

    line 10
  2. Distinctive:

    Use the wrapper for module builds:

    line 37
  3. Very specific:

    Use bazel build //<target> only when a precise target is required.

    line 46
  4. Distinctive:

    Verify expected artifacts and report any warnings affecting reuse or delivery.

    line 56
  5. Distinctive:

    Stop and identify the first actionable error before changing commands or source.

    line 60
  6. Distinctive:

    Do not compile Apollo targets outside the managed container.

    line 64
  7. Distinctive:

    Do not hardcode a username or create root-owned Bazel outputs.

    line 65
  8. Distinctive:

    Do not change verified build flags without a validation reason.

    line 66
  9. Very specific:

    Do not refresh MODULE.bazel.lock to recover from a missing module without first inspecting the registry error and getting approval for the …

    line 67

“Common” is measured: kept by at least 6 in 10 of the 155 edited versions of this file we could read. “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 and Compile

When

Use this only for compiling Apollo source and diagnosing compile failures. For building or publishing WheelOS container images, use the separate Container Image Build skill.

Prerequisites

  • From the repository root, enter the managed development container:

    bash docker/scripts/whl.sh enter
  • enter defaults to dev and starts it if needed. Run build commands in the container from /apollo, as the mapped non-root user.
  • Preserve the mapped user and shared cache. Never run Bazel as root or hide cache-permission problems with a temporary output root.

Steps

  • Build all modules with the exact wrapper command:

    ./apollo.sh build
  • Reuse the Bazel repository cache and existing build outputs. Do not use apollo.sh clean for ordinary incremental builds.
  • Use the wrapper for module builds:

    ./apollo.sh build <module>
  • The wrapper selects the configured CPU/GPU mode. Use ./apollo.sh build_gpu <module> or ./apollo.sh build_opt_gpu <module> only when that build mode is specifically required.
  • Use bazel build //<target> only when a precise target is required.
  • Module tests use ./apollo.sh test <module>.
  • ./apollo.sh check runs the full build, unit-test, and lint path. Use the separate commands when only one validation stage is needed.

Acceptance

  • The requested targets build successfully in the intended CPU/GPU mode.
  • Required tests pass when behavior changes. Build success alone does not establish runtime or release acceptance.
  • Verify expected artifacts and report any warnings affecting reuse or delivery.

Failure handling

  • Stop and identify the first actionable error before changing commands or source. Do not blindly retry or fix unrelated failures; request approval before expanding scope. If Bazel terminates unexpectedly, inspect its log and available memory before considering a retry.
  • Do not compile Apollo targets outside the managed container.
  • Do not hardcode a username or create root-owned Bazel outputs.
  • Do not change verified build flags without a validation reason.
  • Do not refresh MODULE.bazel.lock to recover from a missing module without first inspecting the registry error and getting approval for the lockfile change.

Sources (SSOT)

  • apollo.sh
  • docker/scripts/whl.sh
  • scripts/ci/apollo_build.sh

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.