@rubytech/create-realagent-code 0.1.255 → 0.1.257

package/payload/platform/plugins/slides/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Nils Smed
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/payload/platform/plugins/slides/PLUGIN.md

@@ -0,0 +1,18 @@
+---
+name: slides
+surface: platform
+description: "Generate, extend, theme, and review self-contained HTML slide decks. One HTML file, no build step, no dependencies beyond Google Fonts. Ships seven commands (/slides, /slides-outline, /add-slide, /slides-theme, /slides-review, /slides-new-component, /slides-claus) over a 25-component design system with three themes (Default, Craft, Solid) and six storytelling formats (talk, Sequoia pitch, McKinsey SCR, product launch, board update, sales). Provides one skill: deck-system."
+tools: []
+skills:
+  - skills/deck-system/SKILL.md
+always: false
+embed: false
+---
+
+# Slides
+
+Vendored copy of the open-source Slides™ deck framework (`github.com/noskillish/slides`, MIT). Turns a description into a finished, self-contained `deck.html` — inline CSS and JS, no build step, navigable with arrow keys and exportable to PDF.
+
+No MCP server; the plugin provides commands plus the `deck-system` reference skill (the full component library, design tokens, theme rules, and storytelling routing). The three theme templates (`deck.html`, `deck-craft.html`, `deck-solid.html`) ship inside `skills/deck-system/` and are copied verbatim when applying a predefined theme.
+
+Frozen at a pinned upstream commit — see [`PROVENANCE.md`](PROVENANCE.md). The one divergence from upstream (template path repointed from repo-root to the co-located skill folder) is recorded there.

package/payload/platform/plugins/slides/PROVENANCE.md

@@ -0,0 +1,40 @@
+# Provenance — vendored Slides™ plugin
+
+This plugin is a **frozen vendored copy** of the open-source Slides™ deck framework.
+
+| | |
+|---|---|
+| Upstream | `https://github.com/noskillish/slides` |
+| Subtree vendored | `plugins/slides/` |
+| Pinned commit | `578af900d537e8a2bd8bfca11a4d72dc4e8fb588` |
+| Upstream plugin version | `1.0.0` |
+| License | MIT — see [`LICENSE`](LICENSE) (Copyright © 2026 Nils Smed) |
+| Vendored | 2026-06-05, Task 644 |
+
+## What was copied
+
+`commands/` (all seven) and `skills/deck-system/` (SKILL.md, REFERENCE.md, the
+`STORYTELLING*.md` set, and the three `deck*.html` templates) verbatim from the
+pinned commit, plus the upstream `LICENSE`.
+
+## Divergences from upstream
+
+The upstream `.claude-plugin/plugin.json` was **not** copied — platform plugins
+generate their `plugin.json` from `PLUGIN.md` at bundle time. `PLUGIN.md` is a
+Maxy-platform addition, not upstream.
+
+Upstream keeps a second copy of the theme templates at the repo root and some
+instructions read them from there (`../../deck.html`). The vendored plugin has no
+repo root, so the template-location instructions were repointed to the co-located
+`skills/deck-system/` copies (which upstream already ships). Edited:
+
+- `skills/deck-system/REFERENCE.md` — "from the repo root … `../../deck.html`" → "from this skill folder".
+- `commands/slides-theme.md` (×3) — "from the repo" / unqualified "Read `deck.html`" → "from the deck-system skill folder".
+
+No component CSS, storytelling content, or command behaviour was otherwise changed.
+
+## Re-syncing upstream
+
+Frozen by design — there is no automatic update. To pull a newer upstream
+release, re-vendor `plugins/slides/` at the new commit, re-apply the template-path
+divergences above, and bump the pinned commit in this file.

package/payload/platform/plugins/slides/commands/add-slide.md

@@ -0,0 +1,29 @@
+---
+description: Add one or more slides to an existing deck. Respects the current theme, storytelling arc, and component style.
+---
+
+# /add-slide
+
+Add slides to an existing deck without regenerating the whole thing.
+
+## Usage
+
+- `/add-slide "a stat grid after slide 8 showing our key metrics"`
+- `/add-slide "a dark quote slide before the closing that says 'The question was never if. It was when.'"`
+- `/add-slide "two-column comparison between the old and new workflow after the intro"`
+
+## What the command does
+
+1. Read the existing deck to understand theme, structure, and storytelling arc
+2. Determine the right component type for the requested content
+3. Generate the new slide HTML using the same design tokens and patterns
+4. Insert at the specified position (or suggest the best position if not specified)
+5. Update nothing else. The JS counter and progress bar adjust automatically
+
+## Tips
+
+- Reference slides by number: "after slide 8"
+- Reference slides by content: "after the team slide"
+- Reference storytelling beats: "in the evidence section"
+- Specify the component if you know it: "a dot-flow slide", "a product slide"
+- If you don't specify a position, the command suggests one based on the storytelling arc

