mirror of
https://github.com/jparkerweb/plan2code.git
synced 2026-11-16 04:45:33 -08:00
3822 lines
208 KiB
HTML
3822 lines
208 KiB
HTML
<!doctype html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="utf-8" />
|
||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||
<meta name="color-scheme" content="light dark" />
|
||
<title>Plan2Code Console</title>
|
||
<link rel="stylesheet" href="/app.css" />
|
||
<!-- Every module up front. Without these the browser finds render.js and
|
||
answers.js only once app.js has arrived and been parsed, and marked
|
||
only once render.js has: three round trips in a row before the page
|
||
can draw anything real. -->
|
||
<link rel="modulepreload" href="/app.js" />
|
||
<link rel="modulepreload" href="/answers.js" />
|
||
<link rel="modulepreload" href="/skills.js" />
|
||
<link rel="modulepreload" href="/spec-states.js" />
|
||
<link rel="modulepreload" href="/state.js" />
|
||
<link rel="modulepreload" href="/doc-files.js" />
|
||
<link rel="modulepreload" href="/send-state.js" />
|
||
<link rel="modulepreload" href="/mention-box.js" />
|
||
<link rel="modulepreload" href="/uploads.js" />
|
||
<link rel="modulepreload" href="/sound.js" />
|
||
<link rel="modulepreload" href="/looks.js" />
|
||
<link rel="modulepreload" href="/selectors.js" />
|
||
<link rel="modulepreload" href="/screens/core.js" />
|
||
<link rel="modulepreload" href="/screens/ending.js" />
|
||
<link rel="modulepreload" href="/screens/docs.js" />
|
||
<link rel="modulepreload" href="/screens/cards.js" />
|
||
<link rel="modulepreload" href="/screens/starting.js" />
|
||
<link rel="modulepreload" href="/screens/dashboard.js" />
|
||
<link rel="modulepreload" href="/screens/git-host.js" />
|
||
<link rel="modulepreload" href="/screens/looks.js" />
|
||
<link rel="modulepreload" href="/screens/prefs-dialog.js" />
|
||
<link rel="modulepreload" href="/screens/agents-view.js" />
|
||
<link rel="modulepreload" href="/screens/cleanup.js" />
|
||
<link rel="modulepreload" href="/screens/help-dialog.js" />
|
||
<link rel="modulepreload" href="/screens/workspace.js" />
|
||
<link rel="modulepreload" href="/screens/ask.js" />
|
||
<link rel="modulepreload" href="/screens/notepad.js" />
|
||
<link rel="modulepreload" href="/screens/activities.js" />
|
||
<link rel="modulepreload" href="/activities.js" />
|
||
<link rel="modulepreload" href="/tones.js" />
|
||
<link rel="modulepreload" href="/net.js" />
|
||
<link rel="modulepreload" href="/render.js" />
|
||
<link rel="modulepreload" href="/palette.js" />
|
||
<link rel="modulepreload" href="/labels.js" />
|
||
<link rel="modulepreload" href="/boot.js" />
|
||
<link rel="modulepreload" href="/chat.js" />
|
||
<link rel="modulepreload" href="/help.js" />
|
||
<link rel="modulepreload" href="/tabs.js" />
|
||
<link rel="modulepreload" href="/prefs.js" />
|
||
<link rel="modulepreload" href="/starters.js" />
|
||
<link rel="modulepreload" href="/workspace.js" />
|
||
<link rel="modulepreload" href="/meter.js" />
|
||
<link rel="modulepreload" href="/subagents.js" />
|
||
<link rel="modulepreload" href="/mentions.js" />
|
||
<link rel="modulepreload" href="/favicon.js" />
|
||
<link rel="modulepreload" href="/app-bridge.js" />
|
||
<link rel="modulepreload" href="/git-board.js" />
|
||
<link rel="modulepreload" href="/git-board-view.js" />
|
||
<link rel="modulepreload" href="/pr-url.js" />
|
||
<link rel="modulepreload" href="/vendor/marked.esm.js" />
|
||
<link rel="modulepreload" href="/notepad.js" />
|
||
<link rel="modulepreload" href="/notepad-tabs.js" />
|
||
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
|
||
<link rel="icon" type="image/png" sizes="192x192" href="/favicon.png" />
|
||
</head>
|
||
<body>
|
||
<a class="skip" href="#main">Skip to the questions</a>
|
||
|
||
<div id="banner" class="banner" role="status" hidden></div>
|
||
|
||
<!-- Planny's wake-up on a freshly opened dashboard: a large copy of the
|
||
rail drawing that powers on center stage, then glides into the rail.
|
||
Hidden unless boot.js is playing it; placed entirely by app.css,
|
||
because the CSP refuses style attributes. -->
|
||
<div class="wake" id="wake" hidden>
|
||
<svg class="wake-bot" viewBox="0 0 22 30" focusable="false" aria-hidden="true">
|
||
<g class="body">
|
||
<rect class="foot f1" x="5.7" y="27.1" width="3.6" height="1.7" rx="0.85" />
|
||
<rect class="foot f2" x="12.7" y="27.1" width="3.6" height="1.7" rx="0.85" />
|
||
<rect class="shell" x="3" y="7" width="16" height="20" rx="3.2" />
|
||
<g class="look">
|
||
<path class="eye" d="M11 10.95 L11.79 12.91 L13.9 13.06 L12.28 14.42 L12.79 16.47 L11 15.35 L9.21 16.47 L9.72 14.42 L8.1 13.06 L10.21 12.91 Z" />
|
||
<path class="scan" d="M11 10.6 V17.4" />
|
||
</g>
|
||
<path class="smile" d="M8.3 18.4 Q11 21 13.7 18.4" />
|
||
<g class="limb l"><path d="M3 18 L1.3 21" /><circle cx="1.3" cy="21" r="0.85" /></g>
|
||
<g class="limb r"><path d="M19 18 L20.7 21" /><circle cx="20.7" cy="21" r="0.85" /></g>
|
||
</g>
|
||
<g class="zzz">
|
||
<path d="M15.4 3.4 h2.2 l-2.2 2.2 h2.2" />
|
||
<path d="M17.2 0 h1.8 l-1.8 1.8 h1.8" />
|
||
<path d="M18.8 -3.1 h1.4 l-1.4 1.4 h1.4" />
|
||
</g>
|
||
</svg>
|
||
<p class="wake-hint">Click to wake Planny</p>
|
||
<button class="wake-skip" type="button" aria-label="Skip the intro">Skip</button>
|
||
</div>
|
||
|
||
<header class="topbar">
|
||
<div class="topbar-row">
|
||
<div class="ident">
|
||
<span class="badge" id="badge">Pathfinder</span>
|
||
<h1 id="title">Plan2Code Console</h1>
|
||
<!-- The session meter: how much this console session has done. The
|
||
ring fills with the points (full at 15); the color is the
|
||
level. Hidden until a frame carries `meter`. -->
|
||
<span class="meter-slot">
|
||
<button
|
||
type="button"
|
||
class="meter-pill"
|
||
id="meter-pill"
|
||
hidden
|
||
aria-haspopup="dialog"
|
||
aria-expanded="false"
|
||
aria-controls="meter-pop"
|
||
>
|
||
<svg class="meter-ring" viewBox="0 0 20 20" aria-hidden="true" focusable="false">
|
||
<circle class="meter-track" cx="10" cy="10" r="7" />
|
||
<circle
|
||
class="meter-fill"
|
||
id="meter-fill"
|
||
cx="10"
|
||
cy="10"
|
||
r="7"
|
||
pathLength="100"
|
||
stroke-dasharray="100 100"
|
||
stroke-dashoffset="100"
|
||
/>
|
||
</svg>
|
||
<span id="meter-words">Session: fresh</span>
|
||
</button>
|
||
<div class="meter-pop" id="meter-pop" role="dialog" aria-label="Session meter" hidden>
|
||
<p class="meter-tip" id="meter-tip"></p>
|
||
<ul class="meter-list" id="meter-list" aria-label="What the points are made of" hidden></ul>
|
||
<div class="meter-fresh" id="meter-fresh" hidden></div>
|
||
<button type="button" class="linky" id="meter-help">What is this?</button>
|
||
</div>
|
||
</span>
|
||
</div>
|
||
<div class="progress-block">
|
||
<div class="progress-label">
|
||
<span id="progress-text">Getting started</span>
|
||
<span id="confidence" class="confidence"></span>
|
||
</div>
|
||
<div class="progress-track" role="progressbar" aria-labelledby="progress-text" id="progress-bar">
|
||
<div class="progress-fill" id="progress-fill"></div>
|
||
</div>
|
||
</div>
|
||
<button
|
||
type="button"
|
||
class="icon-btn"
|
||
id="btn-looks"
|
||
title="Colors, theme and sound"
|
||
aria-label="Colors, theme and sound"
|
||
>
|
||
<!-- A gear: ring, hub and eight teeth. -->
|
||
<svg viewBox="0 0 16 16" aria-hidden="true" focusable="false">
|
||
<path class="gr-teeth" d="M12 8h2.6M8 12v2.6M4 8H1.4M8 4V1.4M10.83 10.83l1.84 1.84M5.17 10.83l-1.84 1.84M5.17 5.17L3.33 3.33M10.83 5.17l1.84-1.84" />
|
||
<circle cx="8" cy="8" r="4.2" class="gr-ring" />
|
||
<circle cx="8" cy="8" r="1.6" class="gr-hub" />
|
||
</svg>
|
||
</button>
|
||
<button
|
||
type="button"
|
||
class="icon-btn"
|
||
id="btn-about"
|
||
title="Help"
|
||
aria-label="Help"
|
||
>
|
||
<!-- Drawn, not a "?" glyph, so it does not depend on a font. -->
|
||
<svg viewBox="0 0 16 16" aria-hidden="true" focusable="false">
|
||
<circle cx="8" cy="8" r="7" class="ab-ring" />
|
||
<path class="ab-mark" d="M6.1 6.05a1.95 1.95 0 1 1 2.4 1.9v1.25" />
|
||
<circle cx="8" cy="11.7" r="0.85" class="ab-dot" />
|
||
</svg>
|
||
</button>
|
||
<a
|
||
class="icon-btn"
|
||
id="btn-feedback"
|
||
href="https://github.com/jparkerweb/plan2code/issues/new/choose"
|
||
target="_blank"
|
||
rel="noopener noreferrer"
|
||
title="Report a bug or suggest an idea"
|
||
aria-label="Report a bug or suggest an idea (opens GitHub in a new tab)"
|
||
>
|
||
<!-- A megaphone: horn, handle and two sound waves. -->
|
||
<svg viewBox="0 0 16 16" aria-hidden="true" focusable="false">
|
||
<path class="mg-body" d="M1.8 6.2h2.8L10.4 3v10L4.6 9.8H1.8z" />
|
||
<path class="mg-line" d="M4.6 9.8l.9 3.4h1.6l-.6-2.7M12.4 6.1a2.6 2.6 0 0 1 0 3.8M13.8 4.5a5 5 0 0 1 0 7" />
|
||
</svg>
|
||
</a>
|
||
<!-- Activities: small games for a long wait. Opens a dialog that pauses
|
||
the moment Plan2Code needs the person; nothing in it reaches the agent. -->
|
||
<button type="button" class="icon-btn" id="btn-activities" title="Activities" aria-label="Activities">
|
||
<!-- A die: a rounded square and five pips. -->
|
||
<svg viewBox="0 0 16 16" aria-hidden="true" focusable="false">
|
||
<rect class="dc-body" x="2" y="2" width="12" height="12" rx="2.6" />
|
||
<circle class="dc-pip" cx="5.4" cy="5.4" r="1" />
|
||
<circle class="dc-pip" cx="10.6" cy="5.4" r="1" />
|
||
<circle class="dc-pip" cx="8" cy="8" r="1" />
|
||
<circle class="dc-pip" cx="5.4" cy="10.6" r="1" />
|
||
<circle class="dc-pip" cx="10.6" cy="10.6" r="1" />
|
||
</svg>
|
||
</button>
|
||
</div>
|
||
<div class="topbar-row second">
|
||
<div class="row-left">
|
||
<!-- Back to the dashboard: every skill but the dashboard itself. A
|
||
filled triangle in the highlight color, pointing the way home. -->
|
||
<button
|
||
type="button"
|
||
class="btn ghost small home-btn"
|
||
id="btn-home"
|
||
title="Back to the dashboard"
|
||
aria-label="Back to the dashboard"
|
||
hidden
|
||
>
|
||
<svg viewBox="0 0 12 12" aria-hidden="true" focusable="false"><path d="M9.5 1.5v9L2 6z" /></svg>
|
||
</button>
|
||
<button type="button" class="btn ghost small stop-btn" id="btn-stop">Stop session</button>
|
||
<button type="button" class="btn ghost small brief-btn" id="btn-brief" hidden>
|
||
Write a brief
|
||
</button>
|
||
<!-- Subagents: opted-in skills only. Lit while helpers are on; a click
|
||
opens the Subagents dialog and never toggles them itself. -->
|
||
<button type="button" class="btn ghost small subagents-btn" id="btn-subagents" aria-pressed="false" hidden>
|
||
<!-- An orchestrator and its helpers: one larger node linked to three smaller ones. -->
|
||
<svg viewBox="0 0 16 16" aria-hidden="true" focusable="false">
|
||
<path class="sa-link" d="M6.9 6.6L10.9 3.9M7.4 8h3.5M6.9 9.4l4 2.7" />
|
||
<circle cx="4.6" cy="8" r="2.6" class="sa-hub" />
|
||
<circle cx="12.4" cy="3" r="1.5" class="sa-node" />
|
||
<circle cx="12.4" cy="8" r="1.5" class="sa-node" />
|
||
<circle cx="12.4" cy="13" r="1.5" class="sa-node" />
|
||
</svg>
|
||
</button>
|
||
<!-- Notebook: every screen, never hidden. The person's private notes for this
|
||
folder; a tab reaches the agent only through a send the person
|
||
starts on the dashboard. -->
|
||
<button type="button" class="btn ghost small notepad-btn" id="btn-notepad" title="Notebook" aria-label="Notebook">
|
||
<!-- A pocket notebook: a closed cover with a spine line and an elastic band. -->
|
||
<svg viewBox="0 0 16 16" aria-hidden="true" focusable="false">
|
||
<rect class="np-page" x="3.5" y="1.8" width="9" height="12.4" rx="1.3" />
|
||
<path class="np-line" d="M10.2 1.8v12.4" />
|
||
<rect class="np-band" x="9.4" y="6.5" width="1.6" height="3" rx=".5" />
|
||
</svg>
|
||
<span class="notepad-label">Notebook</span>
|
||
</button>
|
||
</div>
|
||
<div class="views-group">
|
||
<span class="views-arrow" aria-hidden="true">
|
||
<svg viewBox="0 0 10 16" focusable="false"><path d="M2 2l6 6-6 6" /></svg>
|
||
<svg viewBox="0 0 10 16" focusable="false"><path d="M2 2l6 6-6 6" /></svg>
|
||
<svg viewBox="0 0 10 16" focusable="false"><path d="M2 2l6 6-6 6" /></svg>
|
||
</span>
|
||
<nav class="views" id="views" aria-label="Views"></nav>
|
||
</div>
|
||
</div>
|
||
</header>
|
||
|
||
<div class="layout">
|
||
<div class="rail">
|
||
<!-- Planny. Drawn here rather than built in script because the page
|
||
runs under a CSP with no inline script, and because a mascot that
|
||
only ever changes class does not need a renderer. The parts are
|
||
named so app.js can say what he is doing with one class. -->
|
||
<div class="dock" id="dock">
|
||
<!-- Proportioned after the ASCII Planny, a box with a star for an eye,
|
||
plus the stick arms and feet that let him act out a mood. The
|
||
viewBox is cropped to his box, so the arms and sparkles hang
|
||
just outside it rather than shrinking him. -->
|
||
<!-- The flight: stars streaming past while Plan2Code is thinking.
|
||
Filled in by app.js, because this page's CSP refuses the style
|
||
attributes that would place each star in markup. -->
|
||
<div class="sky" id="dock-sky" aria-hidden="true"></div>
|
||
<span class="pilot">
|
||
<span class="trail" aria-hidden="true"><i></i><i></i><i></i></span>
|
||
<svg class="planny" id="planny" viewBox="0 0 22 30" aria-hidden="true" focusable="false">
|
||
<!-- Feet first, so the shell's bottom edge covers their tops. -->
|
||
<rect class="foot f1" x="5.7" y="27.1" width="3.6" height="1.7" rx="0.85" />
|
||
<rect class="foot f2" x="12.7" y="27.1" width="3.6" height="1.7" rx="0.85" />
|
||
<rect class="shell" x="3" y="7" width="16" height="20" rx="3.2" />
|
||
<path class="eye" d="M11 10.95 L11.79 12.91 L13.9 13.06 L12.28 14.42 L12.79 16.47 L11 15.35 L9.21 16.47 L9.72 14.42 L8.1 13.06 L10.21 12.91 Z" />
|
||
<path class="smile" d="M8.3 18.4 Q11 21 13.7 18.4" />
|
||
<!-- One arm set per mood, shown by class alone (the CSP refuses
|
||
style attributes). A mood with no set of its own shows the
|
||
resting arms; adrift shows none at all. -->
|
||
<g class="arms a-rest"><g class="arm"><path d="M3 18 L1.3 21" /><circle cx="1.3" cy="21" r="0.85" /></g><g class="arm"><path d="M19 18 L20.7 21" /><circle cx="20.7" cy="21" r="0.85" /></g></g>
|
||
<g class="arms a-point"><g class="arm"><path d="M3 18 L1.3 21" /><circle cx="1.3" cy="21" r="0.85" /></g><g class="arm wave"><path d="M19 17.5 L21.4 14.9" /><circle cx="21.4" cy="14.9" r="0.85" /></g></g>
|
||
<g class="arms a-work"><g class="arm pump-l"><path d="M3 18 L1.1 20.6" /><circle cx="1.1" cy="20.6" r="0.85" /></g><g class="arm pump-r"><path d="M19 18 L20.9 20.6" /><circle cx="20.9" cy="20.6" r="0.85" /></g></g>
|
||
<g class="arms a-done"><g class="arm"><path d="M3 16.5 L1.1 13.7" /><circle cx="1.1" cy="13.7" r="0.85" /></g><g class="arm"><path d="M19 16.5 L20.9 13.7" /><circle cx="20.9" cy="13.7" r="0.85" /></g></g>
|
||
<g class="arms a-gone"><g class="arm"><path d="M3 18.6 L2.5 22.2" /><circle cx="2.5" cy="22.2" r="0.85" /></g><g class="arm"><path d="M19 18.6 L19.5 22.2" /><circle cx="19.5" cy="22.2" r="0.85" /></g></g>
|
||
<!-- Variant parts, hidden unless a mood variant wants them:
|
||
sparkles for a good moment, Z's for asleep. Each sits in a
|
||
positioning group because a CSS animation on transform would
|
||
overwrite a transform on the path itself. -->
|
||
<g class="spark">
|
||
<g transform="translate(1.4 6.6)"><path d="M0 -2.4 L0.65 -0.65 L2.4 0 L0.65 0.65 L0 2.4 L-0.65 0.65 L-2.4 0 L-0.65 -0.65 Z" /></g>
|
||
<g transform="translate(20.6 5.2)"><path d="M0 -1.9 L0.5 -0.5 L1.9 0 L0.5 0.5 L0 1.9 L-0.5 0.5 L-1.9 0 L-0.5 -0.5 Z" /></g>
|
||
</g>
|
||
<g class="zzz">
|
||
<path d="M19.4 5.6 h2.4 l-2.4 2.4 h2.4" />
|
||
<path d="M20.4 1.8 h1.9 l-1.9 1.9 h1.9" />
|
||
<path d="M21.4 -1.6 h1.4 l-1.4 1.4 h1.4" />
|
||
</g>
|
||
</svg>
|
||
</span>
|
||
<p class="dock-say">
|
||
<span id="agent-spin" class="spinner tiny dock-spin" aria-hidden="true" hidden></span>
|
||
<span id="agent-text" aria-live="polite">Connecting…</span>
|
||
<!-- Outside the live region on purpose: this changes once a second
|
||
while the agent works, and a polite region would read the clock
|
||
out loud every time it did. -->
|
||
<span id="agent-tick" class="tick" aria-hidden="true"></span>
|
||
</p>
|
||
</div>
|
||
<nav class="sidebar" id="sidebar" aria-label="Session outline"></nav>
|
||
</div>
|
||
|
||
<main class="main" id="main" tabindex="-1">
|
||
<!-- The starting screen, in the markup so it is on screen from the
|
||
first paint, before any script has run. The server writes the
|
||
session's own line into the heading; app.js replaces the whole
|
||
pane with the real screen the moment it draws. -->
|
||
<div class="launching boot-pane">
|
||
<div class="spinner" aria-hidden="true"></div>
|
||
<p class="card-kicker">Just a moment</p>
|
||
<h2 class="launch-title" id="boot-title">Opening the console</h2>
|
||
<p class="launch-quip">Getting everything ready…</p>
|
||
</div>
|
||
</main>
|
||
|
||
<aside class="aside" id="aside" aria-label="Notes and discussion"></aside>
|
||
</div>
|
||
|
||
<!-- Planny acting out each skill while it starts up and while it works.
|
||
Inert until app.js clones one onto the starting or waiting screen
|
||
(startStage), so it costs nothing on any other screen. Classes only,
|
||
no style attributes: the CSP refuses them, and the motion lives in
|
||
app.css under `.pose`. -->
|
||
<template id="start-poses">
|
||
<!-- Init / Init Update: laying the foundation. Blocks drop onto a stack
|
||
beside him one at a time and settle with a squash, his star
|
||
following each one down while he reaches to steady the pile. -->
|
||
<svg class="pose pose-init" data-pose="init" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow" cx="120" cy="198" rx="34" ry="5" />
|
||
<ellipse class="shadow" cx="194" cy="198" rx="22" ry="4" />
|
||
<g class="bob">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 126 L66 150" /><circle class="fl" cx="66" cy="150" r="5.5" />
|
||
<path class="ln" d="M160 124 L178 142" /><circle class="fl" cx="178" cy="142" r="5.5" />
|
||
<g class="in-look"><path class="ey blink" d="M124 86 L127.64 94.98 L137.31 95.67 L129.9 101.92 L132.23 111.33 L124 106.2 L115.77 111.33 L118.1 101.92 L110.69 95.67 L120.36 94.98 Z" /></g>
|
||
<path class="es" d="M112 122 Q120 128 128 122" />
|
||
</g>
|
||
<rect class="blk in-b1" x="176" y="180" width="36" height="16" rx="3" />
|
||
<rect class="blk in-b2" x="179" y="164" width="30" height="16" rx="3" />
|
||
<rect class="blk ac in-b3" x="182" y="148" width="24" height="16" rx="3" />
|
||
</svg>
|
||
|
||
<!-- 0 Pathfinder: leaning into the unknown, spyglass held to the
|
||
horizon, a dotted trail rolling by under him. -->
|
||
<svg class="pose pose-pathfinder" data-pose="pathfinder" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<path class="pf-trail" d="M14 212 Q120 196 226 210" />
|
||
<g class="bob">
|
||
<g transform="rotate(6 120 126)">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 126 L66 150" /><circle class="fl" cx="66" cy="150" r="5.5" />
|
||
<path class="ln" d="M160 116 L173.6 81.2" /><circle class="fl" cx="173.6" cy="81.2" r="5.5" />
|
||
<g class="pf-look"><path class="ey blink" d="M126 84 L129.64 92.98 L139.31 93.67 L131.9 99.92 L134.23 109.33 L126 104.2 L117.77 109.33 L120.1 99.92 L112.69 93.67 L122.36 92.98 Z" /></g>
|
||
<path class="es" d="M114 120 Q121 126 128 120" />
|
||
</g>
|
||
</g>
|
||
<g class="prop">
|
||
<g class="pf-glass">
|
||
<line class="lt" x1="181.5" y1="83.5" x2="177" y2="88" />
|
||
<path class="lt" d="M178 80 L190 68 L197 75 L185 87 Z" />
|
||
<path class="lt" d="M191.5 69.5 L203.5 57.5 L207.5 61.5 L195.5 73.5 Z" />
|
||
<circle class="ac" cx="207" cy="58" r="4" />
|
||
</g>
|
||
<circle class="ac twinkle t1" cx="206" cy="40" r="2" />
|
||
<circle class="ac twinkle t2" cx="220" cy="58" r="2.5" />
|
||
<circle class="ac twinkle t3" cx="196" cy="28" r="3" />
|
||
</g>
|
||
</svg>
|
||
|
||
<!-- 1 Plan: a question mark bobbing over his head, hand to his chin,
|
||
star on the clipboard while its boxes tick themselves off. -->
|
||
<svg class="pose pose-plan" data-pose="plan" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow" cx="120" cy="198" rx="34" ry="5" />
|
||
<g class="bob">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 120 L66 114" /><circle class="fl" cx="66" cy="114" r="5.5" />
|
||
<g class="pl-look"><path class="ey blink" d="M114 84 L117.64 92.98 L127.31 93.67 L119.9 99.92 L122.23 109.33 L114 104.2 L105.77 109.33 L108.1 99.92 L100.69 93.67 L110.36 92.98 Z" /></g>
|
||
<line class="es" x1="110" y1="124" x2="124" y2="123" />
|
||
<path class="ln" d="M160 128 L172 142 L134 136" /><circle class="fl" cx="134" cy="136" r="5.5" />
|
||
<g class="pl-q">
|
||
<path class="as" d="M112 36 Q112 22 125 22 Q138 22 138 34 Q138 42 127 46 L127 53" />
|
||
<circle class="ac" cx="127" cy="63" r="3.5" />
|
||
</g>
|
||
</g>
|
||
<g class="prop">
|
||
<rect class="lt pl-board" x="32" y="88" width="34" height="44" rx="4" />
|
||
<rect class="fl" x="42" y="84" width="14" height="7" rx="2" />
|
||
<path class="as pl-check c1" pathLength="1" d="M37 101 L40 104 L45 98" />
|
||
<line class="lt" x1="50" y1="101" x2="60" y2="101" />
|
||
<path class="as pl-check c2" pathLength="1" d="M37 112 L40 115 L45 109" />
|
||
<line class="lt" x1="50" y1="112" x2="58" y2="112" />
|
||
<path class="as pl-check c3" pathLength="1" d="M37 123 L40 126 L45 120" />
|
||
<line class="lt" x1="50" y1="123" x2="60" y2="123" />
|
||
</g>
|
||
</svg>
|
||
|
||
<!-- 2 Document: brow down, writing. He steadies the page while the
|
||
pencil walks it and each line appears behind it. -->
|
||
<svg class="pose pose-document" data-pose="document" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow" cx="120" cy="198" rx="34" ry="5" />
|
||
<g class="bob">
|
||
<g transform="rotate(4 120 126)">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 126 L66 150" /><circle class="fl" cx="66" cy="150" r="5.5" />
|
||
<path class="ln" d="M160 118 L176 108" /><circle class="fl" cx="176" cy="108" r="5.5" />
|
||
<g class="dc-look"><path class="ey blink" d="M120 86 L123.64 94.98 L133.31 95.67 L125.9 101.92 L128.23 111.33 L120 106.2 L111.77 111.33 L114.1 101.92 L106.69 95.67 L116.36 94.98 Z" /></g>
|
||
<path class="ln" d="M107 81 L133 83" />
|
||
<path class="es" d="M113 122 Q120 127 127 122" />
|
||
</g>
|
||
</g>
|
||
<g class="prop">
|
||
<rect class="lt dc-page" x="178" y="84" width="36" height="46" rx="3" />
|
||
<line class="lt" x1="204" y1="84" x2="214" y2="94" />
|
||
<line class="lt dc-line d1" pathLength="1" x1="184" y1="98" x2="200" y2="98" />
|
||
<line class="lt dc-line d2" pathLength="1" x1="184" y1="106" x2="208" y2="106" />
|
||
<line class="lt dc-line d3" pathLength="1" x1="184" y1="114" x2="204" y2="114" />
|
||
<line class="lt dc-line d4" pathLength="1" x1="184" y1="122" x2="196" y2="122" />
|
||
<g class="dc-pencil">
|
||
<line class="ln" x1="220" y1="96" x2="192" y2="124" />
|
||
<path class="ac" d="M188 123 L193 128 L184 132 Z" />
|
||
</g>
|
||
</g>
|
||
</svg>
|
||
|
||
<!-- 3 Implement: fist up, determined. He cranks the wrench, sparks
|
||
fly, and the code badge pulses on the other side. -->
|
||
<svg class="pose pose-implement" data-pose="implement" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow" cx="120" cy="198" rx="34" ry="5" />
|
||
<g class="bob">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 128 L64 138" /><circle class="fl" cx="64" cy="138" r="5.5" />
|
||
<path class="ln" d="M160 118 L174 96" /><circle class="fl" cx="174" cy="96" r="5.5" />
|
||
<path class="ey blink" d="M120 86 L123.64 94.98 L133.31 95.67 L125.9 101.92 L128.23 111.33 L120 106.2 L111.77 111.33 L114.1 101.92 L106.69 95.67 L116.36 94.98 Z" />
|
||
<path class="es" d="M104 121 Q120 128 136 121" />
|
||
</g>
|
||
<g class="prop">
|
||
<g class="im-wrench">
|
||
<line class="ln" x1="64" y1="138" x2="44" y2="118" />
|
||
<path class="ln" d="M30 112 A8 8 0 1 0 38 104" />
|
||
</g>
|
||
<g class="im-spark">
|
||
<line class="lt" x1="20" y1="122" x2="14" y2="124" />
|
||
<line class="lt" x1="18" y1="110" x2="12" y2="110" />
|
||
<line class="lt" x1="28" y1="96" x2="24" y2="92" />
|
||
</g>
|
||
</g>
|
||
<g class="prop p2">
|
||
<rect class="lt" x="176" y="100" width="34" height="24" rx="6" />
|
||
<path class="as im-lt" d="M186 106 L181 112 L186 118" />
|
||
<path class="as im-slash" d="M195 105 L191 119" />
|
||
<path class="as im-gt" d="M200 106 L205 112 L200 118" />
|
||
</g>
|
||
</svg>
|
||
|
||
<!-- 4 Finalize: hopping for joy, both arms up, beside the checkmark
|
||
flag, confetti drifting down. -->
|
||
<svg class="pose pose-finalize" data-pose="finalize" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow fz-shadow" cx="120" cy="198" rx="34" ry="5" />
|
||
<g class="fz-hop">
|
||
<g transform="translate(0 -8)">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 116 L60 90" /><circle class="fl" cx="60" cy="90" r="5.5" />
|
||
<path class="ln" d="M160 116 L180 90" /><circle class="fl" cx="180" cy="90" r="5.5" />
|
||
<path class="ey blink" d="M120 84 L123.64 92.98 L133.31 93.67 L125.9 99.92 L128.23 109.33 L120 104.2 L111.77 109.33 L114.1 99.92 L106.69 93.67 L116.36 92.98 Z" />
|
||
<path class="ey" d="M106 118 Q120 134 134 118 Z" />
|
||
</g>
|
||
</g>
|
||
<g class="prop">
|
||
<line class="ln" x1="196" y1="150" x2="196" y2="96" />
|
||
<g class="fz-flag">
|
||
<path class="ac" d="M196 98 L234 112 L196 126 Z" />
|
||
<path class="es fz-tick" d="M203 112 L207 116 L215 108" />
|
||
</g>
|
||
</g>
|
||
<g class="fz-confetti">
|
||
<g class="cf"><circle class="ac" cx="40" cy="40" r="3" /></g>
|
||
<g class="cf"><rect class="fl" x="58.5" y="20.5" width="3" height="7" transform="rotate(30 60 24)" /></g>
|
||
<g class="cf"><circle class="fl" cx="30" cy="82" r="2" /></g>
|
||
<g class="cf"><rect class="ac" x="50.5" y="58.5" width="3" height="7" transform="rotate(-35 52 62)" /></g>
|
||
<g class="cf"><circle class="ac" cx="120" cy="18" r="2.5" /></g>
|
||
<g class="cf"><rect class="ac" x="194.5" y="26.5" width="3" height="7" transform="rotate(40 196 30)" /></g>
|
||
<g class="cf"><circle class="fl" cx="216" cy="58" r="2.5" /></g>
|
||
<g class="cf"><circle class="fl" cx="182" cy="62" r="2" /></g>
|
||
<g class="cf"><rect class="fl" x="220.5" y="80.5" width="3" height="7" transform="rotate(-20 222 84)" /></g>
|
||
<g class="cf"><circle class="ac" cx="200" cy="12" r="2" /></g>
|
||
</g>
|
||
</svg>
|
||
|
||
<!-- Quick Task: in a hurry. Leaning into a dash, arms pumping and feet
|
||
stepping, speed lines streaming off behind him and a lightning bolt
|
||
crackling ahead. -->
|
||
<svg class="pose pose-quick-task" data-pose="quick-task" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow qt-shadow" cx="120" cy="198" rx="34" ry="5" />
|
||
<g>
|
||
<line class="lt qt-line" x1="72" y1="92" x2="46" y2="92" />
|
||
<line class="lt qt-line l2" x1="68" y1="116" x2="32" y2="116" />
|
||
<line class="lt qt-line l3" x1="64" y1="140" x2="42" y2="140" />
|
||
<line class="lt qt-line l4" x1="60" y1="164" x2="34" y2="164" />
|
||
</g>
|
||
<g class="bob">
|
||
<g transform="rotate(10 120 182)">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 122 L66 138 L58 128" /><circle class="fl" cx="58" cy="128" r="5.5" />
|
||
<path class="ln" d="M160 122 L174 112 L182 122" /><circle class="fl" cx="182" cy="122" r="5.5" />
|
||
<path class="ey blink" d="M132 84 L135.64 92.98 L145.31 93.67 L137.9 99.92 L140.23 109.33 L132 104.2 L123.77 109.33 L126.1 99.92 L118.69 93.67 L128.36 92.98 Z" />
|
||
<line class="es" x1="122" y1="121" x2="138" y2="119" />
|
||
</g>
|
||
</g>
|
||
<g class="qt-zap">
|
||
<path class="ac" d="M212 60 L196 98 L209 98 L200 130 L226 88 L212 88 L222 60 Z" />
|
||
</g>
|
||
</svg>
|
||
|
||
<!-- Review: a magnifying glass over the code. It works down the page,
|
||
stops on the line that is wrong and flags it; his star follows it
|
||
the whole way, one hand on his chin. -->
|
||
<svg class="pose pose-review" data-pose="review" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow" cx="120" cy="198" rx="34" ry="5" />
|
||
<g class="bob">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M160 126 L174 138" /><circle class="fl" cx="174" cy="138" r="5.5" />
|
||
<g class="rv-look"><path class="ey blink" d="M126 86 L129.64 94.98 L139.31 95.67 L131.9 101.92 L134.23 111.33 L126 106.2 L117.77 111.33 L120.1 101.92 L112.69 95.67 L122.36 94.98 Z" /></g>
|
||
<path class="ln" d="M113 82 Q126 76 139 83" />
|
||
<line class="es" x1="114" y1="124" x2="126" y2="122" />
|
||
<path class="ln" d="M80 126 L70 146 L98 150" /><circle class="fl" cx="98" cy="150" r="5.5" />
|
||
</g>
|
||
<g class="prop">
|
||
<rect class="lt" x="174" y="80" width="44" height="60" rx="4" />
|
||
<line class="lt" x1="182" y1="94" x2="204" y2="94" />
|
||
<line class="lt" x1="188" y1="106" x2="210" y2="106" />
|
||
<line class="lt" x1="188" y1="118" x2="206" y2="118" />
|
||
<line class="as rv-flag" x1="188" y1="118" x2="206" y2="118" />
|
||
<line class="lt" x1="182" y1="130" x2="200" y2="130" />
|
||
<g class="rv-pin"><circle class="ac" cx="227" cy="118" r="4" /></g>
|
||
<g class="rv-glass">
|
||
<circle class="lt" cx="197" cy="94" r="12" />
|
||
<line class="ln" x1="206" y1="103" x2="216" y2="113" />
|
||
</g>
|
||
</g>
|
||
</svg>
|
||
|
||
<!-- Handoff: passing it on. Both arms out, holding a wrapped parcel
|
||
toward whoever picks up next, an arrow pulsing the way it is going. -->
|
||
<svg class="pose pose-handoff" data-pose="handoff" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow" cx="126" cy="198" rx="44" ry="5" />
|
||
<g class="bob">
|
||
<g transform="translate(-8 0)">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 126 L66 150" /><circle class="fl" cx="66" cy="150" r="5.5" />
|
||
<path class="ey blink" d="M126 86 L129.64 94.98 L139.31 95.67 L131.9 101.92 L134.23 111.33 L126 106.2 L117.77 111.33 L120.1 101.92 L112.69 95.67 L122.36 94.98 Z" />
|
||
<path class="es" d="M110 120 Q122 129 134 120" />
|
||
<g class="ho-reach">
|
||
<line class="ln" x1="160" y1="124" x2="184" y2="116" />
|
||
<line class="ln" x1="160" y1="148" x2="184" y2="140" />
|
||
</g>
|
||
<g class="ho-give">
|
||
<path class="as" d="M202 102 C194 88 186 94 194 102 M202 102 C210 88 218 94 210 102" />
|
||
<rect class="sh" x="182" y="102" width="40" height="36" rx="4" />
|
||
<line class="as" x1="202" y1="102" x2="202" y2="138" />
|
||
<line class="as" x1="182" y1="120" x2="222" y2="120" />
|
||
<circle class="fl" cx="183" cy="116" r="5.5" />
|
||
<circle class="fl" cx="183" cy="140" r="5.5" />
|
||
</g>
|
||
</g>
|
||
</g>
|
||
<g class="ho-arrow"><path class="as" d="M178 64 L214 64 M204 54 L216 64 L204 74" /></g>
|
||
</svg>
|
||
|
||
<!-- Changelog: keeping the record. A page of release notes stands beside him,
|
||
and one arm reaches over to write the newest line onto it. -->
|
||
<svg class="pose pose-changelog" data-pose="changelog" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow" cx="126" cy="198" rx="44" ry="5" />
|
||
<g class="prop">
|
||
<rect class="sh" x="176" y="58" width="44" height="116" rx="6" />
|
||
<line class="lt" x1="186" y1="76" x2="206" y2="76" />
|
||
<circle class="ac" cx="186" cy="94" r="3" /><line class="lt" x1="194" y1="94" x2="210" y2="94" />
|
||
<circle class="ac" cx="186" cy="112" r="3" /><line class="lt" x1="194" y1="112" x2="206" y2="112" />
|
||
<g class="cl-line"><circle class="ac" cx="186" cy="130" r="3" /><line class="lt" x1="194" y1="130" x2="210" y2="130" /></g>
|
||
</g>
|
||
<g class="bob">
|
||
<g transform="translate(-14 0)">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 126 L66 150" /><circle class="fl" cx="66" cy="150" r="5.5" />
|
||
<path class="ey blink" d="M126 86 L129.64 94.98 L139.31 95.67 L131.9 101.92 L134.23 111.33 L126 106.2 L117.77 111.33 L120.1 101.92 L112.69 95.67 L122.36 94.98 Z" />
|
||
<path class="es" d="M110 120 Q122 129 134 120" />
|
||
<g class="gc-reach">
|
||
<line class="ln" x1="160" y1="126" x2="196" y2="132" />
|
||
<circle class="fl" cx="196" cy="132" r="5.5" />
|
||
</g>
|
||
</g>
|
||
</g>
|
||
</svg>
|
||
<!-- Git: minding the branches. Beside a branch line with a second branch
|
||
forking off it, one arm reaches to set a new commit onto the line. -->
|
||
<svg class="pose pose-git" data-pose="git" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow" cx="126" cy="198" rx="44" ry="5" />
|
||
<g class="prop">
|
||
<line class="lt gc-line" x1="204" y1="62" x2="204" y2="172" />
|
||
<path class="lt" d="M204 152 Q226 140 226 112 L226 72" />
|
||
<circle class="ac" cx="204" cy="82" r="7" />
|
||
<circle class="ac" cx="226" cy="92" r="6" />
|
||
<circle class="ac" cx="204" cy="112" r="7" />
|
||
<circle class="ac gc-dot" cx="204" cy="142" r="7" />
|
||
</g>
|
||
<g class="bob">
|
||
<g transform="translate(-14 0)">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 126 L66 150" /><circle class="fl" cx="66" cy="150" r="5.5" />
|
||
<path class="ey blink" d="M126 86 L129.64 94.98 L139.31 95.67 L131.9 101.92 L134.23 111.33 L126 106.2 L117.77 111.33 L120.1 101.92 L112.69 95.67 L122.36 94.98 Z" />
|
||
<path class="es" d="M110 120 Q122 129 134 120" />
|
||
<g class="gc-reach">
|
||
<line class="ln" x1="160" y1="126" x2="212" y2="142" />
|
||
<circle class="fl" cx="212" cy="142" r="5.5" />
|
||
</g>
|
||
</g>
|
||
</g>
|
||
</svg>
|
||
<!-- Codebase X-ray: seeing how it works. He holds a lens up to a file,
|
||
a scan line sweeps down it to show the structure inside, and a rough
|
||
spot lights up as the scan passes over it. -->
|
||
<svg class="pose pose-xray" data-pose="xray" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow" cx="126" cy="198" rx="44" ry="5" />
|
||
<g class="prop">
|
||
<rect class="sh" x="182" y="60" width="44" height="112" rx="6" />
|
||
<line class="lt" x1="196" y1="76" x2="196" y2="152" />
|
||
<path class="lt" d="M196 96 L212 96 M196 124 L212 124" />
|
||
<circle class="ac" cx="196" cy="76" r="4" />
|
||
<circle class="ac" cx="212" cy="96" r="3.5" />
|
||
<circle class="ac" cx="212" cy="124" r="3.5" />
|
||
<circle class="ac" cx="196" cy="152" r="4" />
|
||
<g class="xr-spot"><circle class="as" cx="212" cy="124" r="8" /></g>
|
||
<line class="as xr-scan" x1="188" y1="70" x2="220" y2="70" />
|
||
</g>
|
||
<g class="bob">
|
||
<g transform="translate(-14 0)">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 126 L66 150" /><circle class="fl" cx="66" cy="150" r="5.5" />
|
||
<g class="xr-look"><path class="ey blink" d="M126 86 L129.64 94.98 L139.31 95.67 L131.9 101.92 L134.23 111.33 L126 106.2 L117.77 111.33 L120.1 101.92 L112.69 95.67 L122.36 94.98 Z" /></g>
|
||
<path class="es" d="M110 120 Q122 129 134 120" />
|
||
<line class="ln" x1="160" y1="126" x2="192" y2="132" />
|
||
<g class="xr-lens">
|
||
<line class="ln" x1="192" y1="132" x2="204" y2="120" />
|
||
<circle class="lt" cx="214" cy="110" r="14" />
|
||
</g>
|
||
<circle class="fl" cx="192" cy="132" r="5.5" />
|
||
</g>
|
||
</g>
|
||
</svg>
|
||
<!-- Diagnose a bug: finding the cause. A small bug scuttles along one
|
||
line of a file, his magnifier follows it until it is caught, and the
|
||
line it sits on is marked in red. He looks, he does not fix. -->
|
||
<svg class="pose pose-diagnose" data-pose="diagnose" viewBox="0 4 240 216" aria-hidden="true" focusable="false">
|
||
<ellipse class="shadow" cx="126" cy="198" rx="44" ry="5" />
|
||
<g class="prop">
|
||
<rect class="sh" x="176" y="60" width="46" height="112" rx="6" />
|
||
<line class="lt" x1="184" y1="78" x2="208" y2="78" />
|
||
<line class="lt" x1="188" y1="96" x2="214" y2="96" />
|
||
<path class="dg-mark" d="M184 124 Q187 120 190 124 T196 124 T202 124 T208 124 T214 124" />
|
||
<line class="lt" x1="188" y1="142" x2="208" y2="142" />
|
||
<line class="lt" x1="184" y1="158" x2="202" y2="158" />
|
||
<g class="dg-bug">
|
||
<path class="dg-leg" d="M195 111 L189 108 M195 115 L189 115 M195 119 L189 122 M205 111 L211 108 M205 115 L211 115 M205 119 L211 122 M198 104 L195 99 M202 104 L205 99" />
|
||
<ellipse class="dg-body" cx="200" cy="115" rx="5.5" ry="7" />
|
||
<circle class="dg-head" cx="200" cy="106" r="3.2" />
|
||
</g>
|
||
</g>
|
||
<g class="bob">
|
||
<g transform="translate(-14 0)">
|
||
<rect class="fl foot f1" x="94" y="179" width="20" height="10" rx="5" />
|
||
<rect class="fl foot f2" x="126" y="179" width="20" height="10" rx="5" />
|
||
<rect class="sh" x="80" y="72" width="80" height="108" rx="16" />
|
||
<path class="ln" d="M80 126 L66 150" /><circle class="fl" cx="66" cy="150" r="5.5" />
|
||
<g class="dg-look"><path class="ey blink" d="M126 86 L129.64 94.98 L139.31 95.67 L131.9 101.92 L134.23 111.33 L126 106.2 L117.77 111.33 L120.1 101.92 L112.69 95.67 L122.36 94.98 Z" /></g>
|
||
<path class="ln" d="M113 82 Q126 77 139 83" />
|
||
<line class="es" x1="114" y1="124" x2="128" y2="124" />
|
||
<line class="ln" x1="160" y1="126" x2="174" y2="140" />
|
||
<g class="dg-lens">
|
||
<line class="ln" x1="174" y1="140" x2="180" y2="127" />
|
||
<circle class="lt" cx="186" cy="114" r="14" />
|
||
</g>
|
||
<circle class="fl" cx="174" cy="140" r="5.5" />
|
||
</g>
|
||
</g>
|
||
</svg>
|
||
</template>
|
||
|
||
<!-- The Help dialog's content, cloned into #help-modal the first time ? is
|
||
pressed, so none of it costs the first paint. Tab order, labels and
|
||
colors live in HELP_TABS (help.js); a test keeps this in step. -->
|
||
<template id="help-content">
|
||
<svg class="help-icons" aria-hidden="true" focusable="false">
|
||
<symbol id="hi-about" viewBox="0 0 24 24" fill="none">
|
||
<circle cx="12" cy="12" r="9" />
|
||
<path d="M12 11v6" />
|
||
<path d="M12 7.5v.5" />
|
||
</symbol>
|
||
<symbol id="hi-stuck" viewBox="0 0 24 24" fill="none">
|
||
<path d="M12 4l9 16H3z" />
|
||
<path d="M12 10v4.5M12 17v.5" />
|
||
</symbol>
|
||
<symbol id="hi-around" viewBox="0 0 24 24" fill="none">
|
||
<circle cx="12" cy="12" r="9" />
|
||
<path d="M15.5 8.5l-2 5-5 2 2-5z" />
|
||
</symbol>
|
||
<symbol id="hi-workspace" viewBox="0 0 24 24" fill="none">
|
||
<path d="M3 7.5V18a1.5 1.5 0 0 0 1.5 1.5h13" />
|
||
<path d="M6 5.5a1.5 1.5 0 0 1 1.5-1.5h3l2 2h6A1.5 1.5 0 0 1 20 7.5v7a1.5 1.5 0 0 1-1.5 1.5h-11A1.5 1.5 0 0 1 6 14.5z" />
|
||
</symbol>
|
||
<symbol id="hi-planny" viewBox="0 0 24 24" fill="none">
|
||
<rect x="6" y="5" width="12" height="13" rx="3" />
|
||
<path d="M12 8.6l1 2.1 2.3.3-1.7 1.6.4 2.3-2-1.1-2 1.1.4-2.3-1.7-1.6 2.3-.3z" />
|
||
<path d="M6 12.5L3.8 15.5M18 12.5l2.2 3M9 18v2M15 18v2" />
|
||
</symbol>
|
||
<symbol id="hi-answering" viewBox="0 0 24 24" fill="none">
|
||
<rect x="4" y="4" width="16" height="16" rx="3" />
|
||
<path d="M8 12.5l3 3 5-6" />
|
||
</symbol>
|
||
<symbol id="hi-sending" viewBox="0 0 24 24" fill="none">
|
||
<path d="M3.5 11.5L20 4l-5.5 16-3.5-6.5z" />
|
||
<path d="M11 13.5L20 4" />
|
||
</symbol>
|
||
<symbol id="hi-notes" viewBox="0 0 24 24" fill="none">
|
||
<path d="M16.5 8l-7 7a2 2 0 0 0 2.8 2.8l7.4-7.4a4 4 0 0 0-5.7-5.7l-7.4 7.4a6 6 0 0 0 8.5 8.5l6-6" />
|
||
</symbol>
|
||
<symbol id="hi-docs" viewBox="0 0 24 24" fill="none">
|
||
<path d="M6 3h8l4 4v14H6z" />
|
||
<path d="M14 3v4h4M9 12h6M9 16h6" />
|
||
</symbol>
|
||
<symbol id="hi-dashboard" viewBox="0 0 24 24" fill="none">
|
||
<rect x="4" y="4" width="7" height="7" rx="1.5" />
|
||
<rect x="13" y="4" width="7" height="7" rx="1.5" />
|
||
<rect x="4" y="13" width="7" height="7" rx="1.5" />
|
||
<rect x="13" y="13" width="7" height="7" rx="1.5" />
|
||
</symbol>
|
||
<symbol id="hi-meter" viewBox="0 0 24 24" fill="none">
|
||
<circle cx="12" cy="12" r="8" />
|
||
<path d="M12 4a8 8 0 0 1 7.6 10.5" />
|
||
<path d="M12 12l3-3" />
|
||
</symbol>
|
||
<symbol id="hi-build" viewBox="0 0 24 24" fill="none">
|
||
<rect x="3" y="9" width="18" height="6" rx="3" />
|
||
<path d="M6 12h7" />
|
||
</symbol>
|
||
<symbol id="hi-loop" viewBox="0 0 24 24" fill="none">
|
||
<path d="M5 12a7 7 0 0 1 12-5l2 2M19 12a7 7 0 0 1-12 5l-2-2" />
|
||
<path d="M19 4v5h-5M5 20v-5h5" />
|
||
</symbol>
|
||
<symbol id="hi-git" viewBox="0 0 24 24" fill="none">
|
||
<circle cx="6" cy="5" r="2" />
|
||
<circle cx="6" cy="19" r="2" />
|
||
<circle cx="18" cy="7" r="2" />
|
||
<path d="M6 7v10M18 9a7 7 0 0 1-7 7H6" />
|
||
</symbol>
|
||
<symbol id="hi-subagents" viewBox="0 0 24 24" fill="none">
|
||
<circle cx="7" cy="12" r="3.5" />
|
||
<circle cx="18" cy="5" r="2" />
|
||
<circle cx="18" cy="12" r="2" />
|
||
<circle cx="18" cy="19" r="2" />
|
||
<path d="M10 10l6-4M10.5 12H16M10 14l6 4" />
|
||
</symbol>
|
||
<symbol id="hi-ask" viewBox="0 0 24 24" fill="none">
|
||
<path d="M4 5h16v11H10l-4 4v-4H4z" />
|
||
<path d="M8 9.5h8M8 12.5h5" />
|
||
</symbol>
|
||
<symbol id="hi-activities" viewBox="0 0 24 24" fill="none">
|
||
<rect x="4" y="4" width="16" height="16" rx="3.5" />
|
||
<path d="M8.5 8.5h.01M15.5 8.5h.01M12 12h.01M8.5 15.5h.01M15.5 15.5h.01" />
|
||
</symbol>
|
||
<symbol id="hi-finishing" viewBox="0 0 24 24" fill="none">
|
||
<path d="M6 21V4" />
|
||
<path d="M6 4h11l-2 4 2 4H6" />
|
||
</symbol>
|
||
<symbol id="hi-prefs" viewBox="0 0 24 24" fill="none">
|
||
<path d="M4 7h16M4 12h16M4 17h16" />
|
||
<circle cx="9" cy="7" r="1.8" />
|
||
<circle cx="15" cy="12" r="1.8" />
|
||
<circle cx="7" cy="17" r="1.8" />
|
||
</symbol>
|
||
<symbol id="hi-privacy" viewBox="0 0 24 24" fill="none">
|
||
<rect x="5" y="10.5" width="14" height="10" rx="2" />
|
||
<path d="M8 10.5V8a4 4 0 0 1 8 0v2.5M12 14.5v2" />
|
||
</symbol>
|
||
</svg>
|
||
|
||
<!-- Tab 1: What this page is -->
|
||
<section class="help-panel" data-tab="about">
|
||
<h3>What this page is</h3>
|
||
<p class="help-lead">
|
||
A page for answering Plan2Code's questions, reading what it has
|
||
written and approving things, instead of typing it all into the
|
||
terminal.
|
||
</p>
|
||
<p>
|
||
New here? <button type="button" class="help-link" data-action="welcome">Show the welcome again</button>
|
||
</p>
|
||
<figure class="help-figure" data-figure="about">
|
||
<svg class="help-diagram" viewBox="0 0 560 160" role="img" aria-labelledby="hd-about-title hd-about-desc">
|
||
<title id="hd-about-title">You, this page, its program and Plan2Code, all on your machine</title>
|
||
<desc id="hd-about-desc">
|
||
Four boxes in a row, each talking both ways with the next: you in
|
||
your browser, this page, a small program on 127.0.0.1, and
|
||
Plan2Code in your terminal. A dashed outline around all four is
|
||
labeled "Your machine only".
|
||
</desc>
|
||
<defs>
|
||
<marker id="hd-about-arrow" viewBox="0 0 8 8" refX="7" refY="4" markerWidth="5" markerHeight="5" orient="auto-start-reverse">
|
||
<path class="hd-arrow" d="M0 0 L8 4 L0 8 z" />
|
||
</marker>
|
||
</defs>
|
||
<rect class="hd-line hd-dash" x="6" y="6" width="548" height="148" rx="10" />
|
||
<text class="hd-label hd-accent" x="18" y="26">Your machine only</text>
|
||
<rect class="hd-box" x="16" y="42" width="100" height="64" rx="8" />
|
||
<rect class="hd-box" x="160" y="42" width="100" height="64" rx="8" />
|
||
<rect class="hd-box" x="304" y="42" width="100" height="64" rx="8" />
|
||
<rect class="hd-box" x="448" y="42" width="100" height="64" rx="8" />
|
||
<text class="hd-label" x="66" y="70" text-anchor="middle">You</text>
|
||
<text class="hd-label small" x="66" y="88" text-anchor="middle" data-app="in the app">in your browser</text>
|
||
<text class="hd-label" x="210" y="79" text-anchor="middle">This page</text>
|
||
<text class="hd-label" x="354" y="70" text-anchor="middle">Small program</text>
|
||
<text class="hd-label small" x="354" y="88" text-anchor="middle">on 127.0.0.1</text>
|
||
<text class="hd-label" x="498" y="70" text-anchor="middle">Plan2Code</text>
|
||
<text class="hd-label small" x="498" y="88" text-anchor="middle" data-app="in its terminal panel">in your terminal</text>
|
||
<path class="hd-line" d="M120 74 H156" marker-start="url(#hd-about-arrow)" marker-end="url(#hd-about-arrow)" />
|
||
<path class="hd-line" d="M264 74 H300" marker-start="url(#hd-about-arrow)" marker-end="url(#hd-about-arrow)" />
|
||
<path class="hd-line" d="M408 74 H444" marker-start="url(#hd-about-arrow)" marker-end="url(#hd-about-arrow)" />
|
||
<path class="hd-flow" d="M66 110 V132 H498 V110" />
|
||
</svg>
|
||
<figcaption>Everything stays on this computer. Both ends have to be running.</figcaption>
|
||
</figure>
|
||
<p>
|
||
A small program running on your own machine, started for you by
|
||
<span data-app="Plan2Code in the terminal panel">Plan2Code in your terminal</span>. Nothing here goes over the internet, and
|
||
there is no account and nothing to install.
|
||
</p>
|
||
<h4>On this machine only</h4>
|
||
<p class="for-browser">
|
||
The address starts with <strong>127.0.0.1</strong>, which always means
|
||
"this computer". Nothing you type leaves your machine, and a colleague
|
||
cannot open your link from theirs. To work through a session together,
|
||
share your screen.
|
||
</p>
|
||
<p class="for-app">
|
||
The app loads this page from <strong>127.0.0.1</strong>, which always
|
||
means "this computer". Nothing you type leaves your machine, and the
|
||
page's address stays inside the app, so there is no link to pass
|
||
around. To work through a session together, share your screen.
|
||
</p>
|
||
<h4>How long it runs</h4>
|
||
<p class="for-browser">
|
||
<strong>It stays up while this tab is open.</strong> Close the tab and
|
||
it shuts itself down <span data-fact="closedTabMinutes">2</span> minutes
|
||
later. It also stops after <span data-fact="idleMinutes">30</span>
|
||
minutes without hearing from anyone, and after
|
||
<span data-fact="maxLifeHours">4</span> hours regardless. Reopening the same link brings everything back: nothing you
|
||
typed is kept in the browser alone.
|
||
</p>
|
||
<p class="for-app">
|
||
<strong>It stays up while the app's window shows it.</strong> Close the
|
||
window and it shuts itself down <span data-fact="closedTabMinutes">2</span>
|
||
minutes later. It also stops after <span data-fact="idleMinutes">30</span>
|
||
minutes without hearing from anyone, and after
|
||
<span data-fact="maxLifeHours">4</span> hours regardless. When it
|
||
stops, the app's own bar notices and brings it back on the same
|
||
session, or offers <strong>Reconnect the console</strong>: nothing you
|
||
typed is kept in the window alone.
|
||
</p>
|
||
<h4>Two halves, both running</h4>
|
||
<p class="for-browser">
|
||
<strong>The terminal is the other half.</strong> This page collects your
|
||
answers; Plan2Code, in the terminal you started it from, is what reads
|
||
them and writes the files. Both have to be running for a question to
|
||
reach you or an answer to reach it.
|
||
</p>
|
||
<p class="for-app">
|
||
<strong>The terminal panel is the other half.</strong> This page collects
|
||
your answers; Plan2Code, the agent running in the app's terminal panel,
|
||
is what reads them and writes the files. Both have to be running for a
|
||
question to reach you or an answer to reach it.
|
||
</p>
|
||
<p id="about-live" class="about-live"></p>
|
||
<p>
|
||
<strong>If it stops.</strong> Press Send anyway. Answers are written to
|
||
disk the moment they leave this page and are held until something
|
||
collects them, so starting Plan2Code again picks them up where you
|
||
left off. <span data-app="Nothing is lost by closing the window either.">Nothing is lost by closing this tab either.</span>
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 2: When something looks stuck -->
|
||
<section class="help-panel" data-tab="stuck">
|
||
<h3>When something looks stuck</h3>
|
||
<p class="help-lead">
|
||
This page and <span data-app="Plan2Code in the terminal panel">Plan2Code in your terminal</span> are two programs, and either
|
||
can stop without the other. Nothing you have typed is lost either way.
|
||
</p>
|
||
<div class="help-callout" role="note">
|
||
<svg class="help-callout-icon" viewBox="0 0 24 24" aria-hidden="true">
|
||
<path d="M12 3.5 22 20.5H2Z" />
|
||
<path d="M12 10v5" />
|
||
<path d="M12 17.8v.4" />
|
||
</svg>
|
||
<div>
|
||
<strong class="help-callout-label">Check this first</strong>
|
||
<p>
|
||
If nothing seems to be happening, <span data-app="look at the terminal panel (collapsed, it shows a dot once the agent has gone quiet)">look at your terminal</span>. Plan2Code
|
||
often stops there to ask your permission, and this page cannot see it.
|
||
</p>
|
||
</div>
|
||
</div>
|
||
<h4>What you might see</h4>
|
||
<ol class="help-rows">
|
||
<li class="help-row">
|
||
<dl>
|
||
<dt>You see</dt><dd>The line beside Planny stays quiet for half a minute or more while it is working.</dd>
|
||
<dt>Likely cause</dt><dd data-app="A permission prompt is waiting in the terminal panel.">A permission prompt is waiting in your terminal.</dd>
|
||
<dt>Do this</dt><dd>Switch to the terminal and answer it.</dd>
|
||
</dl>
|
||
</li>
|
||
<li class="help-row">
|
||
<dl>
|
||
<dt>You see</dt><dd><strong>Not running</strong> (Planny gray and still).</dd>
|
||
<dt>Likely cause</dt><dd>Plan2Code has not checked in for a few minutes.</dd>
|
||
<dt>Do this</dt><dd class="for-browser">Look at the terminal. If it is idle, type <code>continue</code> there.</dd><dd class="for-app">Look at the terminal panel. If it is idle, press <strong>continue</strong> in the line beside Planny, which types it there for you.</dd>
|
||
</dl>
|
||
</li>
|
||
<li class="help-row">
|
||
<dl>
|
||
<dt>You see</dt><dd><strong>Not connected</strong> (Planny faded, his star shut).</dd>
|
||
<dt>Likely cause</dt><dd>The program behind this page shut itself down.</dd>
|
||
<dt>Do this</dt><dd id="help-stuck-table-reconnect-text">Ask Plan2Code to resume the session (or run the command again), and use the new link.</dd>
|
||
</dl>
|
||
</li>
|
||
<li class="help-row">
|
||
<dl>
|
||
<dt>You see</dt><dd>Nothing on the page changes after you press Send.</dd>
|
||
<dt>Likely cause</dt><dd>The agent is busy, or has finished its turn.</dd>
|
||
<dt>Do this</dt><dd>Your answer is saved. Check the terminal.</dd>
|
||
</dl>
|
||
</li>
|
||
</ol>
|
||
<figure class="help-figure" data-figure="stuck">
|
||
<svg class="help-diagram" viewBox="0 0 560 262" role="img" aria-labelledby="hd-stuck-title hd-stuck-desc">
|
||
<title id="hd-stuck-title">What to check when something looks stuck</title>
|
||
<desc id="hd-stuck-desc">
|
||
A decision flow. First: does Planny say Not connected? If yes, run
|
||
the command again and use the new link. If no: does he say Not
|
||
running? If yes, look at the terminal, which may be waiting for
|
||
your permission, finished or errored. Either way, and in every
|
||
other case, answering anyway is safe, because what you send is
|
||
held until Plan2Code collects it.
|
||
</desc>
|
||
<defs>
|
||
<marker id="hd-stuck-arrow" viewBox="0 0 8 8" refX="7" refY="4" markerWidth="5" markerHeight="5" orient="auto-start-reverse">
|
||
<path class="hd-arrow" d="M0 0 L8 4 L0 8 z" />
|
||
</marker>
|
||
</defs>
|
||
<path class="hd-box" d="M20 50 L110 16 L200 50 L110 84 Z" />
|
||
<text class="hd-label" x="110" y="46" text-anchor="middle">Says Not</text>
|
||
<text class="hd-label" x="110" y="63" text-anchor="middle">connected?</text>
|
||
<rect class="hd-box" x="260" y="26" width="284" height="48" rx="8" />
|
||
<text class="hd-label" x="402" y="46" text-anchor="middle" data-app="Press Reconnect the console">Run the command again,</text>
|
||
<text class="hd-label" x="402" y="63" text-anchor="middle" data-app="in the app's own bar">use the new link</text>
|
||
<path class="hd-line" d="M202 50 H256" marker-end="url(#hd-stuck-arrow)" />
|
||
<text class="hd-label small" x="228" y="43" text-anchor="middle">yes</text>
|
||
<path class="hd-line" d="M110 86 V112" marker-end="url(#hd-stuck-arrow)" />
|
||
<text class="hd-label small" x="118" y="103">no</text>
|
||
<path class="hd-box" d="M20 150 L110 116 L200 150 L110 184 Z" />
|
||
<text class="hd-label" x="110" y="146" text-anchor="middle">Says Not</text>
|
||
<text class="hd-label" x="110" y="163" text-anchor="middle">running?</text>
|
||
<rect class="hd-box" x="260" y="120" width="284" height="60" rx="8" />
|
||
<text class="hd-label" x="402" y="144" text-anchor="middle">Look at the terminal: waiting</text>
|
||
<text class="hd-label" x="402" y="162" text-anchor="middle">for permission, finished, errored?</text>
|
||
<path class="hd-line" d="M202 150 H256" marker-end="url(#hd-stuck-arrow)" />
|
||
<text class="hd-label small" x="228" y="143" text-anchor="middle">yes</text>
|
||
<path class="hd-line" d="M110 186 V206" marker-end="url(#hd-stuck-arrow)" />
|
||
<text class="hd-label small" x="118" y="200">no</text>
|
||
<path class="hd-line" d="M402 182 V206" marker-end="url(#hd-stuck-arrow)" />
|
||
<path class="hd-line" d="M546 50 H554 V231 H474" marker-end="url(#hd-stuck-arrow)" />
|
||
<rect class="hd-accent" x="90" y="210" width="380" height="44" rx="8" />
|
||
<text class="hd-label hd-accent" x="280" y="229" text-anchor="middle">Answering anyway is safe:</text>
|
||
<text class="hd-label" x="280" y="246" text-anchor="middle">what you send is held until it is collected</text>
|
||
<path class="hd-flow" d="M202 50 H256 M546 50 H554 V231 H474" />
|
||
</svg>
|
||
<figcaption>Whatever you find, nothing you have typed is lost.</figcaption>
|
||
</figure>
|
||
<h4>Not running, or not connected?</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Not running</strong> (Planny gray and still): this page is
|
||
fine, but Plan2Code in the terminal has not checked in for
|
||
<span data-fact="adriftMinutes">3</span> minutes. It may have finished
|
||
its turn, hit an error, or be waiting on you there.
|
||
</li>
|
||
<li>
|
||
<strong>Not connected</strong> (Planny faded, arms hanging, his star shut in red):
|
||
this page cannot reach its own program, after
|
||
<span data-fact="goneSeconds">8</span> seconds without contact.
|
||
Usually it has shut itself down; <span id="help-stuck-not-connected-ref">see "Getting a new link" below</span>.
|
||
</li>
|
||
</ul>
|
||
<p>"Reading Planny" shows every mood side by side.</p>
|
||
<h4>It may be waiting for you in the terminal</h4>
|
||
<p>
|
||
Plan2Code sometimes stops in the terminal to ask your permission
|
||
before it runs a command or changes a file, and this page cannot see
|
||
that. After about 30 seconds of silence while it is working, the line
|
||
beside Planny asks <span data-app=""Still working, or waiting on an approval in the terminal panel?"">"Still working, or waiting on an approval in your
|
||
terminal?"</span> Have a look at the terminal: answering there sets it going
|
||
again.
|
||
</p>
|
||
<p>
|
||
If it stays quiet a couple of minutes longer, the line changes to
|
||
"Still working on it. Longer tasks can go a few minutes between
|
||
updates", with Planny still
|
||
in his working pose. It may be busy, or still waiting on you in the
|
||
terminal; the terminal is where to look. A build that said a task may
|
||
take longer gets that long before the line changes.
|
||
</p>
|
||
<p>
|
||
Hands-off modes, such as <code>auto</code> mode in Claude Code or
|
||
<code>smart</code> mode in Devin, cut down on those stops, though some
|
||
may still need you.
|
||
</p>
|
||
<h4>Answering anyway</h4>
|
||
<p>
|
||
You can keep answering and press Send while Plan2Code is not running.
|
||
What you send is written to disk and held until something collects it,
|
||
so starting Plan2Code again picks it up where you left off.
|
||
</p>
|
||
<h4 id="help-stuck-reconnect-title">Getting a new link</h4>
|
||
<p>The program behind this page shuts itself down:</p>
|
||
<ul>
|
||
<li class="for-browser">
|
||
<span data-fact="closedTabMinutes">2</span> minutes after the last tab
|
||
showing it closes,
|
||
</li>
|
||
<li class="for-app">
|
||
<span data-fact="closedTabMinutes">2</span> minutes after the app's
|
||
window closes,
|
||
</li>
|
||
<li>
|
||
after <span data-fact="idleMinutes">30</span> minutes without hearing
|
||
from anyone, or
|
||
</li>
|
||
<li>
|
||
after <span data-fact="maxLifeHours">4</span> hours, whatever is
|
||
happening.
|
||
</li>
|
||
</ul>
|
||
<p id="help-stuck-reconnect-text">
|
||
To get it back, ask Plan2Code in the terminal to resume the session,
|
||
or run the step's command again, and use the new link it gives you.
|
||
Everything you typed, sent or not, is still there.
|
||
</p>
|
||
<div class="handoff-command" data-copy id="help-stuck-reconnect-command">
|
||
<code class="handoff-code">resume the session and print the web console address here</code>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Tab 3: Finding your way around -->
|
||
<section class="help-panel" data-tab="around">
|
||
<h3>Finding your way around</h3>
|
||
<p class="help-lead">
|
||
The page is laid out the same way in every session: a bar across the
|
||
top, the outline on the left, the question or document in the middle,
|
||
your notes on the right and the Send button at the bottom.
|
||
</p>
|
||
<figure class="help-figure" data-figure="around">
|
||
<svg class="help-diagram" viewBox="0 0 560 320" role="img" aria-labelledby="hd-around-title hd-around-desc">
|
||
<title id="hd-around-title">A map of the page</title>
|
||
<desc id="hd-around-desc">
|
||
A simplified outline of this page with six numbered areas, in the
|
||
same order as the sections below: 1, the top bar, with the title on
|
||
the left, the progress bar in the middle, the gear and question
|
||
mark buttons on the right, and Stop session under the title;
|
||
2, Planny and the outline down the left; 3, the view tabs, on the
|
||
top bar's second row at the right; 4, the question card in the
|
||
middle with Previous and Next under it; 5, the notes panel on the
|
||
right; 6, the footer with Clear and Send to Plan2Code.
|
||
</desc>
|
||
<rect class="hd-box" x="6" y="6" width="548" height="308" rx="10" />
|
||
<path class="hd-line" d="M6 64 H554 M130 64 V270 M430 64 V270 M6 270 H554" />
|
||
<text class="hd-label" x="20" y="28">Title</text>
|
||
<rect class="hd-line" x="215" y="18" width="130" height="6" rx="3" />
|
||
<rect class="hd-accent" x="215" y="18" width="58" height="6" rx="3" />
|
||
<rect class="hd-box" x="482" y="10" width="22" height="22" rx="5" />
|
||
<circle class="hd-accent" cx="493" cy="21" r="5" />
|
||
<rect class="hd-box" x="510" y="10" width="22" height="22" rx="5" />
|
||
<text class="hd-label" x="521" y="26" text-anchor="middle">?</text>
|
||
<rect class="hd-box" x="20" y="38" width="96" height="20" rx="5" />
|
||
<text class="hd-label small" x="68" y="52" text-anchor="middle">Stop session</text>
|
||
<text class="hd-label small" x="340" y="53">Questions</text>
|
||
<text class="hd-label small" x="408" y="53">Overview</text>
|
||
<text class="hd-label small" x="540" y="53" text-anchor="end">Ask</text>
|
||
<rect class="hd-box" x="46" y="80" width="18" height="26" rx="4" />
|
||
<path class="hd-line" d="M50 80 L46 72 M60 80 L64 72" />
|
||
<path class="hd-line" d="M22 122 H112 M22 138 H100 M22 154 H108 M22 170 H92 M22 186 H104" />
|
||
<rect class="hd-box" x="150" y="80" width="260" height="144" rx="8" />
|
||
<text class="hd-label" x="280" y="148" text-anchor="middle">The question card</text>
|
||
<text class="hd-label small" x="280" y="166" text-anchor="middle">answer it here</text>
|
||
<text class="hd-label small" x="160" y="250">Previous</text>
|
||
<text class="hd-label small" x="400" y="250" text-anchor="end">Next</text>
|
||
<text class="hd-label small" x="442" y="84">Notes on this</text>
|
||
<rect class="hd-box" x="442" y="206" width="100" height="44" rx="6" />
|
||
<text class="hd-label small" x="20" y="297">What is ready</text>
|
||
<rect class="hd-box" x="352" y="282" width="52" height="22" rx="5" />
|
||
<text class="hd-label small" x="378" y="297" text-anchor="middle">Clear</text>
|
||
<rect class="hd-accent" x="412" y="282" width="132" height="22" rx="5" />
|
||
<text class="hd-label small" x="478" y="297" text-anchor="middle">Send to Plan2Code</text>
|
||
<circle class="hd-accent" cx="160" cy="22" r="10" />
|
||
<text class="hd-label hd-accent" x="160" y="27" text-anchor="middle">1</text>
|
||
<circle class="hd-accent" cx="100" cy="94" r="10" />
|
||
<text class="hd-label hd-accent" x="100" y="99" text-anchor="middle">2</text>
|
||
<circle class="hd-accent" cx="316" cy="48" r="10" />
|
||
<text class="hd-label hd-accent" x="316" y="53" text-anchor="middle">3</text>
|
||
<circle class="hd-accent" cx="280" cy="246" r="10" />
|
||
<text class="hd-label hd-accent" x="280" y="251" text-anchor="middle">4</text>
|
||
<circle class="hd-accent" cx="492" cy="128" r="10" />
|
||
<text class="hd-label hd-accent" x="492" y="133" text-anchor="middle">5</text>
|
||
<circle class="hd-accent" cx="250" cy="292" r="10" />
|
||
<text class="hd-label hd-accent" x="250" y="297" text-anchor="middle">6</text>
|
||
</svg>
|
||
<figcaption>The numbers follow the sections below, top to bottom.</figcaption>
|
||
</figure>
|
||
<h4>The top bar</h4>
|
||
<ul>
|
||
<li>The name of the step you are in, and the session's title.</li>
|
||
<li>
|
||
<strong>The progress bar</strong>, for example "4 of 9 answered", or
|
||
"4 of 9 done" while something is being built.
|
||
</li>
|
||
<li>
|
||
The gear button opens <strong>User Preferences</strong>, and the
|
||
<strong>?</strong> button beside it opens this Help. Preferences has four tabs:
|
||
your theme, card width, colors and role, then agents and models,
|
||
cleanup, and sounds and whether Activities shows.
|
||
</li>
|
||
<li class="for-browser">
|
||
The <strong>megaphone</strong> button opens GitHub in a
|
||
new tab, where you can report a bug or suggest an idea.
|
||
</li>
|
||
<li class="for-app">
|
||
The <strong>megaphone</strong> button opens Plan2Code's
|
||
GitHub issues, where you can report a bug or suggest an idea.
|
||
</li>
|
||
<li>
|
||
The <strong>die</strong> beside it opens <strong>Activities</strong>,
|
||
small games to play while you wait. See "Activities".
|
||
</li>
|
||
<li>
|
||
<strong>Stop session</strong> ends the session and saves your place.
|
||
See "Stopping and finishing".
|
||
</li>
|
||
<li>
|
||
The <strong>triangle</strong> beside it, pointing left, saves your
|
||
place and takes you back to the dashboard. It is there on every step
|
||
except the dashboard itself.
|
||
</li>
|
||
</ul>
|
||
<h4>Planny and the outline, on the left</h4>
|
||
<p>
|
||
Planny sits at the top, with a line beside him saying whose turn it is
|
||
and what Plan2Code is doing. Below him the outline lists the session's
|
||
topics and every question in them, with how many are settled. Click any
|
||
question to jump to it.
|
||
</p>
|
||
<h4>The view tabs</h4>
|
||
<p>
|
||
Under the top bar: <strong>Questions</strong> first, then
|
||
<strong>Overview</strong> when the session is working on a spec, then
|
||
one tab per document Plan2Code has written, and <strong>Ask</strong>,
|
||
always last.
|
||
<span data-app="Each tab remembers where you scrolled for as long as the app's window stays open.">Each tab remembers where you scrolled for as long as this browser tab
|
||
stays open.</span>
|
||
</p>
|
||
<h4>Moving between questions</h4>
|
||
<p>
|
||
<strong>Previous</strong> and <strong>Next</strong> under each card walk
|
||
the questions still waiting for you, so you never have to hunt for the
|
||
next one in the outline.
|
||
</p>
|
||
<h4>Notes, on the right</h4>
|
||
<p>
|
||
<strong>Notes on this</strong> shows the back and forth about the
|
||
question you are on, with a box for a note of your own. See "Notes and
|
||
attachments".
|
||
</p>
|
||
<h4>The footer</h4>
|
||
<ul>
|
||
<li>What is ready to send, on the left.</li>
|
||
<li>
|
||
In the middle, the folder the session was started from, any folders
|
||
you added, and its git branch. Click it to open your workspace. See
|
||
"Your workspace".
|
||
</li>
|
||
<li>
|
||
<strong>Clear</strong> and <strong>Send to Plan2Code</strong> on the
|
||
right. See "Sending and what happens next".
|
||
</li>
|
||
</ul>
|
||
<h4>Your notebook</h4>
|
||
<p>
|
||
The <strong>Notebook</strong> button, a small notebook with an elastic
|
||
band, sits beside Stop session on every screen. It opens a notebook of
|
||
your own for this folder, somewhere to jot things down as you go.
|
||
</p>
|
||
<ul>
|
||
<li>
|
||
A notebook is a row of <strong>tabs</strong>, each with its own text
|
||
and its own pictures. <strong>+ New tab</strong> asks for a name
|
||
first. Notes you made before tabs existed show up as a tab called
|
||
Notes.
|
||
</li>
|
||
<li>
|
||
Under the row, <strong>Rename</strong> changes the current tab's
|
||
name (double-click a tab or press <kbd>F2</kbd> works too). Drag a
|
||
tab to reorder it, or use <strong>Move left</strong> and
|
||
<strong>Move right</strong>, or <kbd>Alt</kbd> with the arrow keys.
|
||
The tab you leave open is the one you come back to.
|
||
</li>
|
||
<li>
|
||
<strong>Delete</strong> asks twice before it removes a tab, and
|
||
takes its text and its pictures with it. That cannot be undone.
|
||
With no tabs left, you are asked to make one.
|
||
</li>
|
||
<li>
|
||
Text is styled as you type. Write Markdown, such as
|
||
<code>**bold**</code> or <code># Heading</code>, and headings grow
|
||
and bullets draw in place. The marks come back on the line you are
|
||
on.
|
||
</li>
|
||
<li>
|
||
Images go in the strip under the text. Paste one, drop one on the
|
||
notebook or press <strong>Add image</strong>. Click a picture to see
|
||
it full screen: the arrow keys step through them and
|
||
<kbd>Esc</kbd> closes it. The <strong>×</strong> on a picture asks
|
||
before it deletes it.
|
||
</li>
|
||
<li>
|
||
Everything saves as you go, one notebook per project folder and one
|
||
folder per tab on disk. There is no Save button.
|
||
</li>
|
||
<li>
|
||
It is private to this machine and never sent to Plan2Code.
|
||
Private: the agent never reads your Notebook. A tab reaches it only
|
||
when you start a workflow with it.
|
||
</li>
|
||
<li>
|
||
A lit card's confirm pane can offer <strong>Start with a note from
|
||
your Notebook</strong>. On the dashboard, Pathfinder, Plan and Quick
|
||
Task offer it on Start fresh, and Revise plan on a picked spec with
|
||
no plan change waiting. A tab you started a workflow with wears a
|
||
small <strong>sent</strong> badge.
|
||
</li>
|
||
<li>
|
||
Two open pages on the same folder share one notebook. If both change
|
||
it, the last save wins.
|
||
</li>
|
||
<li>
|
||
<strong>Cleanup</strong>, in User Preferences, offers to remove a
|
||
notebook only after a month untouched. Nothing removes it on its own.
|
||
</li>
|
||
</ul>
|
||
</section>
|
||
|
||
<!-- Tab 4: Your workspace -->
|
||
<section class="help-panel" data-tab="workspace">
|
||
<h3>Your workspace</h3>
|
||
<p class="help-lead">
|
||
The folders Plan2Code uses as context in this session: the folder you
|
||
started in, plus any others you add, such as a shared library or a
|
||
design folder next door.
|
||
</p>
|
||
<h4>Opening it</h4>
|
||
<p>
|
||
Click the folder name in the middle of the bottom bar. It shows your
|
||
folder's name and branch, such as <strong>shop · main</strong>, and
|
||
<strong>shop + 2 folders · main</strong> once you have added some.
|
||
It carries across steps you start from the dashboard.
|
||
</p>
|
||
<h4>Remembered for next time</h4>
|
||
<ul>
|
||
<li>
|
||
Every change is saved as you make it, so the next console session in
|
||
this folder starts with the same folders.
|
||
</li>
|
||
<li>
|
||
Each spec keeps its own list. The first time you pick a spec on the
|
||
dashboard it starts as a copy of the project's list (the one shown
|
||
under <strong>Start from scratch</strong>), and after that the two
|
||
are separate. Picking a spec loads its list; the line under the
|
||
dialog's title says whose list you are looking at.
|
||
</li>
|
||
<li>
|
||
The lists live in <code>workspaces.json</code> in your own
|
||
Plan2Code settings folder, beside your look and feel, never in the
|
||
project. Finalize offers to forget a spec's list when it archives the
|
||
spec.
|
||
</li>
|
||
</ul>
|
||
<h4>Adding a folder</h4>
|
||
<ul>
|
||
<li>
|
||
Paste or type its path and press <strong>Add</strong>. A path such as
|
||
<code>../shared</code> counts from the folder you started in.
|
||
</li>
|
||
<li>
|
||
Or press <strong>Browse…</strong> to pick it from your computer's own
|
||
folder window. Browse… is hidden when the page is being reached from
|
||
another machine; type the path instead.
|
||
</li>
|
||
<li>
|
||
Each folder gets a short name, such as <strong>@shared</strong>, made
|
||
of lowercase letters, numbers and hyphens. Change it, and add a line
|
||
on what the folder is, in the boxes under its path.
|
||
</li>
|
||
<li>
|
||
The folder you started in can be renamed and described, but not
|
||
removed. <strong>Remove</strong> takes any other one out, and
|
||
Plan2Code is told.
|
||
</li>
|
||
</ul>
|
||
<h4>Using @names</h4>
|
||
<p>
|
||
Type <strong>@</strong> in the Ask box, a note or a typed answer and a
|
||
list of your folder names appears. Pick one, and Plan2Code knows
|
||
exactly which folder you mean, for example "use the button styles from
|
||
@shared".
|
||
</p>
|
||
<h4>What Plan2Code does with them</h4>
|
||
<p>
|
||
It reads the added folders for reference, and changes them only if you
|
||
ask it to. Before it first uses one, it reads that folder's own notes
|
||
for agents, so it follows that folder's rules as well.
|
||
</p>
|
||
<h4>Marks you may see</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>This folder no longer exists</strong>: it was moved, renamed
|
||
or deleted since you added it. Remove it, or put it back and the mark
|
||
goes away.
|
||
</li>
|
||
<li>
|
||
<strong>The agent can't read this yet</strong>: Plan2Code tried and
|
||
was refused. Most agents ask your permission the first time; allow it
|
||
in the terminal. In Claude Code, the mark carries a command such as
|
||
<code>/add-dir</code> followed by the path: copy it and run it in the
|
||
terminal.
|
||
</li>
|
||
<li>
|
||
<strong>Inside another folder in the list</strong>: fine to keep. It
|
||
only means one folder already contains the other.
|
||
</li>
|
||
</ul>
|
||
</section>
|
||
|
||
<!-- Tab 5: Reading Planny -->
|
||
<section class="help-panel" data-tab="planny">
|
||
<h3>Reading Planny</h3>
|
||
<p class="help-lead">
|
||
Planny, the little box with a star for an eye at the top left, shows at a glance whose turn
|
||
it is, and the line beside him says it in words.
|
||
</p>
|
||
<figure class="help-figure help-moods" data-figure="planny" role="img" aria-labelledby="hd-planny-title">
|
||
<div class="help-moods-row"></div>
|
||
<span id="hd-planny-title" class="help-moods-title">Planny's six moods, left to right: your turn, working, all caught up, done, not running, not connected.</span>
|
||
</figure>
|
||
<h4>Your turn</h4>
|
||
<p>
|
||
Leaning in and waving, his star lit in your highlight color. Something on this page is
|
||
waiting for you: a question to answer, or answers ready to send.
|
||
</p>
|
||
<h4>Working</h4>
|
||
<p>
|
||
Star turning, arms pumping, feet walking on the spot. Plan2Code has your answers and is thinking, or is
|
||
busy building. The line beside him says what it is doing. After about
|
||
30 seconds of silence it asks <span data-app=""Still working, or waiting on an approval in the terminal panel?"">"Still working, or waiting on an approval
|
||
in your terminal?"</span>, because the terminal may have stopped to ask your
|
||
permission for something, and this page cannot see that.
|
||
</p>
|
||
<h4>All caught up</h4>
|
||
<p>
|
||
A green star. Nothing is waiting on either side: every question is
|
||
answered and Plan2Code has nothing new yet.
|
||
</p>
|
||
<h4>Done</h4>
|
||
<p id="help-planny-done-text">A green star and both arms up. The session is finished. You can close the tab.</p>
|
||
<h4>Not running</h4>
|
||
<p>
|
||
Gray, still, arms down out of sight. This page is fine, but Plan2Code has not checked in
|
||
for <span data-fact="adriftMinutes">3</span> minutes. Anything you answer
|
||
is still saved.
|
||
</p>
|
||
<h4>Not connected</h4>
|
||
<p>
|
||
Faded, arms hanging, his star shut in red. This page cannot reach its program, after
|
||
<span data-fact="goneSeconds">8</span> seconds without contact. Your
|
||
answers are saved.
|
||
</p>
|
||
<p>
|
||
For what to do about the last two, see "When something looks stuck".
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 6: Answering questions -->
|
||
<section class="help-panel" data-tab="answering">
|
||
<h3>Answering questions</h3>
|
||
<p class="help-lead">
|
||
Each question is a card, and every card works the same way: answer it,
|
||
add a note if you like, and send when you are ready.
|
||
</p>
|
||
<h4>The kinds of card</h4>
|
||
<ul>
|
||
<li><strong>Pick one.</strong> Choose a single option. The trade-off for each is written under it.</li>
|
||
<li><strong>Pick any.</strong> Tick as many as apply. Some cards have quick-pick buttons that tick a set in one go.</li>
|
||
<li><strong>Type an answer.</strong> A box for your own words.</li>
|
||
<li><strong>Yes or no.</strong> One of two buttons, sometimes with what each would lead to spelled out.</li>
|
||
<li><strong>Is this right?</strong> Plan2Code plays back what it understood. Agree, or say what is off.</li>
|
||
<li><strong>Read, then approve.</strong> Open the document it points to, then approve it or ask for changes.</li>
|
||
<li><strong>Steps only you can do.</strong> A checklist of things to do outside this page, ticked off as you go.</li>
|
||
<li><strong>Put in order or edit a list.</strong> Drag the rows, or use <strong>Move up</strong> and <strong>Move down</strong>, and edit any row.</li>
|
||
<li><strong>What to do next.</strong> A short menu of where to go from here.</li>
|
||
<li><strong>Something to read.</strong> A notice. Nothing to answer.</li>
|
||
</ul>
|
||
<h4>Help with an answer</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Autofill suggestion</strong> puts the example into the box as
|
||
a real answer for you to edit. It disappears as soon as you have typed
|
||
anything of your own.
|
||
</li>
|
||
<li>
|
||
<strong>Starter templates</strong> sit above the first "What's the
|
||
idea?" box in Pathfinder, Plan and Quick Task. <strong>Blank</strong>
|
||
comes first, then outlines to fill in, in the order your role puts
|
||
them. Picking one fills the box with text you can edit; if you have
|
||
already typed something, it asks before replacing it. Only what is in
|
||
the box is sent.
|
||
</li>
|
||
<li>
|
||
<strong>Something else, in your own words</strong> sits among the
|
||
options on a pick-one card when none of them fits. It is an
|
||
alternative, not an extra: whichever you touched last is your answer.
|
||
</li>
|
||
<li>
|
||
<strong>Anything else, in your own words</strong> sits under a
|
||
pick-any card. What you write there joins your ticks rather than
|
||
replacing them.
|
||
</li>
|
||
<li>
|
||
<strong>Skip this one</strong> appears on questions that are optional,
|
||
and moves you on to the next question by itself; <strong>Do not
|
||
skip</strong> brings the question back.
|
||
</li>
|
||
</ul>
|
||
<h4>After you answer</h4>
|
||
<p>
|
||
<strong>A settled card reads as an answer</strong>: what you chose,
|
||
stated in words, with everything else locked.
|
||
</p>
|
||
<p>
|
||
<strong>A card you have sent is held</strong> until Plan2Code replies,
|
||
showing what you sent. It unlocks by itself when it answers. The rest of
|
||
the page keeps working, so you can read ahead or answer the next
|
||
question meanwhile.
|
||
</p>
|
||
<p>
|
||
If a card has been held for a long time, <strong>Take this back and
|
||
answer again</strong> puts your answer back in the box so you can change
|
||
it and send again.
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 7: Sending and what happens next -->
|
||
<section class="help-panel" data-tab="sending">
|
||
<h3>Sending and what happens next</h3>
|
||
<p class="help-lead">
|
||
Nothing leaves this page until you press
|
||
<strong>Send to Plan2Code</strong>, so you can answer, change your
|
||
mind and answer again without committing to anything.
|
||
</p>
|
||
<figure class="help-figure" data-figure="sending">
|
||
<svg class="help-diagram" viewBox="0 0 560 170" role="img" aria-labelledby="hd-sending-title hd-sending-desc">
|
||
<title id="hd-sending-title">What happens when you send</title>
|
||
<desc id="hd-sending-desc">
|
||
Four steps in a loop: you answer, and it is kept on this page; you
|
||
press Send; your answers are held on disk until Plan2Code collects
|
||
them; Plan2Code replies with the next questions, and the loop
|
||
starts again with you.
|
||
</desc>
|
||
<defs>
|
||
<marker id="hd-sending-arrow" viewBox="0 0 8 8" refX="7" refY="4" markerWidth="5" markerHeight="5" orient="auto-start-reverse">
|
||
<path class="hd-arrow" d="M0 0 L8 4 L0 8 z" />
|
||
</marker>
|
||
</defs>
|
||
<rect class="hd-box" x="8" y="20" width="116" height="72" rx="8" />
|
||
<rect class="hd-accent" x="150" y="20" width="116" height="72" rx="8" />
|
||
<rect class="hd-box" x="292" y="20" width="116" height="72" rx="8" />
|
||
<rect class="hd-box" x="434" y="20" width="116" height="72" rx="8" />
|
||
<text class="hd-label" x="66" y="52" text-anchor="middle">You answer</text>
|
||
<text class="hd-label small" x="66" y="70" text-anchor="middle">kept here</text>
|
||
<text class="hd-label hd-accent" x="208" y="61" text-anchor="middle">Send</text>
|
||
<text class="hd-label" x="350" y="52" text-anchor="middle">Held on disk</text>
|
||
<text class="hd-label small" x="350" y="70" text-anchor="middle">until collected</text>
|
||
<text class="hd-label" x="492" y="45" text-anchor="middle">Plan2Code</text>
|
||
<text class="hd-label small" x="492" y="63" text-anchor="middle">replies with the</text>
|
||
<text class="hd-label small" x="492" y="79" text-anchor="middle">next questions</text>
|
||
<path class="hd-line" d="M126 56 H146" marker-end="url(#hd-sending-arrow)" />
|
||
<path class="hd-line" d="M268 56 H288" marker-end="url(#hd-sending-arrow)" />
|
||
<path class="hd-line" d="M410 56 H430" marker-end="url(#hd-sending-arrow)" />
|
||
<path class="hd-line" d="M492 94 V140 H66 V98" marker-end="url(#hd-sending-arrow)" />
|
||
<text class="hd-label small" x="279" y="158" text-anchor="middle">and round again</text>
|
||
<path class="hd-flow" d="M126 56 H146 M268 56 H288 M410 56 H430 M492 94 V140 H66 V98" />
|
||
</svg>
|
||
<figcaption>Nothing leaves this page until you press Send.</figcaption>
|
||
</figure>
|
||
<h4>Before you send</h4>
|
||
<ul>
|
||
<li>
|
||
Everything you pick or type is a draft that Plan2Code cannot see
|
||
yet, and every bit of it can be undone.
|
||
</li>
|
||
<li class="for-browser">
|
||
Drafts survive a closed tab and a reload: open the same link again and
|
||
your half-typed answers are still there.
|
||
</li>
|
||
<li class="for-app">
|
||
Drafts survive a closed window and a reload: when the app shows this
|
||
session again, your half-typed answers are still there.
|
||
</li>
|
||
<li>
|
||
The footer says what is ready to go, and the Send button pulses gently
|
||
while there is something to send.
|
||
</li>
|
||
<li>
|
||
<strong>Clear</strong> throws away everything you have not sent yet. It
|
||
asks first.
|
||
</li>
|
||
</ul>
|
||
<h4>Sending</h4>
|
||
<p>
|
||
Press <strong>Send to Plan2Code</strong>, or
|
||
<kbd>Ctrl</kbd>+<kbd>Enter</kbd> (<kbd>⌘</kbd>+<kbd>Enter</kbd> on a
|
||
Mac).
|
||
</p>
|
||
<h4>What happens next</h4>
|
||
<ol>
|
||
<li>
|
||
Your answers are written to disk straight away, and held there until
|
||
Plan2Code collects them, so nothing can write over them.
|
||
</li>
|
||
<li>
|
||
A second send waits until the first has been collected. Send stays
|
||
off until then.
|
||
</li>
|
||
<li>Planny switches to Working while Plan2Code reads them.</li>
|
||
<li>
|
||
The next questions appear on their own, with a chime if sounds are on.
|
||
There is nothing to reload.
|
||
</li>
|
||
</ol>
|
||
</section>
|
||
|
||
<!-- Tab 8: Notes and attachments -->
|
||
<section class="help-panel" data-tab="notes">
|
||
<h3>Notes and attachments</h3>
|
||
<p class="help-lead">
|
||
A note lets you say more about any question, and an attachment lets you
|
||
show instead of describe.
|
||
</p>
|
||
<h4>Notes</h4>
|
||
<p>
|
||
The <strong>Notes on this</strong> panel on the right belongs to the
|
||
question you are on. Type in <strong>Add a note, attach a file, or ask
|
||
something</strong> and it goes with your next send. A note qualifies
|
||
your answer without replacing it: "B, but keep the header row" is an
|
||
answer and a note together. Plan2Code's replies appear in the same
|
||
panel.
|
||
</p>
|
||
<h4>Attaching a file</h4>
|
||
<p>Three ways, whichever is handiest:</p>
|
||
<ul>
|
||
<li>the <strong>+ Attach file</strong> button by the box,</li>
|
||
<li><strong>paste</strong> a screenshot or a copied file into the box, or</li>
|
||
<li><strong>drag and drop</strong> files onto the notes panel.</li>
|
||
</ul>
|
||
<p>
|
||
Each file uploads straight away while you keep typing, and sits in a
|
||
tray with a remove button. A failed upload offers to retry or remove,
|
||
and holds back only that note, so the rest of your answers still send.
|
||
</p>
|
||
<h4>What you can attach</h4>
|
||
<ul>
|
||
<li>
|
||
Up to <span data-fact="maxAttachments">5</span> attachments per note,
|
||
images and documents counted together.
|
||
</li>
|
||
<li>
|
||
<strong>Images</strong> are shrunk <span data-app="on this machine">in your browser</span> to a JPEG at most
|
||
<span data-fact="imageEdge">2000</span> px on the long edge, and must
|
||
be under <span data-fact="maxUploadMb">4</span> MB after shrinking.
|
||
</li>
|
||
<li>
|
||
<strong>Documents</strong> up to
|
||
<span data-fact="maxDocMb">10</span> MB each, uploaded exactly as they
|
||
are: plain text, Markdown, JSON, YAML, TOML, INI, CSV, TSV, logs, XML,
|
||
HTML, CSS and SCSS, code (JavaScript, TypeScript, Python, Java, C#, Go,
|
||
Rust, Ruby, PHP, shell, PowerShell, SQL) and PDF.
|
||
</li>
|
||
<li>
|
||
Anything else is refused with a message naming the file: Word files
|
||
such as <code>.docx</code>, files that are too large, and dotfiles such
|
||
as <code>.env</code>, which is where secrets tend to live.
|
||
</li>
|
||
</ul>
|
||
<h4>Where the files go</h4>
|
||
<p>
|
||
With the session, in
|
||
<code>~/.plan2code/console/sessions/<id>/uploads/</code>, never in
|
||
your project. They are removed along with the session after
|
||
<span data-fact="cleanupDays">30</span> days untouched.
|
||
</p>
|
||
<p>
|
||
The exception is a note attachment Plan2Code cites in a spec file.
|
||
Before it writes that file, it copies the attachment into
|
||
<code>specs/<idea>/attachments/</code>, so the link still works
|
||
after the session is gone. Files attached on the Ask tab always stay
|
||
in the session.
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 9: Documents and printing -->
|
||
<section class="help-panel" data-tab="docs">
|
||
<h3>Documents and printing</h3>
|
||
<p class="help-lead">
|
||
What Plan2Code writes appears here as it takes shape, one tab per
|
||
document, so you can read along without opening a file.
|
||
</p>
|
||
<h4>Reading a document</h4>
|
||
<p>
|
||
Each document has its own tab beside <strong>Questions</strong>, with
|
||
its version number next to the title. It is built from sections, and
|
||
each section tells you how firm it is:
|
||
</p>
|
||
<ul>
|
||
<li><strong>Settled</strong> sections are plain: decided, and they will not move.</li>
|
||
<li>
|
||
<strong>Assumed for now, still open</strong> sections have a dashed
|
||
edge. Plan2Code had to pick something to keep going, and it is still
|
||
yours to change.
|
||
</li>
|
||
<li><strong>Draft</strong> sections are dimmed: placeholders, still to be worked out.</li>
|
||
</ul>
|
||
<p>
|
||
<strong>Out of date</strong> by the title means answers have landed that
|
||
the document does not reflect yet.
|
||
</p>
|
||
<h4>The Overview, Map and Plan draft tabs</h4>
|
||
<p>
|
||
When the session is working on a spec that has an
|
||
<code>overview.md</code>, the <strong>Overview</strong> tab shows it. It
|
||
is read-only, and read fresh from disk each time you open the tab, so an
|
||
edit shows up straight away. No file, no tab.
|
||
</p>
|
||
<p>
|
||
On the dashboard, a picked spec that is not documented yet shows its
|
||
main files the same way instead: <strong>Map</strong> for its
|
||
Pathfinder map and <strong>Plan draft</strong> for its plan draft, each
|
||
when it exists.
|
||
</p>
|
||
<h4>Printing and saving</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Back to Questions</strong> (Dashboard or Git on those
|
||
screens) takes you back to the main flow. The row with it stays at
|
||
the top of the tab while you scroll.
|
||
</li>
|
||
<li>
|
||
<strong>Print</strong> prints the document alone, without the rest of
|
||
the page. Choose "Save as PDF" in the print dialog for a PDF.
|
||
</li>
|
||
<li>
|
||
<strong>Download</strong> saves it as a Markdown file. When the
|
||
document is already a file on disk, the page shows
|
||
<strong>Saved as</strong> and its path instead.
|
||
</li>
|
||
</ul>
|
||
<h4>Briefs (Pathfinder)</h4>
|
||
<p>
|
||
<strong>Write a brief</strong>, in the top bar, asks how far back to go:
|
||
<strong>Today</strong>, <strong>This week</strong>, <strong>Since a
|
||
date</strong> or <strong>Everything so far</strong>. Press
|
||
<strong>Write the brief</strong> and Plan2Code writes a plain-English
|
||
report of what has been decided, what is still open and what happens
|
||
next. It opens in its own tab, ready to print or hand to someone who has
|
||
not been in the room. <strong>Save as HTML</strong>, beside
|
||
<strong>Print</strong>, downloads it as a single web page that opens in
|
||
any browser, formatting and images included.
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 10: The dashboard -->
|
||
<section class="help-panel" data-tab="dashboard">
|
||
<h3>The dashboard</h3>
|
||
<p class="help-lead">
|
||
The front door: run <code>/plan2code</code> and every step Plan2Code
|
||
can take is laid out as a card. Pick one and it starts right here, on
|
||
this page.
|
||
</p>
|
||
<figure class="help-figure" data-figure="dashboard">
|
||
<svg class="help-diagram" viewBox="0 0 560 110" role="img" aria-labelledby="hd-dashboard-title hd-dashboard-desc">
|
||
<title id="hd-dashboard-title">The steps, in order</title>
|
||
<desc id="hd-dashboard-desc">
|
||
Five steps left to right, each leading to the next: Pathfinder,
|
||
marked optional; Plan; Document; Implement, done with or without a
|
||
review; and Finalize.
|
||
</desc>
|
||
<defs>
|
||
<marker id="hd-dashboard-arrow" viewBox="0 0 8 8" refX="7" refY="4" markerWidth="5" markerHeight="5" orient="auto-start-reverse">
|
||
<path class="hd-arrow" d="M0 0 L8 4 L0 8 z" />
|
||
</marker>
|
||
</defs>
|
||
<rect class="hd-box hd-dash" x="8" y="20" width="92" height="44" rx="8" />
|
||
<rect class="hd-box" x="120" y="20" width="92" height="44" rx="8" />
|
||
<rect class="hd-box" x="232" y="20" width="92" height="44" rx="8" />
|
||
<rect class="hd-accent" x="344" y="20" width="92" height="44" rx="8" />
|
||
<rect class="hd-box" x="456" y="20" width="92" height="44" rx="8" />
|
||
<text class="hd-label" x="54" y="47" text-anchor="middle">Pathfinder</text>
|
||
<text class="hd-label" x="166" y="47" text-anchor="middle">Plan</text>
|
||
<text class="hd-label" x="278" y="47" text-anchor="middle">Document</text>
|
||
<text class="hd-label hd-accent" x="390" y="47" text-anchor="middle">Implement</text>
|
||
<text class="hd-label" x="502" y="47" text-anchor="middle">Finalize</text>
|
||
<text class="hd-label small" x="54" y="84" text-anchor="middle">optional</text>
|
||
<text class="hd-label small" x="390" y="84" text-anchor="middle">with or without</text>
|
||
<text class="hd-label small" x="390" y="100" text-anchor="middle">review</text>
|
||
<path class="hd-line" d="M102 42 H116" marker-end="url(#hd-dashboard-arrow)" />
|
||
<path class="hd-line" d="M214 42 H228" marker-end="url(#hd-dashboard-arrow)" />
|
||
<path class="hd-line" d="M326 42 H340" marker-end="url(#hd-dashboard-arrow)" />
|
||
<path class="hd-line" d="M438 42 H452" marker-end="url(#hd-dashboard-arrow)" />
|
||
<path class="hd-flow" d="M54 14 V8 H502 V14" />
|
||
</svg>
|
||
<figcaption>Implement runs once per phase, so it repeats until every phase is done.</figcaption>
|
||
</figure>
|
||
<h4>Asking for your role</h4>
|
||
<p>
|
||
Until you pick a role, a one-line banner at the top asks for it, so the
|
||
starter templates can be ordered for you.
|
||
<strong>Set up preferences</strong> opens User Preferences;
|
||
<strong>Not now</strong> puts the banner away. Either way it does not
|
||
come back, and you can change your role any time from the swatch
|
||
button.
|
||
</p>
|
||
<h4>When an update is out</h4>
|
||
<p id="help-update-text">
|
||
When a newer Plan2Code release is out, the dashboard shows
|
||
<strong>UPDATE AVAILABLE</strong> at the top. Click it for the command
|
||
to run in your terminal, <code>plan2code update</code>; × hides it until the next
|
||
<code>/plan2code</code>. The version at the bottom of Help links to
|
||
the Releases page.
|
||
</p>
|
||
<h4>The cards</h4>
|
||
<p>They come in three groups.</p>
|
||
<div class="help-cards"></div>
|
||
<h4>Picking a spec</h4>
|
||
<p>
|
||
Once your project has specs, <strong>Pick up a spec, or start
|
||
fresh</strong>, at the top, lists every spec folder with where it
|
||
stands, plus
|
||
<strong>Start from scratch</strong> for a new idea. The one you pick is
|
||
what a step works on, and it decides which cards make sense: a spec
|
||
that is half built has no use for Pathfinder, and a new idea cannot be
|
||
implemented yet. Cards that do not fit are grayed out with the reason
|
||
why.
|
||
</p>
|
||
<p>
|
||
<strong>Hide unavailable workflows</strong>, under the picker, hides
|
||
them instead. It is on to begin with, and remembered on this machine.
|
||
</p>
|
||
<p>
|
||
The <strong>✕</strong> on a spec deletes its folder, after two steps:
|
||
one says what goes, the other wants the spec's name typed. A fixed
|
||
bug has its own <strong>Delete</strong> button at the bottom of its
|
||
chip instead, and needs just one confirm, since the work is done.
|
||
</p>
|
||
<p id="help-handoff-copy-text">
|
||
A <strong>Handoff</strong> is a note a step left when you stopped it
|
||
with a handoff. It shows as a dashed chip after the specs. Pick one
|
||
and the cards give way to a preview with its Next task and four
|
||
buttons: <strong>Pick it up here</strong> carries on in the same step
|
||
and spec, <strong>Read it all</strong> shows the whole note,
|
||
<strong>Copy for a new conversation</strong> puts a ready prompt on
|
||
the clipboard, and <strong>Delete</strong> removes it. A picked-up
|
||
handoff drops off the list, but stays in
|
||
<code>~/.plan2code/handoffs/</code> until the 30-day sweep.
|
||
</p>
|
||
<h4>The Suggested flag</h4>
|
||
<p>
|
||
One card may carry a <strong>Suggested</strong> flag: where Plan2Code
|
||
would start, given what it found in your project. No AGENTS.md yet
|
||
suggests setting up; a spec part way through suggests its next step,
|
||
with a line on the card saying where it stands.
|
||
</p>
|
||
<h4>Starting a step</h4>
|
||
<p>
|
||
Click a card and it asks you to confirm: what the step does, which spec
|
||
it is for, and a <strong>Start</strong> button named after the step,
|
||
such as <strong>Start Plan</strong> (<strong>Back</strong>,
|
||
or <kbd>Esc</kbd>, returns to the cards). Press Start and Planny flies
|
||
while it gets ready. A few seconds later this same page is that step,
|
||
already running. No command to type, no second window.
|
||
</p>
|
||
<h4>Coming back</h4>
|
||
<p>
|
||
When a step finishes, its last screen has a <strong>Back to the
|
||
dashboard</strong> button that turns the page back into the cards, so
|
||
the next step can start straight away. See "Stopping and finishing".
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 11: Session meter -->
|
||
<section class="help-panel" data-tab="meter">
|
||
<h3>Session meter</h3>
|
||
<p class="help-lead">
|
||
The small ring in the top bar counts how much work this console session
|
||
has done, and tells you when a fresh one would serve you better.
|
||
</p>
|
||
<h4>The three colors</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Green, "Session: fresh".</strong> Under
|
||
<span data-fact="meterYellow">5</span> points. Carry on.
|
||
</li>
|
||
<li>
|
||
<strong>Yellow, "Session: getting long".</strong> From
|
||
<span data-fact="meterYellow">5</span> points. Fine for now; think
|
||
about a fresh start after this step.
|
||
</li>
|
||
<li>
|
||
<strong>Red, "Session: time for a fresh start".</strong> From
|
||
<span data-fact="meterRed">10</span> points. The dashboard also says so
|
||
in a banner.
|
||
</li>
|
||
</ul>
|
||
<h4>What it counts</h4>
|
||
<p>
|
||
Each step you run here adds points: a plan or a set of documents
|
||
weighs more than a quick task, and a built phase more still, by how
|
||
many tasks it completed: a big phase adds more than a small one.
|
||
Every two questions you answer within one step add a point too
|
||
(rounded down, so a single answer adds nothing), so a long
|
||
back-and-forth counts for more than a short one. Click the ring to see the count and a list of each step that added
|
||
points, with what it added. It is a rule of thumb, not a
|
||
reading of Plan2Code's real memory: long sessions tend to make it
|
||
miss things, and the ring is there to remind you.
|
||
</p>
|
||
<h4>What red means</h4>
|
||
<p class="for-browser">
|
||
Starting a <strong>new console session</strong> will keep Plan2Code
|
||
sharp: stop this one, then start Plan2Code again in a new
|
||
conversation. Resuming this session carries its count along, so it
|
||
does not help. Your work is all on disk, so nothing is lost.
|
||
</p>
|
||
<p class="for-app">
|
||
A fresh start will keep Plan2Code sharp: finish the step, then press
|
||
<strong>New Session</strong> at the top of the window. The agent starts
|
||
again on a clean context, in a new console session whose meter starts
|
||
over, and the dashboard offers a brief of where you were. Your work is
|
||
all on disk, so nothing is lost.
|
||
</p>
|
||
<p>
|
||
The meter never blocks anything. Red is advice; you can keep going.
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 12: Watching a build -->
|
||
<section class="help-panel" data-tab="build">
|
||
<h3>Watching a build</h3>
|
||
<p class="help-lead">
|
||
Implement, Implement + review and Quick task spend most of their time
|
||
building rather than asking, so the page shows you the build as it
|
||
happens.
|
||
</p>
|
||
<h4>What it is doing now</h4>
|
||
<p>
|
||
The line beside Planny says what Plan2Code is working on, for
|
||
example "Task 5 of 9: the rate limiter". Tasks are counted within the
|
||
phase, and the progress bar counts the same way: "5 of 9 done".
|
||
</p>
|
||
<h4>The task list and the phase file</h4>
|
||
<ul>
|
||
<li>
|
||
The phase's task list has its own tab, and each task ticks as soon as
|
||
it is finished and saved.
|
||
</li>
|
||
<li>
|
||
The phase file itself, such as <code>phase-3.md</code>, is in the tab
|
||
beside it: what has to be true before the phase starts, and every
|
||
task in full, not just the checklist.
|
||
</li>
|
||
</ul>
|
||
<h4>Questions along the way</h4>
|
||
<p>
|
||
Anything the build needs from you, such as which phase to do next, a
|
||
clash in the spec or tests that are failing, arrives as an ordinary
|
||
card. Answer it like any other.
|
||
</p>
|
||
<h4>Signing off</h4>
|
||
<p>
|
||
When the phase is built, a <strong>Completion report</strong> tab says
|
||
what was done, which files changed and how to check it, and an
|
||
<strong>Approve this phase</strong> card asks for your approval.
|
||
Nothing is marked complete until you give it.
|
||
</p>
|
||
<h4>Reviewing before you approve</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Review the code first</strong>, on the approval card, runs a
|
||
careful review of exactly the files the phase changed. The findings
|
||
come back in their own tab, and a <strong>Which to fix</strong> card
|
||
lists each one with how serious it is. Tick the ones to fix, or use
|
||
<strong>Critical and warnings</strong> or <strong>All of
|
||
them</strong>, and send. Plan2Code fixes and re-checks them, then
|
||
the approval card comes back.
|
||
</li>
|
||
<li>
|
||
A quick task has no approval card, so its last screen offers
|
||
<strong>Review it now</strong> instead, with <strong>No thanks, I am
|
||
done</strong> beside it.
|
||
</li>
|
||
<li>
|
||
Implement + review offers neither: it reviews every phase before
|
||
asking for your approval anyway.
|
||
</li>
|
||
</ul>
|
||
<h4>Long tasks</h4>
|
||
<p>
|
||
Some tasks take a while without anything to show. The build tells the
|
||
page how long it may go quiet, and Planny only says it has stopped
|
||
checking in once that time has passed.
|
||
</p>
|
||
</section>
|
||
|
||
<section class="help-panel" data-tab="loop">
|
||
<h3>Implementation Loop</h3>
|
||
<p class="help-lead">
|
||
In the desktop app, the Implementation Loop builds every remaining
|
||
phase of a documented spec for you, one after another, while you do
|
||
something else. The dashboard's Implementation Loop card starts it.
|
||
</p>
|
||
<figure class="help-figure" data-figure="loop">
|
||
<svg class="help-diagram" viewBox="0 0 560 110" role="img" aria-labelledby="hd-loop-title hd-loop-desc">
|
||
<title id="hd-loop-title">One pass of the loop</title>
|
||
<desc id="hd-loop-desc">
|
||
You answer the setup once. Then, for each phase, the loop builds it,
|
||
reviews it, fixes the findings, re-checks, runs the quick check and
|
||
commits it. When the last phase is done, a summary is written.
|
||
</desc>
|
||
<defs>
|
||
<marker id="hd-loop-arrow" viewBox="0 0 8 8" refX="7" refY="4" markerWidth="5" markerHeight="5" orient="auto-start-reverse">
|
||
<path class="hd-arrow" d="M0 0 L8 4 L0 8 z" />
|
||
</marker>
|
||
</defs>
|
||
<rect class="hd-box" x="1" y="22" width="62" height="40" rx="8" />
|
||
<rect class="hd-accent" x="72" y="22" width="62" height="40" rx="8" />
|
||
<rect class="hd-box" x="143" y="22" width="62" height="40" rx="8" />
|
||
<rect class="hd-box" x="214" y="22" width="62" height="40" rx="8" />
|
||
<rect class="hd-box" x="285" y="22" width="62" height="40" rx="8" />
|
||
<rect class="hd-box" x="356" y="22" width="62" height="40" rx="8" />
|
||
<rect class="hd-box" x="427" y="22" width="62" height="40" rx="8" />
|
||
<rect class="hd-box" x="498" y="22" width="62" height="40" rx="8" />
|
||
<text class="hd-label" x="32" y="47" text-anchor="middle">Setup</text>
|
||
<text class="hd-label hd-accent" x="103" y="47" text-anchor="middle">Build</text>
|
||
<text class="hd-label" x="174" y="47" text-anchor="middle">Review</text>
|
||
<text class="hd-label" x="245" y="47" text-anchor="middle">Fixes</text>
|
||
<text class="hd-label" x="316" y="47" text-anchor="middle">Re-check</text>
|
||
<text class="hd-label" x="387" y="47" text-anchor="middle">Check</text>
|
||
<text class="hd-label" x="458" y="47" text-anchor="middle">Commit</text>
|
||
<text class="hd-label" x="529" y="47" text-anchor="middle">Summary</text>
|
||
<path class="hd-line" d="M64 42 H70" marker-end="url(#hd-loop-arrow)" />
|
||
<path class="hd-line" d="M135 42 H141" marker-end="url(#hd-loop-arrow)" />
|
||
<path class="hd-line" d="M206 42 H212" marker-end="url(#hd-loop-arrow)" />
|
||
<path class="hd-line" d="M277 42 H283" marker-end="url(#hd-loop-arrow)" />
|
||
<path class="hd-line" d="M348 42 H354" marker-end="url(#hd-loop-arrow)" />
|
||
<path class="hd-line" d="M419 42 H425" marker-end="url(#hd-loop-arrow)" />
|
||
<path class="hd-line" d="M490 42 H496" marker-end="url(#hd-loop-arrow)" />
|
||
<path class="hd-flow" d="M103 16 V8 H458 V16" />
|
||
<text class="hd-label small" x="280" y="90" text-anchor="middle">once for every phase</text>
|
||
</svg>
|
||
<figcaption>Review, fixes and re-check are on only when you choose them in the setup.</figcaption>
|
||
</figure>
|
||
<h4>What it does</h4>
|
||
<ul>
|
||
<li>
|
||
It runs on its own, one <strong>fresh agent session per phase</strong>,
|
||
and, when you leave commits on, <strong>commits each phase locally</strong> to the
|
||
branch you are on. It never pushes.
|
||
</li>
|
||
<li>
|
||
Review fixes are chosen with <strong>Smart pick</strong> by a fresh agent
|
||
that skips what is not worth fixing and records each skip, or
|
||
<strong>by level</strong> (Critical, Warning, Suggestion).
|
||
</li>
|
||
<li>
|
||
It uses the launch agent and model the app is running, and it needs
|
||
<strong>permission checks off</strong>: with them on, an agent would
|
||
wait on a prompt nobody sees, so Start stays grayed out.
|
||
</li>
|
||
</ul>
|
||
<h4>What is locked while it runs</h4>
|
||
<p>
|
||
Answers, sign-offs, launches, Workspace, Helpers and
|
||
<strong>Back</strong> are read-only, starting a new session is held
|
||
back, and Ask is off, except for a question the loop is waiting on. Still
|
||
open: Activities, Notebook, Help, Preferences, the docs and the code
|
||
review.
|
||
</p>
|
||
<h4>Stopping it</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Stop after this phase</strong>, on the banner at the top of the window, lets the
|
||
phase finish its review, mark and commit, then ends the loop.
|
||
</li>
|
||
<li>
|
||
<strong>Stop now</strong> ends the agent at once, after you confirm.
|
||
</li>
|
||
<li>Quitting the app ends the loop too.</li>
|
||
</ul>
|
||
<h4>When a phase asks a question</h4>
|
||
<p>
|
||
By default the agent takes its <strong>best guess</strong> and records the
|
||
assumption. If you chose to pause instead, the loop holds, with
|
||
<strong>no time limit</strong>, and nothing is lost. The app calls you back
|
||
with the taskbar dot, a flash of the window and the question sound. Answer,
|
||
and it carries on.
|
||
</p>
|
||
<h4>Being told when it needs you</h4>
|
||
<p>
|
||
Fill in <strong>Send a notification</strong> in the setup and the app sends a message
|
||
when the loop waits on your answer or ends, unless you stopped it yourself. Send it to a
|
||
Discord, Slack, Microsoft Teams or Google Chat webhook, or to any <code>http</code> or
|
||
<code>https</code> address, with the message in its query string or a JSON body.
|
||
<strong>Send a test</strong> tries it right away. One that fails during a loop does not
|
||
change what the loop does; the finish line or the stop screen says so.
|
||
</p>
|
||
<h4>When it stops by itself</h4>
|
||
<ul>
|
||
<li>
|
||
Failing tests or a failing quick check, Critical or Warning findings
|
||
left over at a level you chose to fix, a blocked task, a conflict in the spec, a commit that was
|
||
refused, or a Critical finding the Smart pick skipped.
|
||
</li>
|
||
<li>
|
||
A crashed or silent agent gets <strong>one retry</strong> per phase, if you left that on. After that
|
||
the loop stops.
|
||
</li>
|
||
<li>
|
||
A stop screen says what failed and shows the evidence.
|
||
<strong>Resume the loop</strong> carries on from that phase;
|
||
<strong>Fix it by hand</strong> opens an ordinary Implement session
|
||
on it.
|
||
</li>
|
||
</ul>
|
||
<h4>The report</h4>
|
||
<p>
|
||
One report follows the whole build, across stops and Resume: what each
|
||
phase built and committed, the findings it fixed, the findings it chose
|
||
not to fix and why, the findings left open, each assumption, any other
|
||
decisions the agent reported, and every retry and stop. The agent writes
|
||
most of it, so it holds what the agent noticed. The finish screen counts
|
||
each kind, and <strong>Read the full report</strong> opens it, saved as
|
||
<code>specs/<feature>/LOOP-SUMMARY-<date>.md</code>. After a
|
||
stop, the stop screen shows the report so far.
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 13: The git board -->
|
||
<section class="help-panel" data-tab="git">
|
||
<h3>The git board</h3>
|
||
<p class="help-lead">
|
||
The Git card opens a board for your repository: three tabs — Changes,
|
||
Branches and Sync — and the next step on top. Every button is a request
|
||
to Plan2Code, which runs the git commands and says what each one did.
|
||
</p>
|
||
<h4>The header</h4>
|
||
<ul>
|
||
<li>
|
||
The branch you are on, and how far it is ahead of (↑) or behind (↓)
|
||
its remote copy, or that it is not published yet.
|
||
</li>
|
||
<li>With more than one remote, a badge names the one your branch follows.</li>
|
||
<li>
|
||
With no remote at all, a <strong>No remote</strong> line shows the
|
||
command that adds one, with a copy button.
|
||
</li>
|
||
<li>
|
||
<strong>Last refreshed</strong> says when the remotes were last
|
||
fetched. If a refresh fails, the line says so.
|
||
</li>
|
||
</ul>
|
||
<h4>The tabs</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Changes</strong> lists your uncommitted files, ready to
|
||
commit. Its badge counts them, or shows a dot when the only files
|
||
left are held back (secrets and very large files).
|
||
</li>
|
||
<li>
|
||
<strong>Branches</strong> lists your branches with Switch and Delete,
|
||
plus new branch and clean-up. Its badge counts branches already
|
||
merged, or whose remote copy is gone, that can be cleaned up.
|
||
Branches that exist only on the remote sit under <strong>Remote
|
||
only</strong>, showing the first
|
||
<span data-fact="remoteFold">50</span>; <strong>Search
|
||
branches</strong> filters both lists.
|
||
</li>
|
||
<li>
|
||
<strong>Sync</strong> holds pull, push and publish. Its badge shows
|
||
↑ and ↓ counts, ↑ alone when the branch is unpublished, or ? when the
|
||
remotes have not been checked lately. During a rebase or merge it
|
||
shows <strong>!</strong> instead. Once your branch is pushed, Sync
|
||
also offers <strong>Open pull request</strong>, into the default
|
||
branch or the one you pick beside it; the first time a host is
|
||
unknown, it asks which kind it is and remembers the answer.
|
||
</li>
|
||
<li>A filled badge marks the tab where the next step is.</li>
|
||
</ul>
|
||
<h4>The next step</h4>
|
||
<ul>
|
||
<li>
|
||
The tab that holds it opens with one main button and, at most, one
|
||
quieter one beside it: Commit, Push, Publish, Open pull request, and
|
||
so on.
|
||
</li>
|
||
<li>
|
||
On the other tabs, a line reads <strong>Next step is on
|
||
‹tab›</strong>; click it to go there.
|
||
</li>
|
||
<li>
|
||
Held-back files never count toward the next step. The board offers
|
||
to add them to <code>.gitignore</code> instead.
|
||
</li>
|
||
<li>
|
||
When the remotes were last checked over an hour ago, it says
|
||
<strong>Checked … — Refresh?</strong>.
|
||
</li>
|
||
<li>
|
||
With nothing to do it says <strong>All caught up</strong>, or
|
||
<strong>Nothing to commit … no remote yet</strong> when there is no
|
||
remote.
|
||
</li>
|
||
<li>
|
||
Push, Publish, Delete and Clean up always show exactly what will
|
||
happen and wait for your yes. Nothing is ever force-pushed, and a
|
||
remote branch is never deleted.
|
||
</li>
|
||
</ul>
|
||
<h4>Moving between tabs</h4>
|
||
<ul>
|
||
<li>
|
||
Once a click of yours has landed, the board moves to the tab of the
|
||
next step. Anything else that changes leaves you where you are.
|
||
</li>
|
||
<li>Reloading the page keeps the tab you were on.</li>
|
||
<li>The arrow keys move between tabs, and Home and End jump to the first and last.</li>
|
||
</ul>
|
||
<h4>While something is running</h4>
|
||
<ul>
|
||
<li>
|
||
Everything grays out except switching tabs, searching and opening
|
||
folds, so nothing queues up behind the running command.
|
||
</li>
|
||
<li>What is running shows where the next step usually sits.</li>
|
||
<li>Plan2Code's questions appear under the tab strip.</li>
|
||
<li>
|
||
When it is done, a result line says what happened, with the commit
|
||
hashes, and the board redraws from the repository as it now stands.
|
||
</li>
|
||
</ul>
|
||
<h4>Mid-rebase or merge</h4>
|
||
<p>
|
||
A rebase or merge that stopped on conflicts shows one block on Sync,
|
||
with the files still to fix. <strong>Continue</strong> becomes the main
|
||
button once no conflict markers are left; a single <strong>Abort</strong>
|
||
puts everything back as it was. The other tabs wait until it is
|
||
finished or aborted.
|
||
</p>
|
||
<h4>Done with git</h4>
|
||
<p>
|
||
<strong>Done with git</strong> ends the board. If anything happened, the
|
||
last screen lists the commits, pushes and branches created or deleted,
|
||
with <strong>Back to the dashboard</strong>; if nothing did, the page
|
||
goes straight back to the dashboard. It grays while a command runs and
|
||
comes back when it is done; if Plan2Code stops checking in,
|
||
<strong>Stop session</strong> in the top bar ends the session instead.
|
||
While a question of Plan2Code's waits, it cancels that question and
|
||
finishes.
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 14: Helpers (subagents) -->
|
||
<section class="help-panel" data-tab="subagents">
|
||
<h3>Helpers (subagents)</h3>
|
||
<p>
|
||
On most skills (all but the dashboard, Finalize, Changelog, Git and
|
||
Handoff), Plan2Code
|
||
can hand independent pieces of work to helpers (subagents) while it
|
||
keeps the conversation with you. The <strong>Subagents</strong> button in the top bar, after
|
||
Stop session, is lit while helpers are on.
|
||
</p>
|
||
<h4>The switch</h4>
|
||
<ul>
|
||
<li>
|
||
Clicking the button opens the <strong>Subagents</strong> dialog; it
|
||
never switches helpers on or off by itself. Pick <strong>Use
|
||
helpers</strong> or <strong>Work alone</strong>, edit the instruction
|
||
Plan2Code follows (<strong>Reset to default</strong> puts the
|
||
shipped one back), and say how many may run at once.
|
||
</li>
|
||
<li>
|
||
It is on until you turn it off, and saved for this project and this skill, so
|
||
the next session of the same skill here starts the same way.
|
||
</li>
|
||
<li>
|
||
The change reaches Plan2Code at its next check-in, as a setting,
|
||
not as something you typed. How many helpers it can really start is
|
||
up to your agent; some have no helpers at all.
|
||
</li>
|
||
<li>The button only appears on skills that use helpers, and only when Plan2Code can pass the setting on.</li>
|
||
</ul>
|
||
<h4>Helper strength</h4>
|
||
<p>
|
||
Under Helpers, the dialog also asks how strong the helpers should be.
|
||
Like the rest of the dialog it is saved for this project and this
|
||
skill, and it does nothing under <strong>Work alone</strong>.
|
||
</p>
|
||
<ul>
|
||
<li>
|
||
<strong>Balanced</strong> (the default): each helper gets the
|
||
strength its job needs: light for lookups, stronger for reviews and
|
||
design work.
|
||
</li>
|
||
<li>
|
||
<strong>Thrifty</strong>: one step lighter everywhere to save cost;
|
||
reviews stay at standard or above.
|
||
</li>
|
||
<li>
|
||
<strong>Best</strong>: the strongest model and high effort for
|
||
everything except lookups.
|
||
</li>
|
||
<li>
|
||
<strong>Match my session</strong>: helpers run on whatever your
|
||
session uses; nothing is set for them.
|
||
</li>
|
||
</ul>
|
||
<h4>The Subagents tab</h4>
|
||
<ul>
|
||
<li>
|
||
With the first helper, a <strong>Subagents</strong> tab appears before
|
||
Ask: one row each, with what it was asked, whether it is running, done
|
||
or failed, and a one-line result at the end. The number on the tab is
|
||
how many are still running.
|
||
</li>
|
||
<li>
|
||
Helpers report through Plan2Code, so the rows change at its
|
||
check-ins, not live. The page cannot stop a helper; ask Plan2Code
|
||
on the Ask tab if one should stop.
|
||
</li>
|
||
<li>
|
||
Under each helper, a line such as "Standard, medium effort" shows
|
||
what that helper actually ran with. "Session model" means the agent
|
||
could not set a strength for it, so it ran on the session's own
|
||
model. A helper that reported neither shows no line.
|
||
</li>
|
||
<li>
|
||
<strong>Working alone</strong> means your agent reported it has no
|
||
way to start helpers here. If it starts one after all, the note
|
||
goes away and the helper's row shows instead.
|
||
</li>
|
||
<li>
|
||
Pathfinder always uses helpers for its research questions, whatever
|
||
the switch says, and they show here too.
|
||
</li>
|
||
<li>The tab clears when you go back to the dashboard.</li>
|
||
</ul>
|
||
</section>
|
||
|
||
<!-- Tab 15: Ask a quick question -->
|
||
<section class="help-panel" data-tab="ask">
|
||
<h3>Ask a quick question</h3>
|
||
<p class="help-lead">
|
||
The <strong>Ask</strong> tab, always the last tab, is a chat for
|
||
anything you want to know, without waiting for a card to ask it on.
|
||
</p>
|
||
<h4>Asking</h4>
|
||
<p>
|
||
Ask about this project's files, or about anything at all. Plan2Code
|
||
answers at its next check-in (during a build, once it finishes the task
|
||
it is on), and the work carries on meanwhile. Asking never holds up
|
||
your answers to the cards, and sending those never holds up a question.
|
||
</p>
|
||
<h4>Prompts to carry away</h4>
|
||
<p id="help-ask-prompt-text">
|
||
When what you ask is really a new task, or you ask for a prompt,
|
||
the answer ends with a ready-to-paste prompt in a box with a
|
||
<strong>Copy</strong> button. Copy it into a new conversation: it
|
||
names the skill to use and the files to read, so nothing said here
|
||
needs repeating.
|
||
</p>
|
||
<h4>What it is about</h4>
|
||
<p>
|
||
The box starts with no context, so a question is a general one unless
|
||
you say otherwise. <strong>+ Add context</strong>, beside
|
||
<strong>+ Attach file</strong>, lists the last three places you
|
||
visited (question cards, document sections, and a spec you picked on
|
||
the dashboard) and <strong>This spec</strong>. Pick one and a chip, <strong>About:</strong> followed
|
||
by its name, sits above the box. Press <strong>×</strong> on it to
|
||
remove it. It clears after each send, so pick it again for a
|
||
follow-up.
|
||
</p>
|
||
<h4>Starter questions</h4>
|
||
<p>
|
||
An empty conversation offers a few starter questions for this step,
|
||
with the ones most useful to your Role first. Clicking one fills the
|
||
box for you to edit; it never sends by itself. They come back with
|
||
<strong>New conversation</strong>.
|
||
</p>
|
||
<h4>How much you can ask</h4>
|
||
<ul>
|
||
<li>
|
||
Up to <span data-fact="chatLimit">10</span> questions per
|
||
conversation. The counter at the top of the tab ("3 of 10") is
|
||
always in view.
|
||
Once the last one is answered, <strong>New conversation</strong>
|
||
starts a clean one. So does switching steps through the dashboard.
|
||
</li>
|
||
<li>
|
||
Up to <span data-fact="chatMaxChars">4,000</span> characters per
|
||
question. A count appears near the limit.
|
||
</li>
|
||
<li>
|
||
Up to <span data-fact="maxAttachments">5</span> attachments per
|
||
question, added the same ways as on a note: <strong>+ Attach
|
||
file</strong>, paste, or drag and drop onto the box.
|
||
</li>
|
||
</ul>
|
||
<h4>Typing and sending</h4>
|
||
<p>
|
||
<kbd>Enter</kbd> starts a new line in the Ask box.
|
||
<kbd>Ctrl</kbd>+<kbd>Enter</kbd> (<kbd>⌘</kbd>+<kbd>Enter</kbd> on a
|
||
Mac), or <strong>Send</strong>, sends the question. It sends only the
|
||
question, never your answers to the cards.
|
||
</p>
|
||
<h4>Changes need your approval</h4>
|
||
<p>
|
||
Ask for a change to a file and Plan2Code replies with a summary and
|
||
the list of files it would touch, with <strong>Approve</strong> and
|
||
<strong>Decline</strong> buttons. Nothing changes until you approve.
|
||
Afterwards it lists what changed, with line counts. Nothing is
|
||
committed, and it never touches the running step's own files under
|
||
<code>specs/</code>.
|
||
</p>
|
||
<p>
|
||
A chat message never answers a card or moves the work on. That is what
|
||
the cards are for.
|
||
</p>
|
||
<h4>When you cannot send</h4>
|
||
<ul>
|
||
<li>
|
||
"That's 10 questions in this conversation" means press
|
||
<strong>New conversation</strong> to keep going.
|
||
</li>
|
||
<li class="for-browser">
|
||
"No agent is available right now" means the session has finished or
|
||
Plan2Code has gone quiet. Check the terminal, or resume the session,
|
||
to ask.
|
||
</li>
|
||
<li class="for-app">
|
||
"No agent is available right now" means the session has finished or
|
||
Plan2Code has gone quiet. Check the terminal panel, or press
|
||
<strong>New Session</strong> if the agent has ended, to ask.
|
||
</li>
|
||
</ul>
|
||
<p>Either way, the conversation above stays readable.</p>
|
||
<h4>When an answer lands</h4>
|
||
<p>
|
||
If you are on another tab when a reply arrives, a dot appears on
|
||
<strong>Ask</strong> and a chime plays once (if sounds are on).
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 16: Activities -->
|
||
<section class="help-panel" data-tab="activities">
|
||
<h3>Activities</h3>
|
||
<p class="help-lead">
|
||
The <strong>die</strong> in the top bar opens
|
||
<strong>Activities</strong>: small games to play while you wait, say
|
||
through a long build. Twelve games ship: <strong>Snake</strong>,
|
||
<strong>Mini golf</strong>, <strong>Light Trails</strong>,
|
||
<strong>Bug Hunt</strong>, <strong>Sunset Drive</strong>,
|
||
<strong>Stack Deploy</strong>, <strong>Bumper Ring</strong>,
|
||
<strong>Rapids Run</strong>, <strong>Hot Potato</strong>,
|
||
<strong>Crossing Rush</strong>, <strong>Bounce Road</strong> and
|
||
<strong>Ghoul Rush</strong>. The window opens on a card for each game, with its best score; click one
|
||
(or walk them with the arrows and press <kbd>Space</kbd>) to play it,
|
||
and <strong>All games</strong> takes you back. One game plays at a
|
||
time: a round left for the cards waits, paused, on its card, and
|
||
picking a different game ends it. Nothing you do in it reaches
|
||
Plan2Code.
|
||
</p>
|
||
<h4>The games</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Snake</strong>: steer to the food and grow. The snake speeds
|
||
up as it grows, and a wall, a rock, a comet or your own tail ends
|
||
the round. Food eaten quickly builds a combo of up to x5. Every 5
|
||
foods is a new level, which starts in Slow-mo, and each of the first few brings something
|
||
new: rocks (a flashing cell turns to stone), mystery boxes, portals,
|
||
comets that cut your tail, then chaos. Power-ups turn up on their
|
||
own: Shield, Turbo, Slow-mo, Magnet, Ghost and Scissors, and a
|
||
mystery box can hold any of ten surprises, good or bad. The start
|
||
and end screens count how many of them you have found so far.
|
||
</li>
|
||
<li>
|
||
<strong>Mini golf</strong>: six themed courses of eighteen silly
|
||
holes, seen from above. Its card opens a dashboard of the courses,
|
||
each with a picture of one of its holes, its par and your best on
|
||
it: <strong>Pirate Cove</strong> (a shark sea, cannonballs, a
|
||
kraken and a ghost ship), the <strong>Caves of Doom</strong> (lit
|
||
only around your ball, with lava, a bottomless pit, mine carts and
|
||
stone crushers), <strong>Dino Valley</strong>, <strong>Candy
|
||
Carnival</strong>, <strong>Cosmic Glow</strong> (where black holes
|
||
bend your putt) and <strong>Frosty Peaks</strong> (where the ball
|
||
glides on ice). Pick one to play its eighteen holes, and
|
||
<strong>All courses</strong> takes you back. The aim starts on the cup and follows your mouse once you
|
||
move it, and a click putts where the arrow points. Click (or press
|
||
<kbd>Space</kbd>) to start the power meter, then click again to
|
||
set the power: the gold <strong>MAX</strong> band near the top
|
||
gives a boosted putt, but go past it into the red and you shank it.
|
||
Dawdle for 6 seconds and the meter starts by itself. Hold the mouse
|
||
button or <kbd>Space</kbd> while the ball rolls to speed it up.
|
||
Each hole has a par, and after 8
|
||
strokes the ball is picked up. The scorecard between holes shows how
|
||
the round stands against par.
|
||
</li>
|
||
<li>
|
||
<strong>Power-ups</strong>: roll over a glowing pad to hold it for
|
||
your next putt. A <strong>Lucky Doubloon</strong> makes it free, a
|
||
<strong>Cannonball</strong> fires it 1.6 times as hard, a
|
||
<strong>Ghost Ball</strong> floats over water, sand and bumpers, a
|
||
<strong>Parrot Magnet</strong> bends it toward the cup, a
|
||
<strong>Rubber Duck</strong> bounces off walls at full speed, a
|
||
<strong>Treasure Map</strong> makes the cup huge, and a
|
||
<strong>Spyglass</strong> shows where it will roll while the meter runs.
|
||
You hold one at a time, and it carries over to the next hole.
|
||
</li>
|
||
<li>
|
||
<strong>Light Trails</strong>: you and your rivals each leave a
|
||
glowing wall behind, and the last rider still moving wins the heat.
|
||
A wall, any trail (yours too), a crystal or another rider is out,
|
||
though you hold in place for a split second first, so a quick
|
||
turn still gets you clear.
|
||
Win a heat to move on through nine arenas; a crash costs one of
|
||
three lives and runs the heat again. The arenas bring more rivals,
|
||
power-up pads (Boost, Phase through trails, an Eraser, Slow-mo for
|
||
the rivals, coins and a 1UP), crystals, portals, and walls that
|
||
close in a ring at a time, flashing red first. A rival out scores,
|
||
and more if it hit your trail.
|
||
</li>
|
||
<li>
|
||
<strong>Bug Hunt</strong>: fly Planny's ship along the bottom and
|
||
squash waves of bugs before they dive at you. New bugs join as you
|
||
go: Beetles that split in two, zigzagging Race conditions,
|
||
Exceptions that throw things, Null pointers your shots pass
|
||
through while they fade, and Firewalls that take five shots. Every
|
||
fifth wave is a boss: the Memory Leak, the Spaghetti Monster (shoot
|
||
its tentacles off first) and the Heisenbug. Squashed bugs drop
|
||
coins and power-ups (Spread shot, Rapid fire, Shield, Slow-mo,
|
||
Magnet, Refactor and a 1UP), and quick kills build a combo.
|
||
</li>
|
||
<li>
|
||
<strong>Sunset Drive</strong>: race Planny's convertible down an
|
||
endless road against the clock. Each stage ends at a checkpoint
|
||
that adds time, and just before it the road splits: the side you
|
||
keep to picks the next road, and the harder one scores more.
|
||
Six roads to find: Sunset Coast, Canyon Road, Maple Valley,
|
||
Snowcap Pass, Neon City and Starlight Highway. Traffic, roadside
|
||
props and the median slow you down; coins, clocks (+5 seconds)
|
||
and nitro cans line the road, and passing a car close at speed
|
||
scores a close call. The round ends when the time runs out.
|
||
</li>
|
||
<li>
|
||
<strong>Stack Deploy</strong>: one button. A block slides back and
|
||
forth above the tower; drop it, and whatever hangs over the edge
|
||
is sliced off, so the next block is narrower. Miss the tower and
|
||
the round is over. Land one dead on for a
|
||
<strong>Perfect</strong>: nothing is sliced, a run of them scores
|
||
more (up to x5), and every third in a row grows the block back.
|
||
Gold blocks turn up from floor 15, worth more and growing it
|
||
twice as much. The floors speed up from 10 and bring twists:
|
||
blocks from either side that may turn back at 20, lag spikes that
|
||
freeze a block for a beat at 30, wind at 40, a rush through the
|
||
middle at 70 and everything faster at 90. The tower goes
|
||
from server racks to office floors, glass towers and rockets, and
|
||
a dashed line marks the highest floor you have ever reached.
|
||
</li>
|
||
<li>
|
||
<strong>Bumper Ring</strong>: sumo in bumper cars, on a ring over
|
||
the void. Push into your rivals and the harder hit wins; a car
|
||
whose middle goes past the edge falls, and the last car on the
|
||
ring wins the heat. A rival lets go and revs before it dashes:
|
||
that is your moment to step aside, and a rival that misses near
|
||
the edge may fly off on its own. Win a heat to move on through
|
||
nine arenas, from the <strong>Training Mat</strong> to the
|
||
<strong>Grand Final</strong>, then Finals that keep getting
|
||
sharper; a fall costs one of three lives and runs the heat again.
|
||
After a while the ring shrinks a band at a time (the band flashes
|
||
red first), and a heat that drags on past the smallest ring goes
|
||
to sudden death, shrinking on until two cars no longer fit. The arenas bring rivals (the Bully, the heavy Turtle,
|
||
the Sniper, the Scrapper and the Mirror, who copies your moves),
|
||
power pads (Heavy, Spring, Charge, Shield, Grow, Ghost and
|
||
Slick), bumpers, ice, a turntable, holes, a magnet and a ring
|
||
that turns square. A knockout scores for the last car to touch
|
||
the one that fell, and quick knockouts build a combo of up to x5.
|
||
</li>
|
||
<li>
|
||
<strong>Rapids Run</strong>: pilot Planny's jet-skimmer up a
|
||
winding river that scrolls down the board, its banks narrowing and
|
||
splitting around islands. Hold <kbd>Space</kbd> to fire. The
|
||
battery drains all the while, a little faster at full speed: run
|
||
over a green charge buoy to top it up, or shoot it for a few
|
||
points if you can spare it. A bank, an island, a foe, a bolt or a
|
||
flat battery costs one of three lives, and you start the stretch
|
||
again from the last dam (or, once you have reached a mini-boss,
|
||
from the mouth of its basin); a dam you blasted stays open. Each
|
||
stretch ends at a dam across the river: shoot it open to pass
|
||
(slow down to give yourself time).
|
||
Eight named stretches, from <strong>Willow Run</strong> to
|
||
<strong>Old Lock</strong>, then Night Water again and again,
|
||
quicker. Patrol skiffs drift from bank to bank and bob mines sit
|
||
still from the start; gull drones swoop across from stretch 2,
|
||
bank sentries shoot back from stretch 3, whirlpools tug you from
|
||
stretch 5 and darters swerve into your lane from stretch 6. Every
|
||
fourth dam a mini-boss holds the basin before it (the river stops
|
||
and your battery holds while you fight): the Dredger, Ironclad and
|
||
Old Leviathan. Crates hold Spread shot, a Shield (one crash of any
|
||
kind but a flat battery), a Magnet for charge buoys and a Surge
|
||
(a full battery). Points: 1 for every 5 units of river, 2 at full
|
||
speed; 5 for every quarter second you skim a bank at speed (10 at
|
||
full speed); 20 to 60 for each foe, times your combo (sinks within
|
||
1.6 seconds of each other, up to x5); 10 for a buoy shot; 100
|
||
times the dam's number for each dam, 50 times it more for a
|
||
stretch with no life lost; and 400 for each of the first three
|
||
mini-bosses (800 each the next time around, and so on), each of
|
||
which also gives a life back.
|
||
</li>
|
||
<li>
|
||
<strong>Hot Potato</strong>: one fizzing bomb (a merge conflict,
|
||
its <code><<<<<<<</code> markers showing) and a
|
||
fuse that keeps getting shorter. Whoever holds it passes it on by
|
||
touching someone, and whoever holds it when the fuse runs out is
|
||
blown out of the match. Someone just handed the bomb cannot pass
|
||
it on for a moment (it flashes white), and while three or more are
|
||
left nobody can hand it straight back to the one who just passed
|
||
it (a white ring at their feet shows who is safe). Handed the bomb
|
||
at its last moment, you still get time to pass it: a pass tops the
|
||
fuse up to 1.4 seconds, once a fuse for each runner. The holder runs a little faster, so a chase can end, and a
|
||
rival crouches before it lunges: that is your moment to dodge. The
|
||
last one standing wins the match and moves on through nine venues,
|
||
from the <strong>Break Room</strong> to the
|
||
<strong>Finale</strong>, then Finales that keep getting sharper;
|
||
being blown up costs one of three lives and runs the match again.
|
||
The venues bring rivals (the Sprinter, the Hider, the Trickster,
|
||
who feints before it dashes, the Pal and the Clingy), pickups
|
||
(Freeze, which stops every fuse for 2 seconds, Sneakers, Extra
|
||
Fuse, which adds 2 seconds to every fuse, and Swap, which trades
|
||
places with a random runner), long rows of server racks, a roof
|
||
with no wall at the bottom (off it is out), ice, conveyor belts, a
|
||
blackout and two bombs at once. Points: 10 times the venue for
|
||
every fuse that ends on someone else, 2 for each pass you make, 15
|
||
more for a hot pass (under a second left) times your streak of hot
|
||
passes in a row (up to x5; a pass that is not hot ends it, and so
|
||
does a life lost), and 50 times the venue for a match won.
|
||
</li>
|
||
<li>
|
||
<strong>Crossing Rush</strong>: hop Planny up a strip of lanes,
|
||
racing two rival hoppers to the top: roads of cars and trucks,
|
||
rivers where you ride the logs and turtles (the water, or riding
|
||
off the edge, sends you back), train tracks that flash red and
|
||
ring before a train, and grass with bushes and rocks in the way. A
|
||
car, a train or the water sends you back down to the last grass
|
||
row, never out. Space shoves the hopper in front of you a cell, so
|
||
a well-timed shove puts a rival in the traffic (they will do the
|
||
same to you). First to the top wins the heat and moves on through
|
||
nine zones, from <strong>Side Street</strong> to
|
||
<strong>Rush Hour</strong>, then Rush Hours that keep getting
|
||
quicker; second or third costs one of three lives and runs the
|
||
heat again, though in the first two zones second place still gets
|
||
you through. The zones bring logs, trains, diving turtles, trucks
|
||
and lanes that speed up, a night lit only by headlights, rivers
|
||
that turn round and icy lanes that slide you a cell on, and rivals
|
||
(the Hopper, who waits for a clear gap, the Daredevil, who takes
|
||
the tight ones, the Bruiser, who shoves, and the Tagalong, who
|
||
follows you up and shoves near the top). Pickups sit on the
|
||
grass: Spring (your next hop goes two cells), Shield (the next hit
|
||
does not send you back), Coin and Horn (the nearest road stops for
|
||
a moment). Points: 1 for each row higher than you had got in the
|
||
heat, 50 times the zone for a heat won, times your streak of clean
|
||
wins (a win where you were never sent back adds one to it, up to
|
||
x3; any other win, a second place or a lost heat ends it), plus 3
|
||
for each row the runner-up still had to go, 15 for a rival you
|
||
shoved that is sent back, 5 for a close call (a car or a train
|
||
through the cell you just left within a tenth of a second), and 10
|
||
for a coin.
|
||
</li>
|
||
<li>
|
||
<strong>Bounce Road</strong>: race Planny's springy toy car up a
|
||
road laid across a giant's house and yard, with rival toy cars on
|
||
it that mean to stop you. Bump one sideways off the road, and press
|
||
<kbd>Space</kbd> to jump (you need a little speed, and a faster jump
|
||
goes further). Land on a rival to flatten it and bounce up again,
|
||
and land on another before your wheels touch the road to build the
|
||
bounce chain, up to x8. Every stunt in quick succession (a crush, a
|
||
rival bumped off, a hole, train, ball or barrier jumped, a ramp's
|
||
big air, a close shave, a boost strip) steps the combo: every
|
||
third in a row multiplies your points once more, up to x4, until
|
||
you go 2.6 seconds without one. In the air, a ring in your
|
||
highlight shows where you will come down, and a red one where a
|
||
rival will. Water or a hole under your wheels, a crash (a
|
||
flowerbed or a toy block nose first, a train, a truck's back), or
|
||
anything landing on you costs one of three lives. Ten stages, each
|
||
bringing something new:
|
||
<strong>Chalk Lane</strong> (cracks, boost strips and cones),
|
||
<strong>Hose Creek</strong> (broken bridges, a sprinkler, the Frog,
|
||
who hops), <strong>Kitchen Floor</strong> (oil slicks, a rolling
|
||
orange, the Sneak, who drops cones), <strong>Flowerbed Fork</strong>
|
||
(the road splits, ramps, falling flowerpots, the Nudge, who swipes
|
||
at you), <strong>Sandbox Run</strong> (road that crumbles behind
|
||
you, the Hauler too heavy to bump, the Bruiser, who shoves),
|
||
<strong>Toy Room</strong> (a toy train crossing, toy-block
|
||
chicanes, the Racer to catch), <strong>Garden Pond</strong>
|
||
(swaying bridges, drawbridges, the Cop, who chases you and pushes
|
||
you toward the edge), <strong>Rooftop Gutter</strong> (gusts of
|
||
wind), <strong>Night Lights</strong> (everything, in the dark) and
|
||
<strong>Monster Mash</strong>, where the Monster truck hops at
|
||
you: land on its roof five times to beat it. Then the road goes
|
||
round again from Kitchen Floor, quicker and meaner. Every hole has
|
||
a warning sign and a straight run-up, and can be cleared at 80% of
|
||
the top speed. Power-ups lie on the road from Hose Creek: Spring
|
||
(your next jump goes further), Bubble (one free save), Nitro (a
|
||
burst of speed) and Mega wheels (bigger and heavier: flatten
|
||
whatever you touch). Points: 1 for every 10 units of new road (a car
|
||
is 7 long); each rival's own points when you land on it (100 to
|
||
300, the Racer most), times the chain; 60 for a rival that leaves
|
||
the road within a second and a half of your bump; 25 a hole and 40
|
||
a train, ball or barrier jumped; 60 for a ramp's big air; 30 for a
|
||
close shave; 10 a star and a boost strip, all times the combo;
|
||
250 a stomp on the Monster and 2,000 for beating it, with a life
|
||
back. At each stage line: 100 times the stage, 15 for every second
|
||
under the stage's par, and, with no life lost, 250 more and a life
|
||
back, up to five.
|
||
</li>
|
||
<li>
|
||
<strong>Ghoul Rush</strong>: blast Planny through a haunted
|
||
mansion, a room at a time, seen side on with the view scrolling
|
||
along with him. His flashlight blaster fires the way he faces, and
|
||
a bolt tilts a little toward a monster ahead near his height. It
|
||
heats up as it fires: after about three seconds of shooting it
|
||
slows, down to one bolt a second, a <strong>HEAT</strong> pill shows
|
||
how hot it is, and letting go of fire cools it. Rapid fire never
|
||
heats it. Grab
|
||
each room's key, then reach its door; a boss guards every fourth
|
||
room, and beating it opens the door. <strong>Zombies</strong>
|
||
shamble out of doors in the wall and lurch when you are close (two
|
||
bolts), <strong>crawlers</strong> come up through loose boards,
|
||
<strong>bats</strong> swoop down to your height in passes,
|
||
<strong>ghosts</strong> drift through walls and can only be hit,
|
||
and only hurt, while they are solid, and
|
||
<strong>skeletons</strong> throw bones you can shoot down. A bolt
|
||
to the head or a stomp from above doubles a kill, and kills in
|
||
quick succession build a chain that multiplies them, up to x8, but
|
||
it runs out in a second and a half. The rooms bring pits, shelves to jump up
|
||
through (down drops through one), boards that crumble and
|
||
chandeliers that come down on whatever is under them. Eight rooms,
|
||
the <strong>Foyer</strong>, <strong>Portrait Gallery</strong>,
|
||
<strong>Library</strong>, <strong>Ballroom</strong> (the
|
||
<strong>Great Gourd</strong>, which hops to where you stood:
|
||
watch its shadow), <strong>Kitchen</strong>,
|
||
<strong>Conservatory</strong>, <strong>Attic</strong> and
|
||
<strong>Crypt</strong> (<strong>Old Rattlebones</strong>, whose
|
||
shockwaves you jump), then round again, quicker and tougher.
|
||
Power-ups: Spread shot, Rapid fire, a Garlic shield (shrugs off one
|
||
hit) and a 1UP. A hit or a fall costs one of seven lives and puts
|
||
you back at the room's start (in a boss fight, the arena's), safe
|
||
for a moment. Points: 100 a zombie, 75 a crawler, 50 a bat, 150 a
|
||
ghost, 200 a skeleton, 40 a gourdling, all times the chain, 25 a bone shot down, 10
|
||
a candy, 50 a power-up; through a door, 300 times the room number
|
||
plus the time bonus left (1500, dropping 30 a second; once it runs
|
||
out, zombies shamble in from the edges) and 500 more with no life
|
||
lost; and 2000 for the Gourd and 2500 for Rattlebones, times the
|
||
lap, with a life back.
|
||
</li>
|
||
</ul>
|
||
<h4>It never hides your turn</h4>
|
||
<ul>
|
||
<li>
|
||
A new question, a sign-off or a finish pauses the game at once, and
|
||
a banner above the board says Plan2Code needs you.
|
||
<strong>Go to it</strong> closes the window on that question.
|
||
</li>
|
||
<li class="for-browser">
|
||
Switching to another tab, or clicking outside the page, also pauses it.
|
||
</li>
|
||
<li class="for-app">
|
||
Hiding the window, or clicking outside the page (the app's own bar
|
||
too), also pauses it.
|
||
</li>
|
||
<li>
|
||
Nothing resumes by itself. Any game key plays on, and so does a
|
||
click on the Mini golf or Stack Deploy board. Playing on puts the banner away until
|
||
the next new question.
|
||
</li>
|
||
<li>
|
||
Starting a round, and playing on after a pause, counts down 3, 2, 1
|
||
first, so the game never moves before you are ready.
|
||
</li>
|
||
</ul>
|
||
<h4>Keys</h4>
|
||
<ul>
|
||
<li>
|
||
Snake: the arrow keys, or <kbd>W</kbd> <kbd>A</kbd> <kbd>S</kbd>
|
||
<kbd>D</kbd>, steer.
|
||
</li>
|
||
<li>
|
||
Mini golf: hold left or right to turn the aim (faster the longer
|
||
you hold), press <kbd>Space</kbd> once to start the power meter and
|
||
again to set the power, and hold <kbd>Space</kbd> while the ball
|
||
rolls to speed it up.
|
||
</li>
|
||
<li>
|
||
Light Trails: the arrow keys, or <kbd>W</kbd> <kbd>A</kbd>
|
||
<kbd>S</kbd> <kbd>D</kbd>, steer, and <kbd>Space</kbd> spends a
|
||
boost charge for a burst of speed (two a heat, up to three).
|
||
</li>
|
||
<li>
|
||
Bug Hunt: the arrow keys, or <kbd>W</kbd> <kbd>A</kbd> <kbd>S</kbd>
|
||
<kbd>D</kbd>, fly the ship, and hold <kbd>Space</kbd> to fire.
|
||
</li>
|
||
<li>
|
||
Sunset Drive: hold up (or <kbd>W</kbd>) to drive and down (or
|
||
<kbd>S</kbd>) to brake, left and right steer, and <kbd>Space</kbd>
|
||
burns a nitro can for a burst of speed (two to start, up to three).
|
||
</li>
|
||
<li>
|
||
Stack Deploy: <kbd>Space</kbd>, up (or <kbd>W</kbd>) or a click
|
||
on the board drops the block.
|
||
</li>
|
||
<li>
|
||
Bumper Ring: hold the arrow keys, or <kbd>W</kbd> <kbd>A</kbd>
|
||
<kbd>S</kbd> <kbd>D</kbd>, to push your car that way (two at once
|
||
push on the diagonal), and <kbd>Space</kbd> dashes (two charges a
|
||
heat, one back every few seconds, up to three).
|
||
</li>
|
||
<li>
|
||
Rapids Run: left and right (or <kbd>A</kbd> and <kbd>D</kbd>)
|
||
steer, hold up (or <kbd>W</kbd>) to speed up and down (or
|
||
<kbd>S</kbd>) to slow down, and hold <kbd>Space</kbd> to fire.
|
||
</li>
|
||
<li>
|
||
Hot Potato: hold the arrow keys, or <kbd>W</kbd> <kbd>A</kbd>
|
||
<kbd>S</kbd> <kbd>D</kbd>, to run that way (two at once run on the
|
||
diagonal), and <kbd>Space</kbd> dashes: a lunge for a tag while you
|
||
hold the bomb, a dodge while you do not (two charges, one back
|
||
every 4 seconds).
|
||
</li>
|
||
<li>
|
||
Crossing Rush: the arrow keys, or <kbd>W</kbd> <kbd>A</kbd>
|
||
<kbd>S</kbd> <kbd>D</kbd>, hop one cell, one hop a press (a press
|
||
during a hop waits its turn), and <kbd>Space</kbd> shoves the
|
||
hopper in front of you a cell the way you face (once every 3
|
||
seconds).
|
||
</li>
|
||
<li>
|
||
Bounce Road: hold up (or <kbd>W</kbd>) to drive and down (or
|
||
<kbd>S</kbd>) to brake, left and right steer (only a little in the
|
||
air), and <kbd>Space</kbd> jumps, once a press. A ramp launches you
|
||
on its own.
|
||
</li>
|
||
<li>
|
||
Ghoul Rush: hold left and right (or <kbd>A</kbd> <kbd>D</kbd>) to
|
||
run, up (or <kbd>W</kbd>) jumps, once a press (let go early for a
|
||
short hop), down (or <kbd>S</kbd>) drops through a shelf, and hold
|
||
<kbd>Space</kbd> to fire (in bursts: the blaster slows as it heats
|
||
and cools once you let go).
|
||
</li>
|
||
<li><kbd>Space</kbd> starts a round, and plays again after a pause.</li>
|
||
<li><kbd>P</kbd> pauses and plays.</li>
|
||
<li><kbd>R</kbd> starts the round over, from the countdown.</li>
|
||
<li>
|
||
<kbd>F</kbd>, or <strong>Full screen</strong> under the board, gives
|
||
the game the whole screen: the board as big as the screen allows,
|
||
black bars where its shape leaves room, and a panel over it for the
|
||
game's name, your score and best, the game's <strong>Music</strong> slider, and <strong>Exit full screen</strong>.
|
||
The panel sits in a black bar when one is wide enough; otherwise it
|
||
floats in the top corner and, while you play and the pointer is
|
||
still, shrinks to your score in the bottom corner. The pointer hides while you are not
|
||
moving it. <kbd>F</kbd> or <kbd>Esc</kbd>
|
||
puts it back. A question, a sign-off or a finish puts it back too,
|
||
as it pauses the game.
|
||
<span data-app="The app's window goes full screen with it.">It uses the browser's own full screen where the browser allows one.</span>
|
||
</li>
|
||
<li><kbd>Enter</kbd> does both: it starts a round, pauses it and plays on.</li>
|
||
<li><kbd>Esc</kbd> closes the window, with the game paused where it was (in full screen, the first <kbd>Esc</kbd> leaves full screen).</li>
|
||
</ul>
|
||
<p>Activities need a keyboard: on a touch-only screen the window says so instead of showing the board.</p>
|
||
<h4>Best scores</h4>
|
||
<p>
|
||
The window's title shows the best for the game on screen, and the
|
||
line under the board shows it beside your score, and each card shows
|
||
its game's. For Snake, Light Trails, Bug Hunt, Sunset Drive, Stack Deploy, Bumper Ring, Rapids Run, Hot Potato, Crossing Rush, Bounce Road and Ghoul Rush the best is
|
||
your highest score; for Mini golf it is your lowest full round of eighteen holes,
|
||
kept for each course on its own, and a round left halfway never counts. <strong>Reset best
|
||
scores</strong>, at the bottom of the window, clears them all after a
|
||
second click to confirm.
|
||
</p>
|
||
<h4>Hiding it</h4>
|
||
<p>
|
||
Don't want the die? Untick <strong>Show Activities</strong> in User
|
||
Preferences (the gear) and it is gone from every screen. To play
|
||
without sound, untick <strong>Play game sounds</strong> beside it.
|
||
A game with music (turn on <strong>Play game music</strong> there) has
|
||
its own <strong>Music</strong> slider under the board for how loud it plays.
|
||
</p>
|
||
<p>
|
||
Best scores, Snake's surprises found, Light Trails' furthest arena, Bug Hunt's finds, Sunset Drive's roads found, Stack Deploy's highest floor, Bumper Ring's furthest arena, Rapids Run's furthest dam, Hot Potato's furthest venue, Crossing Rush's furthest zone, Bounce Road's furthest stage, Ghoul Rush's furthest room, each game's music volume, your last pick and that switch are saved privately on
|
||
this machine, with your other preferences, and never sent anywhere.
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 17: Stopping and finishing -->
|
||
<section class="help-panel" data-tab="finishing">
|
||
<h3>Stopping and finishing</h3>
|
||
<p class="help-lead">
|
||
Every session ends with a screen that says what happened and what to
|
||
run next, whether it finished on its own or you stopped it.
|
||
</p>
|
||
<h4>Stopping early</h4>
|
||
<p id="help-finishing-stop-text">
|
||
<strong>Stop session</strong>, at the top, ends the session and saves
|
||
your place. Any answers you have ready go with it, and Plan2Code
|
||
gives you a command to pick up where you left off, in a new
|
||
conversation.
|
||
</p>
|
||
<ul>
|
||
<li>
|
||
It only works when it is your turn. While Plan2Code is busy with
|
||
what you last sent, the button waits, so a stop never lands half way
|
||
through writing your answers down.
|
||
</li>
|
||
<li>
|
||
It asks first, and offers two ways to stop.
|
||
<strong>Stop with a handoff</strong> saves your place and writes a
|
||
note the dashboard can offer to pick up later;
|
||
<strong>Just stop and save</strong> saves what the step keeps on
|
||
disk and gives you a command to resume, without the conversation;
|
||
<strong>Keep going</strong> backs out.
|
||
</li>
|
||
<li>
|
||
A handoff lands in <code>~/.plan2code/handoffs/</code> and shows on
|
||
the dashboard, next to your specs, until you use or delete it.
|
||
</li>
|
||
<li>
|
||
At points where nothing is saved yet, such as early in a plan, the
|
||
dialog says what would be lost and the button reads <strong>Stop
|
||
anyway</strong> instead.
|
||
</li>
|
||
</ul>
|
||
<h4>Back to the dashboard, mid-way</h4>
|
||
<p>
|
||
The <strong>triangle</strong> left of Stop session leaves the step you
|
||
are in for the dashboard, in this same session. Your place is saved
|
||
the way a stop saves it, with any answers you have ready going along,
|
||
and the menu appears here instead of a finish screen. From there,
|
||
pick the same step again to carry on, or pick another one. It follows
|
||
Stop's rules: it only works on your turn, it asks first, and it
|
||
shows the same warning where nothing is saved yet.
|
||
</p>
|
||
<h4>The three endings</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>A next step.</strong> What was done, and under
|
||
<strong>Next step</strong> the exact command to run next, with a
|
||
<strong>Copy</strong> button: the next phase, Finalize, or a commit.
|
||
</li>
|
||
<li>
|
||
<strong>All done.</strong> "All done, nothing left to run." There is
|
||
nothing to copy but the command that opens the dashboard.
|
||
</li>
|
||
<li>
|
||
<strong>Paused.</strong> You pressed <strong>Stop session</strong>.
|
||
The screen names what was saved and gives the command that picks it
|
||
up later. Nothing else is offered.
|
||
</li>
|
||
</ul>
|
||
<p>
|
||
Paused means there is more to do and your place is kept. Finished means
|
||
this step is over.
|
||
</p>
|
||
<h4>Running the next command</h4>
|
||
<p id="help-finishing-command-text">
|
||
Press <strong>Copy</strong>, then paste the command into the terminal
|
||
where you started Plan2Code, in a new conversation. When the next
|
||
step is another Plan2Code step, the command already ends with
|
||
<code>--web</code>, which asks Plan2Code to open this page again, so
|
||
you carry on here rather than in the terminal.
|
||
</p>
|
||
<h4>Back to the dashboard</h4>
|
||
<p id="help-finishing-dashboard-text">
|
||
A finished screen (never a paused one) has a <strong>Back to the
|
||
dashboard</strong> button. It turns this page back into the cards, in
|
||
the same conversation, so the next step starts right here.
|
||
Plan2Code listens for it for as long as the session is open.
|
||
Once the session has closed, the button becomes the
|
||
<code>/plan2code</code> command to run in a new conversation
|
||
instead.
|
||
After a long step, a new conversation is the better choice anyway: it
|
||
starts with a clean slate.
|
||
</p>
|
||
<h4>Update CHANGELOG first</h4>
|
||
<p>
|
||
A finished quick task or finalize that ends on a commit can also show
|
||
<strong>Update CHANGELOG first</strong> beside <strong>Commit it
|
||
now</strong>. It opens Changelog right here; when Changelog asks
|
||
"Commit this now?" and you say yes, it carries on to Git.
|
||
</p>
|
||
<h4>Continue here</h4>
|
||
<p id="help-finishing-continue-text">
|
||
When the next step is another Plan2Code step, the Next step block also
|
||
has a <strong>Continue here</strong> button. It starts that step in
|
||
this same conversation, the way a dashboard card would, with this page
|
||
turning into the new step. It goes away once the session meter is red,
|
||
because a long conversation is the reason to start a fresh one: copy
|
||
the command above into a new conversation instead.
|
||
</p>
|
||
</section>
|
||
|
||
<!-- Tab 18: Keyboard and preferences -->
|
||
<section class="help-panel" data-tab="prefs">
|
||
<h3>Keyboard and preferences</h3>
|
||
<p class="help-lead">
|
||
Everything on the page works from the keyboard, and the gear button
|
||
lets you make it look and sound the way you like.
|
||
</p>
|
||
<h4>Keyboard shortcuts</h4>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th>Keys</th>
|
||
<th>What they do</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td><kbd>Ctrl</kbd>+<kbd>Enter</kbd> (<kbd>⌘</kbd>+<kbd>Enter</kbd> on a Mac)</td>
|
||
<td>Send your answers (not while this Help is open). In the Ask box, send the question.</td>
|
||
</tr>
|
||
<tr>
|
||
<td><kbd>Enter</kbd> in the Ask box</td>
|
||
<td>Start a new line.</td>
|
||
</tr>
|
||
<tr>
|
||
<td><kbd>Esc</kbd></td>
|
||
<td>Close a dialog, this Help included. On the dashboard, back out of a card you picked.</td>
|
||
</tr>
|
||
<tr>
|
||
<td><kbd>Tab</kbd> / <kbd>Space</kbd></td>
|
||
<td>Move between options, and pick one.</td>
|
||
</tr>
|
||
<tr>
|
||
<td>Arrow keys, <kbd>Home</kbd>, <kbd>End</kbd> in Help</td>
|
||
<td>Move between topics.</td>
|
||
</tr>
|
||
<tr>
|
||
<td>Arrow keys, <kbd>Home</kbd>, <kbd>End</kbd> in User Preferences</td>
|
||
<td>Move between its tabs: up and down in the side list, left and right in the strip on a narrow window.</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>
|
||
Every control is a real button, option or checkbox, so screen readers
|
||
and keyboard-only use work too.
|
||
</p>
|
||
<h4>Your preferences</h4>
|
||
<p>
|
||
The gear button at the top, beside <strong>?</strong>, opens
|
||
<strong>User Preferences</strong>, always on its first tab. Its four
|
||
tabs sit in a side list, or in a strip along the top on a narrow
|
||
window:
|
||
</p>
|
||
<ul>
|
||
<li>
|
||
<strong>Appearance</strong>: Theme, Card width, Highlight color and
|
||
Role.
|
||
</li>
|
||
<li>
|
||
<strong>Agents & models</strong>: the agents you can start and
|
||
the models each one offers.
|
||
</li>
|
||
<li>
|
||
<strong>System</strong>: Cleanup<span class="for-app">, and Desktop
|
||
app</span>.
|
||
</li>
|
||
<li>
|
||
<strong>Sounds & activities</strong>: Sounds and Activities.
|
||
</li>
|
||
</ul>
|
||
<p>
|
||
On Appearance and Sounds & activities, each change is saved the
|
||
moment you make it, and a small <strong>Saved</strong> mark shows
|
||
beside it. <strong>Close</strong> (or <kbd>Esc</kbd>) shuts the dialog.
|
||
</p>
|
||
<h4>Appearance</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Theme</strong>: <strong>Follow my system</strong> (the
|
||
default), <strong>Light</strong> or <strong>Dark</strong>.
|
||
</li>
|
||
<li>
|
||
<strong>Card width</strong>: how wide the questions, documents and dashboard are.
|
||
<strong>Narrow</strong> (<span data-fact="cardWidths">720</span> px),
|
||
<strong>Comfortable</strong>
|
||
(<span data-fact="cardWidths">880</span> px, the default),
|
||
<strong>Wide</strong> (<span data-fact="cardWidths">1,080</span> px) or
|
||
<strong>Ultra wide</strong> (<span data-fact="cardWidths">1,440</span> px),
|
||
for an ultrawide monitor.
|
||
On a smaller window they fit the space there is.
|
||
</li>
|
||
<li>
|
||
<strong>Highlight color</strong>: one of
|
||
<span data-fact="accentCount">38</span>, ocean blue to begin with. It marks
|
||
what is yours to do, and Planny's star uses it while he works.
|
||
</li>
|
||
<li>
|
||
<strong>Role</strong>: Engineer, Product lead / PM, Architect / tech
|
||
lead, Designer (UX), QA / test engineer or Engineering manager, or
|
||
<strong>Not set / none of these</strong> (the default). It puts the
|
||
starter templates and Ask starter questions most useful to you first,
|
||
and never changes the questions a skill asks.
|
||
</li>
|
||
</ul>
|
||
<h4>Agents & models</h4>
|
||
<p>
|
||
Most people never need to change this: Plan2Code finds the agents
|
||
installed on this machine and ships an up-to-date model list with
|
||
every release. The tab opens on a table of every agent, with its
|
||
models and whether it was found on this machine. <strong>Edit</strong>
|
||
opens one agent's form, and <strong>Add agent</strong> a blank one.
|
||
</p>
|
||
<ul>
|
||
<li>
|
||
<strong>Models</strong>: each built-in agent (Claude, Devin, Codex)
|
||
shows the models that come with Plan2Code, which every update
|
||
refreshes, and below them <strong>Models you added</strong>: a model
|
||
id and the name shown in the menu. Models you added stay through
|
||
updates. Restart <code>plan2code</code> to see a change in its model
|
||
menu.
|
||
</li>
|
||
<li>
|
||
<strong>Agents</strong>: an agent you add is another command-line
|
||
tool the <code>plan2code</code> launcher can start, beside the
|
||
built-in ones. Give it a name, the command to run and, if you like,
|
||
a start prompt and models. <strong>Test</strong> checks the command
|
||
is on your PATH. The <strong>Command-line arguments</strong> fold
|
||
holds the arguments it is started with, the ones that skip its
|
||
permission prompts, and the ones that pick a model, where
|
||
<code>{prompt}</code> and <code>{model}</code> are filled in for you.
|
||
Added agents are saved in <code>~/.plan2code/agents.json</code>;
|
||
<strong>Delete agent</strong> removes one.
|
||
</li>
|
||
</ul>
|
||
<p>
|
||
Nothing here is saved as you type. Each form has its own
|
||
<strong>Save</strong> and <strong>Discard</strong>, and an
|
||
<strong>Unsaved</strong> badge while it holds a change. Leaving a form
|
||
with an unsaved change (another tab, Back to summary, Close) asks
|
||
first: save it, discard it, or keep editing.
|
||
</p>
|
||
<h4>System</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Cleanup</strong>: <strong>Find files to clean up</strong>
|
||
lists what Plan2Code doesn't need in your
|
||
<code>~/.plan2code</code> folder: sessions nobody has opened for
|
||
30 days, and files or folders that ended up there by mistake. It
|
||
also lists this project's <code>specs--completed/</code> folders
|
||
nobody has touched for 30 days; deleting one is permanent, since
|
||
that folder is usually gitignored and git can't restore it. It
|
||
shows each one with its size, and <strong>Delete these</strong>
|
||
removes exactly that list. Your preferences, saved folders, models,
|
||
the launcher and the session you are in always stay, and the
|
||
<code>handoffs/</code> folder is Plan2Code's own, so it is never
|
||
offered for removal.
|
||
</li>
|
||
<li class="for-app">
|
||
<strong>Desktop app</strong>: shown only in the desktop app.
|
||
<strong>Show on the taskbar when Plan2Code needs me</strong> puts a
|
||
green dot on the taskbar button on Windows when it is your move and
|
||
a red one when it needs you, or a red badge on the dock icon on
|
||
macOS when it needs you.
|
||
</li>
|
||
<li class="for-browser">
|
||
<strong>Desktop app</strong>: shown only inside the desktop app,
|
||
where a switch puts a dot on the taskbar button when Plan2Code
|
||
needs you.
|
||
</li>
|
||
</ul>
|
||
<h4>Sounds & activities</h4>
|
||
<ul>
|
||
<li>
|
||
<strong>Sounds</strong>: <strong>Play sounds</strong> switches every
|
||
sound on or off at once. Below it, each moment has its own box:
|
||
Planny snoring and waking up, starting a skill from the dashboard,
|
||
the session opening, a started skill being ready, the session
|
||
ending, new questions for you, a reply on the Ask tab and a new tab
|
||
joining the strip. Keep only the ones you want; ticking a box plays
|
||
its sound.
|
||
</li>
|
||
<li>
|
||
<strong>Activities</strong>: <strong>Show Activities</strong> puts
|
||
the die in the top bar, which opens small games to play while you
|
||
wait. Untick it to hide the die on every screen.
|
||
<strong>Play game sounds</strong> turns the games' sounds on or
|
||
off, leaving every other sound as it is; with Play sounds off, the
|
||
games are silent too.
|
||
</li>
|
||
</ul>
|
||
<p>
|
||
<strong>Back to default</strong> resets only the tab on screen:
|
||
Appearance's four settings (Role goes back to Not set), or every sound
|
||
and the two Activities switches. Agents & models and System have
|
||
nothing to reset, so it is not shown there. Your Activities best
|
||
scores stay: only <strong>Reset best scores</strong>, in the
|
||
Activities window, clears them.
|
||
</p>
|
||
<p>
|
||
Your choices are remembered on this machine and carry over to every
|
||
session you open here.
|
||
</p>
|
||
<h4>Less motion</h4>
|
||
<p>
|
||
The page has no motion switch of its own. It follows your computer's
|
||
"reduce motion" setting, and with it on, the animations stay still.
|
||
</p>
|
||
<ul>
|
||
<li>
|
||
<strong>Windows:</strong> Settings → Accessibility → Visual effects →
|
||
Animation effects (off).
|
||
</li>
|
||
<li>
|
||
<strong>macOS:</strong> System Settings → Accessibility → Display →
|
||
Reduce motion (on).
|
||
</li>
|
||
</ul>
|
||
</section>
|
||
|
||
<!-- Tab 19: Privacy and where things are saved -->
|
||
<section class="help-panel" data-tab="privacy">
|
||
<h3>Privacy and where things are saved</h3>
|
||
<p class="help-lead">
|
||
Nothing on this page leaves your machine, and nothing it keeps lives in
|
||
your project.
|
||
</p>
|
||
<h4>On this machine only</h4>
|
||
<p class="for-browser">
|
||
The page is served on <strong>127.0.0.1</strong>, which only this
|
||
computer can reach. It is not visible on your network, so sharing the
|
||
link with someone on another machine will not work, by design. To work
|
||
through a session together, share your screen.
|
||
</p>
|
||
<p class="for-app">
|
||
The page is served on <strong>127.0.0.1</strong>, which only this
|
||
computer can reach. It is not visible on your network, and the app
|
||
shows it in its own window, so there is no link to share. To work
|
||
through a session together, share your screen.
|
||
</p>
|
||
<h4>The link is a key</h4>
|
||
<p class="for-browser">
|
||
The link carries a long private code. The first time it is opened, the
|
||
page swaps that code for a cookie in this browser and takes it out of
|
||
the address bar, so it does not linger in your history or show in a
|
||
screenshot. Treat the link like a password all the same: anyone on
|
||
this machine who has it can open the session.
|
||
</p>
|
||
<p class="for-app">
|
||
The page's address carries a long private code. The app opens it for
|
||
you, and the page swaps that code for a cookie in the app's own web
|
||
view, so it never shows in the window, and the agent leaves it out of
|
||
the terminal panel. Anyone on this machine who has the address can
|
||
still open the session, so treat it like a password if you ever see it.
|
||
</p>
|
||
<h4>What is kept, and where</h4>
|
||
<p>
|
||
Everything lives in your home folder, under
|
||
<code>~/.plan2code/console/</code> unless noted:
|
||
</p>
|
||
<ul>
|
||
<li>
|
||
each session's questions, your drafts and your answers, in
|
||
<code>sessions/<id>/</code>;
|
||
</li>
|
||
<li>
|
||
files you attached to notes and questions, in that session's
|
||
<code>uploads/</code> (a note attachment cited in a spec file is also
|
||
copied into the spec's <code>attachments/</code> folder; see "Notes
|
||
and attachments");
|
||
</li>
|
||
<li>
|
||
your role, theme, colors, card width and sounds, the Show
|
||
Activities switch, the last activity you picked and your best
|
||
scores, in <code>looks.json</code>;
|
||
</li>
|
||
<li>
|
||
your Subagents switch for each project and skill, in
|
||
<code>subagents.json</code>;
|
||
</li>
|
||
<li>
|
||
handoffs you save when you stop or with the Handoff skill, in
|
||
<code>~/.plan2code/handoffs/</code>, one <code>.md</code> and one
|
||
<code>.json</code> each, removed after the same
|
||
<span data-fact="cleanupDays">30</span> days.
|
||
</li>
|
||
</ul>
|
||
<p>
|
||
A session nobody has touched for
|
||
<span data-fact="cleanupDays">30</span> days is removed, uploads and
|
||
all, the next time a session opens. Your preferences are never removed.
|
||
</p>
|
||
<p>
|
||
Folders you add to your workspace last for one console session. The
|
||
page keeps only each folder's path, name and description, and never
|
||
looks inside.
|
||
</p>
|
||
<h4>Your project is the real record</h4>
|
||
<p>
|
||
What Plan2Code decides and builds is written to <code>specs/</code>
|
||
and your code, in your project. This page and the terminal are two ways
|
||
of working on those files; neither owns them. Losing a session loses
|
||
nothing that matters, and you can switch between the page and the
|
||
terminal at any time.
|
||
</p>
|
||
</section>
|
||
</template>
|
||
|
||
<dialog class="modal looks prefs" id="looks-modal" aria-labelledby="looks-title">
|
||
<h2 id="looks-title">User Preferences</h2>
|
||
<div class="prefs-body">
|
||
<div class="prefs-layout">
|
||
<div id="prefs-tabs" class="prefs-tabs" role="tablist" aria-orientation="vertical" aria-label="Preference groups"></div>
|
||
<div id="prefs-panels" class="prefs-panels">
|
||
<section class="prefs-panel" data-tab="appearance">
|
||
<p class="modal-blurb">
|
||
Kept on this machine, for every session you open here. Role only puts the
|
||
starter templates most useful to you first; it never changes the questions
|
||
you're asked.
|
||
</p>
|
||
<fieldset data-section="theme" class="modal-ranges looks-row">
|
||
<legend>Theme</legend>
|
||
<label><input type="radio" name="looks-theme" value="system" checked /> <span>Follow my system</span></label>
|
||
<label><input type="radio" name="looks-theme" value="light" /> <span>Light</span></label>
|
||
<label><input type="radio" name="looks-theme" value="dark" /> <span>Dark</span></label>
|
||
</fieldset>
|
||
<fieldset data-section="width" class="modal-ranges looks-row four">
|
||
<legend>Card width</legend>
|
||
<label><input type="radio" name="looks-width" value="narrow" /> <span>Narrow</span></label>
|
||
<label><input type="radio" name="looks-width" value="comfortable" checked /> <span>Comfortable</span></label>
|
||
<label><input type="radio" name="looks-width" value="wide" /> <span>Wide</span></label>
|
||
<label><input type="radio" name="looks-width" value="ultrawide" /> <span>Ultra wide</span></label>
|
||
<p class="help">How wide the questions, documents and dashboard are. On a smaller window they fit the space there is.</p>
|
||
</fieldset>
|
||
<fieldset data-section="accent" class="modal-ranges">
|
||
<legend>Highlight color</legend>
|
||
<div class="swatches" id="looks-swatches"></div>
|
||
<p class="help">
|
||
Your highlight color marks what is yours to do, and Planny's
|
||
star uses it while he works. Green, amber and red also mean done,
|
||
staged and careful, so a highlight close to one of those can blur
|
||
which is which.
|
||
</p>
|
||
</fieldset>
|
||
<fieldset data-section="role" class="modal-ranges looks-row">
|
||
<legend>Role</legend>
|
||
<select id="looks-role" aria-label="Role"></select>
|
||
<p class="help">Only puts the starter templates most useful to you first.</p>
|
||
</fieldset>
|
||
</section>
|
||
<section class="prefs-panel" data-tab="agents">
|
||
<div class="prefs-agents" data-section="agents">
|
||
<p class="help" id="agents-intro">Most people never need to change this. Plan2Code finds the agents installed on this machine and ships an up-to-date model list with every release.</p>
|
||
<table class="prefs-agents-table" id="agents-table">
|
||
<thead>
|
||
<tr><th scope="col">Agent</th><th scope="col" class="prefs-agents-models">Models</th><th scope="col">On this machine</th><th scope="col"></th></tr>
|
||
</thead>
|
||
<tbody></tbody>
|
||
</table>
|
||
<button type="button" class="btn small" id="agents-add">Add agent</button>
|
||
<span class="help" id="agents-status" role="status"></span>
|
||
<div id="agents-form" class="prefs-agents-form" hidden></div>
|
||
</div>
|
||
</section>
|
||
<section class="prefs-panel" data-tab="system">
|
||
<fieldset data-section="cleanup" class="modal-ranges">
|
||
<legend>Cleanup</legend>
|
||
<p class="help">Finds what Plan2Code doesn't need in your <code>~/.plan2code</code> folder: sessions nobody has opened for 30 days, and files or folders that ended up there by mistake. It also lists this project's <code>specs--completed/</code> folders nobody has touched for 30 days; deleting one is permanent, since that folder is usually gitignored and git can't restore it. You see the list before anything is deleted. Your preferences, saved folders, models, the launcher and this session always stay.</p>
|
||
<div class="cleanup-list" id="cleanup-list" aria-label="What would be deleted"></div>
|
||
<div class="models-actions">
|
||
<button type="button" class="btn small" id="cleanup-scan">Find files to clean up</button>
|
||
<button type="button" class="btn small danger" id="cleanup-delete" hidden>Delete these</button>
|
||
<span class="help" id="cleanup-status" role="status"></span>
|
||
</div>
|
||
</fieldset>
|
||
<!-- Only inside the desktop app (framed()): the app saves the switch in its own app.json. -->
|
||
<fieldset data-section="desktop" class="modal-ranges looks-desktop" id="looks-desktop" hidden>
|
||
<legend>Desktop app</legend>
|
||
<label><input type="checkbox" id="looks-taskbar" checked /> <span>Show on the taskbar when Plan2Code needs me</span></label>
|
||
<p class="help">
|
||
Windows: a colored dot on the taskbar button (green on your move, red when it
|
||
needs you) and a short burst of flashes. macOS: a red badge on the dock icon when it needs
|
||
you, and a bounce. Linux: depends on your desktop.
|
||
</p>
|
||
</fieldset>
|
||
</section>
|
||
<section class="prefs-panel" data-tab="sounds">
|
||
<fieldset data-section="sounds" class="modal-ranges looks-sounds">
|
||
<legend>Sounds</legend>
|
||
<label><input type="checkbox" id="looks-sound" checked /> <span>Play sounds</span></label>
|
||
<div class="looks-row looks-sound-events" id="looks-sound-events">
|
||
<label><input type="checkbox" data-sound="snore" checked /> <span>Planny snoring</span></label>
|
||
<label><input type="checkbox" data-sound="bootup" checked /> <span>Planny waking up</span></label>
|
||
<label><input type="checkbox" data-sound="startSkill" checked /> <span>Starting a skill</span></label>
|
||
<label><input type="checkbox" data-sound="sessionStart" checked /> <span>Session opens</span></label>
|
||
<label><input type="checkbox" data-sound="skillReady" checked /> <span>Skill is ready</span></label>
|
||
<label><input type="checkbox" data-sound="sessionEnd" checked /> <span>Session ends</span></label>
|
||
<label><input type="checkbox" data-sound="question" checked /> <span>New questions for you</span></label>
|
||
<label><input type="checkbox" data-sound="chatReply" checked /> <span>Reply on the Ask tab</span></label>
|
||
<label><input type="checkbox" data-sound="newTab" checked /> <span>New tab added</span></label>
|
||
</div>
|
||
<p class="help">Ticking one plays it. Play sounds switches them all off at once and keeps your picks for when you switch back on.</p>
|
||
</fieldset>
|
||
<fieldset data-section="activities" class="modal-ranges looks-activities">
|
||
<legend>Activities</legend>
|
||
<label><input type="checkbox" id="looks-activities" checked /> <span>Show Activities</span></label>
|
||
<label><input type="checkbox" id="looks-activity-sounds" checked /> <span>Play game sounds</span></label>
|
||
<label><input type="checkbox" id="looks-game-music" /> <span>Play game music</span></label>
|
||
<p class="help">The die in the top bar opens small games to play while you wait. Play game sounds turns the games' sounds on or off, and Play game music their chiptune music; Play sounds, above, silences them too.</p>
|
||
</fieldset>
|
||
</section>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost" id="looks-reset">Back to default</button>
|
||
<button type="button" class="btn primary" id="looks-done">Close</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- Subagents: the switch for this skill, filled from the frame's
|
||
`subagents` by app.js and saved through POST /subagents. It borrows
|
||
the User Preferences dialog's classes, so it needs no dialog styles of
|
||
its own, only a themed number box. -->
|
||
<dialog class="modal looks subagents" id="subagents-modal" aria-labelledby="subagents-title">
|
||
<h2 id="subagents-title">Subagents</h2>
|
||
<p class="modal-blurb">
|
||
Let Plan2Code hand independent work to helpers in this skill. Saved for this
|
||
project and this skill.
|
||
</p>
|
||
<!-- On a wide dialog the switch and the cap share a row, and the four
|
||
strengths sit side by side, so the dialog stays short. -->
|
||
<div class="subagents-top">
|
||
<fieldset class="modal-ranges looks-row">
|
||
<legend>Helpers</legend>
|
||
<label><input type="radio" name="subagents-on" value="on" /> <span>Use helpers</span></label>
|
||
<label><input type="radio" name="subagents-on" value="off" checked /> <span>Work alone</span></label>
|
||
</fieldset>
|
||
<fieldset class="modal-ranges">
|
||
<legend>At most</legend>
|
||
<label>
|
||
<input type="number" id="subagents-max" min="1" max="20" step="1" aria-label="At most this many helpers at once" />
|
||
<span>helpers at once</span>
|
||
</label>
|
||
<p class="help">Advisory: your agent's own limit still applies.</p>
|
||
</fieldset>
|
||
</div>
|
||
<!-- Each strength wears the Subagents tab's badge for the rank it leans
|
||
to: Thrifty light, Balanced standard, Best strongest, and the
|
||
session's own model with no rank. -->
|
||
<fieldset class="modal-ranges looks-row" id="subagents-strength-row">
|
||
<legend>Helper strength</legend>
|
||
<label><input type="radio" name="subagents-strength" value="thrifty" /> <span class="sa-badge lvl-1"><span class="sa-bars" aria-hidden="true"><i class="on"></i><i></i><i></i></span>Thrifty</span></label>
|
||
<label><input type="radio" name="subagents-strength" value="balanced" checked /> <span class="sa-badge lvl-2"><span class="sa-bars" aria-hidden="true"><i class="on"></i><i class="on"></i><i></i></span>Balanced</span></label>
|
||
<label><input type="radio" name="subagents-strength" value="best" /> <span class="sa-badge lvl-3"><span class="sa-bars" aria-hidden="true"><i class="on"></i><i class="on"></i><i class="on"></i></span>Best</span></label>
|
||
<label><input type="radio" name="subagents-strength" value="session" /> <span class="sa-badge lvl-0">Match my session</span></label>
|
||
<p class="help" id="subagents-strength-help"></p>
|
||
</fieldset>
|
||
<fieldset class="modal-ranges">
|
||
<legend>Instruction</legend>
|
||
<textarea id="subagents-instruction" rows="4" maxlength="2000" aria-label="Instruction"></textarea>
|
||
<div class="models-actions">
|
||
<button type="button" class="btn small ghost" id="subagents-default">Reset to default</button>
|
||
<span class="help">Passed to the agent as written, at its next check-in.</span>
|
||
</div>
|
||
</fieldset>
|
||
<p class="help" id="subagents-checkin"></p>
|
||
<p class="help" id="subagents-research" hidden></p>
|
||
<p class="help" id="subagents-status" role="status"></p>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost" id="subagents-cancel">Cancel</button>
|
||
<button type="button" class="btn primary" id="subagents-save">Save</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- The Notebook: the person's own notes for this folder, autosaved under
|
||
~/.plan2code/notepads/ by the /notepad routes. Never part of the
|
||
session, and the agent CLI never imports the store: a tab leaves it
|
||
only through a send the person starts on the dashboard. screens/notepad.js
|
||
fills the editor on open. -->
|
||
<dialog class="modal notepad" id="notepad-modal" aria-labelledby="notepad-title">
|
||
<h2 id="notepad-title">Notebook</h2>
|
||
<p class="modal-blurb">A private space to keep track of notes and uploaded images related to your in-progress work on this project. Saved on this machine. <strong class="private-note">Private</strong>: the agent never reads your Notebook. A tab reaches it only when you start a workflow with it.</p>
|
||
<div class="notepad-tabbar">
|
||
<div class="notepad-tabs" id="notepad-tabs" role="tablist" aria-label="Notebook tabs"></div>
|
||
<button type="button" class="btn small ghost notepad-tab-new" id="notepad-tab-new">+ New tab</button>
|
||
</div>
|
||
<div class="notepad-empty" id="notepad-empty" hidden>
|
||
<p>No tabs yet. Make one to start writing.</p>
|
||
<button type="button" class="btn small primary" id="notepad-empty-new">+ New tab</button>
|
||
</div>
|
||
<div class="notepad-body" id="notepad-body">
|
||
<div class="notepad-editor" id="notepad-editor"></div>
|
||
<p class="help notepad-sent" id="notepad-sent" hidden></p>
|
||
<div class="notepad-images" id="notepad-images">
|
||
<button type="button" class="btn small ghost notepad-add" id="notepad-add">Add image</button>
|
||
<input type="file" accept="image/*" multiple id="notepad-file" hidden />
|
||
<ul class="notepad-strip" id="notepad-strip" role="list" aria-label="Notebook images"></ul>
|
||
</div>
|
||
</div>
|
||
<div class="modal-actions notepad-actions">
|
||
<p class="help notepad-status" id="notepad-status" aria-live="polite"></p>
|
||
<button type="button" class="btn ghost" id="notepad-close">Close</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- The Notebook's name and delete questions: small dialogs over the Notebook.
|
||
A tab's double-click (or F2) opens the name one for Rename, + New tab
|
||
opens it for a new name, and a tab's x opens the delete one, which asks twice. -->
|
||
<dialog class="modal notepad-sub" id="notepad-name-dlg" aria-labelledby="notepad-name-label">
|
||
<form class="notepad-name-form" id="notepad-name-form" novalidate>
|
||
<h2 id="notepad-name-label">Name this tab</h2>
|
||
<input type="text" id="notepad-name" autocomplete="off" spellcheck="false" aria-describedby="notepad-name-error" />
|
||
<p class="help notepad-name-error" id="notepad-name-error" aria-live="polite"></p>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost" id="notepad-name-cancel">Cancel</button>
|
||
<button type="submit" class="btn primary" id="notepad-name-save">Save</button>
|
||
</div>
|
||
</form>
|
||
</dialog>
|
||
|
||
<dialog class="modal notepad-sub notepad-delete" id="notepad-delete" aria-labelledby="notepad-delete-title" aria-describedby="notepad-delete-text">
|
||
<h2 id="notepad-delete-title">Delete this tab?</h2>
|
||
<p id="notepad-delete-text"></p>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost" id="notepad-delete-keep">Keep tab</button>
|
||
<button type="button" class="btn danger" id="notepad-delete-go">Delete tab…</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- The Notebook's full-screen picture preview, opened over the Notebook
|
||
from a thumbnail by screens/notepad.js. -->
|
||
<dialog class="modal notepad-preview" id="notepad-preview" aria-label="Image preview">
|
||
<img class="notepad-preview-img" id="notepad-preview-img" alt="" />
|
||
<button type="button" class="notepad-preview-step is-prev" id="notepad-preview-prev" aria-label="Previous image">‹</button>
|
||
<button type="button" class="notepad-preview-step is-next" id="notepad-preview-next" aria-label="Next image">›</button>
|
||
<div class="notepad-preview-bar">
|
||
<p class="notepad-preview-count" id="notepad-preview-count" aria-live="polite"></p>
|
||
<button type="button" class="btn small notepad-preview-close" id="notepad-preview-close">Close</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- Activities: small built-in games for a long wait. Play is private to
|
||
this page and never reaches the agent; screens/activities.js runs the
|
||
game, and pauses it whenever Plan2Code needs the person. -->
|
||
<dialog class="modal activities" id="activities-modal" aria-labelledby="activities-title">
|
||
<h2 id="activities-title">Activities<span id="activities-title-best" class="activities-title-best"></span></h2>
|
||
<p class="modal-blurb">Something to play while you wait. Private to this page, and it pauses whenever Plan2Code needs you.</p>
|
||
<div class="activities-banner" id="activities-banner" role="status" hidden>
|
||
<span class="activities-banner-text" id="activities-banner-text"></span>
|
||
<button type="button" class="btn small" id="activities-unpause" hidden>Unpause game</button>
|
||
<button type="button" class="btn small primary" id="activities-goto">Go to it</button>
|
||
</div>
|
||
<div class="activities-picker" id="activities-picker" hidden></div>
|
||
<!-- The stage: the board, and in full screen the side panel beside it,
|
||
which the score line moves into. Out of full screen it takes no box
|
||
of its own, so the board and the score line sit in the window. -->
|
||
<div class="activities-stage" id="activities-stage">
|
||
<div class="activities-board" id="activities-board" tabindex="-1">
|
||
<canvas id="activities-canvas"></canvas>
|
||
<div class="activities-overlay" id="activities-overlay"></div>
|
||
</div>
|
||
<aside class="activities-rail" id="activities-rail" aria-label="Game" hidden>
|
||
<p class="activities-rail-title" id="activities-rail-title"></p>
|
||
<p class="activities-rail-best" id="activities-rail-best"></p>
|
||
<div class="activities-rail-score" id="activities-rail-score"></div>
|
||
<p class="activities-rail-keys"><kbd>P</kbd> pauses · <kbd>R</kbd> restarts · <kbd>F</kbd> or <kbd>Esc</kbd> leaves full screen</p>
|
||
<button type="button" class="btn small" id="activities-rail-exit">Exit full screen</button>
|
||
</aside>
|
||
</div>
|
||
<p class="activities-score" id="activities-score"></p>
|
||
<p class="help activities-note" id="activities-note" aria-live="polite" hidden></p>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost activities-back" id="activities-back" hidden>All games</button>
|
||
<label class="activities-music" id="activities-music" title="This game's music volume" hidden><span>Music</span><input type="range" id="activities-music-level" min="0" max="100" step="5" aria-label="Music volume" /></label>
|
||
<button type="button" class="btn ghost" id="activities-full" aria-pressed="false" title="Full screen (F)" hidden>Full screen</button>
|
||
<button type="button" class="btn ghost" id="activities-reset">Reset best scores</button>
|
||
<button type="button" class="btn ghost" id="activities-close">Close</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- The Workspace: the folder this session started in plus any added as
|
||
context. The list is drawn by app.js from the frame's `workspace`;
|
||
every change goes through the server's /workspace routes. -->
|
||
<dialog class="modal workspace" id="workspace-modal" aria-labelledby="workspace-title">
|
||
<h2 id="workspace-title">Workspace</h2>
|
||
<p class="modal-blurb">
|
||
The folders the agent uses as context this session. It reads the extra ones for
|
||
reference and only changes them if you ask.
|
||
</p>
|
||
<p class="workspace-scope" id="workspace-scope"></p>
|
||
<ul class="workspace-list" id="workspace-list"></ul>
|
||
<div class="workspace-add">
|
||
<label class="workspace-add-label" for="workspace-path">Add a folder</label>
|
||
<div class="workspace-add-row">
|
||
<input
|
||
type="text"
|
||
id="workspace-path"
|
||
placeholder="Paste or type a folder path"
|
||
autocomplete="off"
|
||
spellcheck="false"
|
||
/>
|
||
<button type="button" class="btn" id="workspace-browse">Browse…</button>
|
||
<button type="button" class="btn primary" id="workspace-add">Add</button>
|
||
</div>
|
||
<p class="workspace-add-msg" id="workspace-add-msg" aria-live="polite"></p>
|
||
</div>
|
||
<div class="modal-actions">
|
||
<button
|
||
type="button"
|
||
class="icon-btn workspace-help"
|
||
id="workspace-help"
|
||
title="Help on the workspace"
|
||
aria-label="Help on the workspace"
|
||
>
|
||
<svg viewBox="0 0 16 16" aria-hidden="true" focusable="false">
|
||
<circle cx="8" cy="8" r="7" class="ab-ring" />
|
||
<path class="ab-mark" d="M6.1 6.05a1.95 1.95 0 1 1 2.4 1.9v1.25" />
|
||
<circle cx="8" cy="11.7" r="0.85" class="ab-dot" />
|
||
</svg>
|
||
</button>
|
||
<button type="button" class="btn primary" id="workspace-done">Close</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- A native dialog, so focus trapping, Esc and the backdrop come from the
|
||
browser rather than from code that has to be got right. -->
|
||
<dialog class="modal help" id="help-modal" aria-labelledby="help-title">
|
||
<h2 id="help-title">Help</h2>
|
||
<div class="help-layout">
|
||
<div id="help-tabs" class="help-tabs" role="tablist" aria-orientation="vertical" aria-label="Help topics"></div>
|
||
<div id="help-panels" class="help-panels"></div>
|
||
</div>
|
||
<div class="modal-actions">
|
||
<span class="help-version" id="help-version" hidden></span>
|
||
<button type="button" class="btn primary" id="help-done">Close</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- Shown once, on the first dashboard a person sees. Closing it by any
|
||
route saves looks.welcomeSeen; Help's first tab reopens it. -->
|
||
<dialog class="modal welcome" id="welcome-modal" aria-labelledby="welcome-title">
|
||
<div class="welcome-poster">
|
||
<div class="welcome-sky" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i></div>
|
||
<!-- Planny is cloned in from #planny by app.js, so he is always the
|
||
same robot as the one in the dock. -->
|
||
<div class="welcome-bot" id="welcome-bot" aria-hidden="true"></div>
|
||
<p class="welcome-kicker">Plan2Code Web Console</p>
|
||
<h2 id="welcome-title">Ideas in. Working code out.</h2>
|
||
<p class="welcome-lead">
|
||
Answer questions, read what gets written and approve each step here,
|
||
instead of in the terminal. It runs on this machine only.
|
||
</p>
|
||
</div>
|
||
<div class="welcome-cols">
|
||
<div class="welcome-col">
|
||
<span class="welcome-dot is-accent">
|
||
<svg viewBox="0 0 24 24" aria-hidden="true" focusable="false"><rect x="3.5" y="9" width="12" height="9" rx="1.6" transform="rotate(-12 9.5 13.5)" /><rect x="8.5" y="6" width="12" height="9" rx="1.6" /></svg>
|
||
</span>
|
||
<h3>Pick a card</h3>
|
||
<p>Start with <strong>Suggested</strong>. Pathfinder for a foggy idea, Quick Task for something small.</p>
|
||
</div>
|
||
<div class="welcome-col">
|
||
<span class="welcome-dot is-stage">
|
||
<svg viewBox="0 0 20 20" aria-hidden="true" focusable="false"><circle cx="10" cy="10" r="7" opacity="0.35" /><circle cx="10" cy="10" r="7" pathLength="100" stroke-dasharray="50 100" stroke-dashoffset="25" transform="rotate(-90 10 10)" /></svg>
|
||
</span>
|
||
<h3>Refresh at half way</h3>
|
||
<p id="welcome-refresh-text">Once the session meter passes half, finish the step and start a new conversation.</p>
|
||
</div>
|
||
<div class="welcome-col">
|
||
<span class="welcome-dot is-bare">
|
||
<svg viewBox="0 0 24 24" aria-hidden="true" focusable="false"><rect x="3.5" y="5" width="17" height="14" rx="2" /><path d="M7.5 10l3 2-3 2M12.5 14.5h4" /></svg>
|
||
</span>
|
||
<h3>Come back</h3>
|
||
<p><code>/plan2code</code> in your agent, or <code>plan2code</code> in any folder.</p>
|
||
</div>
|
||
<div class="welcome-col">
|
||
<span class="welcome-dot is-plain">
|
||
<svg viewBox="0 0 16 16" aria-hidden="true" focusable="false"><path d="M12 8h2.6M8 12v2.6M4 8H1.4M8 4V1.4M10.83 10.83l1.84 1.84M5.17 10.83l-1.84 1.84M5.17 5.17L3.33 3.33M10.83 5.17l1.84-1.84" /><circle cx="8" cy="8" r="4.2" /><circle cx="8" cy="8" r="1.6" /></svg>
|
||
</span>
|
||
<h3>Get help</h3>
|
||
<p><kbd>?</kbd> opens Help. The gear holds your role, theme and sounds.</p>
|
||
</div>
|
||
</div>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn primary" id="welcome-done">Start building</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<dialog class="modal" id="stop-modal" aria-labelledby="stop-title">
|
||
<h2 id="stop-title">Stop this session?</h2>
|
||
<p class="modal-blurb" id="stop-blurb"></p>
|
||
<!-- Only when stopping now would lose answers. A button that says it
|
||
saves has to be true about the times it cannot. -->
|
||
<p class="modal-why" id="stop-warn" hidden></p>
|
||
<div class="stop-choices">
|
||
<button type="button" class="stop-choice suggested" id="stop-handoff">
|
||
<span class="stop-choice-icon" aria-hidden="true">✎</span>
|
||
<span class="stop-choice-text">
|
||
<span class="stop-choice-title">Stop with a handoff</span>
|
||
<span class="stop-choice-detail">Saves your place and writes a handoff note. Next time the dashboard offers to pick it up right where this left off.</span>
|
||
</span>
|
||
</button>
|
||
<button type="button" class="stop-choice" id="stop-go">
|
||
<span class="stop-choice-icon" aria-hidden="true">■</span>
|
||
<span class="stop-choice-text">
|
||
<span class="stop-choice-title">Just stop and save</span>
|
||
<span class="stop-choice-detail">Saves what this step keeps on disk and gives you a command to resume. What we talked about is not kept.</span>
|
||
</span>
|
||
</button>
|
||
</div>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost" id="stop-cancel">Keep going</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- Deleting a spec from the dashboard's picker. Two deliberate steps: the
|
||
first says what goes and that it is for good, the second wants the
|
||
spec's name typed. A fixed bug takes the first step only. The page
|
||
only asks; the agent deletes. -->
|
||
<dialog class="modal" id="delete-modal" aria-labelledby="delete-title">
|
||
<h2 id="delete-title">Delete this spec?</h2>
|
||
<p class="modal-blurb" id="delete-blurb"></p>
|
||
<dl class="delete-facts" id="delete-facts"></dl>
|
||
<p class="modal-why" id="delete-warn">This is permanent. <code>specs/</code> is not tracked by git, so nothing can bring these files back.</p>
|
||
<p class="modal-why" id="delete-warn-handoff" hidden>Handoffs are not kept anywhere else.</p>
|
||
<div class="delete-confirm" id="delete-confirm" hidden>
|
||
<label for="delete-name">To delete it for good, type <strong id="delete-name-hint"></strong></label>
|
||
<input type="text" id="delete-name" autocomplete="off" spellcheck="false" />
|
||
</div>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost" id="delete-cancel">Keep it</button>
|
||
<button type="button" class="btn danger" id="delete-go">Delete this spec…</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- A handoff's whole document, from the dashboard's "Read it all". Escape
|
||
closes it; the body is filled by the page with rendered markdown. -->
|
||
<dialog class="modal handoff-read" id="handoff-modal" aria-labelledby="handoff-title">
|
||
<h2 id="handoff-title">Handoff</h2>
|
||
<div class="handoff-body md" id="handoff-body"></div>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost" id="handoff-close">Close</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<dialog class="modal" id="home-modal" aria-labelledby="home-title">
|
||
<h2 id="home-title">Leave this workflow?</h2>
|
||
<p class="modal-blurb" id="home-blurb"></p>
|
||
<!-- The same warning Stop shows: going home saves the way a stop does,
|
||
so it loses what a stop would lose. -->
|
||
<p class="modal-why" id="home-warn" hidden></p>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost" id="home-cancel">Keep going</button>
|
||
<button type="button" class="btn primary" id="home-go">Back to the dashboard</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- While the stop is being handled. A dialog rather than a painted layer so
|
||
focus, Esc and the backdrop come from the browser; Esc hides it and the
|
||
Stop button brings it back, the stop itself carries on regardless. -->
|
||
<dialog class="modal stopping" id="stopping-modal" aria-labelledby="stopping-title">
|
||
<h2 id="stopping-title">Wrapping up</h2>
|
||
<ol class="stop-steps" id="stop-steps"></ol>
|
||
<div id="stop-extra"></div>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost" id="stopping-hide">Back to the page</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<dialog class="modal" id="brief-modal" aria-labelledby="brief-title">
|
||
<h2 id="brief-title">Write a brief</h2>
|
||
<p class="modal-blurb">
|
||
A plain-English report of what has been decided, what is still open and what
|
||
happens next. Plan2Code writes it to a file and shows it here, ready to
|
||
print or hand to someone who has not been in the room.
|
||
</p>
|
||
<fieldset class="modal-ranges">
|
||
<legend>How far back?</legend>
|
||
<label><input type="radio" name="brief-range" value="today" checked /> <span>Today</span></label>
|
||
<label><input type="radio" name="brief-range" value="this week" /> <span>This week</span></label>
|
||
<label><input type="radio" name="brief-range" value="since" /> <span>Since a date</span></label>
|
||
<label class="since-row">
|
||
<span class="since-label">Date</span>
|
||
<input type="date" id="brief-since" />
|
||
</label>
|
||
<label><input type="radio" name="brief-range" value="full" /> <span>Everything so far</span></label>
|
||
</fieldset>
|
||
<p class="modal-why" id="brief-why"></p>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn ghost" id="brief-cancel">Cancel</button>
|
||
<button type="button" class="btn primary" id="brief-go">Write the brief</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<!-- Opened from the dashboard's UPDATE AVAILABLE banner. The versions and
|
||
the two copy rows are filled by app.js; the update itself runs in a
|
||
terminal, never from this page. -->
|
||
<dialog class="modal" id="update-modal" aria-labelledby="update-title">
|
||
<h2 id="update-title">A new Plan2Code is available</h2>
|
||
<p class="modal-blurb" id="update-versions"></p>
|
||
<ol class="update-steps">
|
||
<li>
|
||
Run this in your terminal (not in this page or your agent):
|
||
<div class="update-command" id="update-command"></div>
|
||
It updates everything that was installed (the skills, the <code>plan2code</code>
|
||
command and any extras you added), with no menu. If the <code>plan2code</code>
|
||
command is not installed, run this instead:
|
||
<div class="update-command" id="update-fallback"></div>
|
||
Back at your prompt with no output at all? npm
|
||
could not reach the repository and hid the reason: run
|
||
<code>git ls-remote https://github.com/jparkerweb/plan2code.git</code> to see it.
|
||
</li>
|
||
<li>When it finishes, close this console and start <code>plan2code</code> again.</li>
|
||
</ol>
|
||
<div class="modal-actions">
|
||
<button type="button" class="btn primary" id="update-done">Close</button>
|
||
</div>
|
||
</dialog>
|
||
|
||
<footer class="footer">
|
||
<div class="footer-summary" id="footer-summary" aria-live="polite">
|
||
Nothing to send yet.
|
||
</div>
|
||
<button type="button" class="footer-where" id="footer-where" hidden></button>
|
||
<div class="footer-actions">
|
||
<span class="hint" id="send-hint"></span>
|
||
<button type="button" class="btn ghost" id="btn-clear" hidden>Clear</button>
|
||
<button type="button" class="btn primary" id="btn-send" disabled>Send to Plan2Code</button>
|
||
</div>
|
||
</footer>
|
||
|
||
<!-- p2c:boot -->
|
||
<script type="module" src="/app.js"></script>
|
||
</body>
|
||
</html>
|