30 Claude Prompts That Build Content Dashboards

You are an editorial-operations analyst who builds brief-to-ship pipelines, not a marketing funnel and not a kanban toy. <context> I need a brief-to-ship production dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic piece statuses so I can click the working screen in the chat. </context> <inputs> - Pipeline name: [PIPELINE] - Stages in order: [E.G. IDEA, BRIEF, DRAFT, REVIEW, SCHEDULED, SHIPPED] - Pieces: [14-24 TITLES OR "INVENT"] - Stuck rule: [E.G. SAME STAGE OVER 7 DAYS] - Today constant: [DATE] </inputs> <task> Build the dashboard with: a header for [PIPELINE]; KPI cards (in pipeline, shipped this window, stuck, median days idea-to-ship for shipped rows); a horizontal stage funnel of counts; a stage table (count, median days, stuck count); chips that filter a piece list; and a stuck list using my rule. Compute days in stage from last stage-change date and the today constant. Clicking a stuck brief opens owner, stage, and days. Do not invent traffic or ranks. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Piece rows with stage and dates in labeled JS constants at the top so I can swap a CMS status export later. - Stuck labeled stuck. Accessible contrast. - Editorial stages only. No MQL or SQL language. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write stuck math and which array to replace. </format>

You are an editorial-operations analyst who ages drafts from first draft date so a busy edit pass cannot hide a stale piece. <context> I need a draft age dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic drafts so I can click the working screen in the chat. </context> <inputs> - Queue name: [DRAFT QUEUE] - Stale rule: [E.G. AGE OVER 14 DAYS AND STILL DRAFT] - Today constant: [DATE] - Sample drafts: [10-16 TITLES WITH FIRST DRAFT DATE, OWNER, WORD COUNT OR "INVENT"] - Publication: [NAME] </inputs> <task> Build the dashboard with: a header for [DRAFT QUEUE]; KPI cards (open drafts, median age, stale count, oldest draft); a histogram of age days; a sortable table (title, owner, first draft, age days, words, next action); owner chips; and a stale-draft list using my rule. Compute age from first draft date and the today constant. Sort default: age descending. Clicking a stale row highlights the histogram bucket. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Draft rows in labeled JS constants at the top so I can swap a draft export later. - Stale labeled stale. Accessible contrast. - Do not invent pageviews. Draft ops only. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write age math and which array to replace. </format>

You are an editorial-operations analyst who measures review SLA from stage-enter time, not from last seen. <context> I need a review SLA dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic review timestamps so I can click the working screen in the chat. </context> <inputs> - SLA name and hours: [REVIEW SLA] - Reviewers: [NAMES OR "INVENT 4"] - Sample pieces in or through review: [10-16 WITH ENTERED REVIEW AT AND EXITED OR STILL OPEN] - Today constant: [DATETIME] - Publication: [NAME] </inputs> <task> Build the dashboard with: a header for [REVIEW SLA]; KPI cards (in review, on time %, late, median hours); a bar of hours in review versus the SLA line; a table (title, reviewer, entered, hours, status on time/late/still open); reviewer chips; and a late list. Compute hours from entered review to exit, or to the today constant if still open. Still-open rows can be late. Clicking a late piece opens reviewer and hours over SLA. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Review rows in labeled JS constants at the top so I can swap review timestamps later. - Late labeled late. Accessible contrast. - Do not invent quality scores. Time only. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write SLA math and which array to replace. </format>

You are an editorial-operations analyst who builds blocked-piece watchlists that force a single next owner. <context> I need a blocked-piece watchlist as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic blocked rows so I can click the working screen in the chat. </context> <inputs> - Reason list: [BLOCK REASONS] - Publication: [NAME] - Sample blocked pieces: [10-16 WITH ONE REASON, OWNER WAITING ON, DAYS BLOCKED OR "INVENT"] - Fix-first rule: [E.G. MONEY PIECE + DAYS OVER 5] - Today constant: [DATE] </inputs> <task> Build the dashboard with: a header for the publication; KPI cards (blocked, by top reason, fix-first count, median days blocked); a bar of count by each item in [BLOCK REASONS]; a sortable watchlist (title, reason, waiting on, days, ship date if any); reason chips that filter; and a fix-first list using my rule. Compute days blocked from block-start and the today constant. Clicking a reason filters every widget. Suggested next owner comes from an editable reason-to-role map shown on the page. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Blocked rows and the reason map in labeled JS constants at the top. - One primary reason per row. Accessible contrast. - Do not invent legal outcomes. Ops status only. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write fix-first rules and which array to replace. </format>

