Landing Website Standards Skill Pack Files

Software Engineer — Dependencies & Design System Check

Runs the middle step of the design playbook: a read-only pass over the site repository before any mock exists. Per required section — does a shared component already render it (reuse / adapt with a named delta / new, with file paths); do the design tokens cover the page; what would pull a NEW dependency (each flagged with its weight/CLS/maintenance cost and a recommendation); where the page lives and whether it can opt out of global chrome; what the form must wire into.

The report is binding downstream: the reuse map is what the design job builds on and the build phase inherits. Verdicts: DEPS_CLEAR — everything required exists or is a named, accepted adaptation; BLOCKERS_FOUND — something structural is missing or contradicts the requirements, each blocker naming what it blocks and who owns the unblock. Prefer the boring answer, stated explicitly: an existing component at 90% fit beats a new one at 100, so design doesn't re-litigate it.