@hybridlabor-api/aos 4.17.0 → 4.18.0

package/skills/global_config/visual-plan/references/wireframe.md

@@ -1,319 +0,0 @@
-# HTML wireframe quality — single source of truth
-
-This file is the canonical quality bar for HTML wireframes / `<Screen>` /
-`WireframeBlock` content, shared word for word by `/visual-plan` and
-`/visual-recap`. Read it in full before authoring ANY wireframe; do not
-author wireframes from memory or paraphrase these rules per command.
-
-<!-- SHARED-CORE:wireframe-quality START -->
-
-**A wireframe is an HTML mockup. The renderer owns the look; you write the
-content.** Set `data.html` to a self-contained, semantic HTML fragment of the
-screen and set `data.surface`. The renderer owns the surface footprint/aspect,
-the dark/light theme, the hand-drawn font, and the rough.js sketch overlay — you
-never write `<html>`/`<body>`/`<script>`/`<style>` tags or any
-width/height/coordinates. You write real HTML layout and real product
-content; the renderer styles and roughens it.
-
-**A wireframe block's data is an HTML screen plus a surface:**
-
-```json
-{
-  "surface": "browser",
-  "html": "<div style=\"display:flex;flex-direction:column;gap:10px;padding:16px;height:100%\"><h1>Sign in</h1><p class=\"wf-muted\">Use your work email to continue.</p><div class=\"wf-card\" style=\"display:flex;flex-direction:column;gap:10px\"><label>Email<input value=\"jane@acme.co\" /></label><label>Password<input value=\"••••••••\" /></label><label style=\"display:flex;align-items:center;gap:8px\"><input type=\"checkbox\" checked /> Remember me</label><button class=\"primary\">Sign in</button></div><a href=\"#\">Forgot password?</a></div>"
-}
-```
-
-**Write PLAIN semantic HTML and let the renderer style it.** Bare elements
-(`h1`/`h2`/`h3`, `p`, `button`, `input`, `<input type="checkbox">`, `a`, `hr`)
-are auto-themed — no classes needed. Helper classes carry the rest:
-
-- `.wf-card` / `.wf-box` — a bordered, padded container (a panel, a list item).
-- `.wf-pill` / `.wf-chip` — a rounded tag or filter; add `.accent`
-  (`<span class="wf-pill accent">`) for the accent-filled variant.
-- `.wf-muted` — secondary/muted text (or use `<small>`).
-- `button.primary` or any element with `[data-primary]` — the accent-filled
-  primary button.
-
-**No decorative shadows around mockups.** Do not put `box-shadow`, `filter:
-drop-shadow(...)`, Tailwind `shadow-*` classes, or other fake depth effects on a
-wireframe frame, root container, `.wf-card` / `.wf-box`, or canvas artboard.
-Mockups should read as flat, bordered surfaces; use spacing, borders, labels,
-and annotations for separation. Only show a shadow when the real product UI
-already has that shadow and it is essential to the change being reviewed.
-
-**Use renderer icons, not visible icon words.** For icon-only buttons or leading
-icons inside fields, chips, menu items, and toolbars, write an empty marker such
-as `<span data-icon="mail" aria-label="Email"></span>` or
-`<i data-icon="lock"></i>`. The renderer replaces it with a Tabler-style SVG and
-the `.wf-icon` class sizes it to the surrounding text. Supported names and
-aliases: `mail`/`email`, `lock`/`password`, `search`, `plus`/`add`, `x`/`close`,
-`check`, `chevronDown`, `chevronUp`, `chevronLeft`, `chevronRight`, `dots`/`more`,
-`chevron`/`caret`/`dropdown` (down chevron), `user`, `settings`, `calendar`,
-`bell`, `send`, `edit`, `arrowLeft`, and `arrowRight`. Do not put visible words
-like "email", "lock", "search", "chevron", or "more" where the product UI would
-show an icon; use text only when it is a real label a user would read.
-
-**Use the `--wf-*` tokens for any custom color, never hex.** The renderer flips
-these on light/dark, so reading them is what keeps a mockup correct in both
-themes. For any inline border, background, or text color, reference a token:
-`style="border:1.4px solid var(--wf-line)"`. The tokens are `--wf-ink` (text),
-`--wf-muted` (secondary text), `--wf-line` (borders/dividers), `--wf-paper`
-(page background), `--wf-card` (container surface), `--wf-accent` /
-`--wf-accent-fg` / `--wf-accent-soft` (brand action), `--wf-warn`, `--wf-ok`,
-and `--wf-radius`. Never hard-code a hex color and never set `font-family` — the
-renderer owns the sketch/clean font.
-
-**Never use host/Tailwind theme classes in wireframe HTML.** Classes such as
-`bg-white`, `bg-zinc-50`, `bg-slate-950`, `text-zinc-950`,
-`text-slate-400`, `border-zinc-200`, `hover:bg-slate-800`, `shadow-xl`,
-or arbitrary color utilities like `bg-[#fff]` leak the host app's CSS into the
-mockup and can make dark-mode canvas frames unreadable. Use bare semantic
-elements, `.wf-*` helper classes, and `--wf-*` color tokens instead. Before
-publishing, scan every wireframe `class` and `style` attribute: if a class sets
-background, text, border, ring, fill, stroke, gradient, placeholder, decoration,
-or shadow color, rewrite it to renderer tokens or remove it. Layout-only classes
-are still discouraged; inline flex/grid styles are safer and easier to review.
-
-**Keep Rough.js sparse.** The renderer sketches the outer frame, standard
-`.wf-*` primitives, controls, and inline border dividers by default. Do not add
-`data-rough` to broad root wrappers, dialog shells, page panels, grid cells, or
-nested containers unless that single container is the visual point. Use
-`data-rough` only for a deliberate one-off shape. If a mockup starts looking
-like stacked/overlapping sketch lines, remove rough targets from parent
-containers and let backgrounds plus spacing separate the surfaces.
-
-**Use literal CSS lengths for spacing.** The `--wf-*` tokens are for colors and
-renderer-owned visual styling, not layout spacing. Do not use guessed spacing
-tokens such as `var(--wf-space-4)`, Tailwind spacing classes, or theme spacing
-variables inside wireframe HTML; if a token is unavailable in the Plan renderer,
-padding collapses and content hugs the border. Use explicit CSS lengths for
-layout: `padding:16px`, `gap:12px`, `margin-top:18px`, `minmax(0,1fr)`.
-
-**Lay out with inline `style` flex/grid.** You write the real layout —
-`display:flex; flex-direction:column; gap:10px; padding:16px` and so on — and the
-renderer never repositions anything. Compose the actual product: reproduce the
-current screen, then show the modification. Real labels, real counts, real dates,
-real button text grounded in the screen you read; not lorem or gray bars.
-
-**Surface presets — match the real footprint, never default to desktop+mobile.**
-Pick the `surface` that matches what the user will actually see:
-
-- `browser`: a web page that needs a browser chrome frame around it.
-- `desktop`: a full desktop app page or app shell.
-- `mobile`: a phone screen, only when the work is genuinely mobile.
-- `popover`: a small floating menu, dropdown, or inline popover.
-- `panel`: a side panel, inspector, or sidebar widget.
-
-A sidebar popover renders as a small surface, not a desktop page and a phone
-frame. Do not emit `desktop` + `mobile` variants unless responsive behavior
-actually changes the layout. For a component or widget, show one broader
-app-context frame only when placement affects understanding, then the focused
-component states.
-
-**Model the actual component shell for small surfaces.** A rendered UI change
-belongs in a wireframe; reserve `diagram` for architecture, dependency, state,
-or data-flow relationships. Popovers, dropdown menus, command palettes, and
-context menus use `surface: "popover"` unless the surrounding page placement is
-the point of the change. Dialogs, sheets, inspectors, sidebars, and long
-property panels use the matching `panel` / `desktop` surface as appropriate.
-Show the real chrome: trigger or anchor when it matters, title/header row,
-top-right actions, separators, fields, options, selected states, body content,
-and footer actions that are visible in the workflow.
-
-**Modify, don't redesign.** When the task changes an existing screen, reproduce
-the current screen's real layout and footprint FIRST, then change only the delta
-and call it out with a single annotation. Do not restack the page into a new
-layout. For net-new surfaces, compose from the real app shell. Inspect the
-actual app components before drawing an existing product: sidebar density,
-toolbar actions, overflow menus, property panels, and framework chrome should
-match the product unless the plan intentionally changes them.
-
-**Keep product screens pure.** A product wireframe shows the app state a user
-would actually see. Do not embed file contracts, architecture arrows, repo pills,
-mode explanations, or implementation callouts inside the screen just to explain
-the plan. Put those in canvas annotations, a separate diagram, or the document
-body. Secondary UI such as properties, history, sync, export, or agent controls
-should appear where the real product would put them: an overflow popover, sheet,
-panel, or separate framework sidebar state, not a generic permanent right
-inspector unless that inspector is the actual design.
-
-**Classify mockup scope before implementation.** Before turning a plan mockup
-into source code, decide whether each artboard represents the whole page/app
-shell, a route body inside an existing shell, or a component/sub-surface. If an
-artboard includes navigation, sidebars, auth banners, or a signup/login form,
-map those pieces to the real shared shell/auth components instead of nesting the
-entire mockup inside the current page. When a mockup references the product's
-standard signup/login page, find and reuse that existing implementation; do not
-approximate it from the wireframe.
-
-**Zoom in on sub-surfaces, don't redraw the page.** For a small sub-surface (a
-popover, menu, dialog, toast), show the full screen once, then add a small
-separate artboard whose `html` contains ONLY that sub-surface — do not re-draw
-the whole page around it, and do not scale a duplicate up. Pick the matching
-`surface` (e.g. `popover`) so the footprint is right; never widen a popover to
-page width.
-
-**Loading / skeleton states.** Set `data.skeleton: true` on the wireframe and
-fill the `html` with neutral, textless placeholder geometry — boxes and bars
-built as `<div>`s with `background:var(--wf-line)` and explicit heights/widths,
-no labels or copy. The renderer drops borders, sketch, and color into the
-skeleton register automatically. Never escape to a `custom-html` document block
-to fake a loader.
-
-**Editing an existing mockup.** In hosted mode, to change one element, text, or
-color in an existing html mockup, do not regenerate the frame — call
-`update-visual-plan` with
-`contentPatches: [{ op: "patch-wireframe-html", blockId, edits: [{ find,
-replace }] }]`. Each `find` is a unique snippet of the current html (read it
-first with `get-visual-plan`); set `all: true` on an edit to replace every
-occurrence. The result is re-sanitized. In local-files privacy mode, do not call
-hosted Plan tools; edit the local MDX source directly and rerun the local
-check/serve or verify command for `<plan-dir>`.
-
-**Choose the outer frame deliberately.** Wireframe and diagram data accept
-`frame: "auto" | "show" | "hide"` in block data (`<Screen frame="hide">` in
-MDX wireframes, `<Diagram frame="hide">` for MDX diagrams). Leave it unset or
-`auto` when the host context should decide: Plan and recap surfaces default to a
-drawn outer frame; docs surfaces default to no outer frame. Use `show` for
-standalone product screens, before/after recap comparisons, screenshot-like
-artifacts, and visuals that need containment from surrounding prose. Use `hide`
-when a docs page, tab, column, card, canvas artboard, or the visual's own
-internal chrome already supplies the boundary. Do not use `hide` to compensate
-for cramped content; fix the layout instead.
-
-**Inner padding and borders still matter.** Always wrap HTML wireframe content
-in a root container with real inner padding before drawing cards, fields, pills,
-labels, or controls. Use at least 14-16px of padding, `box-sizing: border-box`,
-`height: 100%`, and `gap` between child rows on the root node itself so the
-first row never sits flush against the screen edge. Do not rely on padding on a
-nested page section as the first visible inset; the outermost element must
-create the breathing room. Keep text away from borders: every container, field,
-button, menu item, and annotation needs enough padding and line-height to read
-cleanly in the rendered Plan view.
-
-**Center page-like content inside broad surfaces.** For browser or desktop
-screens, let the outer root provide the full-width frame and padding, then keep
-the page body in a centered wrapper such as
-`width:100%;max-width:720px;margin-inline:auto`. Full-width app bars may span
-the root, but onboarding, auth, settings, and other page-like content should
-not hug the left border unless the real product does.
-
-**For feature-cloud or abundance visuals, optimize the composition over line-by-line
-reading.** Some marketing/product sections need to feel like a large surface area
-of capability rather than a precise app workflow. In those cases, use one padded
-root with a short headline and a dense, aesthetic cloud of short feature labels,
-chips, rings, or columns. Vary scale and opacity with tokens, cluster by meaning,
-and let many labels be glanceable rather than individually essential. Do not
-force dozens of features into equal cards with long wrapped sentences; that
-usually creates a messy unreadable mockup.
-
-**Lay out children safely so they never collide.** Use HTML flex/grid with
-`gap`, `min-width: 0`, and sensible overflow. Avoid negative margins, absolute
-positioning, or fixed child widths that can collide when the renderer switches
-between light/dark, sketch/clean, or different zoom levels.
-
-**Do not wrap intentionally single-line labels.** For toolbars, tab rails,
-breadcrumbs, chip/filter rows, branch and file names, file chips, and code
-filenames — any deliberately single-line row — do not let long text wrap. Put
-`white-space: nowrap` on the row (and `overflow: hidden; text-overflow: ellipsis`
-on the individual labels that can grow), so the wireframe demonstrates the actual
-layout behavior instead of producing ugly stacked or vertical text. Use
-horizontally scrollable or clipped rails for overflow.
-
-**Fill the frame; keep labels short.** Each artboard is a fixed-size surface — compose enough realistic HTML to fill it top to bottom with even vertical rhythm; never leave a large empty band. On desktop/app-shell sidebars, let the nav stack flex to fill (`flex:1`) and add any persistent bottom action/status after it so the rail reads complete in taller frames. On mobile especially, flow real rows down the whole screen (status bar, header, then list/detail content) rather than a header floating above a gap. Keep every label short enough to sit on one line within its column — shorten the copy rather than relying on the frame to absorb it (long labels wrap or clip).
-
-**Persistent chrome bars span the full frame width.** Top bars, app headers,
-toolbars, and bottom tab/nav bars are full-width chrome, not centered content.
-Lay each one out as a single flex row that fills the frame
-(`style="display:flex;align-items:center;width:100%"`) and push trailing actions
-to the right edge with a flex spacer (`<div style="flex:1"></div>`) between the
-leading group and the trailing group — never center a bar inside a narrow,
-centered block, and never let it collapse to the width of its contents. In a
-Before/After pair the bar stays full-width in BOTH states even when one state has
-fewer controls; the spacer absorbs the difference so the remaining controls hold
-their edge alignment instead of sliding to the center.
-
-**Pin bottom bars to the bottom of the frame.** For mobile tab bars, footers, and
-any persistent bottom action row, make the frame itself a flex column at
-`height:100%` (`style="display:flex;flex-direction:column;height:100%"`), give the
-scrolling body `flex:1` so it absorbs the slack, and place the bar as the LAST
-child of the frame (or set `margin-top:auto` on it). The bar then sits flush at
-the bottom of the surface instead of floating directly under the content with an
-empty band beneath it.
-
-**Before / after must be comparable.** When showing a state change, preserve the
-unchanged controls in both states so the reviewer can see exactly what moved or
-appeared; do not show an added control as a generic box floating elsewhere in
-the surface. Place the new/changed affordance where the implementation puts it —
-for example, a new `Edit with AI` action in a popover header belongs in the
-top-right header slot, aligned with the title, not in the body or footer. Use
-the same frame size, scale, outer padding, border radius, and visual density on
-both sides unless the change itself alters those properties, and let the frame
-height fit the content rather than leaving a tall empty lower half.
-
-**Name the states with the column header, never inside the frame.** For
-document-body wireframes (recaps), put the two
-states in a `columns` block and set each column's `label` to `Before` and
-`After` — the renderer draws that label as an `h4` heading above each frame. Do
-NOT bake a `Before`/`After` pill, title, or heading into the wireframe `html`: a
-label placed inside reads as part of the product UI, lands in a random corner,
-and clutters the comparison. The column header is the one and only place the
-state name belongs. On a canvas, place the two state artboards as neighbors with
-frame labels — never encode Before/After inside the html.
-
-**Let the surface choose side-by-side vs. stacked.** For document-body
-wireframes (recaps), the `columns` renderer lays
-narrow surfaces (`mobile`, `popover`, `panel`) out side by side, and
-automatically stacks wide surfaces (`desktop`, `browser`) vertically at full
-document width so a large frame is never crushed into a half-width column and
-cropped. Author both wireframes with the real `surface` and the matching
-`Before`/`After` column labels; do not hand-stack the pair into separate
-top-level wireframes or duplicate the state name as body content.
-
-**Good example — a contacts list, surface `browser`.** A small, real screen
-composed from the helper classes and tokens, layout in inline flex, no fonts or
-hex colors:
-
-```html
-<div
-  style="display:flex;flex-direction:column;gap:12px;padding:16px;height:100%"
->
-  <div style="display:flex;align-items:center;justify-content:space-between">
-    <h1>Contacts</h1>
-    <button class="primary">New contact</button>
-  </div>
-  <div style="display:flex;gap:6px">
-    <span class="wf-pill accent">All 128</span>
-    <span class="wf-pill">Favorites</span>
-    <span class="wf-pill">Archived</span>
-  </div>
-  <div
-    class="wf-card"
-    style="display:flex;flex-direction:column;gap:0;padding:0"
-  >
-    <div
-      style="display:flex;align-items:center;gap:10px;padding:10px 12px;border-bottom:1.4px solid var(--wf-line)"
-    >
-      <div
-        style="width:32px;height:32px;border-radius:999px;background:var(--wf-accent-soft)"
-      ></div>
-      <div style="flex:1">
-        <strong>Jane Cooper</strong><br /><small>jane@acme.co</small>
-      </div>
-      <span class="wf-pill">Lead</span>
-    </div>
-    <div style="display:flex;align-items:center;gap:10px;padding:10px 12px">
-      <div
-        style="width:32px;height:32px;border-radius:999px;background:var(--wf-accent-soft)"
-      ></div>
-      <div style="flex:1">
-        <strong>Marcus Lee</strong><br /><small>marcus@globex.io</small>
-      </div>
-      <span class="wf-pill">Customer</span>
-    </div>
-  </div>
-</div>
-```
-
-<!-- SHARED-CORE:wireframe-quality END -->

