Folloze Board Quality Core
This skill is the portable production contract shared by all customer builders. It distills reusable design and QA lessons from the internal Demo Builder while excluding internal account systems, trackers, operator identities, and deal workflows.
Required References
Use these at the matching stage:
references/source-design-dna.md before visual design for external brands, using the validated Brand Harvester bundle as the evidence source.references/experience-shapes.md before layout or interaction selection.references/buyer-experience-quality-gates.md before local review and again before MCP save.references/mcp-publishing-preflight.md before any Folloze save or publish action.
For a Folloze-owned page, $folloze-brand-kit replaces external Source DNA capture. Its visual and voice references remain the brand authority.
Production Sequence
- Confirm the router handoff: motion, brand owner, approved strategy, brand evidence, selected builder, and conversion job.
- Write the message spine and proof plan. Every visible factual claim must trace to user-approved material or a public source.
- Choose one experience shape and record the section order, first-viewport signal, navigation approach, proof requirements, and final CTA.
- Build one self-contained local HTML source in the active Git repo unless the environment explicitly requires another portable format.
- Use named design tokens. Make every visible control functional, accessible, and analytically meaningful.
- Render and visually inspect desktop near
1440 x 900 and mobile near 390 x 844. Add 320, 375, 414, and 768 width checks when tooling allows.
- Fix copy, links, interactions, overflow, placeholders, dead controls, contrast, focus, reduced motion, and asset failures.
- Run the MCP preflight only when the user asked to save, publish, update, or push to Folloze.
- After save or publish, verify each returned state independently. Never infer public deployment from a successful save.
Hard Stops
- The required strategy approval is missing for named-account or one-to-few work.
- The required brand source is missing or invalid.
- A claim, customer name, logo, metric, quote, or proof point cannot be sourced.
- The local page has broken controls, placeholder links, horizontal overflow, unreadable content, or unverified assets.
- The current MCP guide, authentication state, theme decision, or save target is unclear.
Completion Report
Report the local source path, selected shape, strategy approval, brand source, QA evidence, MCP preflight status, board identifier if returned, edit URL if returned, and public deployment verification as separate fields.
1---2name: folloze-board-quality-core3description: Apply shared public-safe design, copy, interaction, responsive QA, analytics, and Folloze MCP publishing gates to every customer-facing Folloze board builder. Use after routing and throughout local build, review, save, and publish readiness.4---56# Folloze Board Quality Core78This skill is the portable production contract shared by all customer builders. It distills reusable design and QA lessons from the internal Demo Builder while excluding internal account systems, trackers, operator identities, and deal workflows.910## Required References1112Use these at the matching stage:1314- `references/source-design-dna.md` before visual design for external brands, using the validated Brand Harvester bundle as the evidence source.15- `references/experience-shapes.md` before layout or interaction selection.16- `references/buyer-experience-quality-gates.md` before local review and again before MCP save.17- `references/mcp-publishing-preflight.md` before any Folloze save or publish action.1819For a Folloze-owned page, `$folloze-brand-kit` replaces external Source DNA capture. Its visual and voice references remain the brand authority.2021## Production Sequence22231. Confirm the router handoff: motion, brand owner, approved strategy, brand evidence, selected builder, and conversion job.242. Write the message spine and proof plan. Every visible factual claim must trace to user-approved material or a public source.253. Choose one experience shape and record the section order, first-viewport signal, navigation approach, proof requirements, and final CTA.264. Build one self-contained local HTML source in the active Git repo unless the environment explicitly requires another portable format.275. Use named design tokens. Make every visible control functional, accessible, and analytically meaningful.286. Render and visually inspect desktop near `1440 x 900` and mobile near `390 x 844`. Add `320`, `375`, `414`, and `768` width checks when tooling allows.297. Fix copy, links, interactions, overflow, placeholders, dead controls, contrast, focus, reduced motion, and asset failures.308. Run the MCP preflight only when the user asked to save, publish, update, or push to Folloze.319. After save or publish, verify each returned state independently. Never infer public deployment from a successful save.3233## Hard Stops3435- The required strategy approval is missing for named-account or one-to-few work.36- The required brand source is missing or invalid.37- A claim, customer name, logo, metric, quote, or proof point cannot be sourced.38- The local page has broken controls, placeholder links, horizontal overflow, unreadable content, or unverified assets.39- The current MCP guide, authentication state, theme decision, or save target is unclear.4041## Completion Report4243Report the local source path, selected shape, strategy approval, brand source, QA evidence, MCP preflight status, board identifier if returned, edit URL if returned, and public deployment verification as separate fields.
0xTrey