poteto
- 64 skills
- 0 followers
- last month last updated
- ▌ Reflect 3 · poteto bundleSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
- ▌
- ▌
- ▌ How 2 · poteto bundleUse for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.
- ▌ Plan 2 · potetoBreak down medium-to-large tasks into phased plans in brain/plans/. Planning only — does not implement. Use for new features, multi-file refactors, or architectural changes — not small fixes. Triggers: "plan this", "break this down".
- ▌ Brain 2 · potetoRead/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers: brain/ modifications, "add to brain".
- ▌ Review 2 · potetoPrinciple-grounded review of code changes, PRs, or plans. Use when asked to review, critique, or assess quality of work — "review", "review this", "code review", "check this".
- ▌ Reflect 2 · potetoReflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this".
- ▌ Meditate 2 · poteto bundleAudit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities. Triggers: "meditate", "audit the brain".
- ▌ Ruminate 2 · poteto bundleMine past Claude Code conversations for uncaptured patterns, corrections, and knowledge. Cross-references with existing brain content. Triggers: "ruminate", "mine my history".
- ▌ TS Best Practices · poteto bundleTypeScript type safety guidelines for writing maximally type-safe code. Apply these patterns when writing or reviewing any TypeScript: discriminated unions, type narrowing, type guards, exhaustiveness checks, avoiding `as` casts, preferring `unknown` over `any`, and making impossible states unrepresentable. Use this skill whenever writing TypeScript code, reviewing TypeScript for type safety issues, or when the user mentions type safety, type narrowing, discriminated unions, or asks to make types stricter/more explicit.
- ▌
- ▌
- ▌
- ▌ Schedule 2 · potetoReads backlog and produces multi-stage work orders including test and deploy stages.
- ▌ Why · poteto bundleUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
- ▌ Arena · potetoSpawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
- ▌ Architect · poteto bundleSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
- ▌ Automate Me · potetoUse for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via create-skill + unslop, optionally pulling fresh evidence from recent transcripts.
- ▌ Interrogate · poteto bundleUse for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
- ▌ Cancel Ralph · potetoCancel an active Ralph Loop. Use when the user wants to stop, cancel, or abort a running ralph loop.
- ▌ Principle Fix Root Causes · potetoApply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
- ▌ Typescript Best Practices · poteto bundleTypeScript best practices. Use when reading or editing any .ts or .tsx file.
- ▌ Pr Review Canvas · potetoRender a PR diff review as a Cursor Canvas that groups changes by reviewer importance, separates boilerplate from core logic, and highlights tricky or unexpected code. Use when reviewing a pull request, summarizing a diff for review, or when the user asks for a PR review canvas, diff walkthrough, or change-set overview.
- ▌ Principle Laziness Protocol · potetoApply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
- ▌ Principle Boundary Discipline · potetoApply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
- ▌ Continual Learning · potetoOrchestrate continual learning by delegating transcript mining and AGENTS.md updates to `agents-memory-updater`.
- ▌ Principle Minimize Reader Load · potetoApply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
- ▌ Principle Foundational Thinking · potetoApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
- ▌ Principle Type System Discipline · potetoApply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.
- ▌ Principle Subtract Before You Add · potetoApply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.
- ▌ Principle Exhaust The Design Space · potetoApply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
- ▌
- ▌ Poteto Mode · poteto bundlepoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
- ▌ Setup Pstack · potetoConfigure which models pstack uses per role. Detects your available models and writes an always-applied rule that overrides the skill defaults. Use for /setup-pstack, "configure pstack models", or changing pstack's model choices.
- ▌ Run Learning Retrospective · potetoEvaluate learning progress, identify blockers, and adjust the learning plan
- ▌ How · poteto bundleExplain how something works in this codebase by exploring code and producing a clear architectural explanation. Optionally critique the architecture for issues.
- ▌ Verify Atlas · poteto bundleDrive the Atlas workspace UI in a running Harbor Labs desktop build via CDP. Use for screenshots, clicks, sending messages, accessibility-tree inspection, JS evaluation, or visual-state checks.
- ▌ Oops · potetoInfrastructure fix for broken builds, failed tests, stale state, and environment drift. Covers both user-project and Noodle-internal failures. Triggers when builds break, tests fail, state is stale, or environment drifts. Use on 'oops', 'fix the build', 'tests are failing', 'something broke', 'broken build'.
- ▌ Plan · poteto bundleSystematic planning for medium-to-large tasks. Gathers context, identifies domain skills, writes phased plans to brain/plans/. Does NOT implement. Use for new features, multi-file refactors, or architectural changes — not small fixes. Triggers: "plan this", "break this down".
- ▌ Todo · potetoAdd, complete, or view items in the brain/todos.md backlog. Use when the user says "todo", "add a todo", "mark done", "what's on the backlog", "show todos", "list tasks", "check off", or wants to manage their task list.
- ▌ Brain · potetoRead/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers after debugging sessions, mistakes, corrections, architectural decisions, or any insight worth preserving across sessions. Use on 'add to brain', 'remember this', 'write a note', or brain/ modifications.
- ▌ Codex · potetoRun Codex CLI (exec, resume) for parallel work, delegating tasks to another model, or background code generation. Handles code analysis, refactoring, and automated editing. Includes Spark vs standard guidance. Triggers: "codex", "run codex", "use codex to".
- ▌ Commit · potetoCreate conventional commit messages. Use when the user says "commit this", "save changes", "git commit", asks to commit code, write a commit message, or format git history. Follows conventional commits specification.
- ▌ Noodle · poteto bundleOperate the Noodle CLI — explain commands, find flags, create/edit .noodle.toml config. Also covers writing skills for Noodle: the orders pipeline, task-type schedule fields, stage composition, and the orders-next.json schema. Use when running noodle commands, editing .noodle.toml, writing or updating a skill's schedule field, authoring new task-type skills, or asking "how to run noodle", "noodle help", "configure noodle".
- ▌ Refine · potetoSharpen todo items in brain/todos.md into precise, actionable prompts via targeted questioning. Triggers: "refine", "refine todos", "clarify todos".
- ▌ Review · potetoReview plans and code changes. Walks Architecture → Code Quality → Tests → Performance, numbering issues with tradeoff options. Triggers: "review", "review this", "code review", "look over this", "check my changes", "audit", "critique", "what do you think", "sanity check".
- ▌ Unslop · potetoRemove AI writing patterns from prose. Use for docs, READMEs, blog posts, any non-code text that should sound human. Triggers: "unslop", "humanize", "make this sound human", "clean up this writing", "edit for voice", "de-AI this text".
- ▌ Execute · poteto bundleImplementation methodology for executing tasks. Handles scoping, decomposition, worktree workflow, verification, and commit conventions. Triggers: "execute", "implement", "build this", "code this".
- ▌ Quality · poteto bundlePost-cook quality gate. Reviews completed cook work for correctness, scope discipline, and principle compliance. Emits stage_message events with findings. Triggers after execute stages, on '/quality', 'review this', 'check the work', 'assess quality'.
- ▌ Reflect · potetoReflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this".
- ▌ Testing · poteto bundleTest-driven development workflow for Noodle. Use when testing changes, writing tests, fixing bugs, creating fixtures, or running the test suite. Triggers: "test", "write a test", "fix this bug", "add a fixture", "run tests", "TDD", or any task involving verification of code changes.
- ▌ Ast Grep · poteto bundleStructural code search via ast-grep — use when code shape and element relationships matter, not just text. E.g., "find async functions without error handling", "refactor foo(a, b) to foo({ a, b })". Use Grep for simple name lookups.
- ▌ Meditate · poteto bundleAudit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities. Triggers: "meditate", "audit the brain", "prune brain", "review skills", "consolidate notes", "prune notes".
- ▌ Ruminate · poteto bundleMine past Claude Code and Codex conversations for uncaptured patterns, corrections, and knowledge. Cross-references with existing brain content. Triggers: "ruminate", "mine my history", "what have I been working on", "review past sessions", "extract learnings".
- ▌ Schedule · poteto bundleOrders scheduler. Reads .noodle/mise.json, writes .noodle/orders-next.json. Schedules work orders based on backlog state, plan phases, session history, and task type schedules. Triggers when orders are empty, after backlog changes, when the loop re-evaluates, or when /schedule is invoked.
- ▌ Worktree · potetoUse for concurrent sessions, agent team isolation, or any work needing a separate branch. Critical for multi-agent workflows. Triggers: "worktree", "new worktree", "clean up worktrees", "need isolation", or when spawning agent teams.
- ▌ Debugging · potetoSystematic root-cause debugging methodology. Use for any technical problem — errors, failures, unexpected behavior, or when stuck. Triggers: "debug", "fix this", "what's wrong", "investigate".
- ▌ Find Skills · potetoDiscover and install agent skills from the open ecosystem. Use IMMEDIATELY when the user asks "how do I do X", "find a skill for X", "is there a skill for X", "can you do X" for specialized capabilities, wants to extend agent functionality, mentions a domain they wish they had help with, or asks about tools/templates/workflows that might exist as installable skills.
- ▌ Skill Creator · poteto bundleGuide for creating or updating skills — specialized knowledge, workflows, and tool integrations packaged for Claude.
- ▌ Go Best Practices · poteto bundleProduction Go patterns — lifecycle, concurrency, config, testing, CI. Use when writing, reviewing, or refactoring Go code. Triggers on Go code review, Go refactoring, or 'go best practices'.
- ▌ Interaction Design · poteto bundleDesign and implement microinteractions, motion design, transitions, and user feedback patterns. Use when adding polish to UI interactions, implementing loading states, creating gesture-based interactions, designing hover/focus states, building notification/toast systems, adding scroll-triggered animations, implementing drag-and-drop, or creating delightful user experiences.
- ▌ React Best Practices · poteto bundleReact performance optimization guidelines. Use when writing, reviewing, or refactoring React components, hooks, effects, data fetching, or bundle optimization. Includes useEffect best practices — when NOT to use effects and better alternatives. Triggers: "when writing React code", "reviewing a React PR", "why is this component re-rendering", "reviewing code for performance issues", "optimizing bundle size".
- ▌ Make Interfaces Feel Better · poteto bundleDesign engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.