skills

Proactively log small friction points, flaky commands, failed tool calls, or setup gotchas to `PAPERCUTS.md` using `yarn papercut`. Trigger on any friction encountered during work or when the user invokes `/papercut`.

Turn real work the user has actually done into a Reddit post for technical, developer-centric, or AI-related subreddits. Use whenever the user says "write me a Reddit post", "help me post on Reddit", "turn this into a Reddit post", "share this on Reddit", or anything similar — and also proactively suggest this skill when the user just finished something post-worthy (a benchmark, a workflow they figured out, a bug/incident diagnosis, a tool/framework comparison, a meaningful failure). The skill REFUSES to generate posts from nothing — it requires real work, real numbers, real experience as the input. Karma-farming generic listicles are explicitly out of scope.

Activates an interactive interview mode to resolve design decisions, clarify vague requirements, and align on a plan. Trigger on "/align", "align", "interview me", "let's align", or when the user has an ambiguous plan and needs to be questioned to solidify it.

Run a user-given shell command directly and return raw output, no commentary.

Triggers on error messages, stack traces, "this is broken", unexpected output, or debugging requests. Focuses on root cause analysis, ranked hypotheses, and targeted fixes.

Execution mode. Trigger on "go ahead", "do it", "execute", "implement", "make the changes", or any approval to act. Stop planning, start building.

Multi-model analysis and synthesis using OpenCode CLI — replicates OpenRouter Fusion style workflows locally. Runs multiple LLMs in parallel, judges their outputs, and produces a single synthesized response. Trigger whenever the user wants to run a task against multiple models, compare model outputs, get a consensus answer, or says things like "fusion run", "multi-model", "run all models", "synthesize model outputs", or "parallel agents". Also trigger when the user wants to reduce hallucinations by cross-checking multiple LLMs, or when high-stakes tasks need more than one model's perspective.

Activates a read-only planning mode where the assistant observes, reads, and reports — but never edits, creates, or modifies anything. Use this skill whenever the user says "planning mode on", "plan:", "let's plan", "just plan this", "don't touch anything, just look", or any similar phrase indicating they want analysis without action. Also triggers for task planning requests where the user wants to understand what exists before deciding what to do. In planning mode, files and context are read, what's there and what's missing is reported, and next steps are proposed — but zero action is taken. Stays active until the user says "planning mode off", "exit planning mode", or "done planning". This skill must be used any time the user signals they want observation-only mode, even if phrased casually.

Critical thinking engine that stress-tests arguments, exposes fragility, and forces rigor. Trigger on: "devil's advocate", "challenge this", "stress test", "poke holes", "the razor", "tear this apart", "what's wrong with this", or when the user presents a claim, strategy, or plan that needs rigorous pushback.

Answer-only mode. Trigger when the user is just asking a question — not requesting edits, builds, or implementations. Respond directly with the answer. No file changes, no commands, no plans.

Product design through Steve Jobs' lens. Trigger on "think like Jobs", "steve jobs mode", "insanely great", "product thinking", "make it magical", or when the user wants ruthless simplicity, user-obsessed design, or opinionated product decisions.

Review, refactor, or rewrite code for readability and maintainability. Trigger on: "clean up", "refactor", "improve code", "code smells", "simplify", "make readable", "too long", "bad naming", "technical debt", or any request to improve existing code quality. Also trigger when code has obvious smells even if the user doesn't name them.

Build crafted, intentional UI for dashboards, admin panels, SaaS apps, tools, settings pages, and data interfaces. Use when building an interactive product — NOT marketing pages, landing pages, or campaigns (redirect those to frontend-design). Triggers on: dashboard, admin panel, app UI, settings page, data table, SaaS interface, tool UI, sidebar navigation, metrics view.

Collaborative brainstorming and critical-thinking mode where Claude withholds solutions, drafts, code, designs, and recommendations, and instead reflects understanding back, maps known vs unknown, asks one sharp question per turn, and pushes back honestly on weak reasoning. Applies to both strategy thinking (pivots, GTM, hiring, positioning) and software/technical thinking (architecture, design tradeoffs, build-vs-buy, data modeling, debugging, stack choice, scoping). Trigger on "let's jam", "jamming", "brainstorm with me", "think out loud with me", "think through this", "help me think through this architecture", "don't write code yet", "don't give me an answer yet", "just help me think" — or whenever the user is still exploring a problem and a premature answer, draft, or code block would shortcut their thinking. Stay in jam mode every turn until the user explicitly releases with "stop jamming", "give me the answer", "draft it", "now write the code", or similar.

Use this skill when brainstorming product features, designing implementations, generating high-quality engineering prompts, or deciding the best technical approach for a feature. Triggers on any mention of: feature design, technical approach, implementation plan, architecture decision, engineering prompt, system design, "how should I build", "best way to implement", "help me design", or when a user describes a feature idea and wants to think it through. Also trigger when the user asks for a prompt to use in Claude Code, Cursor, or Codex. This skill converts rough ideas into production-ready implementation strategies using senior-engineer thinking — use it proactively whenever someone is planning how to build something, even if they don't use these exact words.

CEO/founder-mode review for skill creation and improvement. Challenges whether the skill is solving the right problem, surfaces the 10x version, and stress-tests the design before you invest in writing test cases. Four modes: SCOPE EXPANSION (dream bigger — what should this skill really do?), SELECTIVE EXPANSION (hold scope + cherry- pick improvements), HOLD SCOPE (maximum rigor on the current design), SCOPE REDUCTION (strip the skill to its sharp edge). Use when asked to "rethink this skill", "is this ambitious enough", "challenge my skill design", "think bigger about this skill", or "review my skill before I build it". Proactively suggest when the user seems uncertain about what their skill should do, when the skill description feels generic, when the skill is doing too many things, or when the user has just written a first draft and wants honest feedback before testing.