Overview
- local instructions
- project-specific skills
- project-specific environment values
- active outputs
- durable documentation
For every reusable workflow, specify:
- Where inputs are read from.
- Where outputs are written.
- How files are named.
- Which temporary files may be deleted.
- Which artifacts should be retained.
Run cleanup regularly rather than waiting for the workspace to become unusable. The cleanup instruction should distinguish between temporary loose files and organized subfolders so that durable work is not deleted casually.
For portability, separate model-agnostic project knowledge from vendor-specific wrappers. Maintain equivalent instruction entry points for the harnesses that matter to the workflow, and synchronize them when core project facts change. Test the secondary environment occasionally so that it is not merely theoretical.
A diversified setup does not require equal use of every system. Most work can remain in the strongest preferred harness while a smaller share is performed in alternative environments. The purpose is continuity and comparative capability, not artificial balance.