package/payload/platform/plugins/slides/commands/slides-claus.md

@@ -0,0 +1,39 @@
+---
+description: Generate a Claus Mode deck. Max 4 words per slide. All caps. Extreme buzzwords. Zero nuance. Every slide is a billboard. Minimum 15 slides. Use when the user wants maximum energy and minimum explanation.
+---
+
+# /slides-claus
+
+Generate a high-energy deck of nothing but big bold headlines and extreme buzzwords.
+
+## Usage
+
+- `/slides-claus "AI is eating the world"`
+- `/slides-claus "our company in 30 seconds"`
+- `/slides-claus "why we are winning"`
+
+## What the command does
+
+1. **If the user gave a topic but no details**, ask a few quick questions to fuel the hype. Keep it short and high-energy:
+   - What is the company/product/idea?
+   - What is the one thing you want the audience to remember?
+   - Any specific wins, numbers, or flex points?
+   Then generate immediately after the answers. Do not ask follow-ups.
+2. **If the user already provided enough context**, skip questions and generate.
+3. Load the Claus storytelling guide (`STORYTELLING-claus.md`) from the `deck-system` skill folder.
+4. Generate minimum 15 slides of pure headline energy. No subtitles. No body text. No complex components.
+4. Use the Solid theme by default. Read `deck-solid.html` from the skill folder and copy its style and script blocks verbatim.
+5. Every slide is a dark or light quote slide. Max 4 words. All caps.
+6. Every headline must contain at least one buzzword from the approved list.
+7. No dim spans. No punctuation except question marks on the last slide.
+
+## Rules
+
+- Maximum 4 words per headline
+- All caps always
+- Minimum 15 slides
+- All quote slides, no other components (except cover)
+- No subtitles, no body text, no eyebrows, no meta
+- Every headline contains a buzzword
+- No dim spans. Full intensity.
+- Alternate dark and light slides for rhythm

package/payload/platform/plugins/slides/commands/slides-new-component.md

@@ -0,0 +1,39 @@
+---
+description: Design and build a new slide component that doesn't exist in the standard 25-component library. Ensures it follows the design system tokens and naming conventions.
+---
+
+# /slides-new-component
+
+Build a custom slide component when the standard library doesn't have what you need.
+
+## Usage
+
+- `/slides-new-component "a funnel chart showing conversion rates across 5 stages"`
+- `/slides-new-component "a matrix grid with two axes for effort vs impact"`
+- `/slides-new-component "a horizontal bar chart comparing three metrics"`
+- `/slides-new-component "a kanban-style board showing project status"`
+
+## What the command does
+
+1. Understand what the user needs to visualize
+2. Check if an existing component can be adapted first
+3. If not, design a new component following the Freestyle rules:
+   - **Stay on-token.** Only use colors, fonts, weights, and spacing from the design tokens
+   - **Use the headline pattern.** Bold-then-dim with `<span class="dim">` where applicable
+   - **Match existing craft.** Border radius 10px for cards, 4px for small elements. Padding 1–1.5rem
+   - **Name the class.** Lowercase, hyphenated: `funnel-chart`, `impact-matrix`, `bar-compare`
+   - **Keep CSS inline** in the `<style>` block, grouped with a descriptive comment
+   - **One new idea per slide.** Pair with familiar elements (eyebrow, subtitle)
+4. Generate both the CSS and HTML for the new component
+5. Show an example slide using the component with placeholder content
+
+## What you get back
+
+- CSS to add to the `<style>` block (with comment group header)
+- HTML template for the new component
+- An example slide using it with realistic placeholder content
+- Integration notes (where it fits in a deck, which beats it serves)
+
+## Design constraints
+
+The new component must look like it belongs next to the existing 25 components. If it needs a new color or a different font to work, it needs to be rethought. The design system is deliberately constrained. That constraint is what makes decks look consistent.

package/payload/platform/plugins/slides/commands/slides-outline.md

