A collection of Opencode-based command templates, global agent prompts, and workflow patterns for building sophisticated command-driven projects.
The Opencode Configurator (opencode-configurator/) is a meta-configuration system that makes setting up OpenCode effortless. Just ask naturally:
- "Is there a plugin for reducing token usage?"
- "Set up permissions so destructive commands require approval"
- "Create a /review command that analyzes code without making changes"
- "I want to build a skill for working with our internal API"
The configurator agent draws on five specialized skills:
| Skill | What it does |
|---|---|
| plugin-installer | Find and install community plugins, maintain a local catalog |
| opencode-config | Edit opencode.json with guided setup for models, permissions, providers |
| command-creator | Build custom /slash commands through interactive Q&A |
| skill-creator | Scaffold new skills with proper structure, scripts, and references |
| agent-architect | Design agents with research-backed prompt engineering patterns |
Installation: Drop the skill/ and agent/ folders into ~/.config/opencode/.
See opencode-configurator/README.md for full details.
A universal command template with:
- Command Integration Pattern: 4-part architecture for command-to-tool interfaces (still works, but deprecated - OC now supports skills natively)
- Template Structure: Organized framework for command-based projects
- Documentation System: Automated maintenance via specialized agents
- Example Commands: Repository exploration and mathematical calculation tools
See commands2skills/README.md for implementation details, architecture overviews,
and usage guidance.
Agents are organized into two collections under agents/:
- generic/ – Reusable global agents that belong in
~/.config/opencode/agent/:- agent-architect – Refines agents with research-backed prompts (best after running
opencode agent create). - repo-navigator-creator – Builds lean AGENTS.md navigation guides.
- subagent-orchestrator – Dispatches specialists and enforces scope isolation. (might need some tweaks - dumber models hallucinate agents)
- openspec-orchestrator – Enforces strict OpenSpec formatting/validation and orchestrates subagents for executing OpenSpec proposals (requires OpenSpec installed and
openspec init).
- agent-architect – Refines agents with research-backed prompts (best after running
- vite-react-ts-convex-tailwind/ – Stack-specific experts for the modern Vite + React 19.2 + TS 5.9 + Tailwind 4.1 + Convex stack (also supports Bun). Each agent references its matching documentation file (
CONVEX.md,REACT19.md,TAILWIND4.md,TS59.MD,CODING-TS.md) so it can cite authoritative answers on demand:- vite-react-convex-expert – Master coordinator for the entire stack, orchestrating subagents.
- convex-database-expert – Schema/query/mutation/action specialist grounded in Convex docs.
- react-19-master – React 19.2 implementation reviewer focused on Server Components, Actions, and compiler rules.
- tailwind-41-architect – Tailwind CSS 4.1 designer that enforces the CSS-first workflow.
- typescript-59-engineer – Strict TS 5.9 engineer who guards erasable syntax and configuration hygiene.
See agents/README.md for full tables, usage details, and the complete directory tree.
The commands/ directory provides shareable command files for Opencode users.
Currently available:
/howto(commands/.opencode/command/howto.md): An/init-style command that scans the cloned repository, searches for official documentation, and generates anAGENTS.mdfocused on helping end users set up, operate, and troubleshoot the software (not for development work). Run/howtoright after cloning a repo so your assistant knows how to install, run, and support that project./improve:run(commands/.opencode/command/improve:run.md): Transforms any task into a production-ready prompt using official prompt engineering guides from OpenAI GPT-5.1/5.1-Codex, Anthropic Claude 4.5, and Google Gemini 3 Pro, then executes it immediately./improve:save(commands/.opencode/command/improve:save.md): Same enhancement as/improve:runbut saves the optimized prompt as a markdown file for review and refinement before execution.
The scripts/ directory contains utilities that commands or agents can reuse.
perplexica-cli.js– Node-based CLI wrapper for Perplexica’s search API that handles long-running requests (300s timeout), prints answers with sources, and exposes focus modes (web, academic, Reddit, YouTube, Wolfram) via--modeflags. Point it at your Perplexica instance (defaulthttp://localhost:3000/api/search)./perplexica-search(scripts/.opencode/command/perplexica-search.md) – A specialized command that orchestrates the CLI to perform research with smart mode selection, structured summaries, and full citations.
Use everything inside at/ as prefix instructions during development sessions:
@coding-ts(at/CODING-TS.MD): Universal engineering guidelines emphasizing DRY principles, type safety, and clean architecture. Reference it in prompts (e.g., “Implement feature X following @coding-ts principles”) before starting any new feature or refactor so the LLM stays aligned. These reference files are meant for direct @ mentions in user instructions and are not invoked by subagents.
- Authenticated Chrome DevTools MCP (
mcp-configs/authenticated-chrome-dev-tools-mcp/) – Enables Chrome DevTools MCP to work with authenticated browser sessions. Normally Chromium blocks Google account login in automated browsers, and concurrent sessions can interfere with existing Chrome processes, potentially closing background windows. This wrapper creates a temporary "shadow profile" that clones your cookies, sessions, and login data, allowing AI agents to access your logged-in context without disrupting your main browser.
- Agent Swarm Demo (repo) – Shows how to launch a multi-server swarm where Claude Code handles background process management while OpenCode runs specialized agents. The swarm orchestrator coordinates inter-agent communication across multiple OpenCode instances and currently requires Claude Code because it relies on Claude’s background bash processes to spawn the servers.
- Clone this repository locally.
- Explore
commands2skills/for command templates and tooling patterns. - Install desired agents globally (
~/.config/opencode/agent/) or copy them into your project’s.opencode/agent/directory. - Install OpenSpec and run
openspec initif you plan to use the OpenSpec orchestrator or compatible workflows.
commands2skills/README.md– command architecture, tooling integration, and usage instructions.agents/README.md– agent descriptions, guardrails, and setup guidance.
This repository provides tested Opencode command patterns, global agent prompts, and workflow templates that demonstrate best practices for creating maintainable, scalable command-based projects with external tool integration.
