[JacobStephens2]

Summary

A Prompts and skills page at /prompts/, generated from the same code the binary runs.

 src/
 ├── session.rs        # run(): Command::new("claude").args(claude_args(...))
+│                      # claude_args(): the one shared definition of the arguments
 ├── plugin.rs         # SKILLS, now pub, read by the renderer too
+└── prompts_page.rs   # #[cfg(test)] renderer + golden-file test
 site/
 ├── index.html        # press line skill labels → /prompts/#skill-<name>
 ├── main.js           # fills the commit label from /commit.txt
+└── prompts/index.html  # page; fragment between generated markers

render()
  command line   claude_args("<plugin dir>", None | "<session id>", "<prompt>")
  prompts        prompt::fresh / continuation (no PR, open PR) / conflict_repair / ci_fix_repair / resume
                 with <Issue URL>, <base>, <branch>, <pull request URL>, <failing check> …  → <mark class="ph">
                 each: one line on when it's sent + link to the unit (/#unit-N)
  skills         walk plugin::SKILLS, every file raw, SKILL.md first; each links its unit
  licence        skills/LICENSE raw, link to pr/CREDITS.md

test prompts_page_shows_what_the_binary_sends
  no site/ dir (crates.io package)   → skip with a message
  UPDATE_PROMPTS_PAGE=1              → rewrite the fragment
  fragment != render()               → fail with line diff + "Regenerate it with: UPDATE_PROMPTS_PAGE=1 cargo test prompts_page"

The page includes the fragment literally, between marker comments in site/prompts/index.html, because the site has no build step or server-side includes. The commit label is filled in by main.js from the commit.txt that publish.sh writes. Without it (locally, or JS off) the label reads "As of the commit of main this copy of the site comes from".

Evidence

Page (1440 and 390 wide, with a stand-in commit.txt):

Golden file:

• Before: the prompt changed without regenerating → cargo test fails:

  site/prompts/index.html is out of date with the prompts, the claude arguments or the skills:
     67 - … Build on them; don't start over.
     67 + … Build on them.
  Regenerate it with: UPDATE_PROMPTS_PAGE=1 cargo test prompts_page
  

  The same happens after editing skills/tdd/tests.md.
  After: UPDATE_PROMPTS_PAGE=1 cargo test prompts_page rewrites the fragment, and cargo test passes again.
• Packaged crate: I unpacked cargo package and ran the tests with their own target dir: skipping: no …/thirdshift-0.2.0/site (the crates.io package leaves it out) … ok. tests/packaging.rs passes.
• Prefactor: claude_args produces the same arguments in the same order. All Run tests pass unchanged: cargo test gives 14 suites ok, and clippy is clean.
• Links: I checked every /prompts/#skill-* link on the home page, and every /#unit-N and in-page link on /prompts/, against the ids that exist.

Merge Danger

Door: two-way

Blast Radius: site

Only /prompts/ and the home page's skill labels change what visitors see. The binary's behaviour doesn't change: the session arguments are only refactored. From now on, any PR that changes a prompt, the claude arguments or a skill must regenerate the page, or cargo test fails. That is intended.

Unaddressed findings

Standards

• Skill-to-unit mapping and unit names are duplicated across prompts_page.rs and site/index.html. The site has no templating. A new skill without a unit panics the renderer; renaming a unit is rare and shows on review.
• Placeholder constants are repeated in the PLACEHOLDERS array, and highlighted marks any <base>-style text. No prompt's fixed text uses those tokens (<run-id> isn't one). A unit test covers escaping versus highlighting.
• The u64::MAX issue-number sentinel is only swapped after #. Every prompt uses the number only as Closes #<n>. The review confirmed there are no stray occurrences.
• The regeneration command is written out in three places (the UPDATE constant, the marker comment and the README). They are plain strings for different readers. I didn't think a macro for them was worth it.
• The hand-written LCS diff might be speculative generality. The spec asks for the failure to show a diff, and the crate has no diff dependency.
• The header mark and footer markup are copied from the home page. That is expected on a static site with no build step.

Spec

• "Links to the latest release's skills" is only a link to releases/latest. GitHub has no stable URL for the latest tag's tree. Resolving it would need an extra GitHub API call from the page, or deploy changes.
• The commit line is in the header, not at the end as Spec: thirdshift.app, a site that shows how the factory works #61's order lists. Prompts and skills page, generated from the source #68 sets no order, and in the header the reader sees how current the page is before reading on.

Closes #68

🤖 Generated with Claude Code