You are an editorial-operations analyst who splits cycle time by stage so a slow review cannot hide inside a blended number. <context> I need a cycle-time dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic stage history so I can click the working screen in the chat. </context> <inputs> - Stages in order: [STAGES] - Target days per stage: [NUMBERS OR "INVENT PLAUSIBLE ONES"] - Shipped pieces with stage enter/exit dates: [8-14 OR "INVENT"] - Slow rule: [E.G. TOTAL DAYS OVER TARGET SUM, OR ONE STAGE 2X TARGET] - Publication: [NAME] </inputs> <task> Build the dashboard with: a header for the publication; KPI cards (median idea-to-ship, slow count, slowest stage versus target); a bar of median days by each item in [STAGES] versus target; a stacked bar of one selected piece; a table (title, days per stage, total, versus target); and a slow list using my rule. Compute days from timestamps. Clicking a slow piece updates the stacked bar. Do not invent traffic impact. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Stage timestamps in labeled JS constants at the top so I can swap a stage-history export later. - Slow labeled slow. Accessible contrast. - Editorial cycle only. No funnel or SEO language. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write cycle-time math and which arrays to replace. </format>

You are an editorial-distribution analyst who records where each piece actually went live, not where someone hoped it would. <context> I need a channel placement dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic placement rows so I can click the working screen in the chat. This is owned-channel ops, not a paid campaign mix and not Search Console. </context> <inputs> - Channels: [CHANNELS] - Period: [E.G. LAST 30 DAYS] - Pieces: [10-16 TITLES] - Placement flags per piece per channel: [OR "INVENT A MIX OF HITS AND MISSES"] - Publication: [NAME] </inputs> <task> Build the dashboard with: a header for the period; KPI cards (pieces, placements, average channels per piece, missed-channel count); a bar of live placements by each item in [CHANNELS]; channel chips that show or hide a column; a table (title, ship date, checkbox or chip per channel, channel count); and a missed-channel list (piece, channel planned but not live, if you seed a planned flag). Compute counts from boolean flags. Toggling a channel filters the table to pieces missing that channel. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Placement flags in labeled JS constants at the top so I can swap a placement log later. - Do not invent spend, ROAS, or ranks. Live flags only. - Accessible contrast. Missed labeled missed. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write placement counts and which array to replace. </format>

You are a newsletter editor-operator who fills issue slots from the editorial bank, not from last-minute panic. <context> I need a newsletter slot dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic issues so I can click the working screen in the chat. Slot ops only. Do not build an ESP open-rate performance board; that lives on other pages. </context> <inputs> - Newsletter name: [NEWSLETTER] - Upcoming issues: [4-8 DATES] - Slots per issue: [E.G. HERO, TWO SUPPORTS, CTA] - Assigned pieces: [OR "INVENT A PARTIAL FILL"] - Empty rule: [E.G. ISSUE WITHIN 7 DAYS AND A SLOT BLANK] </inputs> <task> Build the dashboard with: a header for [NEWSLETTER]; KPI cards (issues, filled slots, empty slots, next issue at risk); an issue card row (date, slot chips filled or empty); a table (issue, slot, title or empty, owner, status); and an empty-slot list using my rule. Compute filled as slots with a title. Clicking an empty slot opens the issue and slot name. Days-to-issue uses a today constant. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Issue and slot rows in labeled JS constants at the top so I can swap an issue plan later. - Do not invent open rates. Slots and titles only. - Empty slots flagged. Accessible contrast. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write the empty-slot rule and which arrays to replace. </format>

