briefatto-board

Shows an agent how to plan or hand off "briefatto board" so the concrete output is usable copy or a script. The procedure moves through Design board, Existing sites and work in progress, Brief → references → directions → client review. Use it when a new assignment calls for this craft.

Qu'est-ce que briefatto-board ?

briefatto-board is a Claude Code agent skill that shows an agent how to plan or hand off "briefatto board" so the concrete output is usable copy or a script. The procedure moves through Design board, Existing sites and work in progress, Brief → references → directions → client review. Use it when a new assignment calls for this craft.

Compatible avec✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Briefatto/briefatto-board/tree/HEAD/skill/briefatto-board

Installed? Explore more Productivité et collaboration skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

Design board

npx briefatto-board install places this skill under .claude/skills/ and adds pointers in AGENTS.md and CLAUDE.md. The skills CLI installs it for the selected agents.

If the project has a frozen DESIGN.md, read it before visual work and go straight to making pieces.

Commands shown as board use npx briefatto-board from the project root. If you used the installer from a local Board checkout, run node .claude/skills/briefatto-board/board.mjs. If a render reports missing Playwright Chromium, run the install command it prints and retry.

Write and edit HTML, JSON, Markdown, and scripts with your file tool. Run saved scripts as files. Keep commands compatible with the active shell, including PowerShell on Windows. Quote paths containing spaces and pass globs in quotes for the board to expand. Avoid long heredocs and quoted one-liners that generate files.

Existing sites and work in progress

  • For a frozen board, use the current DESIGN.md. Check board status before resuming. A current piece declares the current version. A stale piece declares an older version. For an unrecorded piece, inspect its source and render, revise it against the current guide if needed, then record the version actually used. For pieces outside the board, find their intended output location and save standalone HTML pieces under outputs/ with their assets. Record the version after checking the piece against the guide.
  • For an existing site without a frozen board, adopt its current look first. Run board adopt . from the project. It finds top-level HTML pages or a conventional build with an index page. Pass --root <built-directory> for a different build root and repeat --page <file> for chosen files relative to that root. For a running site, repeat --page <url> for the representative routes and states. Leave the site running for freeze. The default captures are desktop and mobile. Repeat --viewport WIDTHxHEIGHT to use other sizes.
  • Open each screenshot in .briefatto/adoption/ and read evidence.json for computed styles, visible copy and candidate style files. Inspect the page source, CSS variables, Tailwind configuration, theme and logo files that the pages use. Identify which components carry the brand across routes and screen sizes.
  • Write the root DESIGN.md as a handoff from one designer to another. Describe the existing layout, spacing, navigation, components and logo by role. Take the voice and example copy from the real pages. Freeze records the exact computed styles and any supplied brief or client constraints.
  • For keep our look, freeze with board freeze . once the guide is ready. For tidy it up first, run board adopt . --check on the selected pages, show the findings and proposed fixes, and wait for the user's yes. Fix the agreed issues, rerun the capture and floor check, and update the guide from the revised pages before freezing. board freeze . --check requires a passing floor as well as guide validation.
  • Freeze an adopted board with the same page selection for later brand changes. To change the reference pages, rerun adoption with the new selection. If the project has partial pieces and no board, adopt and freeze first, then review and record the existing pieces. If adoption has already been recorded, use the existing captures and draft to resume writing or freezing.

Brief → references → directions → client review

  1. Read brief.md and the client's materials. For a chat brief, save the client's words to brief.md. Preserve the brand name, offer, copy, URL, details, and literal requirements. When these requirements are in prose, record their exact wording in essentials.json for checking. Use required and terms arrays for shared copy, requiredByFormat to map format IDs to arrays of copy specific to each canvas, and body for body copy. List incoming images in assets as {"path":"assets/photos/store.jpg","origin":"brief"} or use "origin":"client" for a client attachment or later supply. Include only client-supplied images in this list. Board accepts layout whitespace and a rendered line break in place of a standalone middle dot. Preserve the approved words and other punctuation.
  2. Search for live references and capture them in one command, board refs . --capture <url1> first.png <url2> second.png, or copy in images supplied by the client. Use bare PNG filenames other than sheet.png. The command saves them under refs/ and flags captures to retake or replace. Open each capture to confirm it shows the intended reference. In refs/manifest.json, list {"image":"first.png","source":"https://example.com/page","note":"What to look at"} for each picture. Use a source file URL for a client image. If a picture is unavailable, a note entry is labelled text-only fallback. Run board refs ., show the actual refs/sheet.png to the client, and ask which parts to work from. Wait for the client's response before drawing directions. Keep refs/ internal to the review.
  3. Choose the places this client's audience will see the work, such as a README header, docs page and link card for a developer tool. Declare the canvases in project-root formats.json, an array of {"id":"readme","label":"README header","width":1280,"height":360,"seenWidth":900,"source":"Rendered within the repository page"} entries. With no client-specific formats, use hero 1440×900, post 1080×1080 and story 1080×1920. Use the same formats in all three directions and the kit. Set seenWidth to the displayed width in CSS pixels, at most width. The floor scales its 11 px displayed text minimum to the canvas width.
    • Set kind to web, social, print, or story when the brief identifies the channel. For print, use print: { widthMm, heightMm, bleedMm } in JSON, with quoted keys, for the physical trim size and bleed per edge. Supply these measurements from the brief or printer. A button-like call to action in a print piece produces a note.
    • For stories, use safeZones: { top, right, bottom, left } in JSON, with quoted keys, for unsafe edge insets in canvas pixels. Use values from the brief or the target platform. Copy that crosses into those insets fails the check.
  4. Draw three distinct directions with the brief's real copy and a designed wordmark in each. Load open-licence web fonts in the samples. Under each directions/<id>/, save <format>.html for each canvas and a direction.md with its name, reference numbers, format choices and why, exact font load lines and CSS fallback stacks. Describe the recurring graphic device in ## Device and mark it with data-device in the samples. Mark the visible device or a wrapper with its own rendered width and height. Run board directions . and show the sheets for a pick or changes.
  5. Record the client's words verbatim in refs/notes.md. Put each confirmed brand must or must-not in its own fenced constraint block. If none fits, agree on a direction to revise or show replacements. Apply the requests, run board directions . <id>, and show the revised sheet. Wait for explicit production approval. To freeze v1, put the client's exact approval in a fenced approval <id> block, using the chosen direction ID. When the user is their own client and has explicitly approved the direction as a solo developer, use board freeze . <id> --self-approved. The decision appears in board log.

