https://palette.team/_next/static/chunks/1uo93f5mvzd89.js

1(globalThis.TURBOPACK||(globalThis.TURBOPACK=[])).push(["object"==typeof document?document.currentScript:void 0,10435,e=>{"use strict";var t=e.i(18043),a=e.i(79534),s=e.i(60357);let i={name:"copy",size:24,node:[["rect",{width:"14",height:"14",x:"8",y:"8",rx:"2",ry:"2",key:"17jyea"}],["path",{d:"M4 16c-1.1 0-2-.9-2-2V4c0-1.1.9-2 2-2h10c1.1 0 2 .9 2 2",key:"zix9uf"}]]};i.node;let n=(0,s.default)(i);var o=e.i(8801),r=e.i(75157);e.s(["CopyButton",0,function({value:e,label:s="Copy",children:i,className:l}){let[d,c]=(0,a.useState)(!1),h=async()=>{try{await navigator.clipboard.writeText(e),c(!0),setTimeout(()=>c(!1),1600)}catch{}};return(0,t.jsx)("button",{type:"button",onClick:h,"aria-label":d?"Copied":s,"aria-live":"polite",className:(0,r.cn)("inline-flex min-h-11 shrink-0 touch-manipulation items-center gap-1.5 rounded-full border border-line bg-panel px-3 py-1.5 text-xs font-medium leading-none text-surface-700 transition-colors hover:border-surface-300 hover:bg-panel-muted focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-focus",l),children:d?(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(o.Check,{className:"h-3.5 w-3.5 text-success","aria-hidden":"true"}),"Copied"]}):(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n,{className:"h-3.5 w-3.5","aria-hidden":"true"}),i??"Copy"]})})}],10435)},54961,e=>{"use strict";var t=e.i(18043),a=e.i(79534),s=e.i(1356),i=e.i(60357);let n={name:"chevron-down",size:24,node:[["path",{d:"m6 9 6 6 6-6",key:"qrunsl"}]]};n.node;let o=(0,i.default)(n),r=[{id:"risk-pulse",title:"Risk pulse panel",description:"A live dashboard of active risks, unowned work, stretched teammates, and meetings whose outcomes haven't been captured yet.",output:"Standalone HTML panel with an impact × staleness scatter plot, ranked risks with per-row action buttons that send follow-up prompts back to Claude, a recent-events list, and a people-watch grid.",tags:["Panel","Leadership","Weekly"],image:"/images/docs/premade-setups/risk-pulse.png",prompt:`You have access to my organization's context via Palette MCP. Build me a "risk pulse" panel as a single self-contained HTML file I can open in a browser.
2
3Query Palette for:
4- All active risks, blockers, stalled initiatives, and unowned workstreams across the org
5- Recent calendar events (customer meetings, investor calls, partner syncs) whose outcomes haven't been logged back into Palette yet
6- People who look stretched — three or more active workstreams, multiple "needs owner" items landing on them, or declined recurring check-ins
7- Freshness: when the orgtology last re-synthesized and whether there are unsynthesized signals
8
9For each risk, score it on impact (critical / high / medium / low) and days since last action. Flag any risk with no DRI as "needs owner".
10
11Output requirements:
12- A single HTML file with embedded CSS, no external dependencies, dark-mode aware via prefers-color-scheme
13- Top banner if the orgtology is stale (>7 days since last synthesis)
14- Summary stats row: active risks, unowned count, people stretched, events past last sync
15- An SVG scatter plot of risks positioned by impact (y) and days since last action (x), with a highlighted "act now" zone in the top-right
16- A ranked list of risks. Each row must include: title, category pill (customer, product, tech, infra, ops, meta), owner or "needs owner" badge, staleness, and a context-specific action button
17- For every action button, wire an onClick that calls a sendPrompt(text) function I define at the bottom of the file. The prompt should be the exact next step to take — e.g. "Draft a Slack message to Steffen asking for the production dashboard API token" or "Open a Linear bug for the people-mixup issue with examples from Slack". Make the prompts specific to the risk, not generic.
18- An "events since last sync" section — calendar events whose outcomes haven't been captured, each with a "capture follow-ups" button that triggers a prompt to interview me and log signals back to Palette
19- A "people watch" grid showing stretched / watch / ok badges per teammate, with a "triage their load" action button where relevant
20- Use a neutral design palette (off-white backgrounds, subtle borders, category-specific pill colors). Headings at ~13-14px, body copy at ~12-14px. No emojis.
21

22Ground every row in real Palette context — cite dates, ticket IDs, PR numbers, and owner initials from the orgtology. If something is unknown, surface the unknown rather than inventing a value.`},{id:"focus-board",title:"Team focus board",description:"A visual gravity map showing where the team's attention is right now — workstreams as suns, teammates as planets orbiting their primary focus.",output:"Standalone HTML page with an SVG orbital diagram (workstreams sized by activity, pulse rings on the hottest, dashed lines for secondary contributions), a legend, and a recent-activity feed sourced from orgtology signals.",tags:["Panel","Team","Visual"],prompt:`You have access to my team's orgtology via Palette MCP. Build me a "focus board" as a single self-contained HTML file that visualizes where the team's attention is this week.
23
24Query Palette for:
25- All active workstreams (not just Linear projects — include "discovered" work from check-ins and Slack)
26- For each workstream: primary owner, secondary contributors, activity level in the last 14 days (PR merges, Slack mentions, Linear updates, meeting references)
27- Every teammate on the team, their primary focus area, and any secondary areas they've been active in
28
29Output requirements:
30- Single HTML file with embedded CSS and inline SVG, dark-mode aware
31- An SVG "gravity" diagram on a dark starfield canvas:
32  - Each workstream rendered as a colored sun, sized proportional to its recent activity
33  - Pulse rings (animated, via <animate> tags) on the two or three hottest workstreams
34  - Each teammate as a small planet positioned near their primary workstream, labeled with their initial and name
35  - Dashed connector lines from each teammate to any secondary workstream they've also contributed to this week
36  - The viewer (me) gets a thicker ring so I can spot myself immediately
37- A legend panel beneath explaining the color coding (engineering, GTM, product, platform, distribution) and what sun size / pulse rings / dashed lines mean
38- A "recent activity" feed panel (7-10 rows) listing dated signals that shaped the picture, each attributing the people involved
39- Use a calm off-white / warm-paper palette for the surrounding UI and a deep navy canvas for the orbital diagram itself. Readable at small sizes on mobile.
40- Header includes a live-snapshot timestamp and the source ("Palette orgtology")
41
42Only render workstreams and people that Palette has real signal for in the last ~14 days. If the team is smaller than expected, render what exists — don't pad.`},{id:"weekly-digest",title:"Weekly shipped digest",description:"A shareable recap of what shipped this week across the team, with the decisions behind each move — drafted in your team's voice.",output:"Standalone HTML digest with sections for shipped work, decisions logged, unblocked items, and next-week focus. Links out to PRs and tickets. Designed to be copy-pasted into Slack, an email, or a Notion page.",tags:["Panel","Weekly","Reporting"],prompt:`Using my Palette MCP context, build me a "this week in review" digest as a single self-contained HTML page I can share.
43
44Query Palette for:
45- Everything shipped this week across the team — merged PRs, closed tickets, released versions, deployed features, feature-flag rollouts to customers
46- Decisions logged or captured as signals this week, with the rationale
47- Items that became unblocked (work that was stalled and moved)
48- Customer / partner signals — new onboardings, feedback that landed, meetings with outcomes
49- What's queued for next week based on current in-progress work and stated priorities
50
51Output requirements:
52- Single HTML file, embedded CSS, dark-mode aware, readable at A4 width
53- Header with team name (from orgtology), week-of date, and a one-line tagline summarizing the week in under 15 words
54- Four sections: Shipped \xb7 Decided \xb7 Unblocked \xb7 Next. Each item in a section is two lines max: the what + the why / evidence
55- Every shipped item links to its PR or ticket. Every decision credits who made the call.
56- Group shipped work by workstream (from orgtology), not by person. Lead with the most customer-visible items.
57- Match the team's communication voice based on how they actually write in Slack and PRs — terse, evidence-first, no marketing language. Lift real phrasing if orgtology surfaces it.
58- A small "by the numbers" row at the bottom — PRs merged, decisions logged, customer-facing changes, releases shipped
59- Design: clean typographic layout, generous whitespace, a single accent color drawn from the team's brand if detectable
60
61If a section is thin or empty, say so plainly ("Nothing logged this week") rather than 

61inventing items. Flag any week where the orgtology appears stale.`},{id:"onboarding-packet",title:"New-hire onboarding packet",description:"A personalized first-week briefing for a new teammate — who's who, what the team is working on, rituals to attend, and the reads that will catch them up fastest.",output:"Standalone HTML packet with a team roster, current priorities and initiatives, rituals and cadences, a recommended first-week reading list with links, and the top open questions worth asking in week one.",tags:["Panel","Onboarding","Team"],prompt:`Using my Palette MCP context, build a first-week onboarding packet for a new hire joining my team. Ask me two questions first: (1) the new hire's name and role, (2) their start date. Then produce the packet as a single self-contained HTML file.
62
63Query Palette for:
64- The team's current structure, leadership, and every teammate's role, focus, strengths, and what they're actively working on
65- Current team priorities and active workstreams — ranked by importance, with a one-line "why this matters" for each
66- Rituals and cadences: what meetings the new hire will be invited to, whether they're pre-read / show-up / optional, and who runs each one
67- The recent decisions that shape current work — the rationale the new hire needs to pick up without interrupting anyone
68- Tool landscape and where work lives (Linear, Slack channels, GitHub repos, Notion spaces)
69- The top three open questions or unresolved debates the team is sitting with
70
71Output requirements:
72- Single HTML file, embedded CSS, dark-mode aware, print-friendly
73- Personalized header: "Welcome, <name> — here's your first week"
74- Sections, in order:
75  1. Who you'll be working with (the roster — name, role, strengths, what they're focused on, how to ping them). Mark teammates the hire should proactively meet in week one.
76  2. What the team is working on right now — priorities and active workstreams, each with evidence (tickets, recent merges)
77  3. Rituals and cadences — table or grid with meeting name, when, who runs it, and whether pre-read is expected
78  4. Reading list — 5-8 items, each with title, source (Notion doc / Linear project / PR / Slack thread), a one-line why-it-matters, and a link
79  5. Open questions worth asking this week — things the team itself hasn't resolved and would appreciate a fresh perspective on
80  6. A small "by end of week one, you should be able to…" checklist
81- No aspirational filler. If the orgtology doesn't have enough signal on something (e.g. a teammate's strengths), say so rather than fabricating.
82- Tone: warm and specific. Written as if I'm briefing them myself.
83
84At the bottom, include a small "this packet was assembled from Palette orgtology on <date>" footer with the snapshot source.`}];var l=e.i(10435);function d({setup:e,defaultOpen:i}){let[n,r]=(0,a.useState)(!!i),c=`premade-setup-body-${e.id}`;return(0,t.jsxs)("div",{className:"overflow-hidden rounded-lg bg-white shadow-default",children:[(0,t.jsxs)("div",{className:"relative",children:[(0,t.jsxs)("button",{type:"button","aria-expanded":n,"aria-controls":c,onClick:()=>r(e=>!e),className:"block w-full cursor-pointer text-left focus-visible:outline-2 focus-visible:outline-offset-[-2px] focus-visible:outline-focus",children:[(0,t.jsx)("div",{className:"relative aspect-[5/1] w-full border-b border-surface-200 bg-surface-100",children:e.image&&(0,t.jsx)(s.default,{src:e.image,alt:"",fill:!0,sizes:"(min-width: 768px) 640px, 100vw",className:"object-cover"})}),(0,t.jsxs)("div",{className:"flex items-start justify-between gap-4 px-5 py-4 pr-28",children:[(0,t.jsxs)("div",{className:"min-w-0",children:[(0,t.jsx)("h3",{className:"font-heading text-lg font-bold leading-snug text-surface-900",children:e.title}),(0,t.jsx)("p",{className:"mt-1 text-sm leading-relaxed text-surface-600",children:e.description}),(0,t.jsx)("div",{className:"mt-3 flex flex-wrap gap-1.5",children:e.tags.map(e=>(0,t.jsx)("span",{className:"inline-flex rounded-full bg-surface-100 px-2.5 py-0.5 text-xs font-medium text-surface-700",children:e},e))})]}),(0,t.jsx)(o,{"aria-hidden":"true",className:`mt-1 h-4 w-4 shrink-0 text-surface-500 transition-transform motion-reduce:transition-none ${n?"rotate-180":""}`})]})]}),(0,t.jsx)("div",{className:"absolute bottom-4 right-5",children:(0,t.jsx)(l.CopyButton,{value:e.prompt,label:"Copy prompt"})})]}),n&&(0,t.jsxs)("div",{id:c,className:"border-t border-surface-200 px-5 py-4",children:[(0,t.jsx)("p",{className:"text-xs font-semibold uppercase tracking-wide text-surface-500",children:"What it produces"}),(0,t.jsx)("p",{className:"mt-2 text-sm leading-relaxed text-surface-700",children:e.output})]})]})}e.s(["PremadeSetups",0,function(){return(0,t.jsxs)("div",{className:"my-8",children:[(0,t.jsx)("p",{className:"text-base leading-7 text-surface-600",children:"Larger copy-paste prompts that turn your Palette context into full, self-contained panels. Paste any of them into Claude with Palette MCP connected — Claude queries your orgtology, shapes the data, and returns a standalone HTML artifact you can open, share, or embed."}),(0,t.jsx)("div",{className:"mt-8 space-y-4",children:r.map((e,a)=>(0,t.jsx)(d,{setup:e,defaultOpen:0===a},e.id))})]})}],54961)}]);