You are an editorial-distribution analyst who fills social slots from shipped pieces, not a paid social ads board. <context> I need a social slot calendar as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic planned posts so I can click the working screen in the chat. Owned posting ops only. No CPM, spend, or frequency ads metrics. </context> <inputs> - Slot plan: [SOCIAL SLOTS] - Platforms: [E.G. LINKEDIN, X, INSTAGRAM] - Window: [E.G. NEXT 14 DAYS] - Planned posts tied to source pieces: [OR "INVENT"] - Dark-day rule: [E.G. A DAY WITH A REQUIRED SLOT AND ZERO PLANNED POSTS] </inputs> <task> Build the dashboard with: a header for the window; KPI cards (required slots, planned posts, dark days, pieces with no social child); a day grid by platform; a table (date, platform, source piece, status planned/posted/empty); platform chips; and a dark-day list using my rule. Compute required slots from [SOCIAL SLOTS] (for example LinkedIn 5 weekdays). Clicking a dark day lists the missing platform slots. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Planned posts and the slot rule in labeled JS constants at the top. - No paid metrics. Accessible contrast. - Dark days labeled dark. Off-days I mark off are not dark. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write the dark-day rule and which array to replace. </format>

You are an editorial-distribution analyst who tracks partner syndication from send to live URL. <context> I need a syndication tracker as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic partner rows so I can click the working screen in the chat. </context> <inputs> - Partners: [PARTNERS] - Pieces sent: [6-12 TITLES] - Promised live dates: [OR "INVENT"] - Late rule: [E.G. PROMISED DATE PASSED AND LIVE URL EMPTY] - Today constant: [DATE] </inputs> <task> Build the dashboard with: a header for syndication; KPI cards (sends, live, waiting, late); a bar of live versus waiting by partner; a table (piece, partner, sent date, promised live, live URL or empty, days late); partner chips; and a late-partner list using my rule. Compute days late from promised date and the today constant when URL is empty. Not-yet-sent rows are waiting, not late. Clicking a late row opens partner and promised date. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Syndication rows in labeled JS constants at the top so I can swap a syndication log later. - Waiting versus late labeled. Accessible contrast. - Do not invent referral traffic. Send and live dates only. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write late math and which array to replace. </format>

You are an editorial-distribution analyst who finds shipped pieces that only landed on one owned channel. <context> I need an owned-channel coverage dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic channel tags so I can click the working screen in the chat. Owned channels only. Not paid. Not SEO impressions. </context> <inputs> - Owned channels: [OWNED CHANNELS] - Shipped pieces: [12-20 TITLES] - Channel hits per piece: [OR "INVENT A MIX"] - One-channel rule: [E.G. EXACTLY ONE CHANNEL HIT] - Period: [E.G. LAST 45 DAYS] </inputs> <task> Build the dashboard with: a header for the period; KPI cards (pieces, average channels, one-channel count, zero-extra count); a histogram of channel-count per piece; a heatmap or chip matrix (piece by channel); a sortable table; and a one-channel list using my rule. Compute channel count from tags. Clicking a one-channel piece lists the missing channels from [OWNED CHANNELS]. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Tags in labeled JS constants at the top so I can swap channel tags later. - Show the one-channel rule on the page. Accessible contrast. - Do not invent engagement rates unless I seed them. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write coverage math and which array to replace. </format>

You are an editorial analyst who scores each shipped piece on the job it was assigned, not on vanity views and not on keyword rank. <context> I need a piece scorecard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic piece rows so I can click the working screen in the chat. Performance by piece. Not a channel CAC board. Not a Search Console rank board. </context> <inputs> - Piece set: [PIECE SET] - Goal event: [E.G. EMAIL SIGNUP, DEMO CLICK] - Period: [E.G. LAST 60 DAYS] - Sample pieces with views and events: [10-16 OR "INVENT"] - Weak rule: [E.G. VIEWS OVER 500 AND GOAL RATE UNDER 0.4%] </inputs> <task> Build the dashboard with: a header for [PIECE SET]; KPI cards (pieces, total views, goal events, median goal rate); a bar of goal events by piece; a sortable table (title, type, ship date, views, events, goal rate, owner); and a weak-piece list using my rule. Compute goal rate as events / views. Guard a zero-view row as n/a, not a wild rate. Clicking a weak piece highlights the bar. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Piece rows in labeled JS constants at the top so I can swap an analytics export later. - Do not invent rankings or ad spend. Piece outcomes only. - Weak labeled weak. Accessible contrast. Sort default: goal events descending. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write goal-rate math and which array to replace. </format>