@@ -0,0 +1,43 @@
+---
+description: Generate a slide-by-slide outline without writing HTML. Fast iteration on structure, beats, and component types before committing to code.
+---
+
+# /slides-outline
+
+Draft the structure of a deck before writing any HTML.
+
+## Usage
+
+- `/slides-outline "a 15-minute talk about why we rebuilt our data pipeline"`
+- `/slides-outline --format sequoia "pitch for a developer productivity tool"`
+- `/slides-outline`, then describe in the follow-up
+
+## What the command does
+
+1. Read the user's description and detect the best storytelling format
+2. Generate an outline as a markdown table:
+
+```
+| # | Beat | Component | Headline | Notes |
+|---|------|-----------|----------|-------|
+| 1 | Open | Quote slide | "We threw away six months of work." | Hook, surprise |
+| 2 | Act 1 | Eyebrow + headline | The old pipeline. | Status quo |
+| 3 | Act 1 | Two-column | Before vs. after. | Pain points |
+| ... | | | | |
+```
+
+3. Present the outline for feedback
+4. Iterate until the user approves
+
+## What you get back
+
+- A numbered slide list with storytelling beats
+- Component type recommendations
+- Headline drafts
+- Estimated time allocation per section
+
+## Tips
+
+- Use this before `/slides` to iterate on structure quickly
+- Once approved, run `/slides` to generate the full HTML from the outline
+- Specify format with `--format` if you know what you want (talk, sequoia, mbb, launch, board, sales)

package/payload/platform/plugins/slides/commands/slides-review.md

@@ -0,0 +1,52 @@
+---
+description: Review an existing slide deck for storytelling structure, design consistency, pacing, and common mistakes. Produces actionable feedback.
+---
+
+# /slides-review
+
+Get a structured review of your deck before you present.
+
+## Usage
+
+- `/slides-review`: review the current deck.html
+- `/slides-review deck-craft.html`: review a specific file
+
+## What the command does
+
+Reads the deck and evaluates it across six dimensions:
+
+### 1. Storytelling arc
+- Does the deck follow a recognizable structure (six-beat, SCR, pitch, etc.)?
+- Is there a clear open, turn, evidence section, and close?
+- Does it build toward something?
+
+### 2. Pacing
+- Are there too many text-heavy slides in a row?
+- Are dark slides and quote slides used as punctuation?
+- Is Act 3 (evidence) roughly 40% of the deck?
+
+### 3. Headline pattern
+- Do headlines use bold-then-dim (`<span class="dim">`)?
+- Are headlines statements?
+- Are they specific enough?
+
+### 4. Component variety
+- Is the deck using the right component for each content type?
+- Are there missed opportunities (e.g., a stat grid instead of a text slide)?
+
+### 5. Design rules
+- Max 1 dark callout? Max 2–3 dark slides?
+- Are eyebrows, spacing, and typography on-token?
+- No em-dashes in body copy?
+
+### 6. Tone
+- Specific numbers over vague claims?
+- Names instead of pronouns?
+- No fluff sentences?
+
+## What you get back
+
+A structured report with:
+- Overall assessment (strong / needs work / major issues)
+- Specific findings per dimension
+- Suggested fixes with slide numbers

package/payload/platform/plugins/slides/commands/slides-theme.md

