feat(prompts): RM-19078 Publish agent setup prompts to npm

[xavierandueza]

🚥 Resolves RM-19078

🧰 Changes

Makes a thin JS package that just exports the individual setup prompts (based on what we have in skills) to an NPM package.

WHY?

To make sure that we base the instructions that homepage (and eventually the monorepo) shows to users doesn't drift from the rest of the skills.

This way, we can, on a new release trigger we will create PRs in the readme and homepage repos. Makes keeping in-sync long term easier, while still letting us actually show the prompts to the user.

Need Assistance

The release and downstream workflows need setup before they work. Until then we're hard-coding these in homepage.

• Install the ai-deploy-readme Github App on both agent-plugins and homepage repos
  • Add the AI_DEPLOY_APP_ID / AI_DEPLOY_PRIVATE_KEY secrets to this repo - need so that it can create PRs in homepage (and eventually monorepo)
• Publish @readme/agent-plugins to npm - needs to be a member of readme team on npm
  • Add this repo's release.yml to the npm package's trusted publishing (should be under "Github Actions")
• Approval + Merge for the PR to add pnpm support for update-downstream-deps

🧬 QA & Testing

• Read over all generated content, LGTM.

[greptile-apps]

Confidence Score: 5/5

[High impact] No confirmed blocking issue remains in the changes since the previous review.

_{Reviews (2) · Last reviewed commit: "chore: drop node_version from homepage d..." · Reviewed by Greptile}

[xavierandueza]

self-reviewed, LGTM

[xavierandueza]

NOTE - everything under prompts/ aren't used by anything aside from checking final output.

I wanted left in because its good to be able to see, as a user, what these final prompts are.

[xavierandueza]

(agent response)
No code change. One correction: prompts/ is used for more than reviewing output. It does three things:

• It's the release trigger. release.yml runs on pushes to main under prompts/**, so a change to the client instructions only publishes once the regenerated prompts are committed.
• It's shipped in the npm package. files includes prompts/, and exports exposes @readme/agent-plugins/prompts/<key>.md, which the README documents. Consumers that want raw Markdown read it directly rather than through setupPrompts.
• It's the drift check. build-prompts.mjs --check compares these files with the client instructions in Validate.

So keeping it committed matters beyond readability. If we only wanted it for review, we'd also need to change the release trigger and drop the raw Markdown export.

Dismissed because a newer commit was pushed; Greptile will re-review the current head.