Explorar skills

Use when legacy prompts or older framework flows reference `using-git-worktrees` and you need the modern runtime to resolve that capability cleanly.

Use when important product, technical, or founder decisions need to be captured as durable context with rationale, tradeoffs, and follow-up implications.

Executes authorized attack simulations against Active Directory environments to identify misconfigurations, weak credentials, dangerous privilege paths, and exploitable trust relationships that could lead to domain compromise. The tester uses BloodHound for attack path analysis, Mimikatz for credential extraction, and Impacket for protocol-level attacks including Kerberoasting, AS-REP Roasting, an

Official Helius AI tooling repository

Explore Solana's architecture and protocol internals. Covers the SVM execution engine, account model, consensus, transactions, validator economics, data layer, development tooling, and token extensions using the Helius blog, SIMDs, and Agave/Firedancer source code.

Use when legacy prompts or older framework flows reference `elite-developer` and you need the modern runtime to resolve that capability cleanly.

Use when the founder needs a single orchestrator to route work across multiple departments, synthesize specialist output, or translate an ambiguous business request into a concrete execution path.

Minimal codex-native review loop. Use for local diff review with measurable quality gates and a JSON artifact.

Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

Use when legacy prompts or older framework flows reference `conversion-engineer` and you need the modern runtime to resolve that capability cleanly.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation