AI Agent Workflow Collection

Produces a production-ready logo pack for a product, service, or project — a tailored set of professional, diverse logo prompts (minimalist one-color, a monochrome variation, a comfortable/approachable variation, and a polished professional version, plus icon/wordmark/monogram). First checks whether a brand guide or logo already exists; if a logo exists it analyzes and refines it, otherwise it designs new directions. Use when the user wants a logo, brand mark, app icon, wordmark, favicon, logo prompts, or to refresh/refine an existing logo.

Captures consistent, repeatable screenshots of a running web app for documentation, and fills [SCREENSHOT: id] markers in a user guide with the images. Config-driven and re-runnable, so screenshots can be regenerated whenever a feature changes. Use when the user wants screenshots for a user guide, help docs, a feature announcement, or a README; wants to refresh stale screenshots; or asks to capture app screens, fill screenshot placeholders, or document a new feature visually.

Generates a complete, production-ready brand kit from docs/brand.json — an expanded color palette (50–900 tints/shades with WCAG-checked text pairings), a modular type scale, a favicon + app-icon spec/manifest at standard sizes, a social avatar + banner, and an Open Graph share image. Discovers existing brand assets first, derives everything deterministically from brand.json with a dependency-free script, and is generator-agnostic for the actual images. Use when the user wants a brand kit, favicon, app icons, social/OG images, a color palette, design tokens, a type scale, a web manifest, or to turn brand.json into real assets.

Generates realistic, obviously-fake demo/seed data plus a guided live-demo script for any project. Discovers the data model (Drizzle, Prisma, raw SQL/Supabase, TypeORM, Sequelize, Mongoose, or TS types), writes an idempotent seed script that builds a few complete, wired-up "hero" records, and writes docs/demo/script.md — a step-by-step walkthrough that hits the best features in a sensible order with what-to-say and what-to-show — then renders it to a themed presenter page. Use when the user wants demo data, seed data, sample/test/fixture data, a demo environment, a sales or investor demo, a demo script, a walkthrough, a guided product tour, a "fill the app with data" task, or to prep a live demo. Triggers on "seed the database", "demo data", "demo script", "walkthrough", "prep for a demo", "sample data", "populate the app".

Turns a shipped release into audience-tailored announcement assets — a customer email (themed HTML + plain-text), an in-app "What's new" modal snippet, and a short social post — all in the product's brand voice, written separately for homeowners vs. investors vs. crew (or any custom audience). Reads docs/SHIPPING-LOG.md for what shipped and docs/brand.json for colors + fonts, and writes everything to docs/announcements/ /. Use when the user wants to announce a release, write a launch or update email, a "what's new" email or modal, release-announcement copy, a customer/investor update, or a social post for a feature — or says "announce this", "email about the release", "tell our customers what shipped", "what's new email". Part of the /ship- pack.

