taskfiles

A curated collection of reusable Taskfile include modules. Each module ships as a single YAML file under src/ and consumers wire it remotely through Taskfile's remote-taskfiles experiment. There is no build step and no runtime artefact—the YAML files themselves are the product.

Module	Tasks	Key variables
mkdocs	start	MKDOCS_PORT
kind	start, destroy, recreate	KIND_CREATE_EXTRA_ARGS
pre-commit	install, start	PYTHON_VENVS_BASEDIR
k8s	bootstrap, install-argocd	ARGOCD_EXTRA_ARGS, KUBECTL_TIMEOUT

Every task in every module sets dir: '{{.USER_WORKING_DIR}}', so commands run in the consumer project's working directory, never in this repository.

Where to start

This site serves three reader clusters. Pick the one that matches the task at hand:

• Adopt a module. Wire an include into a consumer project, pick a pin, tune the variables. Start with Getting Started, then open the matching page under References → Modules.
• Contribute back. Add a module, change an existing task, or update the rendered docs. Read Guides → Contributing.
• Verify conformance. Confirm the repository still satisfies the portfolio specs (project structure, release automation, Renovate, Vale). Read References → Governance and specs.

The structure shown here reflects the audience analysis recorded in AUDIENCES.md. Every page declares its audience, content_mode, and track in its front matter so the link between an audience and the content it gets stays visible.

Sources

• README.md (intro, via marker-bounded include)
• AUDIENCES.md