Total 58,637 skills
Showing 12 of 58637 skills
Install, audit, repair, and manage a loopback-only CLIProxyAPI bridge that registers subscription-backed Codex, Grok, Antigravity/Gemini, or newly added CLI models in WorkBuddy. Use whenever the user asks to connect a local CLI or agent model to WorkBuddy, install CLIProxyAPI, add or repair a WorkBuddy custom model, preserve image/tool/reasoning/Fast capabilities, onboard another CLI provider, or diagnose a WorkBuddy model that stopped working. This Skill is macOS-first and should be used even when the user names only the model or says their local WorkBuddy API has expired.
Create, rewrite, shorten, or review /goal prompts for Codex, Claude Code, and other coding agents. Use only when the user explicitly requests /goal text or asks to convert a task into /goal; never start the goal automatically.
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, RELIABILITY.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says 'this works on my machine but I am scared to touch it'. For a large aged codebase, use remove-technical-debt; to decide structure before building, use design-code-architecture; for a product and UX pass, use improve-app. For one framework in isolation, invoke that skill directly.
Design shared vocabulary for deep modules. Use this when you want to design or improve a module's interface, identify opportunities for deepening, decide where to place seams, make code more testable or navigable by AI, or when other skills require vocabulary for deep modules.
Test-Driven Development. Use this when users want to build features or fix bugs with a test-first approach, mention "red-green-refactor", or want to integrate tests.
Scaffold a new product page or screen from the compiled StyleSeed output grammar, surface adapter, brand recipe, and project lock.
Generate a composed UI pattern from the active StyleSeed grammar and brand recipe using existing primitives.
Design review grounded in Checklist Design's 100+ published checklists. Two modes — audit works through a matching checklist item by item and reports what's present, partially present or missing and whether each gap matters; critique gives quick, honest peer-style feedback on hierarchy, layout, typography, colour, accessibility, interaction and polish. Use when someone shares a UI screenshot, mockup, live URL or local build and wants a design review, feedback, an audit, a completeness check, or to know what's missing — phrasings like "does this look right," "roast my landing page," "is this accessible," "review my dashboard," "what's missing from this checkout," "does this cover everything," or "check this against the Login checklist." Covers websites, web apps, mobile apps, design system components and user flows.
Create a COMPLETE, render-safe brand kit for ANY brand under brand/<id>/ — design.md + the editorial engine (editorial/) + an engine-agnostic voice lock + outlined logos + palette-driven static & dynamic backgrounds + device mockups + stickers + a brand board & sheet + a brand.json manifest. The kit is consumed by /use-brand, which turns it into any deliverable — website, slide deck, PDF, social/OG cards, marketing copy, dev tokens, or a video (handed to /make-video). Two modes - GENERATE from scratch via an interactive discovery flow + a multi-direction inspiration board the user picks in the browser, or IMPORT an existing brand by crawling its portal. Self-contained - every generator reads bundled templates in $SKILL_DIR/assets/, never a reference kit. Trigger - /make-brand.
Prepare a reusable, technology-agnostic environment for local tests and QA. Compiles discovery into cross-platform launch scripts, provisions the configured browser provider autonomously, and writes the shared test-env descriptor consumed by UI and integration-test skills.
Render Blender scenes with the right engine and settings — Cycles for photoreal, EEVEE for speed/stylized, sample counts, denoising (OptiX/OIDN), light path tuning, color management (AgX/Filmic), file output (PNG/EXR/MP4), animation rendering. Use whenever the user asks to "render this", "produce an image", "render a frame / animation", "make a final image", "save the render", or any output-generation request. Make sure to use this skill even if the user does not say "render" — also covers "make a picture", "save the result", "produce a final image", "export as image".
Use when investigating Jetpack Compose recomposition cost, compiler stability reports, skippability, unstable parameters, frame-rate State reads, cross-phase snapshot back-writing, or @ReadOnlyComposable contracts.