@@ -0,0 +1,64 @@
+---
+description: Switch a deck between visual themes (Default, Craft, Solid, or a custom style). Accepts text descriptions or image attachments. Replaces the CSS style block and adjusts theme-specific classes.
+---
+
+# /slides-theme
+
+Convert a deck from one visual theme to another.
+
+## Usage
+
+- `/slides-theme craft`: switch to the Craft theme
+- `/slides-theme solid`: switch to the Solid theme
+- `/slides-theme default`: switch to the Default theme
+- `/slides-theme dark blue with orange accents`: switch to a custom theme from text
+- `/slides-theme` + attached image: match the design from a screenshot
+- `/slides-theme "like this but darker"` + attached image: match the image with overrides
+
+## Available themes
+
+| Theme | Source | Character |
+|-------|--------|-----------|
+| **Default** | `deck.html` | Warm off-white, minimal, editorial. The starting point. |
+| **Craft** | `deck-craft.html` | Richer textures, art overlays, painterly backgrounds. More visual weight. |
+| **Solid** | `deck-solid.html` | Glass morphism, gradients, frosted cards. Modern SaaS aesthetic. |
+| **Custom** | Text or image | Any visual style the user describes or shows. |
+
+## Predefined themes (Default, Craft, Solid)
+
+1. Read the target template file (`deck.html`, `deck-craft.html`, or `deck-solid.html`) from the deck-system skill folder
+2. Copy the entire `<style>` block from the template file verbatim into the deck
+3. Copy the entire `<script>` block from the template file verbatim into the deck
+4. Preserve all slide content and structure unchanged
+5. Always read the actual template file. Never generate theme CSS from memory or descriptions.
+
+## Custom theme
+
+When the argument does not match "default", "craft", or "solid", treat it as a custom theme. Custom themes can come from text, an attached image, or both.
+
+### From text
+
+1. Read `deck.html` from the deck-system skill folder as the structural base. Copy the `<script>` block verbatim.
+2. Rewrite the `<style>` block to match the description:
+   - Keep every CSS selector and class name identical to the Default theme.
+   - Change only visual properties: colors, backgrounds, gradients, shadows, border styles, border-radius, font weights.
+   - Preserve all layout properties: padding, margin, grid, flexbox, clamp values, media queries.
+   - Define a cohesive palette with at minimum 6 tokens: background, surface, ink, border, dim text, accent.
+3. Show the user the proposed palette before applying. Get approval first.
+4. Replace the deck's `<style>` block with the new CSS. Preserve all slide content.
+
+### From image
+
+When the user attaches a screenshot, slide, website capture, or brand guideline:
+
+1. Analyze the image and extract: base mode (dark/light), background, surface, ink, accent, dim text, border style, corner radius, shadows, typography weight, and font if recognizable.
+2. Read `deck.html` from the deck-system skill folder as the structural base. Copy the `<script>` block verbatim.
+3. Rewrite the `<style>` block using the extracted tokens. Same rules as text-based: keep all selectors, change only visual properties.
+4. If the user also wrote text, apply it as an override on top of what was extracted.
+5. Generate immediately. No approval step needed. The image is the approval.
+
+## Important
+
+- All themes share the same HTML component structure
+- The difference is purely in CSS: colors, backgrounds, card styles, shadows
+- Content, slide order, and component types remain identical after switching

package/payload/platform/plugins/slides/commands/slides.md

@@ -0,0 +1,59 @@
+---
+description: Generate a complete slide deck from a description. Auto-detects the best storytelling format (talk, pitch, sales, board, product launch) and produces a single self-contained HTML file.
+---
+
+# /slides
+
+Generate a complete presentation deck from a description.
+
+## Usage
+
+- `/slides`, then describe your presentation in the follow-up
+- `/slides "a 20-minute conference talk about AI-assisted development"`
+- `/slides --format sequoia "our Series A pitch for a developer tools company"`
+
+## What the command does
+
+Runs the `deck-system` skill end-to-end:
+
+1. **Use what the user already provided.** The user's message, form responses, and attachments are the brief. Do NOT re-ask for information already given. If topic, format, length, or theme were stated, use them directly. Proceed to the outline.
+2. If critical info is missing (you have no idea what the deck is about), ask once. One short question. Then move on.
+3. Detect the best storytelling format from context (or use the one the user specified)
+4. Load the corresponding storytelling guide (bundled in the `deck-system` skill folder)
+5. Draft a slide-by-slide outline (titles, component types, beats)
+6. Present the outline for approval
+7. Generate the full HTML deck using the component reference and design tokens
+8. Output a single `deck.html` file
+
+## Format detection
+
+The skill auto-detects format from context. Override with `--format`:
+
+| Flag | Format |
+|------|--------|
+| `--format talk` | TED Talk / six-beat |
+| `--format sequoia` | Sequoia pitch deck |
+| `--format mbb` | McKinsey SCR / pyramid |
+| `--format launch` | Product launch (Apple-style) |
+| `--format board` | Board / strategy update |
+| `--format sales` | Sales deck |
+
+The storytelling guides are bundled in the `deck-system` skill folder. The skill handles loading them.
+
+## What you get back
+
+- A complete, self-contained HTML file
+- CSS and JS copied verbatim from the template file
+- Keyboard and touch navigation built in
+
+## How themes work
+
+For predefined themes (default, craft, solid), the skill reads the actual template file and copies its `<style>` and `<script>` blocks verbatim. Only the slide content is generated.
+
+For custom themes, the user describes the visual style in plain language (e.g. "dark blue with orange accents", "brutalist black and white"). The skill starts from the Default template structure, rewrites the CSS to match the description, and shows the palette for approval before generating slides.
+
+## Tips
+
+- Be specific about your audience, duration, and goal
+- Mention the format if you have a preference: "pitch deck", "conference talk", "sales presentation"
+- Mention the theme if you want one: "use the solid theme", "craft theme", or describe your own: "warm earth tones with terracotta accents". Default is the Default theme.