agentleFS
projectbluefinprojectbluefin/finpilot/.agents/skills/overview/SKILL.md

overview

Skill131 starsChanged 18 days agoApache-2.0View on GitHub

Architecture, repository layout, and file map for this template. Use when orienting to the repository, tracing how the image is assembled, or deciding which skill covers a task.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Overview

This repository builds a bootc operating system image by assembling OCI layers rather than by modifying an existing image. Bluefin, Aurora, and Bluefin LTS are built the same way, so the desktop configuration here is the one they ship.

How the image is assembled

The Containerfile is the source of truth, and it is deliberately verbose. It defines three things:

  1. Context stage (ctx) — combines the local build/ and custom/ directories with files pulled from two OCI images:

    • ghcr.io/projectbluefin/common — the shared desktop configuration, branding, and the Brew/Flatpak/ujust plumbing
    • ghcr.io/ublue-os/brew — the Homebrew integration
  2. Base image — the FROM line. It defaults to Fedora Silverblue and is the only place the base is chosen. just build reads the image name and tag from it; the Fedora major is read from the base image itself during the build.
  3. Phases — each build script runs in its own RUN block, in the order the Containerfile names them. build/README.md lists them.

Layout

PathHolds
ContainerfileImage assembly: identity, base image, and phases.
JustfileBuild, VM, release, and test recipes.
build/Build-time scripts: the phases, helpers, and the .example catalogue.
custom/brew/Brewfiles, installed at runtime.
custom/flatpaks/Flatpak preinstall declarations, installed on first boot.
custom/ujust/ujust recipes.
custom/files/System files overlaid onto /.
custom/config/Per-user config seeded into /etc/skel/.config/.
iso/Installer ISO and disk-image configuration.
tests/contract/ (interfaces the image must satisfy) and template/ (this repository's build wiring).
.github/Workflows, Renovate config, issue templates.

Which skill

I need to…Load
Understand the repository, or find the right skilloverview
Fork it and reach a first green buildonboarding
Add or remove a package, app, or commandcustomize
Change the Containerfile, Justfile, or a build phasebuild
Change a workflow, Renovate, or the release modelci
Fix something broken, or check before a pull requesttroubleshooting

Upstream

The template consumes Project Bluefin's shared infrastructure rather than copying it:

  • projectbluefin/common — the shared runtime layer and the lifecycle label workflow
  • projectbluefin/actions — the reusable workflows for image build, promotion, sync, PR validation, and Renovate
  • ublue-os/brew — the Homebrew integration

Changes stay in this repository. ublue-os/* is read-only.

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.