@ctxthuta/cxops 1.0.6 → 1.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (94) hide show
  1. package/.antigravity-plugin/plugin.json +34 -0
  2. package/.claude-plugin/marketplace.json +20 -0
  3. package/.claude-plugin/plugin.json +25 -0
  4. package/.codex-plugin/plugin.json +50 -0
  5. package/CLAUDE.md +94 -0
  6. package/assets/antigravity-logo.png +0 -0
  7. package/assets/app-icon.png +0 -0
  8. package/assets/superpowers-small.svg +1 -0
  9. package/hooks/hooks-cursor.json +10 -0
  10. package/hooks/hooks.json +18 -0
  11. package/hooks/run-hook.cmd +79 -0
  12. package/hooks/session-start +90 -0
  13. package/package.json +13 -2
  14. package/plugin/plugin.json +25 -14
  15. package/plugin/skills/brainstorming/SKILL.md +316 -0
  16. package/plugin/skills/brainstorming/builder-check-prompt.md +23 -0
  17. package/plugin/skills/brainstorming/scripts/frame-template.html +213 -0
  18. package/plugin/skills/brainstorming/scripts/helper.js +167 -0
  19. package/plugin/skills/brainstorming/scripts/server.cjs +723 -0
  20. package/plugin/skills/brainstorming/scripts/start-server.sh +216 -0
  21. package/plugin/skills/brainstorming/scripts/stop-server.sh +120 -0
  22. package/plugin/skills/brainstorming/visual-companion.md +299 -0
  23. package/plugin/skills/diagnosing-superpowers/SKILL.md +120 -0
  24. package/plugin/skills/diagnosing-superpowers/prompts/analyst-common.md +38 -0
  25. package/plugin/skills/diagnosing-superpowers/prompts/cost-and-time.md +28 -0
  26. package/plugin/skills/diagnosing-superpowers/prompts/plan-adherence.md +29 -0
  27. package/plugin/skills/diagnosing-superpowers/prompts/quality-evidence.md +26 -0
  28. package/plugin/skills/diagnosing-superpowers/prompts/repeated-work.md +30 -0
  29. package/plugin/skills/diagnosing-superpowers/prompts/request-conflicts.md +20 -0
  30. package/plugin/skills/diagnosing-superpowers/prompts/scrub-audit.md +33 -0
  31. package/plugin/skills/diagnosing-superpowers/prompts/scrub.md +29 -0
  32. package/plugin/skills/diagnosing-superpowers/prompts/similar-session.md +38 -0
  33. package/plugin/skills/diagnosing-superpowers/prompts/skill-timeline.md +30 -0
  34. package/plugin/skills/diagnosing-superpowers/prompts/stumbles.md +28 -0
  35. package/plugin/skills/diagnosing-superpowers/references/context-safety.md +22 -0
  36. package/plugin/skills/diagnosing-superpowers/references/github-issues.md +47 -0
  37. package/plugin/skills/diagnosing-superpowers/references/redaction-policy.md +34 -0
  38. package/plugin/skills/diagnosing-superpowers/references/session-discovery.md +31 -0
  39. package/plugin/skills/diagnosing-superpowers/templates/bundle-README.md +77 -0
  40. package/plugin/skills/diagnosing-superpowers/templates/case.md +64 -0
  41. package/plugin/skills/diagnosing-superpowers/templates/issue.md +70 -0
  42. package/plugin/skills/diagnosing-superpowers/templates/report.md +82 -0
  43. package/plugin/skills/dispatching-parallel-agents/SKILL.md +167 -0
  44. package/plugin/skills/executing-plans/SKILL.md +323 -0
  45. package/plugin/skills/executing-plans/scripts/task-done +55 -0
  46. package/plugin/skills/executing-plans/scripts/task-start +32 -0
  47. package/plugin/skills/finishing-a-development-branch/SKILL.md +225 -0
  48. package/plugin/skills/receiving-code-review/SKILL.md +205 -0
  49. package/plugin/skills/requesting-code-review/SKILL.md +95 -0
  50. package/plugin/skills/requesting-code-review/code-reviewer.md +198 -0
  51. package/plugin/skills/subagent-driven-development/SKILL.md +339 -0
  52. package/plugin/skills/subagent-driven-development/implementer-prompt.md +154 -0
  53. package/plugin/skills/subagent-driven-development/re-review-prompt.md +116 -0
  54. package/plugin/skills/subagent-driven-development/references/batching.md +11 -0
  55. package/plugin/skills/subagent-driven-development/references/cannot-verify.md +10 -0
  56. package/plugin/skills/subagent-driven-development/references/final-review.md +49 -0
  57. package/plugin/skills/subagent-driven-development/references/fix-loop.md +77 -0
  58. package/plugin/skills/subagent-driven-development/references/handling-reports.md +15 -0
  59. package/plugin/skills/subagent-driven-development/references/preflight.md +26 -0
  60. package/plugin/skills/subagent-driven-development/references/resuming.md +12 -0
  61. package/plugin/skills/subagent-driven-development/scripts/review-package +64 -0
  62. package/plugin/skills/subagent-driven-development/scripts/sdd-repo +54 -0
  63. package/plugin/skills/subagent-driven-development/scripts/sdd-workspace +110 -0
  64. package/plugin/skills/subagent-driven-development/scripts/task-brief +108 -0
  65. package/plugin/skills/subagent-driven-development/task-reviewer-prompt.md +209 -0
  66. package/plugin/skills/systematic-debugging/SKILL.md +283 -0
  67. package/plugin/skills/systematic-debugging/condition-based-waiting-example.ts +158 -0
  68. package/plugin/skills/systematic-debugging/condition-based-waiting.md +115 -0
  69. package/plugin/skills/systematic-debugging/defense-in-depth.md +122 -0
  70. package/plugin/skills/systematic-debugging/find-polluter.sh +72 -0
  71. package/plugin/skills/systematic-debugging/root-cause-tracing.md +169 -0
  72. package/plugin/skills/test-driven-development/SKILL.md +330 -0
  73. package/plugin/skills/test-driven-development/writing-good-tests.md +198 -0
  74. package/plugin/skills/using-git-worktrees/SKILL.md +167 -0
  75. package/plugin/skills/using-superpowers/SKILL.md +65 -0
  76. package/plugin/skills/using-superpowers/references/antigravity-tools.md +23 -0
  77. package/plugin/skills/using-superpowers/references/claude-code-tools.md +29 -0
  78. package/plugin/skills/using-superpowers/references/codex-tools.md +108 -0
  79. package/plugin/skills/using-superpowers/references/gemini-tools.md +63 -0
  80. package/plugin/skills/using-superpowers/references/hermes-tools.md +56 -0
  81. package/plugin/skills/using-superpowers/references/muse-tools.md +35 -0
  82. package/plugin/skills/using-superpowers/references/pi-tools.md +16 -0
  83. package/plugin/skills/verification-before-completion/SKILL.md +120 -0
  84. package/plugin/skills/writing-plans/SKILL.md +204 -0
  85. package/plugin/skills/writing-skills/SKILL.md +399 -0
  86. package/plugin/skills/writing-skills/references/CLAUDE_MD_TESTING.md +189 -0
  87. package/plugin/skills/writing-skills/references/anthropic-best-practices.md +1150 -0
  88. package/plugin/skills/writing-skills/references/bulletproofing.md +80 -0
  89. package/plugin/skills/writing-skills/references/discovery.md +201 -0
  90. package/plugin/skills/writing-skills/references/flowcharts.md +37 -0
  91. package/plugin/skills/writing-skills/references/graphviz-conventions.dot +172 -0
  92. package/plugin/skills/writing-skills/references/persuasion-principles.md +187 -0
  93. package/plugin/skills/writing-skills/references/testing-skills-with-subagents.md +384 -0
  94. package/plugin/skills/writing-skills/render-graphs.js +169 -0
