菜单
Dual sync of bigbounce HTML pages (index.html, paper.html, activity.html, data-explorer.html, explained.html, glossary.html, figures.html, etc.) AND the Next.js site/ subdirectory. Both must update in same commit as SSOT — never as follow-up. Site staleness ≥20 fires = red flag.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/houstongolden/bigbounce --skill bigbounce-site-sync命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
When any quantitative claim changes (f_NL number, σ, anomaly count, MCMC sample count, redshift, etc), grep every .tex AND every HTML/TSX page in the repo for the old value, replace with new in one atomic commit. Zero stale instances allowed. Claims-table on index.html must match paper abstract.
Mirror a compiled paper PDF to every hosting path: public/papers/ (legacy static site) and site/public/ (Next.js site). Both must serve the same PDF. If only one is updated, one of the two site surfaces shows the stale PDF.
Bigbounce-specific specialization of /revision-tracker-update. Binds the schema to project-context/peer-reviews/REVISION_TRACKER.md and to the 6-paper layout (P1A, P1B, P2, P3, P4, P5). Same workflow as the global skill but tied to this repo's file paths.
基于 SOC 职业分类
正在显示 SKILL.md
| name | bigbounce-site-sync |
| version | 0.1.0 |
| description | Dual sync of bigbounce HTML pages (index.html, paper.html, activity.html, data-explorer.html, explained.html, glossary.html, figures.html, etc.) AND the Next.js site/ subdirectory. Both must update in same commit as SSOT — never as follow-up. Site staleness ≥20 fires = red flag. |
| triggers | ["update the site","sync the website","bigbounce site sync"] |
Source: CLAUDE.md "WEBSITE SYNC PROTOCOL"; AGENT_RULES.md §5.3-5.4; feedback_website_sync.md; feedback_site_sync_same_commit.md; project_site_routing.md
Scope: bigbounce-only
Trigger: any paper result, MCMC chain, figure, version, or branch state change
Updates every public-facing page when bigbounce state changes. Houston tracks progress via the site, not the terminal — site staleness vs SSOT is how he loses orientation. Site update must commit ATOMICALLY with SSOT (/ssot-update).
| Change | Pages to update |
|---|---|
| New experiment result | index.html, activity.html, data-explorer.html, paper.html if relevant |
| New MCMC chain | data-explorer.html, paper.html, status surfaces |
| New figure | figures.html, index.html if hero, paper.html |
| Paper version change | paper.html, index.html stat cards, activity.html entry |
| Branch open/close | activity.html, index.html if barrier/result count changes, research/project_master_dossier/index.html |
| Glossary / equation change | glossary.html |
| Barrier/result count | index.html stat cards, research/project_master_dossier/index.html |
| Quantitative claim change | grep + sweep every HTML page |
The Next.js site lives at site/ and is the new default at root per project_site_routing.md (2026-05-01). Legacy static HTML moved to /old. Every site-sync MUST hit the Next.js site primarily:
site/src/app/*/page.tsx — Next.js pagessite/public/papers/*.pdf — Next.js-served PDFsIf a change appears in index.html but not in site/src/app/page.tsx, the site is broken on the new default.
Houston commonly says:
When you hear these, this skill is the answer.
git diff HEAD~1 if just landed.grep -rn "<old-number>" --include="*.html" --include="*.tsx"
site/src/app/....*.html AND site/src/app/*.tsx updatedactivity.html → no trail of what changed