Generates a help center for a project from its user guide — a real-question docs/FAQ.md (grounded in the guide's workflows, troubleshooting, and glossary), a set of canned support reply templates, and a searchable, themeable single-file help page (docs/help.html). Use when the user wants an FAQ, help center, knowledge base, support docs, "frequently asked questions", canned/saved support replies, a self-serve help page, or to turn a user guide into customer-facing help. Triggers on "make an FAQ", "build a help center", "knowledge base", "support replies", "help page", "turn the guide into help docs".

Turns a project's shipping log into machine-readable data plus an embeddable changelog widget. Parses docs/SHIPPING-LOG.md + docs/VERSION into a structured docs/changelog.json (releases with version, date, and items grouped by category), then emits an RSS/Atom feed (docs/changelog.xml) and a self-contained, brand-themed web component + static HTML embed that read that JSON. For a company-page "What's new" section, an in-app "What's new" badge, and a subscribe-able feed. Use when the user wants a changelog API or JSON, an RSS/Atom changelog feed, a "what's new" widget or web component, an embeddable changelog, a release feed, or to make their shipping log machine-readable / syndicatable. Triggers on "changelog as data", "changelog.json", "RSS feed for releases", "what's new widget", "embed the changelog", "release feed", "ship-feed". Part of the /ship- pack.

Builds an embeddable "ask the guide" assistant for any app: chunks the project's user-guide markdown into docs/guide-index.json, emits a framework-agnostic web component, and a reference /api/ask-docs route that retrieves the top sections and asks an LLM to answer WITH citations to guide anchors. Model-pluggable (Claude API, Vercel AI Gateway, or local Ollama). Use when the user wants an in-app help bot, docs chatbot, "ask the docs/guide" widget, support assistant, RAG over the user guide, embeddable help search, or "answer questions from my documentation." Triggers on "ask the guide", "help bot", "docs chatbot", "ask-docs", "in-app help assistant", "chat with my user guide", "guide search widget".

Generates an in-app first-run onboarding tour from a project's user guide and screenshots — an ordered docs/onboarding.json (steps with target selectors, copy, and optional screenshot ids) plus an embeddable, themeable coachmark/tour web component. Derives the activation path from the guide's main workflows, themes from docs/brand.json, and stays in sync via docs/VERSION. Use when the user wants an onboarding tour, first-run experience, product tour, guided tour, coachmarks, walkthrough overlay, tooltips/hints for new users, a "show me around" flow, an onboarding checklist, or to turn the user guide into an in-app tour. Triggers on "onboarding tour", "first-run", "product tour", "coachmarks", "guided tour", "in-app walkthrough", "new-user tour", "ship-onboarding".

Generates an investor one-pager plus a slide-by-slide pitch deck outline from a project's own evidence — docs/brand.json (name, tagline, colors, fonts), the shipping log + git momentum stats, and the user guide. Produces docs/pitch/one-pager.md, a themeable HTML render, and docs/pitch/deck-outline.md covering problem, solution, what's shipped (momentum), who it's for, and clearly-labeled traction placeholders. Never fabricates a metric. Use when the user wants an investor pitch, one-pager, pitch deck, deck outline, fundraising doc, investor update, exec summary, or "turn what we've shipped into a pitch." Triggers on "investor one-pager", "pitch deck", "deck outline", "fundraising one-pager", "investor summary", "make a pitch", "pitch from our shipping log".

Generates a launch kit from a release — a press release, Product Hunt assets, and a launch-day checklist — written from the project's shipping log and brand.json. This skill should be used when the user wants to launch or announce a release: a press release, a Product Hunt / Hacker News / Show HN / Reddit / Indie Hackers submission (tagline, description, maker's first comment), a launch announcement, a launch-day plan, or a "launch kit" / "launch assets" / "press kit" / "media kit". Triggers on "press release", "launch kit", "Product Hunt assets", "launch this release", "announce v1.2", "maker comment", "launch checklist", "PH tagline". Public-safe by design — it never fabricates quotes, customers, or metrics.

Turns a project's changelog, shipping log, or user guide into a short promo-video PLAN — a brand-voiced voiceover script, a timed shotlist, and a storyboard outline written to docs/promo/. Reads docs/brand.json (colors + fonts) and docs/VERSION so the plan matches the current release, and emits ready-to-run prompts for whatever generator the user has (Ad Lab generate- scripts, Directors Palette, or any local image/video tool) via adapters — nothing is assumed installed. Use when the user wants a promo video, launch teaser, demo reel, trailer, sizzle, social ad, "what's new" video, video script, voiceover script, shotlist, or storyboard for a release or feature. Triggers on "make a promo", "promo plan", "launch video", "teaser", "video script for this release", "storyboard the changelog".

Generates a public-facing, investor-enticing changelog ("shipping log") from a git or GitHub repository's recent history. This skill should be used when the user wants a changelog, release notes, a "what's new" feed, or a "shipping log" written for end users and investors rather than engineers — grouped by version (or date/release) with New / Improved / Fixed / Security sections, benefit-first copy, momentum stats, and an optional landing-page component. Triggers on requests like "changelog for the last N days", "shipping log", "what's new for the public/investors", "turn my commits into release notes", or "show that we're shipping constantly".

Creates or updates a complete, versioned user and admin guide for any project, written for non-developers. Stamps the guide with the shared docs/VERSION anchor and links to the shipping log so "how to use it" stays in sync with "what changed". Use when the user asks for user docs, admin docs, a product manual, feature guide, walkthrough, onboarding or help docs, an SOP, or wants the project explained from an end-user rather than a developer perspective.