Everything installs with one command. What differs is what each skill needs after that. Required means the skill cannot do its job without it; optional means it does more with it; convention means a place the skill reads or writes, owned by you.
| Skill | Required | Optional | Convention |
|---|---|---|---|
| all | the install; an agent that reads skills | a DESIGN.md from pe-design, understand mode |
a .product/ folder |
| product-engineering | nothing beyond the install | say “product engineering, …” | |
| pe-design | a browser to open the HTML artifacts | the app running locally for vary mode; network for understand mode from a public URL | approvals land in .product/approved/<slug>/ |
| pe-build | the project’s code, in its own stack | the dev server, so the rendered result can be checked; the animations.dev course pack, installed locally by owners | reads DESIGN.md and .product/approved/ |
| pe-review | a diff, a URL, or a screenshot to review | a browser for screen and a11y modes | fidelity mode reads .product/approved/ |
| pe-verify | python3; Playwright with Chromium for browser checks | ffmpeg for mp4 recordings | .product/qa-list.md; ~/.product-engineering/memories.md |
| pe-product-description | the source repo and commit; a way to run the product | python3 for the link checker | its output is a repo of documents |
| pe-brand-assets | brand truth: DESIGN.md, a style guide, or a brand/ folder; with none, values you supply in the conversation, labeled provisional |
an SVG-to-PNG renderer for OG images | SVG is the source of truth |
The two installs worth doing now
Playwright with Chromium, for pe-verify’s browser checks:
npx playwright install chromiumAnd a DESIGN.md, which pe-build, pe-review, and pe-brand-assets all read:
“Document our design system”
pe-design writes it from the repo’s tokens and components, or from a public URL.