ynh-compose

Topics in the source

• Compose a harness
• Before you start
• Step 1 — Find out what they are copying
• Step 2 — includes — use artifacts without owning them
• Step 3 — profiles — one harness, several ways of working
• Step 4 — focuses — a named way in
• Step 5 — delegatesto — hand work to a specialist
• Step 6 — fork — take it and make it yours

Someone with one working harness is one step from the thing that makes ynh worth using. Composition is what separates a harness from a folder of markdown you copy between repos, and it is exactly what a new user will not discover unaided. Five mechanisms. Reach for them in this order, because that is the order of increasing commitment. | Mechanism | Question it answers | |---|---| | includes | can I use someone else's artifacts without copying them? | | profiles | can this harness behave differently in different situations? | | focuses | can I skip explaining what I want every time? | | delegatesto | can this harness hand work to a specialist? | | fork | I want someone's harness, but mine | references/composition-patterns.md — worked patterns, the resolution rules, and the traps Ask directly: Is there anything in this harness you have copied from somewhere else, or that you would want in another project? Copied artifacts are the signal. A skill duplicated across three repos wants to be an include. A rule everyone on the team pastes wants to be a team harness. An include pulls skills/, agents/, rules/ and commands/ from another harness at assembly time. Nothing is copied into the re

This is an excerpt. Refer to the complete source and its current requirements.