package/skills/global_config/visual-recap/README.md

@@ -1,103 +0,0 @@
-# /visual-recap
-
-Turn a branch, commit, or PR diff into an interactive visual recap with
-annotated diffs, diagrams, API/schema summaries, file maps, UI state summaries,
-and focused review notes.
-
-`/visual-recap` is the reverse of `/visual-plan`: instead of planning a future
-change, it summarizes a diff, branch, commit, or PR after the work exists. The
-goal is to help reviewers understand the shape of a change before they dive into
-raw line-by-line diffs.
-
-It solves for diffs that hide the shape of the change. Reviewers can understand
-contracts, architecture moves, schema changes, and UI impact before diving into
-raw line-by-line review.
-
-The recap is a human-optimized MDX document with custom components for the
-things raw diffs are bad at explaining: annotated diffs, diagrams, visual schema
-maps, OpenAPI-style API diffs, file maps, UI state summaries, and focused review
-notes.
-
-Visual recaps are MDX, customizable with your own components, and viewed with
-the [Agent-Native plans app](https://www.agent-native.com/docs/template-plan).
-The hosted app is 100% free and open source; local-files mode writes the recap
-MDX locally, starts a localhost bridge, and opens the hosted Plan UI with no
-sharing.
-[Source here](https://github.com/BuilderIO/agent-native/).
-
-<picture>
-  <img alt="Visual recap review surface animation" src="../../media/visual-recap.gif">
-</picture>
-
-## What It Does
-
-- Reads the actual changed files and diff.
-- Publishes an interactive recap with file maps, diagrams, visual schema
-  maps, API diffs, annotated diffs, UI state summaries, and focused key changes.
-- Keeps recaps substantial enough for real review without dumping every line.
-- Makes large changes consumable before a reviewer opens raw GitHub diff view.
-- Can be installed with a reusable GitHub Action for PR visual recaps.
-
-## When To Use It
-
-Use it for PRs or work units that are large, multi-file, UI-heavy, or touch
-schema, API contracts, permissions, architecture, or review-critical behavior.
-
-Skip it for tiny, obvious diffs that review faster directly in GitHub.
-
-## What Reviewers Get
-
-Reviewers get the shape of the change first: what moved, which contracts
-changed, what data or API surfaces were touched, how UI states differ, and where
-the risky lines are. Then they can review the raw diff with a map in their head.
-
-## Modes
-
-`/visual-recap` can run in three modes:
-
-- **Hosted Plans, shareable links (recommended):** uses the free, open-source
-  Agent-Native plans app at plan.agent-native.com for shareable links, comments,
-  and the browser editor.
-- **Local files only:** writes a local MDX folder, starts a localhost bridge,
-  and opens the hosted Plan UI against that local source. No sharing, all local,
-  and no recap content is written to the hosted database.
-- **Self-hosted/custom URL:** connects the skill to your own Plan app or local
-  development tunnel.
-
-Use hosted mode when you want comments and shareable links. Use local files mode
-when the recap should live in source control or stay on your machine. Use
-`plans/<slug>/` when you want to check the files in, or a temp/ignored folder
-when you do not. The bridge URL works on the machine running it and is not a
-share link.
-
-## GitHub Action
-
-When installed with `--with-github-action`, this repo writes a PR workflow that
-can automatically generate a visual recap from every pull request diff.
-Reviewers open the generated PR recap in the
-[Plan app review surface](https://www.agent-native.com/docs/template-plan)
-before moving into raw GitHub diff view.
-
-The top-level installer also offers the PR action as an option:
-
-```sh
-npx @agent-native/skills@latest add
-```
-
-![Example of a visual recap posted to a PR](https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2Fcf9bac396cf24a4ba976fc331af6fc5d)
-
-## Install
-
-```sh
-npx @agent-native/skills@latest add --skill visual-recap --with-github-action
-```
-
-The interactive installer asks whether to use hosted Plans or local files. To
-force the no-sharing local path:
-
-```sh
-npx @agent-native/skills@latest add --skill visual-recap --mode local-files
-```
-
-The skill expects the [Plan MCP connector](https://www.agent-native.com/docs/template-plan)
-to be available when hosted mode is used.