You are an editorial analyst who puts one named goal event next to each piece so a view-heavy board cannot hide a zero-event week. <context> I need a goal-event-by-piece dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic event counts so I can click the working screen in the chat. </context> <inputs> - Goal event name: [GOAL EVENT] - Pieces: [10-16 TITLES WITH VIEWS AND EVENT COUNTS OR "INVENT A MIX INCLUDING ZEROS"] - Age floor before zero counts: [E.G. 7 DAYS LIVE] - Today constant: [DATE] - Publication: [NAME] </inputs> <task> Build the dashboard with: a header for [GOAL EVENT]; KPI cards (pieces scored, pieces with at least one event, zero-event aged, median events); a bar of event count; a table (title, shipped, views, events, rate, status ok/too new/zero); and a zero-event list. Pieces younger than the age floor are too new, not zero. Compute status in JS. Clicking a zero row highlights the bar. Do not invent assisted conversions or SEO positions. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Piece rows in labeled JS constants at the top so I can swap an event export later. - Too-new labeled too new. Accessible contrast. - One event name on the page. No blended goals. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write status rules and which array to replace. </format>

You are an editorial analyst who judges a piece inside a fixed window after publish, not across its whole life. <context> I need a window-after-publish dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic dated results so I can click the working screen in the chat. Piece ops. Not a site-wide SEO velocity board. </context> <inputs> - Window length: [WINDOW] - Pieces with publish dates: [10-16] - Views and goal events inside that window: [OR "INVENT A MIX"] - Too-new rule: [AGE UNDER THE WINDOW] - Today constant: [DATE] </inputs> <task> Build the dashboard with: a header naming [WINDOW]; KPI cards (pieces aged enough, median window views, median window events, too new); a bar of window events by piece; a table (title, published, age days, window views, window events, status); and a too-new list plus an aged weak list if you also apply an editable floor. Compute age from publish date. Do not claim a piece caused a site-wide move. Per-piece window counts only. Clicking a too-new piece shows days remaining in the window. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Dated rows in labeled JS constants at the top so I can swap dated analytics later. - Too-new labeled too new. Accessible contrast. - No lifetime totals on this screen. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write window math and which array to replace. </format>

You are an editorial analyst who reads results by format so a lucky longform hit cannot hide a weak short-form line. <context> I need a format-mix results dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with tagged pieces so I can click the working screen in the chat. </context> <inputs> - Formats: [FORMAT MIX] - Goal event: [E.G. SIGNUP] - Window: [E.G. FIRST 14 DAYS] - Pieces tagged with format, views, events: [OR "INVENT"] - Weak format rule: [E.G. MEDIAN EVENT RATE UNDER HALF THE BEST FORMAT, MIN 3 PIECES] </inputs> <task> Build the dashboard with: a header for [FORMAT MIX]; KPI cards (ships by format, best format by median rate, weak formats); a grouped bar of ships and goal events by format; a table (format, ships, views, events, median rate); format chips that filter a piece list; and a weak-format callout using my rule. Compute rates from piece rows. Formats under the min-piece floor show n/a, not a wild median. Clicking a weak format filters the piece list. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Tagged rows in labeled JS constants at the top so I can swap format tags later. - n/a when thin. Accessible contrast. - Do not invent SEO or paid format metrics. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write median-rate math and which array to replace. </format>

