How do I install the Powerforge Website Starter skill?

Run npx skillmds@latest add tomevault-io/powerforge-website-starter in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Powerforge Website Starter safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Powerforge Website Starter?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Powerforge Website Starter free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Powerforge Website Starter?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Powerforge Website Starter by tomevault-io

Name: Powerforge Website Starter
Author: tomevault-io

Powerforge Website Starter

Create, refactor, or standardize PowerForge.Web websites. Use when setting up or fixing site.json/pipeline.json, dev vs CI modes, baselines and budgets, theme.manifest.json contracts (features/requiredPartials/slots/CSS selectors), navigation consistency, API docs (header/footer + multi-CSS), and agent handoff docs to prevent half-cooked websites and regressions across multiple sites. Use when this capability is needed.

tomevault-io 02cff89 2 files · 3.4 KB Updated Sep 17, 2026

File contents

PowerForge Website Starter

Follow a deterministic "golden path" so agents can build sites without guessing.

Golden Path (Do This In Order)

Identify the repo root and build outputs.
- Repo root contains site.json and pipeline.json.
- Output is usually ./_site, temp is ./_temp.
Make the site explicit (avoid inference).
- In site.json set defaultTheme, features, and navigation.
Standardize pipeline modes (dev vs ci).
- Dev: fast iteration; skip heavy steps.
- CI/release: strict; fail on new issues; enforce budgets.
Make the theme portable and contract-driven.
- Prefer theme.manifest.json with schemaVersion: 2.
- Declare features and featureContracts (required layouts/partials/slots + CSS selectors).
Ensure page layouts include required hooks.
- Scriban: {{ extra_css_html }}, {{ extra_scripts_html }}, {{ assets.css_html }}, {{ assets.js_html }}.
Make API docs use site chrome and correct CSS.
- Provide api-header/api-footer partials that match the site header/footer structure/classes.
- Use multi-CSS: "/css/app.css,/css/api.css" (or the equivalent for the site).
- Emit API coverage report (coverageReport) so CI can track documentation completeness.
- For PowerShell APIs, wire psExamplesPath (or rely on Examples/ discovery) to enable fallback examples when help XML is sparse.
Add quality gates with an escape hatch.
- Use baselines for legacy noise; fail only on new issues in CI.
Run locally in dev and ci modes and verify output.
- Dev should warn, not spam, and stay fast.
- CI should be deterministic and block regressions.
Update agent handoff docs so the next agent knows where everything is.
- Paths to sibling repos, theme structure, and the site’s “rules”.

Reference Files (Read As Needed)

references/blueprint.md: minimal recommended site.json/pipeline.json/theme contract patterns.
references/theme-contracts.md: feature contract checklist (docs/apiDocs/blog/search/404).
references/agent-prompts.md: copy/paste prompts for Claude/agents (new site, refactor theme, fix api docs).

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: powerforge-website-starterdescription: Create, refactor, or standardize PowerForge.Web websites. Use when setting up or fixing site.json/pipeline.json, dev vs CI modes, baselines and budgets, theme.manifest.json contracts (features/requiredPartials/slots/CSS selectors), navigation consistency, API docs (header/footer + multi-CSS), and agent handoff docs to prevent half-cooked websites and regressions across multiple sites. Use when this capability is needed.---# PowerForge Website StarterFollow a deterministic "golden path" so agents can build sites without guessing.## Golden Path (Do This In Order)1. Identify the repo root and build outputs. - Repo root contains `site.json` and `pipeline.json`. - Output is usually `./_site`, temp is `./_temp`.2. Make the site explicit (avoid inference). - In `site.json` set `defaultTheme`, `features`, and navigation.3. Standardize pipeline modes (dev vs ci). - Dev: fast iteration; skip heavy steps. - CI/release: strict; fail on new issues; enforce budgets.4. Make the theme portable and contract-driven. - Prefer `theme.manifest.json` with `schemaVersion: 2`. - Declare `features` and `featureContracts` (required layouts/partials/slots + CSS selectors).5. Ensure page layouts include required hooks. - Scriban: `{{ extra_css_html }}`, `{{ extra_scripts_html }}`, `{{ assets.css_html }}`, `{{ assets.js_html }}`.6. Make API docs use site chrome and correct CSS. - Provide `api-header`/`api-footer` partials that match the site header/footer structure/classes. - Use multi-CSS: `"/css/app.css,/css/api.css"` (or the equivalent for the site). - Emit API coverage report (`coverageReport`) so CI can track documentation completeness. - For PowerShell APIs, wire `psExamplesPath` (or rely on `Examples/` discovery) to enable fallback examples when help XML is sparse.7. Add quality gates with an escape hatch. - Use baselines for legacy noise; fail only on new issues in CI.8. Run locally in dev and ci modes and verify output. - Dev should warn, not spam, and stay fast. - CI should be deterministic and block regressions.9. Update agent handoff docs so the next agent knows where everything is. - Paths to sibling repos, theme structure, and the site’s “rules”.## Reference Files (Read As Needed)- `references/blueprint.md`: minimal recommended `site.json`/`pipeline.json`/theme contract patterns.- `references/theme-contracts.md`: feature contract checklist (docs/apiDocs/blog/search/404).- `references/agent-prompts.md`: copy/paste prompts for Claude/agents (new site, refactor theme, fix api docs).---> Converted and distributed by [TomeVault](https://tomevault.io/claim/evotecit) — claim your Tome and manage your conversions.

Frequently asked questions