Desenvolvimento

Check domain availability (Available/Taken) for any TLD with confidence scoring, SSL certificate inspection, and IP resolution. Uses 5+ sources in parallel — RDAP, WHOIS (TLD-specific patterns for 30+ ccTLDs/gTLDs, IANA fallback for unknown TLDs), authoritative DNS NS lookup as GDPR tiebreaker for .de/.eu/.at/.ch/.es, DNS A/AAAA, HTTP reachability, and TLS certificate validation. Returns a clear b

Defines the testing standards, patterns, and conventions for all C# unit and integration test projects. Rules cover test framework usage, naming, structure, mocking, assertions, and parameterization. Apply these rules uniformly across all test projects.

Use before claiming ANY task is complete. Activates at the end of every skill execution, every deliverable generation, and every user request fulfillment. Blocks completion claims that lack enumerated evidence.

SWI-Prolog-specific tooling, standards, and idioms. Use when working with SWI-Prolog code. Emphasizes relational thinking, steadfastness, DCGs, constraints, and mandatory testing with PlUnit.

Manage Julia packages (add, remove, status, update, test, develop)

Use when diagnosing plugin health, MCP server connectivity, SAP system connection issues, or configuration problems. Runs systematic health checks and produces a diagnostic report.

Injected at session start. Use when any SAP-related question, task, or project is detected. Governs skill routing, workflow chains, knowledge retrieval, and agent delegation for the entire SAP Superpowers system.

{{ 𝛀𝛀𝛀 }} Assess branch readiness for PR submission

Create technical implementation plans and architecture designs. Use when someone needs a detailed technical approach before coding begins — "create a plan", "plan this ticket", "how should we implement this", "technical design", "architect this", "design the approach", "plan the migration", "refactor plan", "how should we structure this", or when shaped work or a groomed ticket needs a concrete im

Defines the C# coding standards, patterns, and conventions to be applied consistently across all C# projects. Rules cover naming, structure, async patterns, null handling, dependency injection, logging, result patterns, and formatting. Apply these rules uniformly in all production code.

{{ 𝚫𝚫𝚫 }} Create a status report that knows what you've done since the last one

Use when encountering any bug, test failure, or unexpected behavior — enforces root cause investigation before fixes. Prevents symptom-fixing, masking bugs, and "just try this" approaches. For code-forge features, use code-forge:fix instead.