pixel-face

Topics in the source

• pixel-face — author & refine the Frontier Faces pixel art
• Where things are
• Conventions (condensed — full detail in FACE-DESIGN.md)
• Tools (exact)
• Create a new persona
• Improve an existing persona
• Multi-agent variant loop (use for likeness — "doesn't look like them")
• QA bar

A persona face is pure data in examples/04-frontier-faces/personas.mjs (one entry per persona). The same data drives the terminal renderer (face-term.mjs), the browser element (web/cotal-face.js), and the PNG tool — so edit personas.mjs once and it's live everywhere. Always work from examples/04-frontier-faces/. personas.mjs — the entries (rows, colors, glow, mouths, expr, eyes, lines). Single source of truth. FACE-DESIGN.md — the full conventions (grid zones, color keys, eye recipe, visemes). Read it first. tools/img2rows.mjs — rough a reference photo into a 32×32 rows+palette. tools/render-png.mjs — render a 7-state contact sheet (PNG) for review. This is the validator. tools/face-template.mjs — copy-me starter entry that encodes the conventions. gallery.html (all personas, original-vs-pixel) and preview.html?p= (one persona) — served via python3 -m http.server or tools/serve-wall.mjs; for visual QA. assets/ . — reference photos. Gitignored / local-only — never commit them. Persona key ≠ agent name. The roster uses agent-file basenames; the face comes from each agent's face: frontmatter: elon→musk, steve→jobs, rayan→ray (others match). Persona keys: neon david ray sven garry jobs

This is an excerpt. Refer to the complete source and its current requirements.