docs: deploy user pages to Web Assets, not plugin bundle

[simons-plugins]

Summary

The `/indigo:html-pages` skill previously recommended deploying user pages into a plugin's `Contents/Resources/static/pages/` folder. This is wrong — plugin bundles are wiped on every update, so user pages deployed there get destroyed on the next plugin release.

This PR updates the skill to point at Indigo's `Web Assets/static/pages/` folder as the primary deployment target for user-owned pages. That folder lives outside any plugin bundle and survives plugin updates, reinstalls, and Indigo upgrades.

Changes

`SKILL.md` Phase 4 (DEPLOY)

• Explicit warning not to drop user content in plugin `Resources/` folders
• Option A is now "Indigo Web Assets folder" with Web Assets path
• Option C is "Shipping as part of a plugin" (plugin authors only — commit to source repo, never at deploy time)

`references/design-guidelines.md`

• Rewrote Deployment Options section with Web Assets as primary target
• Added new Page Manifest section documenting the Domio plugin's `/pages/` endpoint response shape, including the new `source` field (`plugin` | `user`) and the URL patterns each source maps to

Companion PRs

• feat: discover user pages from Indigo Web Assets folder indigo-domio-plugin#13 — plugin scans Web Assets folder
• simons-plugins/domio-code#172 — iOS app routes URLs by source

Version bumped to 1.5.0.

Test plan

• Version check CI passes
• Skill docs read coherently for someone deploying a new page

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@simons-plugins has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 13 minutes and 19 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 13 minutes and 19 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ee97b436-c741-47b8-bb7d-e9875e32a49f

📥 Commits

Reviewing files that changed from the base of the PR and between 61fce8a and 52d5b98.

📒 Files selected for processing (4)

• .claude-plugin/marketplace.json
• .claude-plugin/plugin.json
• skills/html-pages/SKILL.md
• skills/html-pages/references/design-guidelines.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/user-pages-deployment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}