Explorar skills

Use to write long-form gated lead magnets (ebooks, guides, reports). Drafts the outline first for sign-off, then writes each page humanized through Walter, with end-of-document summary and optional follow-up email sequence.

development skills category for SAP Superpowers. Contains 8 sub-skills.

Use when generated or modified ABAP code has syntax errors, ATC findings, test failures, or activation issues. Runs an iterative fix-check-fix loop until the code is clean, tested, and activated. Equivalent to a persistent development TDD cycle.

Use NotebookLM for grounded research — documentation queries, stack comparisons, session log search. Trigger when user needs answers FROM SPECIFIC DOCUMENTATION or FROM PAST SESSIONS: "по документации", "check docs", "как в Payload", "как в Next.js", "что мы решили про", "when did we decide", "по нашим записям", "спроси в нотбуке", "ask notebooklm", "query notebook", "загрузи доки", "load docs", "

Fetches a GitHub issue by number, analyzes the requirements, finds the relevant code, implements a fix, and optionally creates a PR. Use when working through your issue backlog.

Use when reverse-engineering an existing ABAP program into a functional or technical specification. Reads code and produces structured documentation — not a code dump, a proper spec document that a consultant can hand to a client.

Build frontend interfaces for Manzanita Research — warm, editorial, California-rooted design for music tools and brand pages. React + Tailwind. Use when building web components, pages, landing pages, dashboards, plugin UIs, or any web interface for Manzanita projects.

Break down complex products, features, or systems into fundamental primitives and building blocks from a software creator's perspective. Use when starting a new application, designing a large feature, or needing to understand a complex system's moving parts before building. Trigger phrases: "break down X", "decompose this", "what are the primitives", "building blocks of Z", "map the architecture",

Performs a comprehensive pull request code review covering correctness, security, performance, test coverage, and coding standards. Use when reviewing any code changes before merge.

When designing loosely coupled systems that react to state changes asynchronously.

Conduct two-stage code review: Stage 1 verifies spec compliance (criterion-to-code mapping), Stage 2 evaluates security, correctness, performance, and maintainability across 6 parallel facets with P1/P2/P3 synthesis and deduplication by file:line. Use when reviewing code changes or pull requests. This skill MUST be consulted because reviewing quality on broken logic is wasted effort, and unmet acc

Audita e refatora interfaces de usuário, substituindo elementos mal projetados por componentes modernos com caráter visual. Realiza uma entrevista detalhada sobre identidade de marca e referências de design antes de qualquer alteração.