@@ -0,0 +1,316 @@
1
+ ---
2
+ name: brainstorming
3
+ description: "You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation)."
4
+ ---
5
+
6
+ # Brainstorming
7
+
8
+ You are very good at building. You build what you believe your human
9
+ partner wants, and that belief is usually thinner than it feels. This
10
+ skill is for finding out what they actually want, and why, before
11
+ anything gets built.
12
+
13
+ People often haven't finished working out what they want. Good questions
14
+ help them think it through. When you understand the why, you make the
15
+ hundred decisions they never mention the way they would have made them.
16
+
17
+ ## First: What Do You Actually Know?
18
+
19
+ Before you reply, ask yourself: what do I know about what they want, and
20
+ why?
21
+
22
+ - **Everything that matters is in the request** ("make the icon cornflower
23
+ blue"). This is a quick, clear task. Do it, and say what you did.
24
+ - **Something non-trivial is missing.** Start the conversation.
25
+
26
+ Before you start implementing, you must, in order:
27
+
28
+ 1. Lay out the approaches in a message of their own, and have your
29
+ human partner pick one (see Lay out the approaches).
30
+ 2. Write the design doc, short or full (see Size the Work).
31
+ 3. Get their approval of that doc.
32
+ 4. Invoke the superpowers:writing-plans skill.
33
+
34
+ If nothing is open when you write your first message and there's one
35
+ sensible way, steps 1 to 3 happen in that message (see Your First
36
+ Message).
37
+
38
+ Two things aren't implementing: a spike they said yes to (see Spike to
39
+ feel things out), and doing what they asked once they've opted out of
40
+ the questions.
41
+
42
+ ## Look Before You Ask
43
+
44
+ In an existing project, or when they've given you context (a spec, a plan,
45
+ a handoff, files they pointed at, earlier conversation), dig in before your
46
+ first message. Read what they referred to and the code or material it
47
+ connects to, and keep reading until you can explain how the relevant
48
+ parts work today and what this change would touch. Never ask what the
49
+ project or their context already answers, or reopen what they've
50
+ already decided.
51
+
52
+ ## Your First Message
53
+
54
+ Move the work forward, with one of these:
55
+
56
+ - **They've already said what they want** (a spec, a plan, a detailed
57
+ request): aim for about 200 words for the whole message. Echo their
58
+ request back in your own words, so they can see whether you've got its
59
+ shape: what they want, who it's for, and why, as far as they've said.
60
+ Add what you found that bears on it: how the relevant parts work today
61
+ and what the change would touch. If you found something they may not
62
+ have considered that would change what they're asking for or how it
63
+ has to be built, like a constraint, a conflict, or a cheaper path, say
64
+ so plainly. How to build it comes later, once you understand what they
65
+ want (see Lay out the approaches). End with one line inviting
66
+ corrections. Then, if they haven't told you why they want it, even if
67
+ you can guess, ask about that: one open question in their own terms,
68
+ with nothing to pick from. If they have told you, and their request
69
+ and the project leave open something whose answer would change what
70
+ gets built, ask about the one that would change it most; when its
71
+ choices can be named, sketch each concretely, with what it trades off
72
+ and which you'd pick. If nothing like that is open, there's one
73
+ sensible way: end with the short design itself (the approach, a line on
74
+ why the others don't fit, and the design in a few lines) and ask them
75
+ to approve it. Their approval covers the approach and the design: write
76
+ the short design doc as approved and go on to the plan.
77
+ Specs are often incomplete, so confirm before you build on one.
78
+ - **They haven't:** one open question, in their own terms, about the
79
+ biggest thing their request leaves unsettled. Say why you're asking:
80
+ what the answer would change about what you build. For "a website for
81
+ my bakery": "If it's mostly for people deciding whether to stop by,
82
+ I'd lead with hours and what's in the case today; taking orders is a
83
+ different site. What do you want someone to do when they land on it?"
84
+
85
+ How the message ends depends on whether their message asked for
86
+ brainstorming:
87
+
88
+ - **They asked for it** (by name, by invoking it, or by asking for a
89
+ design discussion): end there. They want this conversation.
90
+ - **They didn't:** they may not want a conversation at all. End with a
91
+ light, one-line offer to just get going instead, like
92
+ "Or if you'd rather I just dive in, say so." If they take you up on
93
+ it, this skill is done: state any significant how-it-gets-made choice
94
+ (platform, language, medium) in one plain line, then do what they
95
+ asked through the normal workflow.
96
+
97
+ That's the whole message.
98
+
99
+ ## The Conversation
100
+
101
+ Ask a question only when the answer would change what gets built and
102
+ neither the request nor the project answers it. Otherwise, state your
103
+ call and your reason as a proposal they can correct, and move the work
104
+ forward. Process steps are always your calls: writing things up, where
105
+ files go, looking further, how to show something. Do them and say so.
106
+ Ask one at a time. Use plain language, pitched just a little above where
107
+ your human partner is. Match their vocabulary; never use process jargon.
108
+ You never need to quote this skill to your human partner.
109
+
110
+ Be clear and concise. Lead with what matters. Avoid jargon. When you
111
+ report what you found, give them the most important findings and offer
112
+ the rest.
113
+
114
+ **Get them describing.** Until you know why they want it, ask open
115
+ questions, with no example answers attached. Their own words carry
116
+ intent that your options can't. Once you know why, when a decision has
117
+ choices you can name, sketch each concretely, with what it trades off
118
+ and which you'd pick. When they say "just guess" or "what do you think?",
119
+ propose something concrete.
120
+
121
+ **How it gets made.** Every project rests on choices about medium, tools,
122
+ materials, and resources: the platform, programming language, and
123
+ libraries for an app; the medium for a piece of art. Read from how they
124
+ talk which of those choices they want to make. Someone who raises the how
125
+ or asks about trade-offs wants the options with your pick. Someone who
126
+ talks about outcomes is handing you the how: make those calls and state
127
+ each in a line. When there's existing work, build on what it already
128
+ uses. Any choice you make goes in the design as your call, never as
129
+ something they agreed to.
130
+
131
+ **Ground to cover.** This is territory, not a script. Never read these
132
+ out as questions:
133
+
134
+ - what kind of thing this is, and what makes it special
135
+ - why now, and what success looks like to them
136
+ - goals, non-goals, and anti-goals (what would make this a failure even
137
+ if it technically works)
138
+ - prior art: what they've seen elsewhere, loved or hated
139
+ - current state: what exists now, what they've tried
140
+ - the details they care about
141
+
142
+ **Make every question specific** to their project and what they've told
143
+ you. Ask Socratically, the way a sharp colleague would: build each
144
+ question on their last answer or on something you found, so it helps
145
+ them think through a consequence or a case they may have missed
146
+ ("Voting closes before the meeting, and two members joined this month.
147
+ Does someone who joins mid-round get a vote?"). When the reason isn't
148
+ already plain, say what you're hoping to learn or what the answer would
149
+ change. A proposal they can correct, plus your reason for it, often
150
+ beats a question.
151
+
152
+ **Do recon.** Once you have a bit of grounding and looking further
153
+ would help, go look: deeper into their codebase or project, their own
154
+ files and data, or the web. Say what you looked for and what you found.
155
+
156
+ **Lay out the approaches.** Once you understand what they want, and
157
+ before you write anything up, put the ways of building it in a message
158
+ of its own. Come up with several real alternatives and drop the weak
159
+ ones, including any that work against why they want it and any the
160
+ existing work rules out. Sketch the two or three that remain concretely
161
+ enough to picture, grounded in what the project actually does, with what
162
+ each trades off. Recommend one and say why, then ask which way they want
163
+ to go; if they've handed you the how, say you'll go with your pick
164
+ instead. When there's genuinely one sensible way, say so in that
165
+ message and explain why the others don't fit; the design comes in the
166
+ next one. This is for how it gets built; for what they want, get them
167
+ describing first.
168
+
169
+ **Show, don't tell.** Whenever seeing would help more than reading,
170
+ sketch it in text: a few lines of what they'd see. Offer the visual
171
+ companion (below) when the look itself is theirs to decide:
172
+
173
+ - something they'll look at: a screen, a page, a printout, a sign
174
+ - a layout or arrangement: of a screen, a room, a schedule
175
+ - a flow or a sequence of steps
176
+ - options that would look different from each other
177
+ - a structure that's easier to see than read: a diagram, a timeline, a map
178
+
179
+ Once they've accepted, use it for mockups to react to, side-by-side
180
+ options, and throwaway prototypes they can click.
181
+
182
+ **Spike to feel things out.** Agentic work is waterfall, but very, very
183
+ fast. A quick throwaway build is often the cheapest way to learn what
184
+ they want or whether something works. Offer one when it would help.
185
+ When they just want to spike, get out of the way. Spikes get no tests
186
+ or minimal ones, aren't bulletproof, and skip the plan, implementation,
187
+ and review process. Bring what the spike taught you back into the
188
+ conversation.
189
+
190
+ ## Play It Back
191
+
192
+ Play back as you go. As soon as you understand one part well enough to
193
+ describe it (what it's for and who it serves, say, or how one piece
194
+ behaves), describe that part back in about 200-300 words, then return to
195
+ questions about the next part. Playback and questions alternate through
196
+ the whole conversation; the last chunk covers whatever is left.
197
+
198
+ Only what they said goes in as theirs. Anything you filled in goes in
199
+ as your proposal, with your reason. End each chunk by asking what's wrong
200
+ or missing.
201
+
202
+ Before you send a chunk, check it: does it describe something they'll
203
+ look at, like a page, a screen, a schedule, or a printout? If so, put a
204
+ text sketch next to the description. If the look itself is theirs to
205
+ decide and they haven't seen the visual companion offer yet, send the
206
+ offer instead (its own message, below) and hold the chunk for the next
207
+ message. Once they've accepted, put a mockup next to the description.
208
+
209
+ ## Size the Work
210
+
211
+ Once you understand what they want and they've picked an approach, say
212
+ how big the work is in plain words. They can override it.
213
+
214
+ | Size | The design doc |
215
+ |------|----------------|
216
+ | A small change | a short one: what you already covered together, written down |
217
+ | A project | the full written design (below) |
218
+
219
+ Short or full, the design doc has an **Approaches** part: the two or
220
+ three ways you considered building it, what each trades off, which one
221
+ they picked, and why. They pick in the conversation, before you write
222
+ the doc.
223
+
224
+ If it grows mid-task, stop, say so, and step up a size.
225
+
226
+ If this is really several independent projects, say so, agree on an
227
+ order, and brainstorm them one at a time.
228
+
229
+ ## The Written Design
230
+
231
+ Write a plain document a talented builder in the domain could plan
232
+ from without going back to your human partner. Cover:
233
+
234
+ - intent and the why
235
+ - goals, non-goals, anti-goals
236
+ - constraints
237
+ - approaches (above)
238
+ - the parts of the how they decided, as they decided them
239
+ - what's left to the builder
240
+
241
+ For a small change, the short design covers the same points in a line
242
+ or two each and goes straight to your human partner, without the
243
+ builder check.
244
+
245
+ **Where it goes:** in a software repo,
246
+ `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`, committed.
247
+ Otherwise, pick a sensible place and say where. Your human partner's
248
+ preferences override both.
249
+
250
+ **Builder check** (for a project): dispatch a fresh subagent with
251
+ `builder-check-prompt.md` in this directory. When you tell your human
252
+ partner you're writing it up, say a reviewer will read it first and you
253
+ may come back once with a few questions. Don't hand over the document
254
+ until the check is back. Sort what the builder asks into three piles:
255
+
256
+ - **Answered already** by the conversation or the project: put the answer
257
+ in the document.
258
+ - **Minor:** a sensible builder could settle it without changing what gets
259
+ built. Settle it yourself and mark it in the document as your call.
260
+ - **Theirs:** only your human partner can answer it, and the answer changes
261
+ what gets built.
262
+
263
+ Bring the "theirs" pile in one message, most important first. Update the
264
+ document with their answers, then hand it over with a short list of the
265
+ calls you made so they can check those while reading. That's the only
266
+ round of questions the check produces. Without a subagent tool, read the
267
+ document as that builder yourself.
268
+
269
+ <HARD-GATE>
270
+ Nothing gets built until your human partner approves the design doc:
271
+ the short one for a small change, the full one for a project.
272
+ Building includes writing product code, scaffolding, installing
273
+ dependencies, creating projects, and invoking an implementation skill.
274
+ Reading and exploring are fine.
275
+
276
+ Two exceptions. If they opted out of the questions, the skill is done
277
+ and the gate goes with it. A spike they said yes to may be built; it
278
+ stays labeled throwaway, and keeping what it produced is a new request
279
+ that comes back through this gate.
280
+
281
+ After the design doc is approved, the next step is the plan: invoke
282
+ superpowers:writing-plans and no other skill.
283
+ </HARD-GATE>
284
+
285
+ ## Red Flags
286
+
287
+ | Thought | Reality |
288
+ |---------|---------|
289
+ | "I'll offer a menu of what they might want" | Options steer. Ask them to describe it first. |
290
+ | "I'll fill in sensible defaults" | Good. Say them out loud. A default they never heard is one they couldn't reject. |
291
+ | "I've answered their questions, so I'll write the doc" | Lay out the approaches first, in a message of their own (or, when nothing was open from the start, in your first message's short design). |
292
+ | "I should explain the process first" | Ask your question. The process shows itself. |
293
+ | "They said 'sounds good' to the idea" | Approval covers what you showed them. A design doc you haven't written isn't approved. |
294
+ | "The spike works, I'll keep building on it" | Keeping it is a new request. Back through the gate. |
295
+
296
+ ## Visual Companion
297
+
298
+ A browser tab for showing mockups, diagrams, and prototypes. It's a
299
+ tool, not a mode: accepting it doesn't send every question to the
300
+ browser.
301
+
302
+ **Offer it just-in-time.** Offer it the first time one of the moments
303
+ above comes up, never upfront. The offer is its own message with nothing
304
+ else in it:
305
+
306
+ > "This might be easier if I show you. Want me to open a browser tab with some mockups?"
307
+
308
+ If they decline, stay in text and don't offer again unless they raise it.
309
+
310
+ **Per question, ask: would they understand this better by seeing it?**
311
+ Mockups, layouts, diagrams, and side-by-side designs go in the browser.
312
+ Requirements, scope, tradeoffs, and conceptual choices stay in text. A
313
+ question about a UI topic isn't automatically a visual question.
314
+
315
+ If they accept, read `visual-companion.md` in this directory before
316
+ starting the server.
@@ -0,0 +1,23 @@
1
+ # Builder Check Prompt
2
+
3
+ Dispatch a fresh general-purpose subagent with this prompt once the
4
+ written design exists. Fill in the domain and the document path.
5
+
6
+ ```
7
+ You are a talented [DOMAIN, e.g. "software engineer", "event planner",
8
+ "bakery consultant"]. You've been handed a design document and asked to
9
+ put together a plan to build what it describes. You will not be able to
10
+ talk to the person who wrote it.
11
+
12
+ Read [DOCUMENT_PATH].
13
+
14
+ Report only the questions you'd still need answered before you could plan
15
+ this well: places where you'd have to guess and a wrong guess would
16
+ matter. For each, give the question and why the answer changes the plan.
17
+ Rank them by importance.
18
+
19
+ Skip anything the document explicitly leaves to the builder, and anything
20
+ you could reasonably decide yourself. Skip nitpicks about wording.
21
+
22
+ If nothing important is left, say "nothing important left".
23
+ ```
@@ -0,0 +1,213 @@
1
+ <!DOCTYPE html>
2
+ <html>
3
+ <head>
4
+ <meta charset="utf-8">
5
+ <title>Superpowers Brainstorming</title>
6
+ <style>
7
+ /*
8
+ * BRAINSTORM COMPANION FRAME TEMPLATE
9
+ *
10
+ * This template provides a consistent frame with:
11
+ * - OS-aware light/dark theming
12
+ * - Header branding and connection status
13
+ * - Scrollable main content area
14
+ * - CSS helpers for common UI patterns
15
+ *
16
+ * Content is injected via placeholder comment in #frame-content.
17
+ */
18
+
19
+ * { box-sizing: border-box; margin: 0; padding: 0; }
20
+ html, body { height: 100%; overflow: hidden; }
21
+
22
+ /* ===== THEME VARIABLES ===== */
23
+ :root {
24
+ --bg-primary: #f5f5f7;
25
+ --bg-secondary: #ffffff;
26
+ --bg-tertiary: #e5e5e7;
27
+ --border: #d1d1d6;
28
+ --text-primary: #1d1d1f;
29
+ --text-secondary: #86868b;
30
+ --text-tertiary: #aeaeb2;
31
+ --accent: #0071e3;
32
+ --accent-hover: #0077ed;
33
+ --success: #34c759;
34
+ --warning: #ff9f0a;
35
+ --error: #ff3b30;
36
+ --selected-bg: #e8f4fd;
37
+ --selected-border: #0071e3;
38
+ }
39
+
40
+ @media (prefers-color-scheme: dark) {
41
+ :root {
42
+ --bg-primary: #1d1d1f;
43
+ --bg-secondary: #2d2d2f;
44
+ --bg-tertiary: #3d3d3f;
45
+ --border: #424245;
46
+ --text-primary: #f5f5f7;
47
+ --text-secondary: #86868b;
48
+ --text-tertiary: #636366;
49
+ --accent: #0a84ff;
50
+ --accent-hover: #409cff;
51
+ --selected-bg: rgba(10, 132, 255, 0.15);
52
+ --selected-border: #0a84ff;
53
+ }
54
+ }
55
+
56
+ body {
57
+ font-family: system-ui, -apple-system, BlinkMacSystemFont, sans-serif;
58
+ background: var(--bg-primary);
59
+ color: var(--text-primary);
60
+ display: flex;
61
+ flex-direction: column;
62
+ line-height: 1.5;
63
+ }
64
+
65
+ /* ===== FRAME STRUCTURE ===== */
66
+ .brand { display: flex; align-items: center; min-width: 0; overflow: hidden; color: var(--text-secondary); line-height: 1; }
67
+ .brand a { color: inherit; text-decoration: none; display: flex; align-items: center; gap: 0.5rem; min-width: 0; max-width: 100%; line-height: 1; }
68
+ .brand-copy { display: block; min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; line-height: 1; transform: translateY(-1px); }
69
+ .brand-logo { display: block; height: 1em; width: auto; max-width: 180px; flex-shrink: 0; filter: invert(1); }
70
+ @media (prefers-color-scheme: dark) {
71
+ .brand-logo { filter: none; }
72
+ }
73
+ .status { font-size: 0.7rem; color: var(--status-color, var(--success)); display: flex; align-items: center; gap: 0.4rem; justify-self: end; white-space: nowrap; line-height: 1; }
74
+ .status::before { content: ''; width: 6px; height: 6px; background: var(--status-color, var(--success)); border-radius: 50%; }
75
+
76
+ .main { flex: 1; overflow-y: auto; }
77
+ #frame-content { padding: 2rem; min-height: 100%; }
78
+
79
+ .header {
80
+ background: var(--bg-secondary);
81
+ border-bottom: 1px solid var(--border);
82
+ padding: 0.5rem 1.5rem;
83
+ flex-shrink: 0;
84
+ display: grid;
85
+ grid-template-columns: minmax(0, 1fr) auto;
86
+ align-items: center;
87
+ gap: 1rem;
88
+ min-height: 42px;
89
+ }
90
+ .header .brand { justify-self: start; width: 100%; font-size: 0.75rem; line-height: 1; }
91
+ .header .status { grid-column: 2; line-height: 1; }
92
+ .header span {
93
+ font-size: 0.75rem;
94
+ color: var(--text-secondary);
95
+ }
96
+ .header .selected-text {
97
+ color: var(--accent);
98
+ font-weight: 500;
99
+ }
100
+
101
+ /* ===== TYPOGRAPHY ===== */
102
+ h2 { font-size: 1.5rem; font-weight: 600; margin-bottom: 0.5rem; }
103
+ h3 { font-size: 1.1rem; font-weight: 600; margin-bottom: 0.25rem; }
104
+ .subtitle { color: var(--text-secondary); margin-bottom: 1.5rem; }
105
+ .section { margin-bottom: 2rem; }
106
+ .label { font-size: 0.7rem; color: var(--text-secondary); text-transform: uppercase; letter-spacing: 0.05em; margin-bottom: 0.5rem; }
107
+
108
+ /* ===== OPTIONS (for A/B/C choices) ===== */
109
+ .options { display: flex; flex-direction: column; gap: 0.75rem; }
110
+ .option {
111
+ background: var(--bg-secondary);
112
+ border: 2px solid var(--border);
113
+ border-radius: 12px;
114
+ padding: 1rem 1.25rem;
115
+ cursor: pointer;
116
+ transition: all 0.15s ease;
117
+ display: flex;
118
+ align-items: flex-start;
119
+ gap: 1rem;
120
+ }
121
+ .option:hover { border-color: var(--accent); }
122
+ .option.selected { background: var(--selected-bg); border-color: var(--selected-border); }
123
+ .option .letter {
124
+ background: var(--bg-tertiary);
125
+ color: var(--text-secondary);
126
+ width: 1.75rem; height: 1.75rem;
127
+ border-radius: 6px;
128
+ display: flex; align-items: center; justify-content: center;
129
+ font-weight: 600; font-size: 0.85rem; flex-shrink: 0;
130
+ }
131
+ .option.selected .letter { background: var(--accent); color: white; }
132
+ .option .content { flex: 1; }
133
+ .option .content h3 { font-size: 0.95rem; margin-bottom: 0.15rem; }
134
+ .option .content p { color: var(--text-secondary); font-size: 0.85rem; margin: 0; }
135
+
136
+ /* ===== CARDS (for showing designs/mockups) ===== */
137
+ .cards { display: grid; grid-template-columns: repeat(auto-fit, minmax(280px, 1fr)); gap: 1rem; }
138
+ .card {
139
+ background: var(--bg-secondary);
140
+ border: 1px solid var(--border);
141
+ border-radius: 12px;
142
+ overflow: hidden;
143
+ cursor: pointer;
144
+ transition: all 0.15s ease;
145
+ }
146
+ .card:hover { border-color: var(--accent); transform: translateY(-2px); box-shadow: 0 4px 12px rgba(0,0,0,0.1); }
147
+ .card.selected { border-color: var(--selected-border); border-width: 2px; }
148
+ .card-image { background: var(--bg-tertiary); aspect-ratio: 16/10; display: flex; align-items: center; justify-content: center; }
149
+ .card-body { padding: 1rem; }
150
+ .card-body h3 { margin-bottom: 0.25rem; }
151
+ .card-body p { color: var(--text-secondary); font-size: 0.85rem; }
152
+
153
+ /* ===== MOCKUP CONTAINER ===== */
154
+ .mockup {
155
+ background: var(--bg-secondary);
156
+ border: 1px solid var(--border);
157
+ border-radius: 12px;
158
+ overflow: hidden;
159
+ margin-bottom: 1.5rem;
160
+ }
161
+ .mockup-header {
162
+ background: var(--bg-tertiary);
163
+ padding: 0.5rem 1rem;
164
+ font-size: 0.75rem;
165
+ color: var(--text-secondary);
166
+ border-bottom: 1px solid var(--border);
167
+ }
168
+ .mockup-body { padding: 1.5rem; }
169
+
170
+ /* ===== SPLIT VIEW (side-by-side comparison) ===== */
171
+ .split { display: grid; grid-template-columns: 1fr 1fr; gap: 1.5rem; }
172
+ @media (max-width: 700px) { .split { grid-template-columns: 1fr; } }
173
+
174
+ /* ===== PROS/CONS ===== */
175
+ .pros-cons { display: grid; grid-template-columns: 1fr 1fr; gap: 1rem; margin: 1rem 0; }
176
+ .pros, .cons { background: var(--bg-secondary); border-radius: 8px; padding: 1rem; }
177
+ .pros h4 { color: var(--success); font-size: 0.85rem; margin-bottom: 0.5rem; }
178
+ .cons h4 { color: var(--error); font-size: 0.85rem; margin-bottom: 0.5rem; }
179
+ .pros ul, .cons ul { margin-left: 1.25rem; font-size: 0.85rem; color: var(--text-secondary); }
180
+ .pros li, .cons li { margin-bottom: 0.25rem; }
181
+
182
+ /* ===== PLACEHOLDER (for mockup areas) ===== */
183
+ .placeholder {
184
+ background: var(--bg-tertiary);
185
+ border: 2px dashed var(--border);
186
+ border-radius: 8px;
187
+ padding: 2rem;
188
+ text-align: center;
189
+ color: var(--text-tertiary);
190
+ }
191
+
192
+ /* ===== INLINE MOCKUP ELEMENTS ===== */
193
+ .mock-nav { background: var(--accent); color: white; padding: 0.75rem 1rem; display: flex; gap: 1.5rem; font-size: 0.9rem; }
194
+ .mock-sidebar { background: var(--bg-tertiary); padding: 1rem; min-width: 180px; }
195
+ .mock-content { padding: 1.5rem; flex: 1; }
196
+ .mock-button { background: var(--accent); color: white; border: none; padding: 0.5rem 1rem; border-radius: 6px; font-size: 0.85rem; }
197
+ .mock-input { background: var(--bg-primary); border: 1px solid var(--border); border-radius: 6px; padding: 0.5rem; width: 100%; }
198
+ </style>
199
+ </head>
200
+ <body>
201
+ <div class="header">
202
+ <!-- BRANDING -->
203
+ <div class="status">Connecting…</div>
204
+ </div>
205
+
206
+ <div class="main">
207
+ <div id="frame-content">
208
+ <!-- CONTENT -->
209
+ </div>
210
+ </div>
211
+
212
+ </body>
213
+ </html>