Use this agent when the user is about to perform git operations like creating branches, making commits, or needs guidance on git workflow standards for this project. Examples: Context: User needs to create a new branch for adding a login feature. user: 'I need to create a branch for adding user authentication'…
Use this agent when the user is about to perform documentation operations like updating the openspec file, or needs guidance on openspec standards for this project. Examples: Context: User needs to add a new path for a new controller endpoint: 'I need to add a new path to the openspec file' assistant: 'I'll use the…
Signs and submits Solana transactions using @orquestradev/signer-mcp. Accepts a base64-encoded wire transaction produced by orquestra-tx-builder, presents a human-readable approval summary, and signs + sends only after explicit user confirmation. Uses ONLY signer-mcp tools. Examples: Context: User has an unsigned…
Central Orquestra orchestrator. Handles ANY Solana task end-to-end by delegating to four specialized sub-agents in sequence. Always start here — this agent decides which sub-agents to invoke and in what order. Sub-agents it controls: orquestra-researcher — program discovery, docs, instruction listing…
This file defines the role boundaries, tool restrictions, and execution pipeline for all Orquestra-powered Solana agents in OpenCode. Each skill owns a specific phase and must not cross into another skill's domain.
Implements tests from a guard specification and proves each guard bites by removing the named production line. Use for regression guards, contract tests, table tests, and vitest cases. Requires a caller-supplied specification — it does not decide what to guard.
Adversarial read-only defect hunt over a named area — wire handling, resource leaks, concurrency, silently dropped events, unwired seams. Produces ranked candidates with a reproduction path. It finds and argues; it never fixes.
Scoped implementation work whose correctness a test or lint run can prove. Use for Go/Svelte changes inside named files with a stated acceptance command. NOT for composition-root wiring, wire formats, REST/WS contract semantics, Matter parity constants, or auth/secret code.