CleanExpo
56 verified skills56 total stars
.claude/skills/arch-plan
# Architecture Plan Skill **Name:** arch-plan **Triggers:** `/arch-plan`, "design implementation for", "architect this feature" **Version:** 1.0.0 --- ## Purpose Lightweight architectural planning that runs in an isolated subagent context. Returns a structured 350-word plan to the main conversation without polluting it with the dozens of file reads the planner walked through. **This is NOT the canonical interactive planning command.** For interactive planning with CEO approval gates, the pr
data-ai1
autoplan
Auto-review pipeline — reads the full CEO, design, and eng review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when asked to "auto review", "autoplan", "run all reviews", "review this plan automatically", or "make the decisions for me". Proactively suggest when the user has a plan file and wants to run the full review gauntlet without answering 15-30 intermediate questions. (gstack)
development1
benchmark
Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time". (gstack)
development1
browse
Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence. Use when asked to "open in browser", "test the site", "take a screenshot", or "dogfood this". (gstack)
testing1
canary
Post-deploy canary monitoring. Watches the live app for console errors, performance regressions, and page failures using the browse daemon. Takes periodic screenshots, compares against pre-deploy baselines, and alerts on anomalies. Use when: "monitor deploy", "canary", "post-deploy check", "watch production", "verify deploy". (gstack)
testing1
.claude/skills/chrome-linear
# CHROME-LINEAR-TRIAGE SKILL **Skill Name**: chrome-linear-triage **Version**: 1.0.0 **Trigger**: `/chrome-linear`, "triage linear in browser", "open linear", "check linear board" **Description**: Open Linear in Chrome, screenshot current board state, triage issues, and update statuses without leaving the browser. --- ## SKILL PURPOSE Navigate to the Linear workspace in Chrome, capture the board, triage backlog issues visually, and mark issues Done/In Progress directly through the browser wh
testing1
.claude/skills/chrome-prod
# CHROME-PRODUCTION-VERIFY SKILL **Skill Name**: chrome-production-verify **Version**: 1.0.0 **Trigger**: `/chrome-prod`, "verify production", "smoke test", "check the live site" **Description**: Full browser smoke test of the CCW production site — login, dashboard, key modules, video banners — with screenshots at each step. --- ## SKILL PURPOSE Run a visual smoke test of `ccw-crm-web.vercel.app` after every deployment. Confirm login works, key modules render, the DemoVideoBanner shows corre
development1
.claude/skills/chrome-vercel
# CHROME-VERCEL-MONITOR SKILL **Skill Name**: chrome-vercel-monitor **Version**: 1.0.0 **Trigger**: `/chrome-vercel`, "check vercel", "vercel deployment", "check build logs" **Description**: Navigate to the Vercel dashboard in Chrome to monitor deployment status, check build logs, and verify or set environment variables. --- ## SKILL PURPOSE Provide visual confirmation of CCW production deployment state on Vercel — build logs, deployment status, domain health, and environment variable verifi
development1
.claude/skills/context-monitor
# Context Monitor Skill **Name:** context-monitor **Triggers:** `/context`, auto (every 10 messages) **Version:** 1.0.0 --- ## Purpose Monitors conversation context usage and prevents context overflow. --- ## Commands ### `/context` Shows current context status **Output:** ``` 📊 Context Status Tokens used: ~85,000 / 200,000 (42%) Status: 🟢 Normal Messages: 42 Last CLAUDE.md read: 15 messages ago (⚠️ re-read recommended) Recommendations: - Continue normally - Re-read CLAUDE.md within
development1
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use /plan-design-review. Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish". Proactively suggest when the user mentions visual inconsistencies or wants to polish the look of a live site. (gstack)
development1
document-release
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped. (gstack)
development1
heygen-brand-governor
Single source of truth for HeyGen avatar, voice, dimension, and background selection across all CCW demo video productions. Ensures brand consistency across batch runs. Use when: producing any HeyGen video, selecting avatars/voices, or reviewing brand compliance.
development1
heygen-script-optimizer
Transforms raw narration scripts into HeyGen-optimised format. Handles character limits, avatar speech pacing (140 wpm), segment splitting, and duration tier enforcement. Use when: preparing a script for HeyGen avatar delivery, or generating module demo scripts.
development1
.claude/skills/implement
# Implement Skill **Name:** implement **Triggers:** `/implement` (manual invocation only — not natural language) **Version:** 1.0.0 --- ## Purpose Three-phase structured build pipeline: PLAN → BUILD → VERIFY. Each phase runs in an isolated subagent context so the main session sees only the verdict, not the file-by-file walkthrough. Designed to drive a complete feature from approved plan to commit-ready code without polluting the main conversation. This skill is **manual invocation only** (n
development1
.claude/skills/next
# Next Skill **Name:** next **Triggers:** `/next` (manual invocation only — not natural language) **Version:** 1.0.0 --- ## Purpose Task transition. Snapshots the current task state to disk, then guides the user to either `/compact` (if the next task is related) or `/clear` (if unrelated). Single biggest token saver in the optimization pack — the audit found that 98.5% of tokens in long sessions are conversation re-reading, and `/clear` between unrelated tasks eliminates that cost entirely.
testing1
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. (gstack)
development1
qa
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack)
development1
remotion-render-pipeline
Renders CCW Remotion videos to MP4, validates output, copies to YouTube upload queue, triggers the YouTube upload script, patches DemoVideoBanner.tsx with new IDs, and commits + pushes all changes. Full render-to-live pipeline. Use when: any CCW Remotion video needs to be rendered and published to YouTube.
testing1
remotion-scene-builder
Creates production-ready Remotion scene TSX files for CCW ERP walkthrough videos. Follows established patterns from existing scenes (BoardroomVideo, OnboardingVideo). Handles animation timing, interpolation, and CCW brand guidelines. Use when: building a new scene for any CCW Remotion video, editing existing scenes, or debugging animation/layout issues.
development1
retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. (gstack)
development1
setup-deploy
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".
testing1
.claude/skills/spec-interview
# Spec Interview Skill **Name:** spec-interview **Triggers:** `/spec-interview`, when requirements unclear **Version:** 1.0.0 --- ## Purpose Interviews user to gather complete requirements before planning. --- ## Interview Questions When requirements are unclear, ask: ### 1. Feature Clarity **Question:** "What is this feature supposed to do?" **Why:** Need clear objective ### 2. User Impact **Question:** "Who will use this and why?" **Why:** Understand user needs ### 3. Success Criteri
tools1
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack)
testing1
careful
Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", or "careful mode". (gstack)
development1
.claude/skills/chrome-github
# CHROME-GITHUB-PR SKILL **Skill Name**: chrome-github-pr **Version**: 1.0.0 **Trigger**: `/chrome-github`, "open github pr", "review pr in browser", "check github actions" **Description**: Navigate GitHub in Chrome to create PRs, review diffs, check Actions CI status, and merge branches when the `gh` CLI is unavailable or when visual diff review is needed. --- ## SKILL PURPOSE Provide browser-based GitHub workflow automation for the CCW-CRM repository — PR creation, CI monitoring, diff revi
tools1
.claude/skills/fix
# Fix Skill **Name:** fix **Triggers:** `/fix`, "quick fix for", "patch this bug" **Version:** 1.0.0 --- ## Purpose Minimal-context targeted fix. Reads only the implicated files (line ranges, never full files), makes the minimum viable change, runs the targeted test, and reports under 80 words. The cheapest skill in the pack — designed for typos, missing nullchecks, wrong constants, off-by-one errors, and other surgical edits. This is the opposite end of the spectrum from `/implement`. Use
testing1
office-hours
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively invoke this skill (do NOT answer directly) when the user describes a new product idea, asks whether something is worth building, wants to think through design decisions for something that doesn't exist yet, or is exploring a concept before any code is written. Use before /plan-ceo-review or /plan-eng-review. (gstack)
development1
.claude/skills/chrome-supabase
# CHROME-SUPABASE-INSPECT SKILL **Skill Name**: chrome-supabase-inspect **Version**: 1.0.0 **Trigger**: `/chrome-supabase`, "open supabase dashboard", "check supabase rls", "supabase browser" **Description**: Navigate Supabase dashboard in Chrome to inspect RLS status, run SQL queries in the editor, check auth hooks, and review security advisors. --- ## SKILL PURPOSE Provide visual access to the Supabase dashboard for tasks that require the UI — activating the JWT hook, reviewing security ad
testing1
.claude/skills/chrome-youtube
# CHROME-YOUTUBE-UPLOAD SKILL **Skill Name**: chrome-youtube-upload **Version**: 1.0.0 **Trigger**: `/chrome-youtube`, "upload to youtube", "open youtube studio", "schedule youtube video" **Description**: Open YouTube Studio in Chrome to upload, schedule, or manage CCW demo and boardroom videos when the API quota is exhausted or OAuth setup is incomplete. --- ## SKILL PURPOSE Automate or assist YouTube video management for the CCW channel through the browser UI. This is the fallback path whe
development1
codex
OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via codex review with pass/fail gate. Challenge: adversarial mode that tries to break your code. Consult: ask codex anything with session continuity for follow-ups. The "200 IQ autistic developer" second opinion. Use when asked to "codex review", "codex challenge", "ask codex", "second opinion", or "consult codex". (gstack)
tools1
connect-chrome
Launch real Chrome controlled by gstack with the Side Panel extension auto-loaded. One command: connects Claude to a visible Chrome window where you can watch every action in real time. The extension shows a live activity feed in the Side Panel. Use when asked to "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser".
tools1
cso
Chief Security Officer mode. Infrastructure-first security audit: secrets archaeology, dependency supply chain, CI/CD pipeline security, LLM/AI security, skill supply chain scanning, plus OWASP Top 10, STRIDE threat modeling, and active verification. Two modes: daily (zero-noise, 8/10 confidence gate) and comprehensive (monthly deep scan, 2/10 bar). Trend tracking across audit runs. Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review". (gstack)
testing1
.claude/skills/ctx
# Context Health Check Skill **Name:** ctx **Triggers:** `/ctx` (manual invocation only — not natural language) **Version:** 1.0.0 --- ## Purpose One-line context health check. Runs the built-in `/context` command, summarises the result, and recommends ONE action: disconnect an idle MCP server, run `/compact`, run `/clear`, or "context clean" (no action needed). Designed to be cheap enough to run between tasks without itself adding measurable context. This is the diagnostic counterpart to `
tools1
design-consultation
Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview pages. Creates DESIGN.md as your project's design source of truth. For existing sites, use /plan-design-review to infer the system instead. Use when asked to "design system", "brand guidelines", or "create DESIGN.md". Proactively suggest when starting a new project's UI with no existing design system or DESIGN.md. (gstack)
testing1
design-shotgun
Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. Standalone design exploration you can run anytime. Use when: "explore designs", "show me options", "design variants", "visual brainstorm", or "I don't like how this looks". Proactively suggest when the user describes a UI feature but hasn't seen what it could look like. (gstack)
data-ai1
.claude/skills/docker-ops
# Docker Operations Skill **Name:** docker-ops **Triggers:** `/docker` **Version:** 1.0.0 --- ## Purpose Manages Docker containers for local development. --- ## Commands ### `/docker status` Shows status of all containers ```bash cd C:\CCW-Online ERP && docker-compose ps ``` ### `/docker up` Starts all services ```bash cd C:\CCW-Online ERP && docker-compose up -d ``` ### `/docker down` Stops all services ```bash cd C:\CCW-Online ERP && docker-compose down ``` ### `/docker logs [serv
development1
freeze
Restrict file edits to a specific directory for the session. Blocks Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits". (gstack)
development1
gstack-upgrade
Upgrade gstack to the latest version. Detects global vs vendored install, runs the upgrade, and shows what's new. Use when asked to "upgrade gstack", "update gstack", or "get latest version".
testing1
guard
Full safety mode: destructive command warnings + directory-scoped edits. Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety". (gstack)
development1
heygen-cost-tracker
Budget management and cost tracking for HeyGen video production. Maintains a cost ledger, provides forecasts, and enforces monthly budget caps. Use when: checking HeyGen spend, forecasting batch costs, or reviewing production history.
testing1
heygen-production-orchestrator
End-to-end orchestration for HeyGen demo video production. Single module or batch. Coordinates script generation, brand config, API submission, polling, quality gate, and cost tracking. Use when: producing demo videos for CCW modules, running batch production, or testing the pipeline.
development1
heygen-quality-gate
Post-production validation for HeyGen demo videos. Checks completion status, duration tolerance, cost compliance, and URL availability before publishing. Use when: a HeyGen video has finished rendering and needs verification before upload.
testing1
investigate
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)
development1
land-and-deploy
Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production". (gstack)
testing1
learn
Manage project learnings. Review, search, prune, and export what gstack has learned across sessions. Use when asked to "what have we learned", "show learnings", "prune stale learnings", or "export learnings". Proactively suggest when the user asks about past patterns or wonders "didn't we fix this before?"
tools1
plan-design-review
Designer's eye plan review — interactive, like CEO and Eng review. Rates each design dimension 0-10, explains what would make it a 10, then fixes the plan to get there. Works in plan mode. For live site visual audits, use /design-review. Use when asked to "review the design plan" or "design critique". Proactively suggest when the user has a plan with UI/UX components that should be reviewed before implementation. (gstack)
testing1
qa-only
Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack)
development1
remotion-audio-sync
Generates ElevenLabs narration audio for CCW Remotion videos and syncs it with scene animations. Covers script writing, audio generation, Remotion Audio component integration, and timing alignment between voice and visuals.
content-media1
remotion-video-producer
Orchestrates end-to-end production of CCW ERP Remotion walkthrough videos. Covers scripting, scene planning, composition assembly, rendering, and YouTube upload. Entry point for producing any new CCW training or marketing video. Use when: creating a new video from scratch, extending an existing video with new scenes, or running the full produce-and-publish workflow.
testing1
.claude/skills/research
# Research Skill **Name:** research **Triggers:** `/research`, "how does X work", "trace this flow", "explain the auth path", "where is X implemented" **Version:** 1.0.0 --- ## Purpose Answers codebase questions in an isolated subagent context so the main conversation never bloats with intermediate file reads. The parent session sees only the final 250-word summary — never the dozens of grep results, file fragments, and dead-end imports the subagent walked through to find the answer. This s
development1
.claude/skills/resume
# Resume Skill **Name:** resume **Triggers:** `/resume` (manual invocation only — not natural language) **Version:** 1.0.0 --- ## Purpose Recovers from a saved task snapshot after `/clear` or after starting a new session. Reads `.claude/snapshots/last-task.md` and `.claude/snapshots/pre-compact-diff.txt` (if they exist), reports a brief status under 80 words, and asks what to work on next. Does NOT re-read previously-touched files — that defeats the entire point of clearing context. This is
business1
review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes. (gstack)
development1
setup-browser-cookies
Import cookies from your real Chromium browser into the headless browse session. Opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages. Use when asked to "import cookies", "login to the site", or "authenticate the browser". (gstack)
testing1
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)
development1
unfreeze
Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits". (gstack)
data-ai1
youtube-uploader
Autonomously uploads CCW HeyGen demo videos to YouTube as Unlisted, collects video IDs, and patches DemoVideoBanner.tsx + video-registry.json. One-time OAuth setup required. Handles resume, retries, and ID propagation.
content-media1