ckorhonen
- 80 skills
- 0 followers
- 6 hours ago last updated
- ▌ Reflect · ckorhonen bundleReview a work session, transcript, or tool-call log and compound the learnings into durable improvements: agent rules (AGENTS.md/CLAUDE.md), new or updated skills, slash commands, deterministic scripts, sub-agent delegation, and context-bloat reduction. Use when the user says "reflect", at the end of a work session, on a schedule, or when asked how to make the agent faster, cheaper, or more reliable in this project. Do not use for ordinary code review unless the requested output is agent/process improvement.
- ▌ Reflect Memory · ckorhonenLifecycle maintenance for accumulated agent memory: dedupe, merge, expire, and resolve contradictions across AGENTS.md/CLAUDE.md agent rules, .reflect/ state, and other agent instruction files reflect maintains. Use monthly, when instruction files feel bloated or contradictory, when the agent cites stale rules, or after many reflect runs have accumulated. Not for extracting new learnings — that is the reflect skill.
- ▌ Reflect Skills · ckorhonen bundleScan local agent session logs (Claude Code, Codex) across many sessions, cluster the common failure and friction patterns, then manage the skill portfolio to address them: find and install existing ecosystem skills, create or modify local skills, fix under- or over-triggering descriptions, and remove skills that misfire. Use when the user asks to scan session logs for failure patterns, audit or tune their skills, or asks why a skill never fires. For single-session extraction use reflect instead.
- ▌ Reflect Feedback · ckorhonenAudit whether past reflect improvements are actually working. Reads the .reflect/applied.md ledger and checks each applied rule, skill, command, or script for evidence it fired and helped; grades entries verified, unused, or regressed, and prunes dead weight. Use on a schedule (weekly or every ~10 sessions), when the user asks "are these improvements working?", or before a reflect-memory consolidation pass. Requires prior reflect runs — if no .reflect/ ledger exists, run reflect first.
- ▌ Hone Duplication Hunt · ckorhonenFinds duplicated code patterns across the codebase including exact copies and structural duplication (same logic with different variable names). Ranks by frequency and suggests extraction candidates. Designed for weekly runs. Do NOT use for method length, naming, or style concerns.
- ▌ Hone Magic Number Hunt · ckorhonenSurfaces magic numbers, unexplained string literals, hardcoded URLs, configuration values buried in code, and other "magical" values that should be named constants or config entries. Use when you want a weekly sweep for unnamed literals. Do NOT use for style or formatting audits.
- ▌ Hone Test Naming Audit · ckorhonenChecks that test method and function names read as complete sentences describing behavior. Flags cryptic names like test1, testFoo, or abbreviated names that do not describe what is being tested. Designed to run on every PR. Do NOT use for test coverage, test structure, or non-test code.
- ▌ Hone Broken Windows Hunt · ckorhonenDetects entropy signals in a codebase: stale TODOs, disabled tests, lint suppressions, commented-out code, dead imports, empty catch blocks, and deprecated API usage. Designed for daily runs to catch quality erosion early. Do NOT use for feature work, refactoring planning, or security audits.
- ▌ Hone Intent Clarity Audit · ckorhonenFinds code that obscures its intent: unclear variable names, nested ternaries, boolean parameters without names, overly clever one-liners, and comments that restate code instead of explaining why. Focuses on recently changed files. Do NOT use for method length, duplication, or test naming concerns.
- ▌ Hone Method Brevity Audit · ckorhonenScans a codebase for methods and functions that exceed configurable length thresholds. Reports a ranked list of the longest methods with file:line, language, and surrounding complexity signals. Designed for scheduled weekly runs. Do NOT use for style formatting, indentation, or naming concerns.
- ▌ Hone Automation Opportunities · ckorhonenFinds manual processes that could be automated: manual deploy steps in READMEs, setup instructions that could be scripts, repetitive git workflows, manual testing procedures, and undocumented tribal knowledge. Also checks for artifacts not in source control. Use monthly to surface automation ROI. Do NOT use for code quality or style audits.
- ▌ Hone Naming Specificity Audit · ckorhonenFlags classes, modules, and functions with vague generic names like Manager, Handler, Processor, Helper, Utils, Service, Base, Common, and Misc. Suggests more specific alternatives based on what the code actually does. Use weekly to prevent naming drift. Do NOT use for variable-level naming or style enforcement.
- ▌ Swe Init · ckorhonenInitializes an optional repo-local agent collaboration preference file at `.ai/swe.json` by running a short interview or a zero-question quick mode. Use when a user says `initialize agent settings for this repo`, `set up my local agent prefs here`, `run quick init for this project`, or `create .ai/swe.json for how I like to work`. Do NOT use for `npm init`, project scaffolding, dependency installation, or environment bootstrap.
- ▌ Swe Babysit Pr · ckorhonenBabysits an open pull request end-to-end by polling every minute, triaging new comments and reviews, handling CI failures, iterating on reviewer scores, and stopping only when the PR is ready to merge. Use when a user says `babysit this PR`, `watch this PR until it's merge-ready`, `handle review feedback on my PR`, or `keep iterating on this PR until reviewers are happy`. Do NOT use for a one-shot PR risk review, merged PR production monitoring, or repo-wide CI debugging with no scoped PR.
- ▌ Swe Create Skill · ckorhonenCreates or revises `swe:` skills for this repository using a repeatable authoring workflow: define concrete use cases, tune trigger boundaries, apply progressive disclosure, add matching eval assets, and validate the package. Use when adding a new skill, tightening an existing skill that over- or under-triggers, or distilling an external workflow into a repo-ready skill. Do NOT use for generic documentation edits or for executing the workflow the skill would describe.
- ▌ Swe Test Gap Hunt · ckorhonenIdentifies and prioritizes the highest-value test coverage gaps in a repository or workspace, then incrementally adds or strengthens tests using the local test stack and cleanly scoped subagent work when available. Use when a user says `improve test coverage`, `find weak tests`, `add missing test cases`, `run a recurring test-improvement pass`, or asks for a language-agnostic workflow to strengthen mocks, fixtures, and test structure without chasing raw coverage numbers. Do NOT use for first-time framework selection, broad test-stack migrations, or large production refactors.
- ▌ Swe Pr Risk Review · ckorhonenReviews open or draft pull requests for engineering risk before merge, focusing on missing validation, hidden coupling, rollout and rollback gaps, migrations, feature flags, and other agent-safe next actions. Use when a user says `review this PR for risk`, `pre-merge review`, `is this PR safe to merge`, or asks for a risk-focused PR review. Do NOT use for post-merge production monitoring, broad code smell review, or commit-scoped bug hunting.
- ▌ Swe Security Audit · ckorhonenAudits a repository, workspace, or monorepo for dependency vulnerabilities, outdated security-sensitive packages, license issues, and dependency hygiene gaps, then compiles one evidence-backed report. Use when a user says `run a security audit`, `check dependencies and licenses`, `audit this monorepo for vulnerable packages`, or asks for a package-level security review. Do NOT use for a general secure-code review, threat model, or speculative vulnerability hunt without manifests, lockfiles, or package surfaces to inspect.
- ▌ Swe Docs Drift Audit · ckorhonenAudits a repository for human-facing or operational documentation that drifted from code, config, interfaces, workflows, or repo structure changes. Use when a user says `check docs drift`, `docs are stale`, `update the runbook after this change`, or `what documentation is missing after this change`. Do NOT use for agent-guidance updates, generic documentation rewrites, or writing docs without evidence that they are stale.
- ▌ Swe Performance Hunt · ckorhonenHunts for concrete performance bottlenecks in a scoped repository surface using profiler output, benchmarks, query plans, traces, bundle analysis, or repo evidence, then returns the smallest high-value follow-up experiments or fixes. Use when a user says `find performance bottlenecks`, `why is this slow`, `profile this flow`, `hunt hot paths`, or asks for a recurring performance review. Do NOT use for live incident response, generic observability audits, speculative micro-optimization, or broad architecture rewrites with no bottleneck evidence.
- ▌ Swe Capture Knowledge · ckorhonenAudits a repository's code and docs to find important conventions, workflows, and architectural decisions that are missing from agent-facing guidance, then drafts review-ready updates. Use when a user says `capture repo knowledge`, `document implicit conventions`, `turn repo patterns into agent rules`, or asks what future agents should remember about a codebase. Do NOT use for a generic repo tour, onboarding walkthrough, or architecture summary that does not need reusable guidance updates.
- ▌ Swe Ownership Risk Map · ckorhonenMaps engineering ownership risk in a repository using repo evidence such as git history, churn, bus factor, CODEOWNERS coverage, test density, and orphaned or unclear-owner surfaces. Use when a user says `map ownership risk`, `find bus factor hotspots`, `which files look orphaned`, `high-change low-test areas`, or asks for a recurring maintenance pass that identifies risky surfaces before they become incidents. Do NOT use for org charts, HR ownership assignments, or generic maintainer lists without repo evidence.
- ▌ Swe Repo Introspection · ckorhonenInspects an unfamiliar software repository and produces a concrete orientation report covering structure, tooling, entry points, boundaries, active surfaces, and safe places to start work. Use when a user says `help me understand this repo`, `map this codebase before I edit it`, `where should I start`, or asks for an engineering walkthrough before planning or delegation. Do NOT use when the user already knows the target change and wants implementation, or when they need a specific bug diagnosis rather than repo orientation.
- ▌ Swe Merged Pr Monitoring · ckorhonenReviews recently merged pull requests, confirms whether they reached production, compares pre- and post-deploy signals, and summarizes observable impact. Use when a user says `monitor merged PRs`, `did this deploy hurt prod`, `check production impact of yesterday's merges`, or asks for a post-deploy readout tied to merged GitHub PRs. Do NOT use for a pre-merge code review, incident analysis with no PR scope, or generic dashboard triage disconnected from merged changes.
- ▌ Swe Observability Gap Hunt · ckorhonenInspects services, jobs, and code paths for missing or weak logs, metrics, traces, alerts, dashboards, or deployment-linked telemetry, then returns a tightly scoped backlog of observability gaps. Use when a user says `find observability gaps`, `audit telemetry coverage`, `what logs or metrics are missing`, `check alerting coverage`, or asks for a recurring telemetry review. Do NOT use for live incident response, root-cause analysis, generic performance tuning, or a broad code review.
- ▌ Swe Recent Commit Bug Hunt · ckorhonenScans recent commits in one or more repositories, identifies likely bugs using concrete repo evidence only, and proposes tightly scoped remediation sessions. Use when a user says `scan recent commits for bugs`, `what did I probably break`, `review yesterday's changes for regressions`, or asks for a commit-scoped bug hunt. Do NOT use for a broad code health review, full security audit, or speculative bug hunting with no repo or time scope.
- ▌ Swe Refactor Opportunities · ckorhonenReviews a repository and returns a short, best-first backlog of small, low-risk refactor tickets with clear write boundaries and validation paths. Use when a user says `find refactor opportunities`, `what small cleanup tickets should we hand to agents`, `give me parallelizable refactors`, or asks for narrow maintainability wins in an existing repo. Do NOT use for a broad architecture redesign, style-only cleanup sweep, or bug hunt focused on functional regressions.
- ▌ Swe Incident Followup Audit · ckorhonenAudits post-incident engineering follow-through after a sev or incident to verify whether the durable follow-up happened: regression tests, monitors, docs, runbooks, ownership updates, tickets, rollback learnings, and remaining backlog. Use when a user asks whether incident follow-up is complete, what still needs to be done after a postmortem, or how to close the engineering loop. Do NOT use for live incident response, root-cause analysis, or a generic bug hunt unrelated to an incident.
- ▌ Swe Change Validation Planner · ckorhonenPlans the narrowest trustworthy validation path for a scoped code change or diff. Use when a user asks what to run before merging, how to validate a specific change, whether the current checks are enough, or wants a bounded command order from narrow to broad. Do NOT use for writing tests, fixing the code change itself, broad QA sweeps, or generic debugging that needs root cause analysis.
- ▌ Content Trend Researcher · ckorhonen bundleResearch content trends and generate data-driven article outlines by analyzing Google Trends, Reddit, LinkedIn, X, Substack, Medium, YouTube, and more. Use when asked to research content ideas, find trending topics, generate article outlines, analyze audience intent, or when user says "what should I write about", "find trending topics in X", or "research content ideas".
- ▌ Github Actions Templates · ckorhonenCreate production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
- ▌ Scientific Critical Thinking · ckorhonen bundleEvaluate research rigor and scientific claims. Assess methodology, experimental design, statistical validity, biases, confounding, and evidence quality using GRADE, Cochrane ROB, and preregistration standards. Use for critical analysis of research papers, evaluating AI/ML study claims, reviewing preprints, or fact-checking scientific assertions in any domain.
- ▌ Agent Engineering · ckorhonenBattle-tested engineering principles for AI coding agents. Covers plan-first workflow, subagent delegation, self-improvement loops, verification gates, elegant solutions, autonomous bug fixing, and structured task management. Use when configuring agent behavior, writing AGENTS.md files, or improving agent reliability and code quality.
- ▌ Evangelion Design · ckorhonen bundleDesign original Evangelion-inspired web and mobile interfaces with NERV-like command-center, HUD, psychographic, sync-monitor, breach-warning, and title-card language: sharp geometry, tactical typography, disciplined data density, danger-first palettes, wireframe analysis forms, repeated instrument arrays, and mechanical animation. Use when users ask for Evangelion, NERV, anime control room UI, sci-fi military instrumentation, diagnostic overlays, psychographic displays, sync monitors, countdown screens, or dramatic system-state motion for product interfaces.
- ▌ App Marketing Copy · ckorhonen bundleWrite marketing copy and App Store / Google Play listings (ASO keywords, titles, subtitles, short+long descriptions, feature bullets, release notes), plus screenshot caption sets and text-to-image prompt templates for generating store screenshot backgrounds/promo visuals. Use when asked to: write/refresh app marketing copy, craft app store metadata, brainstorm taglines/value props, produce ad/landing/email copy, or generate prompts for screenshot/creative generation.
- ▌ Blockchain Auditor · ckorhonen bundleSecurity audit smart contracts for exploitable vulnerabilities from an unprivileged context. Use when analyzing Solidity contracts, reviewing bytecode, testing exploits on forks, or searching for ways to extract funds without owner access. Covers verified and unverified contracts, bytecode disassembly, vulnerability ranking, proof-of-concept exploit generation, DeFi protocol attacks, and cross-chain bridge security.
- ▌ Cloudflare Manager · ckorhonen bundleComprehensive Cloudflare account management for deploying Workers, KV Storage, R2, Pages, DNS, and Routes. Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing. Requires CLOUDFLARE_API_KEY in .env and Bun runtime with dependencies installed.
- ▌ Continuous Learning · ckorhonen bundleCapture reusable knowledge and create new skills automatically during coding sessions, problem solving, and retrospectives. Use when finishing a complex task, running a retrospective, discovering a reusable pattern, or when user says "save this as a skill", "capture this solution", "run a retrospective", or "what did we learn from this".
- ▌ Practical Typography · ckorhonen bundleProfessional typography guidance based on Matthew Butterick's Practical Typography. Use when evaluating, critiquing, or improving document formatting, text layout, font choices, punctuation, spacing, or any typography-related decisions for print or web content.
- ▌ Systematic Debugging · ckorhonen bundleSystematic step-by-step debugging process for bugs, test failures, and unexpected behavior. Use when a test fails, something isn't working as expected, user says "this is broken", "why isn't X working", "help me debug", or when you encounter any error before proposing a fix.
- ▌ Security Threat Model · ckorhonen bundleRepository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, then writes a concise actionable Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Covers STRIDE, PASTA, and attacker-goal-based methodologies, with modern considerations for AI/ML systems, cloud-native deployments, and supply chain threats.
- ▌ Direct Mail Strategist · ckorhonenExpert direct mail marketing strategist for writing compelling copy, designing high-converting mail pieces, and developing measurement strategies. Use when planning direct mail campaigns, writing mailer copy, designing postcards/letters, or measuring campaign effectiveness with incremental lift analysis.
- ▌ Gemini Image Generator · ckorhonen bundleGenerate images using Google's Gemini API. Use when creating images from text prompts, editing existing images, or combining reference images for AI-generated visual content.
- ▌ Security Best Practices · ckorhonen bundlePerform language and framework specific security best-practice reviews and suggest improvements. Trigger when the user requests: security review, security report, threat assessment, vulnerability scan, security audit, secure-by-default coding, hardening guidance, or security best practices guidance. Supported languages: Python, JavaScript/TypeScript, Go. Covers OWASP Top 10, supply chain security, secrets management, dependency auditing, and modern cloud deployment hardening.
- ▌ SEO Optimizer · ckorhonen bundleAnalyze and optimize websites for search engine visibility. Use when asked to run an SEO audit, improve page rankings, fix meta tags, add schema markup, generate a sitemap, optimize for Core Web Vitals, or when user says "improve my SEO", "audit this site's SEO", or "help me rank higher on Google".
- ▌ Writing Plans · ckorhonenWrite structured implementation plans from specs or requirements before touching code. Use when given a spec, requirements doc, or feature description, when user says "plan this out", "write a plan for", "how should we implement", or before starting any multi-step coding task.
- ▌ LLM Evaluation · ckorhonenImplement comprehensive evaluation strategies for LLM applications using automated metrics, LLM-as-judge, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, comparing prompts/models, or establishing evaluation frameworks. Covers RAGAS for RAG pipelines, evals-as-code CI/CD integration, and modern 2025/2026 practices including structured output evaluation and agentic task success measurement.
- ▌ Markdown Fetch · ckorhonen bundleFetch and extract web content as clean Markdown when provided with URLs. Use this skill whenever a user provides a URL (http/https link) that needs to be read, analyzed, summarized, or extracted. Converts web pages to Markdown with 80% fewer tokens than raw HTML. Handles all content types including JS-heavy sites, documentation, articles, and blog posts. Supports three conversion methods (auto, AI, browser rendering). Always use this instead of web_fetch when working with URLs - it's more efficient and provides cleaner output.
- ▌ Prompt Factory · ckorhonen bundleGenerate world-class, production-ready prompts in one shot through intelligent 5-7 question flow and 69 presets across 15 professional domains. Supports XML/Claude/ChatGPT/Gemini formats with quality validation. Returns a single mega-prompt ready to use—skill does NOT implement the work described in the prompt. Optimized for modern LLMs including Claude 3.5+, GPT-4.1, and Gemini 2.5.
- ▌ Ascii Pixel Art · ckorhonen bundleGenerate animated ASCII art from images with subject detection, blurred pixelated backgrounds, and dynamic visual effects. Use when asked to create ASCII art, convert an image to ASCII, generate pixel art, add animated text art effects, or make retro-style visual art from photos.
- ▌ Executing Plans · ckorhonenExecute a written implementation plan with review checkpoints and structured progress tracking. Use when you have a spec or plan ready to implement, when user says "execute this plan", "implement this spec", "carry out these steps", or "start working on the plan".
- ▌ Coreml Optimizer · ckorhonen bundleOptimize CoreML models for iOS and macOS deployment. Covers quantization, palettization, pruning, Neural Engine targeting, compute unit selection, and performance profiling. Use when converting ML models to CoreML, optimizing model size/latency, debugging Neural Engine issues, or benchmarking on-device inference.
- ▌ Gsplat Optimizer · ckorhonen bundleOptimize 3D Gaussian Splat scenes for real-time rendering on iOS, macOS, and visionOS. Use when working with .ply or .splat files, targeting mobile/Apple GPU performance, or needing LOD, pruning, or compression strategies for 3DGS scenes.
- ▌ MCP Tester · ckorhonenTest and evaluate MCP server tools in the current Claude Code session. Use when auditing MCP configurations, validating tool quality, testing MCP servers end-to-end, generating test cases, checking tool descriptions and schemas, analyzing tool efficiency and redundancy, or debugging MCP integration issues. Covers tool discovery, quality analysis, test generation with AAA pattern, execution, rating, and cross-tool redundancy analysis.
- ▌ Autopredict · ckorhonen bundleWrap the howdymary/autopredict Polymarket trading-agent repo. Use when you need to scan live Polymarket markets, inspect structural event mispricing, evaluate a market with your own fair probability, run reproducible backtests against a JSON dataset, tune strategy parameters safely, or review the repo's paper/live trading scaffolds and failure modes.
- ▌ LLM Advisor · ckorhonenConsult other LLMs (GPT-4.1, o4-mini, Gemini 2.5 Pro, Claude Opus) for second opinions on complex bugs, hard problems, planning, and architecture decisions. Use proactively when stuck for 15+ minutes or facing complex debugging. Use when user says 'ask Gemini/GPT/Claude about X' or 'get a second opinion'.
- ▌ MCP Builder · ckorhonen bundleGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP/MCP SDK) or Node/TypeScript (MCP SDK). Covers tool design, output schemas, Streamable HTTP transport, authentication patterns, evaluation creation, and common debugging.
- ▌ Nano Banana · ckorhonen bundleGenerate and edit high-quality AI images using Google's Gemini image models (Nano Banana series) via MCP. Use when user wants to create images, edit photos, generate graphics, or needs visual content with text rendering. Supports gemini-3.1-flash-image-preview (Nano Banana 2) and gemini-2.5-flash-image-preview (Nano Banana).
- ▌ Subway Info · ckorhonen bundleGet real-time NYC transit information — subway, bus, ferry, and commuter rail — via the subway-info CLI or REST API at subwayinfo.nyc. Use when asked about NYC subway status, train times, bus routes, ferry schedules, transit delays, MTA service alerts, or "what's the next train to X".
- ▌ Autoresearch · ckorhonen bundleRun a rigorous autonomous experiment loop for any optimization target using explicit hypotheses, repeated trials, structured experiment logs, and local HTML reports. Use when asked to "run autoresearch", "optimize X in a loop", "start experiments", or "improve this with benchmark-driven iteration".
- ▌ Playdate Dev · ckorhonen bundlePlaydate game development in Lua with the Playdate SDK. Covers game loop, sprites, graphics, input (crank, buttons, accelerometer), audio, UI, performance, metadata (pdxinfo), and simulator/device workflow. Use when asked to make a Playdate game, implement Playdate-specific mechanics, or apply Playdate design and accessibility guidelines.
- ▌ Tui Designer · ckorhonen bundleDesign and implement retro/cyberpunk/hacker-style terminal UIs. Covers React (Tuimorphic), SwiftUI (Metal shaders), and CSS approaches. Use when creating terminal aesthetics, CRT effects, neon glow, scanlines, phosphor green displays, or retro-futuristic interfaces.
- ▌ Agent Browser · ckorhonenAutomate headless browser interactions using agent-browser CLI. Use when scraping web pages, automating form submissions, testing web apps, or performing browser automation tasks. Works with element refs (@e1, @e2) optimized for AI agent reasoning.
- ▌ Brainstorming · ckorhonenExplore user intent, requirements and design before implementation through structured dialogue and design proposals. Use when asked to: create features, build components, add functionality, modify behavior, plan projects, or when user says 'help me design X', 'what should we build', 'let's brainstorm', or starts describing a new feature without a design.
- ▌ Gemini Visual · ckorhonen bundleVisual and front-end development assistant powered by Google Gemini's multimodal models. Use for UI analysis, design comparison, accessibility audits, color palette extraction, screenshot-to-code conversion, generating UI assets, and text-based design assistance from briefs.
- ▌ Idea Md · ckorhonen bundleCreate or expand an Idea.md / IDEA.md file from a rough description, existing repo, conversation history, notes, or other early-stage product inputs. Use when the user asks to "write an Idea.md", "turn this into an idea file", "capture this product idea", "expand this concept", or wants a repo-grounded concept brief before validation, PRD, or implementation work.
- ▌ Imagegen · ckorhonen bundleUse when the user asks to generate or edit images via the OpenAI Image API (for example: generate image, edit/inpaint/mask, background removal or replacement, transparent background, product shots, concept art, covers, or batch variants); run the bundled CLI (`scripts/image_gen.py`) and require `OPENAI_API_KEY` for live calls.
- ▌ Bird Fast · ckorhonenPost tweets, read threads, search X/Twitter from the terminal using the bird CLI. Use when automating Twitter/X, posting from scripts, analyzing tweet threads, monitoring mentions, or working with the Twitter API without OAuth setup.
- ▌ Ck Review · ckorhonenReview documents, proposals, and plans through the lens of a senior principal engineer. Simulates feedback from a technically deep IC who values clarity, pragmatism, and shipping velocity. Use when you want direct, blunt technical feedback on a proposal, architecture doc, design doc, or spec — especially around structure, tradeoffs, and scope.
- ▌ Paperclip · ckorhonen bundleInteract with the Paperclip control plane API to manage tasks, coordinate agents, track goals, and run your AI-powered company. Use when working with Paperclip issues, agents, projects, or goals.
- ▌ Shadertoy · ckorhonen bundleWrite, debug, and optimize Shadertoy shaders and GLSL fragment shaders for procedural graphics. Use when creating visual effects, generative art, or WebGL shaders; when writing .glsl files; or when user says "write a shader", "make a Shadertoy effect", "help with GLSL", or "create a procedural animation".
- ▌ Skimmable · ckorhonenEnforce code readability and state minimisation before opening or updating a pull request. Use when code is functionally complete and needs a final simplification pass focused on skimmability: reducing arguments, removing optionality and overrides, collapsing unnecessary abstractions, preferring discriminated unions, adding assertions at boundaries, handling variants exhaustively, deleting incidental changes, and making the diff shorter, clearer, and easier to review.
- ▌ UI Design · ckorhonenOpinionated constraints for building better interfaces with agents. Use when building UI components, implementing animations, designing layouts, reviewing frontend accessibility, or working with Tailwind CSS, motion/react, or accessible primitives like Radix/Base UI.
- ▌ Babysit Pr · ckorhonen bundleCreate, monitor, and shepherd a GitHub pull request end-to-end: respect repo PR templates, watch CI and reviews, fix branch-related failures, address valid comments, and validate post-merge deployment when possible.
- ▌ Ceo Review · ckorhonenReview documents, proposals, and plans through the lens of a CEO. Simulates feedback from a founder-CEO who is technical, data-driven, and focused on long-term vision while navigating market volatility. Use when you want high-level strategic review: does this idea make sense as a company bet? Is the team right-sized? Will this survive a downturn? Is it community-first?
- ▌ Cto Review · ckorhonenReview documents, proposals, and plans through the lens of a CTO. Simulates feedback from a technical leader who has built and scaled multiple companies and values platform thinking, mobile-first craft, and iterative execution. Use when you need engineering leadership review: platform strategy, architecture decisions, team structure proposals, or anything that needs a 'will this scale and can we ship fast?' lens.
- ▌ Hyperagent · ckorhonen bundleRun a self-referential self-improving agent loop where a meta-agent iteratively modifies a task-agent's code to optimize for any measurable target. Based on Facebook Research's Hyperagents paper (arXiv:2603.19461). Use when asked to "run hyperagent", "self-improve this", "optimize with self-modification", or "evolve this agent/script".
- ▌ Macos Apps · ckorhonen bundleBuild professional native macOS apps in Swift with SwiftUI and AppKit. Full lifecycle - build, debug, test, optimize, ship. CLI-only, no Xcode. Use when asked to: create macOS apps, build Swift apps, develop SwiftUI interfaces, fix macOS app issues, add macOS app features, or when user says 'build a Mac app', 'create a Swift project', 'develop for macOS'.
- ▌ Qmd · ckorhonenLocal hybrid search for markdown notes and docs. Use when searching notes, finding related content, or retrieving documents from indexed collections.
- ▌ Google · ckorhonen bundlePersonal assistant for Google Workspace using gog CLI. Search Gmail, manage Calendar, organize Drive, update Sheets, track Tasks, and lookup Contacts. Use when triaging email, scheduling meetings, finding availability, searching documents, managing tasks, or any Google service interaction from the terminal.