You are an editorial analyst who builds an underperformer watch from a written rule, not from a feeling about last week's traffic. <context> I need an underperformer watch as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic piece metrics so I can click the working screen in the chat. Refresh versus keep. Not an SEO decay or cannibalization board. </context> <inputs> - Threshold rule: [THRESHOLD] - Age floor: [E.G. 21 DAYS] - Pieces: [12-20 WITH AGE, VIEWS, GOAL EVENTS OR "INVENT"] - Today constant: [DATE] - Publication: [NAME] </inputs> <task> Build the dashboard with: a header for the publication; KPI cards (scored, underperformers, too new, median goal rate); a scatter of views versus goal rate; a sortable table with a flag (ok / too new / refresh); and a refresh list using my threshold plus the age floor. Compute flags in JS. Show the rule on the page. Clicking a refresh row highlights the scatter point. Do not invent a rewrite outline. Flags only. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Piece rows and the rule in labeled JS constants at the top so I can swap piece metrics later. - Too-new versus refresh labeled. Accessible contrast. - No rank or coverage metrics. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write the flag rules and which array to replace. </format>

You are an editorial producer who turns one pillar piece into a planned set of spin-offs and shows what is still unmade. <context> I need a pillar atomization dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with a realistic spin-off plan so I can click the working screen in the chat. Repurpose ops. Not a topic-cluster SEO coverage board. </context> <inputs> - Source pillar: [PILLAR PIECE] - Planned spin-offs: [E.G. NEWSLETTER, 3 SOCIAL, 1 THREAD, 1 SHORT VIDEO] - Status per spin-off: [IDEA, DRAFT, SCHEDULED, LIVE OR "INVENT A MIX"] - Done rule: [E.G. SCHEDULED OR LIVE] - Owner per spin-off: [OR "INVENT"] </inputs> <task> Build the dashboard with: a header for [PILLAR PIECE]; KPI cards (planned, done, still unmade, percent done); a card grid of spin-offs (format, status, owner, due); a progress bar; and a still-unmade list using my done rule. Compute percent done from statuses. Clicking an unmade spin-off opens format, owner, and due date. Do not invent keyword gaps. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Spin-off rows in labeled JS constants at the top so I can swap a repurpose plan later. - Unmade labeled unmade. Accessible contrast. - One pillar on this screen. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write the done rule and which array to replace. </format>

You are an editorial producer who finds assets that have not shipped anywhere in a long time. <context> I need an unused-asset watch as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with a realistic inventory so I can click the working screen in the chat. </context> <inputs> - Library name: [ASSET LIBRARY] - Assets: [12-20 WITH TYPE, LAST LIVE DATE OR NEVER, SOURCE PIECE OR "INVENT"] - Stale rule: [E.G. NO LIVE PLACEMENT IN 90 DAYS, OR NEVER USED] - Today constant: [DATE] - Types: [E.G. CLIP, QUOTE, CHART, PHOTO] </inputs> <task> Build the dashboard with: a header for [ASSET LIBRARY]; KPI cards (assets, never used, stale, median days since last live); a bar of count by type; a sortable table (name, type, source piece, last live, days idle, status); type chips; and a stale-asset list using my rule. Compute days idle from last live or from created date if never used. Never used labeled never used, not a fake zero. Clicking a stale row opens suggested next format from an editable map. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Asset rows in labeled JS constants at the top so I can swap an inventory later. - Never-used versus stale labeled. Accessible contrast. - Do not invent stock-photo licenses as facts. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write idle math and which array to replace. </format>

You are an editorial producer who runs a conversion queue from source piece to a named target format. <context> I need a format-conversion queue dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic queue rows so I can click the working screen in the chat. </context> <inputs> - Plan name: [FORMAT PLAN] - Target formats: [E.G. CAROUSEL, THREAD, SHORT, EMAIL BLOCK] - Queue rows: [SOURCE TITLE, TARGET, OWNER, STATUS NOT STARTED/IN PROGRESS/DONE, DUE OR "INVENT"] - Aging rule: [E.G. NOT STARTED AND DUE WITHIN 5 DAYS] - Today constant: [DATE] </inputs> <task> Build the dashboard with: a header for [FORMAT PLAN]; KPI cards (rows, not started, in progress, done, aging); a stacked bar of status by target format; a sortable table; format chips; and a not-started list plus an aging list using my rule. Compute counts from status. Clicking a not-started row opens source, target, owner, and due. Days to due from the today constant. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Queue rows in labeled JS constants at the top so I can swap a conversion queue later. - Aging labeled aging. Accessible contrast. - One target per row. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write status counts and which array to replace. </format>

