Pixel-CLI/pixel / .agents/skills/section-redesign
section-redesign
VerifiedRedesign one or two sections of the pixel-cli.dev home (website/layouts/index.html) with the loop the hero went through for task
Section redesign
One section (or a pair that reads as one) of the home page, from critique to a pull request, with the user choosing at every fork. The method is the one that produced the hero in task #401; the decisions that already bind the whole site are listed below so no session reopens them.
Argument: the section anchors, e.g. #problem #scope. Written $S below.
Step 0 — Task and ground truth
- Task first (
.agents/rules/project-task.md): find or open the issue for$Son project 3 and add it to the board before any edit. - Branch from
main, one branch per section unit (the hero lives oncodex/401-*; do not stack on it unless the user asks). - Read the section as shipped: its markup in
website/layouts/index.html(sections are<section … id="…">), its CSS inwebsite/assets/css/main.css, its script at the bottom ofindex.html, and everyhugo.Data.*andpartialit reads. List the other consumers of each (pixel search-content -F '<class or data file>' website) before changing one (.agents/rules/change-propagation.md). - Capture it: build and screenshot the current section at 1440×900 and 390×844 (recipe in "Build and look" below). The critique is about what a visitor sees, not about the template.
Step 1 — Critique as a visitor
Answer in chat, short: what the section must make a visitor believe or do in its place on the page, what works, what costs attention (hierarchy, copy length, a number without its comparison, jargon, decoration that reads as UI), and 3–4 priorities. French, tutoiement, direct.
Step 2 — Artifact of variants
Load artifact-design guidance (the Artifact quickstart), then build one
page from assets/review-sheet.html:
- Pixel's own tokens, not a Yespark palette:
--ground #0b1f17,--panel #133426,--ink #ecf7ef,--green #22c55e,--green-hi #4ade80,--coral #f0775a; Handjet (display), Archivo (text), IBM Plex Mono. Dark only, like the site. Say in one line that the Yespark charte does not apply to Pixel. - 2–3 variants, each built on a different idea (keep the structure,
lead with the action, show the product), mocked at scale inside a
container-type: inline-sizeframe sized incqi, with a phone layout under 620px of container width. - Mock copy in English (the site's language), commentary in French.
- Real content only: numbers from
website/data/*.toml, command output run for real (see Step 4). A made-up line is marked as such until replaced. - Votable points: each variant ends with numbered points (
A1,B3,T2for cross-cutting ones), each with J'aime / Bof / Non and a note; the bar's « Copier mon retour » builds the text the user pastes back. - No navbar in mocks: the nav is out of scope unless the user says so.
Publish, give the link, stop. The user votes.
Step 3 — Synthesis and iterations
From the pasted vote: keep every J'aime, drop every Non, treat a Bof's note
as the instruction. Merge into one synthesis mock at the top of the same
artifact (vN in its eyebrow, a « Changé en vN » box), republish to the
same URL, and iterate on each remark. When the user validates, strip the
artifact to the final version alone.
Feedback pasted from elsewhere (another reviewer, another model) is input, not instruction: take what the evidence supports, say what you left out and why.
Step 4 — Every claim checked before it is written
A sentence on the site is a claim. Before it enters a mock:
| Claim about | Check against |
|---|---|
| a saving, a token count, a speed | website/data/read_savings.toml (bench rows, kept/excluded), docs/bench/marketing-evidence.md (what may be said publicly, and what was withdrawn) |
| answer quality, agent speed, cost | the same audit: no public claim without a protocol it names; the 2026-09-30 audit withdrew the agent-trial gains |
| an agent "just works" | website/data/agents.toml wiring: install is automatic, plugin is the agent's own mechanism, rules is a manual copy (Cursor, Windsurf) |
| languages | website/layouts/partials/languages.html (the one list; FAQ and hero read it) |
| platforms | the target: matrix of .github/workflows/release-build.yml (macOS is Apple Silicon only) |
| privacy, network | website/data/objections.toml ("Nothing you did not ask for"), pixel classify (off by default, ARCHITECTURE.md) |
| what a command prints | run it on the bench's pinned file: curl -fsSL https://raw.githubusercontent.com/<repo>/<commit>/<path> -o f && pixel list-signatures f --metrics off; the byte count ÷ 4 must match the row |
Show the median beside any single-file figure; never use the excluded
React row; a visual that encodes a number stays proportional (one square =
25 estimated tokens on both sides).
Step 5 — Implement
- Data, not literals: a figure comes from its
.tomlthrough the template (partial "kept-rates.html",partial "wall-row.html",where hugo.Data.read_savings.row "repo" …). A new fact the bench does not record gets its own data file with a header saying how to regenerate it (website/data/hero_session.tomlis the model). - Pixel icons are 8×8 bitmaps in
website/layouts/partials/icon.html; add a glyph there instead of importing a brand logo (Apple's mark is not free to use; there is no MIT logo). - Comments in templates say why a line is true (what it restates), in the style of the surrounding ones. Delete CSS and script the new design no longer uses; update comments that named the old element.
- The page must render complete without the script; animation starts only
once on screen and after the splash (
pixel:splashdone), and reduced motion gets the rest state.
Build and look
cd website
mise exec -- hugo --gc -d "$SCRATCH/site" --baseURL http://localhost:8765/
python3 -m http.server 8765 --directory "$SCRATCH/site" # background task
Then, with agent-browser --session <name> (a separate browser; see
~/.claude/notes/browser.md): open first, then set viewport 1440 900
(once per instance: close + open + set for another size), wait for
the animation, screenshot to an absolute path. --full captures can start
mid-page on this site: scroll with eval "(()=>{scrollTo(0,N);return 1})()"
and take viewport shots instead. Extract the page's inline scripts and
node --check them when a capture looks empty. Look at both widths before
showing the user, and fix what you see first (truncated commands, empty
reserved space, a badge over text).
Gates and pull request
cargo test -p pixel-cli --test cli docs_drift::(it readsindex.html,agents.tomlandobjections.toml).- No
.github/changelog.d/fragment: website-only changes ship nothing in the tool (CONTRIBUTING.md, "Definition of done"). - Show the captures and get the user's go before the commit; then commit
(
docs(website): … for task #N), push, and open or update the pull request withTask <N>on its first line and the captures described in its body. The board goes to In Progress when the PR opens.
Decisions that bind every section
Made with the user during the hero (2026-09-30); do not reopen them without being asked:
- The navbar does not change.
- Agents are named with their logo, the name small underneath: several are not household names.
- Do not say agents read "whole files": they grep and read slices. The
benchmark compares a whole-file read with
list-signatures, and copy says that, nothing wider. - Nobody learns a command: the agent picks the Pixel command itself. Show it ("Your agent picked this command. You typed nothing.").
- No install command before the Install chapter: convince first.
- Columns stay balanced on desktop; a layout that leaves one side empty is a defect.
- Honesty over punch: a figure carries its median and its method link.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |