Desenvolvimento

{{ ƔƔƔ }} Tackle a task from Linear

{{ 𝛀𝛀𝛀 }} Add a task to a project roadmap with correct ID, dependency wiring, and graph integrity. Use this skill whenever the user wants to add a task, feature, or work item to a roadmap — even if they just say 'add this to the roadmap', 'put this in the plan', or 'track this as a task'. Handles task ID assignment, section placement, dependency edges in both directions, and ensures no task is

Automatically detect the language, framework, package manager, test runner, linter, and build tool used in the current project. Produces an .claude/autoimprove/config.md file that the improve loop uses as its measurement suite. Run this once before starting the improve loop in a new project.

Pedagogical framework for teaching programming through Socratic dialogue. Use when a learner wants to LEARN programming rather than have code written for them. Triggers include "teach me", "help me understand", "I'm learning", "tutor mode", or requests to not provide solutions. Emphasizes productive struggle, graduated hints, metacognitive scaffolding, and emotional support.

Systematically debugs issues using structured diagnosis — reproduce, isolate, identify root cause, and fix. Use when facing bugs, errors, unexpected behavior, or failing tests.

Use when designing, planning, or executing a testing strategy for an SAP implementation, upgrade, or change project. Triggers on any request involving test planning, UAT, test cases, test automation, defect management, or sign-off readiness.

{{ ƔƔƔ }} Rename branch if needed

{{ 𝛀𝛀𝛀 }} Create a new Linear issue with automatic dependency detection

Display code-forge feature dashboard with task-level progress from state.json, or show detailed status for a specific feature. Use when checking progress, asking "what's left", viewing task completion, or wanting a bird's-eye view of the project.

Use when creating, reworking, reviewing, or improving any SAP Superpowers skill file. Triggers on requests to write a skill, update a skill, add a section to a skill, or pressure-test a skill.

Browser-based QA verification after any implementation. Use when someone says "QA this", "test this in browser", "verify the feature", "qa test", "browser test", or after completing an /implement-change to verify acceptance criteria in a real browser. Opens Chrome via MCP, exercises each acceptance criterion, verifies via DOM snapshots, and reports pass/fail. The "closer" for every implementation

{{ 𝛀𝛀𝛀 }} Investigate this repo's dependencies in detail