Freeze → make pieces → feedback

  1. Write the prose in the project-root DESIGN.md after the client picks a direction. Open the chosen samples as images and read their HTML and styles. Brief the next designer on the decisions they need to make.
    • Freeze writes Brand facts, Campaign copy, Client musts and must-nots, and the exact computed styles. Use board freeze . <id> --dry-run to preview the generated guide without writing files. Leave the marked block to Board on later edits.
    • If a text role needs a more specific name than its HTML element supplies, label it in the sample with data-board-role, such as data-board-role="price numeral". Board records each role's rendered sizes and colours per canvas.
    • Name each recurring part by its job, then explain how it is built and how the parts sit together. Include details such as base rules, lockups and footer treatments when they carry the identity. Explain how the arrangement recomposes for different canvases. Leave out measured ratios, coverage percentages and centroid coordinates.
    • Under ## Typography, explain which parts use each face and include the font load lines as HTML <link rel="stylesheet" href="…">, CSS @import, or @font-face code. Use resolvable sources.
    • Make the guide sufficient on its own. Describe how to build the parts directly and refer only to assets that ship with the project. The reader may have only this file and the supplied brand assets.
    • Run board freeze . <id>. Read its validation report, correct any named failures in the draft or required campaign copy in the samples, and rerun. Freeze stamps and archives the guide. Use board log, board diff v1 v2, and board status for version history and piece status.
  2. Make the kit in the chosen formats from the frozen DESIGN.md. Recompose for each canvas. Save final layouts as outputs/<format>.html with <meta name="board-version" content="v2"> for the version used. Keep review proofs under outputs/review/, or mark them with <meta name="board-purpose" content="review">. Export the actual files for delivery and list every PNG and PDF in project-root deliverables.json, an array of entries such as {"file":"delivery/card.png","html":"outputs/post.html","width":1080,"height":1080}. Use editable HTML that renders on its own for each entry. For a transparent mark use "transparent":true. Add viewport if the CSS layout size differs from the export size, "fullPage":true for full-page PNG capture, and pageSizeMm if a single-page PDF has a specified physical page size. board check . validates the listed exports. board kit . --campaign "<launch name>" checks the layouts and final files and writes outputs/kit-check.json and the kit sheet. Fix failed checks before handoff. If a format has no checkable brief requirements, record the ones it must meet in essentials.json and freeze again.
  3. For brand feedback, record the client's exact words, revise and confirm the direction as above, update DESIGN.md, then run board freeze . <id> --note "<brand change>". Use board status to find pieces to revisit and update each piece's version when revised. For piece feedback, edit only that piece.

board check runs the floor, including visible copy clipping and overlap at the canvas size, and checks the brand name where it appears. Give later one-off pieces their own filenames, such as outputs/holiday-hours-post.html, and check them with board check . <file.html>. To add a later piece to the campaign, give it <meta name="board-campaign" content="campaign-name"> so normal checks enforce required copy and photos. Pass --brief to check all inputs against the campaign requirements for that run. Read each piece's scope and checks in the command output or check.json before handing it off.

Optional tools

  • Add --check to board directions . to see floor and campaign brief findings on each sample. Add it to board freeze . <id> to make the full sample floor a condition of freezing, alongside guide and required campaign copy validation.

  • Add --consistency to board check for frozen-board comparisons and composition notes on named kit formats such as post.html or march-post.html.

  • Composition families and sample pages in board/ are optional references. Use their arrangements as options when composing a new piece.

  • board export astryx writes an Astryx theme from the frozen board.

  • board freeze . <id> --extract generates a guide from measured sample values. It replaces the root guide with its generated file.

Skills associés