Rico Sta. Cruz rstacruz

Inspected Properties

Detailed notes on properties we've visited.

Back: Property Search Index · Inspection Schedule

#1 — 275 Inkerman St, Balaclava ❌ Ruled out

Opencode plugin development guide

Generated with LLM assistance on 2 Nov 2025 with minimal human verification.

Overview

Opencode plugins extend the functionality of the Opencode AI assistant by allowing you to add custom tools, authentication providers, event handlers, and hooks into the core system. This guide covers how to create, configure, and distribute plugins.

Source files:

Keeping up with a changelog

Got a fast-moving changelog like in https://github.com/sst/opencode/releases ? OpenCode itself can help you keep track.

Add this file
- Add opencode_changes.md below into your Notes and snippets git repo
- You have a notes repo, don't you? If not, start a repo where you dump random Markdown files. It's useful for a lot of things
Ask OpenCode to update it

Copy file path to clipboard

Here's a simple way to integrate Neovim with OpenCode or Claude Code.

Select some text
Press <leader>fyr
Paste it into the LLM agent of your choice

This copies the file path into your clipboard in a format like @lib/keymaps.lua#L24-36. This mimics what the Claude Code VS Code extension would do (Alt+Cmd+K).

One-step quick commit

Commit and push in one step with opencode.

$ oc-commit
.
.

feat(bin): update help formatting and clarify LLM agent usage

OpenCode notification plugin

Shows desktop notifications with a summary of what the agent last said:

Place AGENTS.md in ~/.config/opencode/AGENTS.md
Place notification.ts in ~/.config/opencode/plugin/notification.ts

Also check out https://github.com/rstacruz/spec-mode-prompt

Spec mode guidelines

You are a senior software engineer assisting a user in defining and planning a new feature. Your goal is to guide the user through a structured process, resulting in a clear set of documents that can be handed off for implementation.

Guiding principles

Planner, not doer:
- Your primary role is to create planning artifacts (requirements.md, design.md, tasks.md).
- You MUST NOT write the implementation code yourself.
Phased approach:

	# NixOS config for LLM-API-Key-Proxy
	# https://gist.github.com/rstacruz/3a7e9b4a2cabdd9c21947eeb3e191f2c
	# https://github.com/Mirrowel/LLM-API-Key-Proxy
	#
	# First start:
	# git clone https://github.com/Mirrowel/LLM-API-Key-Proxy.git
	# cd LLM-API-Key-Proxy
	# # ...then copy this shell.nix in
	# nix shell --run "pip install -r requirements.txt"
	#

	#!/usr/bin/env bash
	# Prints a random name.
	#
	# Usage:
	# echo $(gen-name)
	# # oceanwood
	# # raincloud
	# # mahoganybay
	# # scarletfog