ai-builder-kit

Generate polished demo videos (MP4) from Playwright specs with AI voiceover, captions, and music. Use when the user says "demo video", "playwright demo", "generate demo", "caption extraction", "voiceover pipeline", "freeze frame merge", or "auto-discover demo" — or wants to: create demo videos for web projects, extract captions from Playwright specs, generate TTS voiceover with ElevenLabs, merge video with freeze-frame timing, add background music, or auto-discover project features to generate demo specs.

Log the current Claude.ai chat conversation as a timestamped, downloadable markdown file ready for an AI second brain. Captures the user's prompts verbatim — every word, plus attachment types — summarizes Claude's responses concisely, and notes every tool, artifact, and MCP call. Use this skill whenever the user types '/log', 'log this conversation', 'log this session', 'save conversation log', 'convo log', 'archive this chat', or any similar phrasing — even casually. This skill is manually invoked only: do NOT trigger on your own initiative without an explicit user request, even if the conversation seems like it might be useful to archive.

Log AI coding agent conversation sessions with timestamps in structured markdown. Supports Claude Code, OpenAI Codex CLI, and GitHub Copilot. Use when the user says 'log this session', 'convo log', or wants to create a record of prompts and responses for a project. Auto-detects which agent is running and reads timestamps from the correct history file.

Structured git commit skill for all agents and humans. Use when: committing code changes, the user says "commit", "/jack-git-commit", a worker completes a task and needs to commit, or any agent needs to record work in git. Generates Conventional Commit messages with traceable metadata footers (Goal, Step, Worker) so git log serves as a self-documenting work ledger. Enforces atomic commits, staged-only policy, and NEVER pushes.

Generate draw.io diagrams (`.drawio` XML files) from detailed user prompts, in Jack's brand style. Use when the user asks to create, visualize, draw, or diagram architectures, workflows, pipelines, systems, or processes in draw.io / diagrams.net / XML form. Requires a description of what to diagram — does not analyze codebases automatically. Ask clarifying questions if diagram type, complexity, or subsystems are unclear. Every diagram is exported to PNG via the draw.io CLI and visually validated in a render-view-fix loop before delivery.

Harvests AI documentation into a centralized private knowledge repo using a project-first taxonomy. Two modes: (1) Repo scan - collects AI docs (specs, prompt logs, CLAUDE.md files, gap analyses, kickoff prompts, agent configs) from a source repo. (2) Ad-hoc ingest - captures pasted content exported from ChatGPT, Claude web, Clo.ai, or any AI interface. Triggers on phrases like 'harvest AI docs from', 'move my AI docs to', 'collect my prompt logs', 'sync AI docs to knowledge repo', 'organize my ai-docs folder', 'save this conversation', 'store this export', 'add this to my knowledge repo', or any request to consolidate AI documentation across repositories and AI tools into a single searchable private store. Also trigger when the user pastes a large markdown block that looks like an AI conversation export or asks to file away content from an AI session.

Compare two pull requests or two branches that were produced by different agents attempting the same goal, and recommend which one to adopt. Use when the user asks to "compare PR X and PR Y", "which branch is better", "two agents gave me different PRs for the same task", "triage competing PRs", or any situation where multiple worktrees/branches solved (or attempted) the same goal in parallel and a decision is needed on which to merge or continue from. Produces a functional-requirements table with per-requirement verdicts, a file-level scope audit (extras check), a branch recommendation, and a concrete follow-up plan for what the agent should do after switching to the chosen branch.

Create highly branded PowerPoint presentations from a template .pptx file. Use when the user provides a branded template and wants to generate new slides that look like a professional consultant created them — on-brand, on-layout, using the template's themes, slide masters, and layouts. Triggers on: 'branded deck', 'use this template to create', 'make a presentation matching this brand', 'on-brand slides', or any request to produce a .pptx that must follow an existing template's visual identity. REQUIRES the anthropic pptx skill (or equivalent) as a baseline — this skill does not replicate pptx reading/writing/editing capabilities, it layers brand-aware intelligence on top.

Interactive AEM Edge Delivery Services (EDS/Helix 5) Admin API executor with human-in-the-loop oversight. Use when working with the AEM Admin API (admin.hlx.page) to: (1) Plan and execute admin operations step-by-step (preview, publish, config, access, cache, index, snapshots, code), (2) Execute ONE API request at a time with human review and approval, (3) Document all requests/responses in EXECUTION.md with full traceability, (4) Follow GET/SET/GET verification patterns for safe configuration changes, (5) Resume existing executions and add new steps, (6) Manage site configuration, access control, content operations, and code deployments. For careful AEM admin operations where mistakes are costly - NOT for bulk automation.