Tick off Your Turn as you go.
12 min read
People keep asking how we made the map on our Grok Bot page look like a circuit board that lights up as the day moves. You can build your own version for whatever you want to track: a shop floor, a content calendar, a family week, a study plan. You do not need a graphics card or a design team. A single HTML file, one data file per day, and a short list of layout rules will get you a dark board, neon traces, and a replay of the day.
The live example is the pulse map on our Grok Bot page. This guide is the recipe behind that look. The small dashboard later on this page uses made-up sample days so you can see the pieces move. It is not a copy of our shop's private traffic, and it does not invent times we did not log.
The Bots Talk It Through
Jump To: What You Are Building · What To Track Daily · A Simple Data Format · The Layout Rules · Colour And Glow Tokens · Build It With SVG, CSS And A Little JS · Or Let A Grok Bot Build It · Per-Day Replay Tabs · Mobile Tips · Accessibility · Common Mistakes · Why This Matters To Me · Quick Answers · How Grok Bot Usage Works
What You Are Building
A daily visual tracker is a board that shows who did what, in the order it happened. Ours looks like a printed circuit: dark substrate, neon traces, cards with pins on the left and right, and a shared storage bar along the bottom. When you press Replay, a pulse runs along the trace for each logged event.
You can track a bot team, like we do. You can just as easily track people, tools, or rooms. The look stays the same. The data is just a list of timed events between named cards.
Three parts make the whole thing:
- A layout. Cards, a centre spine, one shared data line on each side, and a storage bar.
- A day file. JSON or CSV, one file per date, with the events you actually logged.
- A little motion. A replay of that file, with a pause control, and tabs for the last 10 days.
What To Track Daily
Track the work you already write down, not a new ritual. If you cannot point to a note, a ticket, or a sent draft, it does not go on the board. That rule keeps the replay honest. If an event has a count but no time, show it as background traffic on its line. Do not invent a clock time to make the animation prettier.
A useful day for a small shop or a solo practice usually has some mix of:
- Messages that arrived and the list you made from them.
- Jobs or tasks that actually finished.
- Drafts that moved (a web page, a post, a letter), still waiting on your OK before anything is sent or published.
- Money checks: invoices, deposits, or a flag that something does not match.
- Approvals you gave, in your own words.
- Handoffs from a coordinator to the person or bot who owns the next step.
Keep customer details off any board you might show to someone else. Use a role name (Inbox, Bench, Website, Books) and a short note like "morning list written to storage."
A Simple Data Format
Store one file per day. JSON is easier for a browser. CSV is easier to edit in a spreadsheet. Use the same field names in both so you can convert them later.
A day file looks like this:
{
"date": "2026-11-10",
"events": [
{
"t": "09:12",
"from": "inbox",
"to": "storage",
"kind": "write",
"note": "Morning list written to storage."
},
{
"t": "11:48",
"from": "hub",
"to": "website",
"kind": "command",
"note": "Hub sent a command to Website."
}
]
}
The same day as CSV:
date,time,from,to,kind,note
2026-11-10,09:12,inbox,storage,write,Morning list written to storage.
2026-11-10,11:48,hub,website,command,Hub sent a command to Website.
Put the files in a folder named by kind, then by date:
tracker/
days/
2026-11-02.json
2026-11-03.json
...
archive/
2026-10-28.json
Only the newest 10 dates stay in days/. When the 11th day arrives, move the oldest file into archive/ and drop its tab. The data is still there; it just is not hanging on the board.
The Layout Rules
These are the same rules we use on the pulse map. Follow them and a small board will still read clearly when it grows.
- Centre spine. Put your coordinator and your command hub in the middle. Their lines run straight down to storage. Everything else is laid out from that spine.
- Side trunks. One shared data line on the left, one on the right. Each card taps onto its side line at a via, then the line runs down to the storage bar.
- Pins only on the left and right. Connection points sit on the sides of cards, evenly spaced. The storage bar has real pins too. Do not attach lines to the top or bottom of a card unless you are dropping a spine into it.
- One to three bends. A line may bend once, twice, or three times. Add an extra bend only when you must land on a pin. No zigzags.
- Under-passes. When a line must cross the spine, it goes under: a dashed segment, with a via at both ends. The spine stays straight.
- Even spacing. Parallel lines share one pitch so they look like a bus, not a tangle.
- Shoulders stay on desktop. Outside data sources (web search, a calendar, a database) sit in the upper corners and feed the cards that read them. Hide those blocks on a phone.
Colour And Glow Tokens
You can steal these tokens from our board. There are two palettes: a printed-circuit look and a neon "tron" look. The sample dashboard on this page uses the neon set. The live map on the Grok Bot page can show both.
-
Board
#020409neon#0A111Ccircuit -
Spine
#22D3EEcyan
glow: drop-shadow -
Command
core#05070B
silver#DCE3EC -
Shared data
#8A96A8
one grey per side -
Card fill
#02070Dneon#111C2Ccircuit -
Card name
#F2FEFFneon#E5EDF8circuit -
Card role
#9CEBFFneon
via stroke matches this -
Pulse
#00E5FF
one event at a time
In CSS, keep them as variables so both palettes can share the same markup:
:root {
--board: #020409;
--grid: rgba(0, 229, 255, 0.13);
--card: #02070D;
--name: #F2FEFF;
--role: #9CEBFF;
--spine: #22D3EE;
--cmd: #05070B;
--silver: #DCE3EC;
--data: #8A96A8;
--pulse: #00E5FF;
--via: #9CEBFF;
}
.board {
background-color: var(--board);
background-image:
linear-gradient(var(--grid) 1px, transparent 1px),
linear-gradient(90deg, var(--grid) 1px, transparent 1px);
background-size: 32px 32px;
}
.spine {
stroke: var(--spine);
fill: none;
stroke-width: 3;
filter: drop-shadow(0 0 4px var(--spine));
}
.command-silver { stroke: var(--silver); stroke-width: 3.4; fill: none; }
.command-core { stroke: var(--cmd); stroke-width: 1.4; fill: none; }
Draw a command line twice: a wider silver stroke underneath, then the black core on top. That is the outline that makes a dark command branch readable on a dark board. When the same branch passes under the spine, the dashed under-piece should be silver too, or it will disappear.
Build It With SVG, CSS And A Little JS
A browser can draw the whole board. SVG holds the cards and traces. CSS holds the tokens and the reduced-motion rule. A short script loads a day file, draws a pulse, and manages the tabs.
A two-bend data path, from a card pin to the shared line and down to storage, is just a few coordinates:
<path class="data" d="M48 174 H36 V324 H48" />
<circle class="via" cx="36" cy="174" r="3.5" />
<circle class="via" cx="36" cy="324" r="3.5" />
A pulse is the same path, with a short dash that moves once:
.pulse {
fill: none;
stroke: var(--pulse);
stroke-width: 4;
stroke-linecap: round;
stroke-dasharray: 10 90;
stroke-dashoffset: 100;
visibility: hidden;
}
.pulse.is-run {
visibility: visible;
animation: pulse-run 1.2s linear 1 both;
}
@keyframes pulse-run {
from { stroke-dashoffset: 100; }
to { stroke-dashoffset: 0; }
}
Here is a working starter on this page. It has four work cards, a You card, a Lead card, a Hub, a storage bar, desktop source blocks, one shared data line per side, silver command branches, replay, pause, 10 day tabs, and an archive for anything older. Copy the idea, then swap the sample events for your own day files.
Sample data only, so you can see the pieces move. Tap a day, then Replay. The last 10 days stay on the tabs; older days drop into the archive.
Pick a day, then press Replay day.
Older days (stored after 10 tabs)
Or Let A Grok Bot Build It For You
If you would rather not write the SVG yourself, give a Grok Bot the rules and a day file, then review the HTML before you use it. Ask it to draft, not publish. Start with one of these prompts, and fill in the brackets.
Build a single HTML file for a daily visual tracker in the style of the Franchitti's Fix Grok Bot pulse map. Dark board, neon traces, cards with pins only on the left and right, a centre spine, one shared grey data line per side, a storage bar with real pins, and at most three bends per line. When a line crosses the spine, dash it underneath with a via at both ends. Use these CSS tokens: board #020409, spine #22D3EE, command core #05070B with silver outline #DCE3EC, data #8A96A8, pulse #00E5FF. Include Replay and Pause controls. Honor prefers-reduced-motion by not animating automatically. Put captions under the board, never on the traces. Do not invent event times that are not in my data. Use this day file: [paste JSON].
Add day tabs to this tracker. Keep the newest 10 dates as tabs. When an 11th day is added, move the oldest file into an archive folder and list it under Older days. Do not delete the data. Show a short status line under the board for the event that is playing. Check the layout at 1280 and 390 pixels and fix any overlapping text before you hand it back.
Revise this board for a phone. Hide the outside source blocks in the upper corners. Keep one shared data line per side. Keep the spine. Do not add zigzags. If a label does not fit inside its card, shorten the label or enlarge the card. Do not place text on a trace.
A good first message for a new bot also sets the limits:
Your job: help me build and revise a daily visual tracker
in a neon circuit-board style.
Check first: the day JSON I attach, and my layout rules.
Each afternoon: if I added a new day file, rebuild the tabs,
keep 10, and archive anything older.
Never: invent a time I did not log, put labels on traces,
publish a page, or include private customer details.
Per-Day Replay Tabs
Give each day its own tab. The board always shows one day at a time. Replay plays that day's events in the order they were logged. The status line under the board is the caption, so the traces can stay clean.
The tab rule is simple, and you can keep it in a few lines:
const KEEP = 10;
function splitDays(days) {
const sorted = days.slice().sort((a, b) => a.date.localeCompare(b.date));
return {
tabs: sorted.slice(-KEEP),
archive: sorted.slice(0, -KEEP)
};
}
When you add tomorrow's file, the oldest of the 10 tabs moves into the archive list. Opening an archived day still replays it; it just does not take a tab slot until you decide to pin it back. That is enough history to compare a week and a bit, without a row of tabs you cannot read on a phone.
Mobile Tips
A phone cannot hold the desktop shoulders. Hide the outside source blocks, and skip any pulse that would have lit a feed into a block that is not on screen. Keep the spine. Keep one shared data line per side. Move the card rows up into the space you freed.
Use two SVG views, not one drawing that shrinks until the labels collide:
svg.wide { display: none; }
svg.narrow { display: block; }
@media (min-width: 700px) {
svg.wide { display: block; }
svg.narrow { display: none; }
}
On the narrow view, give each card enough height for a name and a short role on two lines. Shorten names before you shrink type. If a line still cannot land on a pin in two bends, give it a third, then stop. A straight run or a small U is better than a line that weaves through the cards.
Accessibility
Motion on a board is helpful until it is not. Build in a pause control from the first version, and respect the device setting that asks for less motion.
@media (prefers-reduced-motion: reduce) {
.pulse {
animation: none !important;
visibility: hidden !important;
}
.card, .spine {
filter: none;
}
}
Under that setting, Replay should still change the status line and can still highlight a trace without a moving dash. Keep tab and pause targets at least 44 pixels tall. Give each SVG a title that describes the layout in words. Do not flash a line more than once a second, and do not play a loop until someone presses Replay.
Common Mistakes
- Labels on the traces. They collide as soon as two lines run side by side, and they get worse on a phone. Put the words under the board.
- A trunk for every card. That is how the left side turns into a rail yard. One shared data line per side is enough.
- Invented times. If you did not log a clock time, do not make one up so the replay has a beat. Leave it as background traffic on its line.
- Zigzags and top-edge pins. Extra bends and surprise joins are harder to read than a longer, calmer path.
- No pause control. If it moves, someone needs a way to stop it, including people who asked their device to reduce motion.
- Private details on a pretty board. A tracker you might show off should use role names and short public notes.
Why This Matters To Me
I run Franchitti's Fix by myself, out of a home-based shop, by appointment. The pulse map started as a way to see how the bots hand work off during a real day. Once it was in front of me, I wanted other people to be able to build the same kind of board for their own work, without needing our whole setup. A dark board and an honest day file are enough to start.
Want To Talk Shop?
I'm Steve, and I run Franchitti's Fix, a home-based, by-appointment iPhone repair shop in San Diego. Questions about bots, or an iPhone that needs fixing? Book An Appointment, or read more about me.
This post shares my own experience and opinions running Franchitti's Fix. Franchitti's Fix isn't affiliated with or endorsed by xAI or the owners of any film, game or product names used to describe a look. Product names belong to their owners. Features and plans change, so check each company's current docs. AI makes mistakes, so review its work. The sample dashboard on this page uses made-up tutorial events.
Quick Answers
Do I Need A Graphics Card?
No. This board is SVG, CSS and a little JavaScript. A graphics card helps with 3D work, which is a different guide: Grok Bots, Python And Your Own GPU.
Can A Grok Bot Build The Whole File?
Yes. Give it the layout rules, the colour tokens and a day file, and ask it to draft one HTML page. Review the result at desktop and phone widths before you rely on it, and do not let it publish anything on its own.
What If I Have More Than 10 Days?
Keep the newest 10 as tabs. Move older day files into an archive folder and list them under Older days. The data stays; the tab row stays readable.
How Grok Bot Usage Works
Franchitti's Fix is run by Steve with help from Grok Bot, so here's the plain version of how its usage works.
- Your Plan Includes A Usage Allowance. Paid plans come with included usage that refreshes every week. Higher-tier plans include more. Unused usage doesn't roll over. (Source)
- Bigger Jobs Use More. In general, long research, tasks that use lots of tools and routines running in the background do more work, so they draw down the allowance faster than a quick question.
- Light Settings Stretch It. Lower effort for simple jobs, fewer and less frequent routines and short, focused requests all help the allowance last. See How To Regulate Grok Bot Usage.
- Checking Your Usage. In Grok Bot, open Settings, then Usage & Billing. On The X Subscription, you can also check Usage at grok.com/dashboard, which shows the weekly pool, the next reset date and any prepaid credit. (Source)
Supercharge Your Workflow or Business
Try Grok Bot
Affiliate link: we may earn a referral reward if you sign up.
Related Guides
- The Grok Bot Pulse Map
- How My Repair Shop Runs On A Team Of Grok Bots
- How To Set Up An AI Assistant With Grok Bot
- Grok Bots, Python And Your Own GPU: Put Your Computer To Work
- Cortana: The Coordinator
- Every AI Guide In One Place
Thanks! Glad it helped.
Thanks for saying so. I'll keep improving it.
Your Turn: Get To Work
Try these four steps today.
0 of 4 done
More In This Series
This guide is part of Grok Bot Guides: Start Here.
- How To Set Up An AI Assistant With Grok Bot
- Grok Bot Pricing And Usage: One Bot Or Many
- How My Repair Shop Runs On A Team Of Grok Bots
- Grok Bot Front Desk: The RepairDesk Clerk
- The Localizer: Copy, Landing Pages, And Pricing Language
- Social: Daily Posts And A Weekly Plan
- R&D: Research, Photos, And Parts Facts
- The Accountant: Books, Money Checks, And Tax Deadlines
- The Designer: Website, Theme, And Listings
- Cortana: The Coordinator
- Bot Manager: Audits And Team Rules
- Routines: SEO, Price Checks, And Competitor Scans
- Grok Bot Setup Scripts For Every Area Of Life
- Grok Bot Prompt Library: Roles, Routines And Life
- 26 Grok Bot Routine Recipes You Can Copy
- How To Use Helper Bots So Your Main Bots Stay Focused
- Running More Than One Grok Bot: Usage And What To Expect
- How To Regulate Grok Bot Usage Without Losing Results
- Get Better Answers From Your Grok Bot: Before And Afters, Answer Cards And Rule Sets
- Keep Your Grok Bots Fast And Accurate: Shorter Requests And Regular Cleanup
- Grok Bot Integrations For A Small Store: What Each Does
- Grok Bot Vs Other AI Assistants: Honest Pros And Cons
- Grok Bots, Python And Your Own GPU: Put Your Computer To Work
- How To Build A Franchitti's Fix Inspired Tron Circuit Dashboard You’re here
Back to the series index: Grok Bot Guides: Start Here. All series: Every AI Guide In One Place. The live map: Grok Bot pulse map.



