Source of truth for reusable configuration and environment definitions that shape a personal coding setup.
The repository is organized into profiles. Each profile README defines its
purpose and maintenance workflow. Profiles that synchronize assets with another
workspace also provide content-hub.yaml; other profiles are consumed directly
from this checkout.
profile/agent: agent skills and configuration.profile/repositories: repository-scoped editor and workspace assets.profile/toolbox-images: Fedora Toolbx container image definitions.
Profiles that use content-hub.yaml require the project Python environment.
Install uv, then
create or update that environment:
uv syncStart with the relevant profile README for prerequisites, execution context, and
commands. For synchronized profiles, use contentctl to deploy or adopt assets,
and edit content-hub.yaml only when changing synchronized paths, workspace
targets, or inclusion and exclusion rules.
Repository formatting and spell-checking commands are documented in
.dev/README.md.