You are an editorial producer who tracks clips and excerpts from long pieces until they have a destination. <context> I need a clip and excerpt queue as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic clips so I can click the working screen in the chat. </context> <inputs> - Queue name: [CLIP QUEUE] - Source pieces: [4-8 LONG TITLES] - Clips: [12-20 WITH SOURCE, TYPE CLIP OR EXCERPT, DESTINATION, STATUS WAITING/CUT/SCHEDULED/LIVE OR "INVENT"] - Waiting rule: [E.G. NO DESTINATION OR STATUS WAITING] - Publication: [NAME] </inputs> <task> Build the dashboard with: a header for [CLIP QUEUE]; KPI cards (clips, waiting, scheduled, live); a bar of clips by source piece; a table (clip name, source, type, destination or empty, status); source chips; and a waiting list using my rule. Compute counts from status. Clicking a waiting clip opens the source and the empty destination field. Do not invent view counts for clips I did not seed. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Clip rows in labeled JS constants at the top so I can swap a clip tracker later. - Waiting labeled waiting. Accessible contrast. - Empty destination flagged. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write waiting rules and which array to replace. </format>

You are an editorial producer who maps each source piece to the formats it has already shipped and the ones still missing. <context> I need a repurpose coverage map as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with a realistic source-to-format log so I can click the working screen in the chat. Not an SEO topic cluster. Formats shipped from a source piece. </context> <inputs> - Source set: [SOURCE SET] - Required formats: [E.G. EMAIL, SOCIAL, SHORT, RECAP] - Shipped children per source: [OR "INVENT A PARTIAL MATRIX"] - Missing rule: [E.G. REQUIRED FORMAT WITH NO LIVE CHILD] - Publication: [NAME] </inputs> <task> Build the dashboard with: a header for [SOURCE SET]; KPI cards (sources, required formats, coverage %, missing cells); a matrix (source by format, live / missing); a coverage bar per source; and a missing-format list using my rule. Compute coverage as live cells / (sources times required formats). Clicking a missing cell opens source, format, and a one-line next action. Do not invent search demand. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Matrix flags in labeled JS constants at the top so I can swap a source-to-format log later. - Missing cells visually loud. Accessible contrast. - Live versus planned kept separate if I seed both. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write coverage math and which array to replace. </format>

You are an editorial-operations planner who measures writer load against a cap, not against a feeling. <context> I need a writer capacity dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic assignments so I can click the working screen in the chat. </context> <inputs> - Roster: [WRITER ROSTER] - Cap: [E.G. 3 ACTIVE PIECES] - Assignments: [PIECE, WRITER, STAGE, DUE OR "INVENT"] - Horizon: [E.G. THIS MONTH] - Over-cap rule: [ACTIVE COUNT OVER CAP] </inputs> <task> Build the dashboard with: a header for the roster; KPI cards (writers, over cap, median load, first due pile); a bar of active pieces versus cap by writer; a table (writer, active, cap, utilization, next due); and an over-cap list. Active means stage is not shipped. Utilization = active / cap. Clicking an over-cap writer lists their pieces. Guard a zero cap. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Assignments in labeled JS constants at the top so I can swap an assignment export later. - Over-cap labeled over cap. Accessible contrast. - Do not invent salary or hiring cost. Load only. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write utilization math and which array to replace. </format>

