Menu
Verify site/dist/ is up to date before merging site changes (go:embed reads directly from committed bundle).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
How to write comprehensive architectural proposals that drive alignment before code is written
How the eval engine works: generate → grade → review → report
Record final outcomes to history.md, not intermediate requests or reversed decisions
Tone enforcement patterns for external-facing community responses
Team initialization flow (Phase 1 proposal + Phase 2 creation)
Core conventions and patterns for this codebase
| name | embedded-asset-freshness |
| description | Verify site/dist/ is up to date before merging site changes (go:embed reads directly from committed bundle). |
| confidence | high |
| applies-to | ["site","serve"] |
hyoka's site is shipped via go:embed all:dist in site/embed.go. The bundle lives at site/dist/ and is committed to git. Vite builds deterministically (content-hashed filenames), so rebuilding identical source produces byte-identical output.
CI enforcement: The site-bundle-freshness.yml workflow rebuilds site/dist/ on every PR and fails if git diff --exit-code site/dist/ detects uncommitted changes.
cd site && npm run build
git add site/dist/
git commit -m "site: rebuild bundle"
CI will verify the bundle is fresh. No manual copy step required — go:embed reads site/dist/ directly.
site/src/** without running npm run buildnpm install) that affect bundle output without rebuildinghyoka serve still shows the old thing" reportssite/src/** but don't update site/dist/site-bundle-freshness workflow.github/workflows/site-bundle-freshness.yml — CI enforcementsite/embed.go — go:embed directive