بنقرة واحدة
sync-spec-docs
Refresh the Browser Support and Open Questions doc pages from the upstream WICG/html-in-canvas repo
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Refresh the Browser Support and Open Questions doc pages from the upstream WICG/html-in-canvas repo
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Capture a requirement, feature idea, or task from conversation context
View or change n-dx configuration with guided assistance
Submit feedback, bug reports, or feature requests for n-dx
Analyze the codebase and propose PRD updates
Restructure the PRD hierarchy — regroup epics, change levels, merge overlaps, create new containers
Show comprehensive project status combining PRD progress and codebase health
| name | sync-spec-docs |
| description | Refresh the Browser Support and Open Questions doc pages from the upstream WICG/html-in-canvas repo |
Pull the latest content for the two "living" doc pages on the site — Browser Support and Open Questions — straight from the WICG/html-in-canvas upstream on GitHub. Use this whenever the upstream explainer or issue list has moved enough to be worth refreshing the site.
Confirm the current spec doc state. Before running the script, note whether spec/browser-support.md or spec/open-questions.md have uncommitted local edits — the sync rewrites both files and any unsaved edits will be lost.
Run the sync script from the repo root:
node scripts/sync-spec-docs.mjs
The script hits the public GitHub API unauthenticated (60 requests/hour). If you've been rate-limited, set GITHUB_TOKEN to a personal access token with public_repo scope before running.
Review the diff. Check what changed against the previous state:
git diff spec/browser-support.md spec/open-questions.md
Scan for:
Spot-check the rendered pages. Start the dev server (npm run dev) and visit:
Commit the sync once the diff looks right. Use a commit message that mentions the upstream source so future developers can trace where the content came from:
git add spec/browser-support.md spec/open-questions.md
git commit -m "Sync spec docs from WICG/html-in-canvas upstream"
README.md from WICG/html-in-canvas/main, extracts the ## Status and ## Developer Trial (dev trial) Information sections, and writes a fresh spec/browser-support.md with preserved frontmatter (title, order)./issues endpoint (paginating as needed, filtering out pull requests), sorts them newest-first, and writes each as a section in spec/open-questions.md with title, upstream link, author, labels, and a short body preview._Auto-synced … on YYYY-MM-DD via scripts/sync-spec-docs.mjs._ line under the page heading so readers can see how fresh the content is.## Status heading was renamed), the extraction will silently write a placeholder. Inspect the output and adjust the extraction in scripts/sync-spec-docs.mjs if needed.