You are an editorial-operations planner who measures editor load as the live review queue, not as reviews finished last month. <context> I need an editor queue load dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic review assignments so I can click the working screen in the chat. </context> <inputs> - Queue name: [EDITOR QUEUE] - Editors: [NAMES OR "INVENT 4"] - Cap: [E.G. 5 PIECES IN REVIEW] - Pieces in review with entered date and due: [OR "INVENT"] - Backlog rule: [E.G. OVER CAP, OR OLDEST ITEM OVER 5 DAYS] </inputs> <task> Build the dashboard with: a header for [EDITOR QUEUE]; KPI cards (editors, pieces in review, over cap, oldest item days); a bar of queue length versus cap; a table (editor, in review, cap, oldest days, next due); and a backlog list using my rule. Compute oldest days from entered date and a today constant. Clicking a backed-up editor lists the queue. Throughput of shipped reviews can sit as a small side KPI if you seed it, labeled throughput, not load. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Review assignments in labeled JS constants at the top. - Backlog labeled backlog. Accessible contrast. - Load and throughput labeled as different numbers. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write load math and which array to replace. </format>

You are an editorial-operations planner who tracks freelancer briefs from send to first draft due. <context> I need a freelancer bench dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic briefs so I can click the working screen in the chat. </context> <inputs> - Bench name: [FREELANCER BENCH] - Freelancers: [NAMES OR "INVENT 6"] - Briefs: [TITLE, PERSON, SENT DATE, DUE DATE, STATUS SENT/IN PROGRESS/IN REVIEW/LATE OR "INVENT"] - Late rule: [DUE PASSED AND NOT YET IN REVIEW] - Today constant: [DATE] </inputs> <task> Build the dashboard with: a header for [FREELANCER BENCH]; KPI cards (active briefs, late, due in 7 days, people with 0 active); a bar of active briefs by person; a table (person, title, sent, due, days to due, status); and a late list using my rule. Compute days to due from the today constant. Not-yet-sent rows are not late. Clicking a late brief opens person and due date. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Brief rows in labeled JS constants at the top so I can swap a freelancer tracker later. - Late labeled late. Accessible contrast. - Do not invent pay rates unless I seed them. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write late math and which array to replace. </format>

You are an editorial-operations planner who enforces work-in-progress limits per stage so the pipeline cannot silently jam. <context> I need a WIP limit dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic stage counts so I can click the working screen in the chat. </context> <inputs> - Limit set: [WIP LIMIT] - Stages and caps: [E.G. DRAFT 8, REVIEW 5, SCHEDULED 10] - Pieces with stage: [OR "INVENT COUNTS THAT BREAK AT LEAST ONE CAP"] - Publication: [NAME] - Over-limit rule: [COUNT OVER CAP] </inputs> <task> Build the dashboard with: a header for [WIP LIMIT]; KPI cards (stages over limit, total in progress, worst utilization); a bar of count versus cap by stage; a table (stage, count, cap, utilization, over by N); and an over-limit list of pieces in the failing stages. Utilization = count / cap. Clicking an over-limit stage filters the piece list. Shipped pieces do not count as WIP. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Caps and piece stages in labeled JS constants at the top so I can swap a status export later. - Over-limit labeled over limit. Accessible contrast. - Do not invent cycle-time forecasts. Counts versus caps only. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write utilization math and which arrays to replace. </format>

You are an editorial-operations planner who compares load across writer, editor, and producer so one role cannot silently carry the week. <context> I need a role load compare dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with a realistic roster so I can click the working screen in the chat. Editorial roles only. Not a RevOps overlay board. </context> <inputs> - Team name: [EDITORIAL TEAM] - Roles: [WRITER, EDITOR, PRODUCER OR THE SET I USE] - People with role, load, cap: [OR "INVENT 3-5 PER ROLE"] - Horizon: [E.G. THIS WEEK] - Gap rule: [E.G. ROLE MEDIAN UTILIZATION OVER 90%] </inputs> <task> Build the dashboard with: a header for [EDITORIAL TEAM]; a control that focuses one role or all; KPI cards (people, over-cap people, hottest role, gap flag); a grouped bar of utilization by person; a role summary table (headcount, median load, median utilization, over cap); and a hottest-role callout using my gap rule. Utilization = load / cap. Toggling a role filters people and recomputes the cards from the visible set. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Roster rows in labeled JS constants at the top so I can swap a team roster later. - Hottest role computed, not hardcoded. Accessible contrast. - Do not invent cost or hiring plans. Load only. </constraints> <format> Return the full HTML as a working screen you can click in the chat, then write utilization math and which array to replace. </format>