@haus-tech/haus-workflow 0.14.0 → 0.16.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +22 -0
- package/dist/cli.js +964 -577
- package/library/global/commands/haus-setup.md +26 -4
- package/package.json +1 -1
|
@@ -18,11 +18,33 @@ Do this in order:
|
|
|
18
18
|
as a flat `{ "question": "answer" }` object (the exact question strings as
|
|
19
19
|
keys). This is what lets setup proceed without re-prompting.
|
|
20
20
|
|
|
21
|
-
4. **Apply.** Run `haus apply --write`. Read the result.
|
|
21
|
+
4. **Apply the basics.** Run `haus apply --write`. Read the result. This installs
|
|
22
|
+
the core guardrails and helpers — including the documentation skill haus uses
|
|
23
|
+
in the next step.
|
|
22
24
|
|
|
23
|
-
5. **
|
|
24
|
-
|
|
25
|
-
|
|
25
|
+
5. **Write the project docs.** Open and follow the instructions in
|
|
26
|
+
`.claude/skills/writing-documentation/SKILL.md`, which step 4 just installed.
|
|
27
|
+
Following it, do a deep read of the project and:
|
|
28
|
+
- write the project documentation (the `CLAUDE.md` body and `docs/` files).
|
|
29
|
+
NEVER alter the `<!-- HAUS:BEGIN haus-imports … -->` … `<!-- HAUS:END … -->`
|
|
30
|
+
block in `CLAUDE.md`; write around it.
|
|
31
|
+
- write `.haus-workflow/deep-context.json` describing what the deep read found
|
|
32
|
+
(roles, stacks, patterns the quick scan in step 1 could not see).
|
|
33
|
+
If this step can't be completed for any reason, say so plainly and skip to
|
|
34
|
+
step 8 — setup still finishes correctly with the basics from step 4.
|
|
35
|
+
|
|
36
|
+
6. **Re-check recommendations with the new understanding.** Run `haus recommend`.
|
|
37
|
+
It re-reads `deep-context.json` and may surface extra helpers matching what the
|
|
38
|
+
deep read discovered. You MUST run this before the next apply — `haus apply`
|
|
39
|
+
does not re-calculate recommendations on its own.
|
|
40
|
+
|
|
41
|
+
7. **Apply the rest.** Run `haus apply --write` again. It only writes what changed,
|
|
42
|
+
so this just adds the newly-matched helpers from step 6.
|
|
43
|
+
|
|
44
|
+
8. **Confirm.** End with one plain-language line, for example:
|
|
45
|
+
"✅ Your project is configured — I wrote your project docs, added N guardrails
|
|
46
|
+
and M coding helpers (K matched after reading your code in depth). Run
|
|
47
|
+
`/haus-doctor` any time to re-check." Fill the numbers from the apply output.
|
|
26
48
|
|
|
27
49
|
If anything fails, explain what happened in plain language and what you'll try
|
|
28
50
|
next — don't dump raw errors.
|