poteto

poteto/how

Skill Claude CodeCodex

Explain how something works in this codebase by exploring code and producing a clear architectural explanation. Optionally critique the architecture for issues.

poteto/brainmaxxing

Skill Claude CodeCodex

Read/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".

poteto/brainmaxxing

Skill Claude CodeCodex

Audit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities. Triggers: "meditate", "audit the brain".

poteto/brainmaxxing

Skill Claude CodeCodex

Break 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".

poteto/brainmaxxing

Skill Claude CodeCodex

Reflect 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".

poteto/brainmaxxing

Skill Claude CodeCodex

Principle-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".

poteto/brainmaxxing

Skill Claude CodeCodex

Mine past Claude Code conversations for uncaptured patterns, corrections, and knowledge. Cross-references with existing brain content. Triggers: "ruminate", "mine my history".

poteto/brainmaxxing

Hook Claude Code

Runs when a session starts on startup and resume, executing inject-brain.sh. From poteto/brainmaxxing.

poteto/brainmaxxing

Hook Claude Code

Runs after a tool call finishes for brain/ tool calls, executing auto-index-brain.sh. From poteto/brainmaxxing.

poteto/brainmaxxing

Settings file Claude Code

Agent settings declaring 2 hook events (SessionStart, PostToolUse).

poteto/brainmaxxing

Instructions file

Instructions for poteto/brainmaxxing: The brain/ directory is an Obsidian vault — persistent memory across sessions.

poteto/noodle

Skill Claude CodeCodex

Adversarial code review using cross-model approach. Spawns reviewers on the opposing model (Claude uses Codex, Codex uses Claude) to challenge work from distinct critical lenses. Produces a synthesized verdict with findings and lead judgment. Triggers: "adversarial review".

poteto/noodle

Skill Claude CodeCodex

Structural 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.

poteto/noodle

Skill Claude CodeCodex

Read/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…

poteto/noodle

Skill Claude CodeCodex

Run 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".

poteto/noodle

Skill Claude CodeCodex

Create 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.

poteto/noodle

Skill Claude CodeCodex

Systematic root-cause debugging methodology. Use for any technical problem — errors, failures, unexpected behavior, or when stuck. Triggers: "debug", "fix this", "what's wrong", "investigate".

poteto/noodle

Skill Claude CodeCodex

Implementation methodology for executing tasks. Handles scoping, decomposition, worktree workflow, verification, and commit conventions. Triggers: "execute", "implement", "build this", "code this".

poteto/noodle

Skill Claude CodeCodex

Discover 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…

poteto/noodle

Skill Claude CodeCodex

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…

poteto/noodle

Skill Claude CodeCodex

Production 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'.

poteto/noodle

Skill Claude CodeCodex

Design 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…

poteto/noodle

Skill Claude CodeCodex

Design 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…

poteto/noodle

Skill Claude CodeCodex

Audit 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".