kitfunso
- 163 skills
- 0 followers
- 2 days ago last updated
- ▌ Hyperframes Keyframes · kitfunso bundleUse when a HyperFrames composition needs a punch-in, punch-out, zoom, reframe, Ken Burns treatment, camera move, visual match/whip handoff, or other seek-safe 2D/3D keyframes; also for GSAP, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.
- ▌ Jev · kitfunsoWire TypeSafe Jev into a hook, script or repo the measured way. Our question-writing rules, the lint, the labelled bench against a free baseline, the transcript replay, and the go-live rule. Use with /typesafe-ai whenever a Jev, TypeSafe, noul, choice or score call is being written, changed or reviewed, and whenever code adds an LLM call that classifies, routes, filters, grades or answers yes/no (to test whether Jev should replace it).
- ▌
- ▌ Coord · kitfunso bundleClaims board for parallel Claude sessions on one repo. Use before starting a roadmap item, PR or release another session might own, or when a command is refused with "held by another live session".
- ▌ Learn · kitfunso bundleManage project learnings: log, show, search, prune, or export them. Use whenever someone asks to log a learning or whether a lesson is worth keeping, what we have learned, or to check learnings for stale or contradicting entries.
- ▌ SEO Review · kitfunso bundleSEO and AEO (answer-engine) review of any website. Covers Search Console totals and trends, index coverage, AI-crawler access, duplicate hosts, share images, structured data, Bing and IndexNow, a local HTML report, then one fix PR. Use when asked to check GSC, review or improve SEO/AEO, or explain why a site gets little or less search traffic, for hippo-memory.com, phzse.com, braingymdaily.app, mure-energy.com, boring-math.com or any other site. boring-math.com's weekly calculator-page batch is /gsc-review.
- ▌ Investigate 2 · kitfunso bundleSystematic debugging with root cause investigation. Use when asked to debug, investigate or fix a bug, an error, or a result that looks wrong. (gstack)
- ▌ Prune Tests · kitfunso bundleMake a repo's commit gate (CI) fast and green: time each hook, fix red tests, narrow what a change runs, and cut tests that catch no bug another test catches, proved with planted bugs and replayed past fixes. Use when asked to clean up, dedupe or trim tests, cut useless or redundant tests, make tests or CI faster, or get CI green.
- ▌ General Video · kitfunso bundleAuthor or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated motion-first unit, including an animated title. Route fresh creation through hyperframes before using this skill.
- ▌ Executing Plans · kitfunso bundleUse when you have a written implementation plan to execute in a separate session with review checkpoints
- ▌
- ▌ Hyperframes Studio · kitfunsoHyperFrames Studio layout: timeline tracks, sub-compositions per scene, caption safe zones. Single edits live in /hyperframes-core.
- ▌ Writing For Agents · kitfunso bundleWriting documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
- ▌ Project Scaffold 3 · kitfunso bundleScaffold a new project using a four-document engineering framework — PRD, Architecture, AI Rules, and Plan — that turns "vibe coding" into disciplined engineering. Use when the user starts a new project, app, or major feature, or asks to scaffold, plan, or set up a project with proper structure and guardrails against scope creep and spaghetti code.
- ▌ Brainstorming · kitfunsoUse before creative work: new features, components, or behavior changes. Explores intent, requirements, design before implementation.
- ▌ Full Power 2 · kitfunso bundleMaximize agent capability by spawning sub-agents, leveraging all available resources, thinking deeply, and making no mistakes. Use when tackling complex or high-stakes tasks that demand thoroughness.
- ▌ De Sloppify 2 · kitfunso bundleTwo-pass development pattern for cleaner output. Use after implementing a large feature, complex refactor, or any substantial code change. Separates implementation from cleanup for better results. Two focused agents beat one constrained agent.
- ▌ Self Review 2 · kitfunso bundleReview all changes made in the current session for mistakes, missed requirements, and regressions. Use when the user asks to review changes, check work, or verify correctness before wrapping up.
- ▌ Publish Repo 2 · kitfunso bundleShip an npm package release: bump version, update CHANGELOG/README/manifests, build, test, commit, tag, npm publish, push, and optionally install globally. Use when the user says 'publish', 'release', 'ship the package', 'bump version and push', or 'update docs and publish npm'. Works for any Node.js repo with a package.json.
- ▌ Search First 2 · kitfunso bundleResearch-before-coding workflow. Use BEFORE implementing any significant feature to check for existing libraries, MCP servers, patterns, or solutions. Prevents reinventing the wheel. Use when adding new dependencies, building integrations, or starting features that might have existing solutions.
- ▌ Build Release 2 · kitfunso bundleBump iOS/Android build numbers, build the Android .aab bundle, commit and push. Use this skill whenever the user says 'build release', 'bump build', 'build aab', 'bump and push', 'bump ios build number', 'build the aab file', or any combination of bumping build numbers, building Android bundles, and pushing. Also trigger when user says 'release build' or 'ship the build'.
- ▌ Eval Driven Dev 2 · kitfunso bundleEval-Driven Development (EDD) — treating evals as unit tests for AI-assisted development. Use when building or modifying AI workflows, agent pipelines, prompt engineering, or any feature where output quality needs measurement. Define success criteria BEFORE implementing.
- ▌ Project Scaffold 2 · kitfunso bundleGenerate the four foundation documents for a new project: PRD, Architecture, AI Rules (CLAUDE.md), and Plan. Use when starting a new project, repo, or major initiative from scratch. Triggered by 'scaffold', 'new project', 'kickoff', 'project init', or 'set up a new project'.
- ▌ Git Commit Helper 2 · kitfunso bundleGenerate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
- ▌ Gstack Upgrade 2 · kitfunsoUpgrade 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".
- ▌ QA 3 · kitfunso bundleSystematically 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.
- ▌ Browse 3 · kitfunso bundleFast 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".
- ▌ QA Only 3 · kitfunso bundleReport-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.
- ▌ Office Hours 3 · kitfunso bundleYC 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 suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use before /plan-ceo-review or /plan-eng-review.
- ▌ Design Review 3 · kitfunso bundleDesigner'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.
- ▌ Plan Ceo Review 3 · kitfunso bundleCEO/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.
- ▌ Plan Eng Review 3 · kitfunso bundleEng 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.
- ▌ Document Release 3 · kitfunso bundlePost-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.
- ▌ Plan Design Review 3 · kitfunso bundleDesigner'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.
- ▌ Design Consultation 3 · kitfunso bundleDesign 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.
- ▌ Setup Browser Cookies 3 · kitfunso bundleImport cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) 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 2 · kitfunsoFast 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. gstack also includes development workflow skills. When you notice the user is at these stages, suggest the appropriate skill: - Brainstorming a new idea → suggest /office-hours - Reviewing a plan (strategy) → suggest /plan-ceo-review - Reviewing a plan (architecture) → suggest /plan-eng-review - Reviewing a plan (design) → suggest /plan-design-review - Creating a design system → suggest /design-consultation - Debugging errors → suggest /investigate - Testing the app → suggest /qa - Code review before merge → suggest /review - Visual design audit → suggest /design-review - Ready to deploy / create PR → suggest /ship - Post
- ▌ QA 2 · kitfunsoSystematically 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.
- ▌ Browse 2 · kitfunsoFast 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".
- ▌ QA Only 2 · kitfunsoReport-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.
- ▌ Office Hours 2 · kitfunsoYC 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 suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use before /plan-ceo-review or /plan-eng-review.
- ▌ Design Review 2 · kitfunsoDesigner'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.
- ▌ Plan Ceo Review 2 · kitfunsoCEO/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.
- ▌ Plan Eng Review 2 · kitfunsoEng 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.
- ▌ Document Release 2 · kitfunsoPost-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.
- ▌ Plan Design Review 2 · kitfunsoDesigner'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.
- ▌ Design Consultation 2 · kitfunsoDesign 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.
- ▌ Setup Browser Cookies 2 · kitfunsoImport cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) 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".
- ▌ PDF · kitfunso bundlePDF toolkit for extracting, creating, merging, splitting, and filling forms. Use to process or analyze PDF documents programmatically.
- ▌ Eli5 · kitfunsoExplain a topic like I'm 5, using a big-picture HTML artifact with few words. Use for a dead-simple picture explainer of how something works.
- ▌ Figma · kitfunso bundleImport Figma assets, brand tokens, components, motion, and shaders into HyperFrames. Use for figma.com links or Figma design imports.
- ▌ Autoplan · kitfunso bundleRuns CEO, design, eng, and DX plan reviews with auto-decisions. Use for 'run all reviews', 'autoplan', full review pipelines. (gstack)
- ▌ Media Use · kitfunso bundleAgent Media OS for HyperFrames: resolve/generate BGM, SFX, images, icons, logos, voice, color grade, LUT; handles vague visual feedback.
- ▌ Sync Gbrain · kitfunsoRefreshes gbrain against this repo's code and updates CLAUDE.md agent search guidance. Wraps gstack-gbrain-sync. (gstack)
- ▌ Setup Gbrain · kitfunso bundleSet up gbrain for this coding agent - install CLI, init brain (PGLite/Supabase), register MCP, set trust policy. (gstack)
- ▌ Gstack Upgrade · kitfunso bundleUpgrade 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".
- ▌ Artifacts Builder · kitfunso bundleBuild complex multi-component claude.ai artifacts with React, Tailwind, and shadcn/ui. Use for state, routing, or shadcn/ui components.
- ▌ Product Launch Video · kitfunso bundleTurn a product URL, script, or brief into a launch/promo video - promos, feature reveals, demos, site tours. Unclear → /hyperframes.
- ▌ Verification Before Completion · kitfunsoRequires running verification commands and confirming output before claiming work is complete, fixed, or passing, or before committing/PRs.
- ▌ Memory · kitfunsoProject memory powered by Hippo. Use when starting a session, after learning something, after hitting an error, or when the user mentions memory/remember/recall. Auto-invoked at session start.
- ▌ Token Discipline · kitfunso bundleMake the agent use proportional effort and spend fewer tokens. Use whenever the user wants concise answers, quick mode, low-token mode, fast diagnosis, minimal prompting, compact planning, answer-first behavior, or cheaper agent behavior. Also use for low-stakes repo-local checks like "old version", "stale badge", "release tag", "current repo", or "ready to push", especially when the user says things like "just answer", "diagnose only", "one line", "short answer", "no tools", or "no browser". Use it whenever a task risks expanding beyond what was asked, when duplicate messages arrive, when browser/tool overuse is likely, or when the agent should solve the task via the cheapest adequate path first and escalate only if needed.
- ▌ QA · kitfunso bundleSystematically 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.
- ▌ Browse · kitfunso bundleFast 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 · kitfunso bundleFast 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. gstack also includes development workflow skills. When you notice the user is at these stages, suggest the appropriate skill: - Brainstorming a new idea → suggest /office-hours - Reviewing a plan (strategy) → suggest /plan-ceo-review - Reviewing a plan (architecture) → suggest /plan-eng-review - Reviewing a plan (design) → suggest /plan-design-review - Creating a design system → suggest /design-consultation - Debugging errors → suggest /investigate - Testing the app → suggest /qa - Code review before merge → suggest /review - Visual design audit → suggest /design-review - Ready to deploy / create PR → suggest /ship - Post
- ▌ Roll Check · kitfunso bundleCheck and fix futures contract roll adjustments. Detects when active contracts have rolled since signal entry, adjusts signal_price by the roll spread to maintain PnL continuity, and updates Supabase + local files. Use when asked to "check rolls", "contract roll", "roll check", "roll adjustment", or when investigating price jumps on active positions.
- ▌ Smoke Test · kitfunso bundleUse when the user asks to smoke test, verify, or check the frontend after a deploy or frontend change. Runs Playwright smoke tests against production or local dev server.
- ▌ Office Hours · kitfunso bundleYC 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 suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use before /plan-ceo-review or /plan-eng-review.
- ▌ Quant Report · kitfunso bundleUse when presenting validation results, backtest metrics, model comparisons, or pipeline status. Formats output in consistent structured templates. Trigger on validation reports, model results, pipeline summaries, or when the user asks for a status check.
- ▌ Social Brand · kitfunso bundleApplies AUTOMATION Creators brand guidelines to social media content, presentations, and marketing materials. Use when creating content for AUTOMATION Creators that requires consistent branding including colors, typography, visual style, and brand voice. Particularly relevant for social media posts, lead magnets, guides, and promotional materials.
- ▌ Design Review · kitfunso bundleDesigner'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.
- ▌ Model Improve · kitfunso bundleFull commodity model improvement workflow — from audit through exhaustive feature engineering, two-stage selection, Optuna optimization, multi-layer validation, data source verification, and production deployment. Use PROACTIVELY when the user asks to improve, rebuild, develop, upgrade, or remodel any commodity trading model. Also trigger when user mentions feature engineering, model performance, Sharpe improvement, or adding new features to a commodity model. This is the primary workflow for all model development work in the Quantamental project.
- ▌ Plan Ceo Review · kitfunso bundleCEO/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.
- ▌ Plan Eng Review · kitfunso bundleEng 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.
- ▌ Autonomous Loops · kitfunso bundlePatterns for autonomous agent loops — sequential pipelines, parallel generation, continuous PR loops, and de-sloppify passes. Use when setting up automated workflows, CI/CD agent loops, batch processing with Claude, or multi-agent orchestration. Covers loop architecture from simple sequential to RFC-driven DAG orchestration.
- ▌ Document Release · kitfunso bundlePost-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.
- ▌ Strategic Compact · kitfunso bundleGuide for when to use /compact strategically. Use when context is getting large, when transitioning between task phases (research→planning→implementation), or when the user asks about compaction timing. Also use when tool call count is high or context feels stale.
- ▌ Content Hash Cache · kitfunso bundlePattern for caching expensive file operations using SHA-256 content hashes instead of file paths. Use when building data pipelines that process files (PDF parsing, OCR, image analysis, signal computation) and need caching. File rename = cache hit. Content change = auto-invalidation.
- ▌ Plan Design Review · kitfunso bundleDesigner'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.
- ▌ Creator Style Mimic · kitfunso bundleAnalyze and mimic the writing style, hooks, voice, and patterns of successful creators from your Airtable database and content frameworks. Match creator voice based on audience, platform, and content type. Use when testing different voices, creating content in a specific influencer's style, or finding your unique voice through analysis.
- ▌ Viral Hook Generator · kitfunso bundleApply proven viral hook formulas (contrarian, benefit-driven, transformation, how-to) to transform content ideas into attention-grabbing openings. Use when creating social media posts, video scripts, headlines, or any content requiring high-engagement hooks. Based on Kallaway's 6 Power Words Framework.
- ▌ Twitter Thread Builder · kitfunso bundleConvert long-form content into engaging Twitter threads with hooks, numbered tweets, visual hierarchy, and strategic CTAs. Optimized for Twitter's algorithm and thread readability. Use when adapting blog posts, articles, or complex ideas for Twitter's 280-character format.
- ▌ Framework Content Mixer · kitfunso bundleCombine multiple content frameworks (viral hooks + title patterns + AI video structures) for compound engagement effects. Layers persuasion techniques to create long-form content, video scripts, or multi-platform campaigns. Use when single frameworks aren't enough or when creating flagship content requiring maximum impact.
- ▌ Youtube Title Optimizer · kitfunso bundleGenerate high-performing YouTube titles using 97+ proven patterns from viral AI/automation creators (Jack Roberts, Riley Brown). Optimizes for clicks, SEO, and engagement. Includes performance data and pattern matching for specific content types. Use when creating video titles, thumbnails, blog post headlines, or any content requiring maximum click-through rates.
- ▌ Ship · kitfunsoShip 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", or "merge and push". Proactively suggest when the user says code is ready or asks about deploying.
- ▌ Guard · kitfunsoFull 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".
- ▌ Retro · kitfunsoWeekly 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.
- ▌ Freeze · kitfunsoRestrict 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".
- ▌ Review · kitfunsoPre-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.
- ▌ Careful · kitfunsoSafety 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".
- ▌ Investigate · kitfunsoSystematic 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 suggest when the user reports errors, unexpected behavior, or is troubleshooting why something stopped working.
- ▌ Wtf · kitfunsoPlain-English debrief of recent work, a named thing, a decision, or project status. Use for 'wtf is X', '/wtf', '/wtf status'.
- ▌ Canary · kitfunsoPost-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)
- ▌ Commit · kitfunsoStage, commit, and push changes with a plain message, no diff review. Use for 'commit this' or 'commit and push'.
- ▌ Wizard · kitfunso bundleGenerate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
- ▌ QA Only · kitfunso bundleReport-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)
- ▌ Quiz Me · kitfunso bundleLearning-gate quiz on a recent diff or shipped feature. Use for 'quiz me', 'test my understanding', 'force me to learn', or as the mandatory ship-stage hook in /dev-framework-rl.
- ▌ Show Me · kitfunsoHelp the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
- ▌ All Done · kitfunsoAnswer a completion challenge with YES or NO backed by fresh evidence. Use when asked 'all done?' or similar completion checks.
- ▌ Critique · kitfunsoBrutal-honesty critique of completed work, findings ranked by severity with cited evidence and a concrete fix each.
- ▌ Grill Me · kitfunsoAdversarial grilling, interrogate my work, assumptions, and plans until they break or hold