菜单
Run an automated end-to-end test of the pageclaw-batch pipeline using bundled fixtures. Validates batch generation with a small style matrix. Use to verify pageclaw-batch behavior after changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Batch generate static HTML page templates by combining a style matrix (design intents + layouts) with page-story markdown files. Skips interactive design questions — each style entry provides a design intent description that drives the full pipeline. Input: style-matrix.yaml + page-story files. Output: organized HTML + design docs.
Use when the user wants to turn a page-story markdown file (page-story-*.md) into a polished static HTML page. Trigger for: personal pages, academic homepages, portfolio pages, profile pages, any request to build a page from a structured markdown brief. Runs the full pipeline automatically: design context gathering, design system, implementation plan, build, and quality pass.
Run a full automated end-to-end test of the page-claw pipeline using a bundled fixture page-story. Simulates user responses autonomously. Use when you want to verify page-claw behavior after making changes to the skill.
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
| name | pageclaw-batch-test |
| description | Run an automated end-to-end test of the pageclaw-batch pipeline using bundled fixtures. Validates batch generation with a small style matrix. Use to verify pageclaw-batch behavior after changes. |
| license | MIT |
| metadata | {"author":"pageclaw","version":"1.0.0","homepage":"https://github.com/XY-Showing/pageclaw"} |
Run the full pageclaw-batch pipeline on bundled fixtures and produce a test report.
skills/pageclaw-batch-test/fixtures/style-matrix-test.yamlskills/pageclaw-test/fixtures/page-story-test.md (shared with pageclaw-test)Read both files at the start. These are the only inputs for the entire test run.
Override output directory. All pageclaw-batch output must go to test-output/batch/ instead of the default output/. Before invoking pageclaw-batch, create test-output/batch/html/ and test-output/batch/docs/. When pageclaw-batch references output/, substitute test-output/batch/ throughout.
Invoke pageclaw-batch with the test style matrix and the shared page-story. Run in autonomous mode -- do not wait for user confirmation at the summary table. The matrix contains 3 styles; expect 3 combinations.
Do not ask the user any questions during the run. If pageclaw-batch would normally ask for confirmation, proceed automatically.
After the batch pipeline completes, run these checks against test-output/batch/.
01-sidebar-brutalist, 02-col-whitespace, 03-topnav-editorial): all steps A-E completed without error.test-output/batch/index.html generated.<id>)test-output/batch/docs/<id>-design.md exists, contains ## Design Context and ## Design System.test-output/batch/docs/<id>-impl.md exists, contains a task-by-task plan.test-output/batch/html/<id>.html exists, is valid HTML (has <!DOCTYPE html> or <html).--bg, --fg, --accent, etc. per Technical Contract).[data-theme="dark"] override block.100vw).:root and [data-theme="dark"] blocks.layout field.test-output/batch/index.html exists.Print the following report after validation:
## Pageclaw Batch Test Report
### Pipeline
- [ ] Pre-flight: passed / FAILED
- [ ] Parse Inputs: passed / FAILED
- [ ] Style 01-sidebar-brutalist: completed / FAILED
- [ ] Style 02-col-whitespace: completed / FAILED
- [ ] Style 03-topnav-editorial: completed / FAILED
- [ ] Master Index: generated / FAILED
### Artifact Checks
For each style <id>:
- [ ] output/docs/<id>-design.md exists and contains ## Design Context + ## Design System
- [ ] output/docs/<id>-impl.md exists and contains task-by-task plan
- [ ] output/html/<id>.html exists and is valid HTML
- [ ] HTML has CSS custom properties (--bg, --fg, --accent, etc.)
- [ ] HTML has light/dark mode toggle with [data-theme="dark"] block
- [ ] HTML is responsive (no fixed widths > 100vw)
- [ ] Zero raw hex/rgb outside :root and [data-theme="dark"]
- [ ] Layout matches style-matrix layout field
- [ ] Design intent reflected in visual output
### Master Index Check
- [ ] output/index.html exists
- [ ] Links to all generated HTML files
- [ ] Has light/dark mode toggle
### Violations
(list any issues, or "None")
### Notes
(observations about quality, timing, etc.)
Mark each item with a check (passed) or note the failure. After the report, open test-output/batch/index.html in the browser if possible.