skills.rest
vcntttt
vcnttttCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

opencode-primitives

Aligns OpenWork implementations with official OpenCode documentation terminology and metadata requirements.

1|Updated Sep 11, 2023
Search Tags:#documentation#skills#MCP servers#plugins#frontmatter#opencode
One-click install
npx skills add https://github.com/vcntttt/dotfiles --skill opencode-primitives
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opencode-primitives
Source: https://github.com/vcntttt/dotfiles/tree/main/.agents/skills/opencode-primitives
Command: npx skills add https://github.com/vcntttt/dotfiles --skill opencode-primitives

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenWork implementations often drift from official OpenCode terminology, leading to inconsistent UI and guidance across projects.

Core Features & Use Cases

  • Reference OpenCode docs for skills, plugins, MCP servers, and config sources to ensure consistent terminology and guidance across projects.
  • Serve as a governance anchor to align UI labels and behavior with OpenCode terminology.
  • Provide a centralized starting point for onboarding and design reviews when adding new OpenCode primitives.

Quick Start

Call the opencode-primitives skill before implementing any OpenCode primitives to align terminology with official docs.

Frequently Asked Questions about opencode-primitives

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I align my custom OpenCode skills and plugins with official documentation?▼

To align OpenCode implementations, reference centralized official documentation to ensure consistent terminology and guidance. This approach prevents UI drift and maintains consistency across skills, plugins, and MCP servers.

What is the required YAML frontmatter format for SKILL.md files?▼

The required YAML frontmatter for SKILL.md files must include name and description metadata fields. Enforcing this frontmatter ensures OpenCode primitives maintain consistent documentation standards across projects.

When do I need to centralize documentation sources for OpenCode primitives?▼

Centralize documentation sources when building OpenCode primitives like skills, plugins, MCP servers, or opencode.json configurations. Centralization maintains terminology consistency and serves as a starting point for design reviews.

Can I use opencode.json configurations to standardize terminology across multiple projects?▼

Yes, opencode.json driven configurations can be standardized across projects by referencing official OpenCode documentation. This ensures consistent UI labels, behavior, and terminology guidance when adding new OpenCode primitives.

Why does my OpenCode implementation drift from official terminology?▼

OpenCode implementations drift from official terminology when development lacks a centralized documentation reference. Aligning implementations with official docs prevents inconsistent UI labels and guidance across different projects.

Related Skills

Explore More Software Engineering Skills→
AshenDulsankaAshenDulsanka
4

grill-with-docs

Validate project plans against domain models and update documentation inline.

Community
Intermediate
HadiCherkaouiHadiCherkaoui

go-data-structures

Explain Go data structures, allocation primitives, and iota to developers.

Community
Intermediate
dzackgarzadzackgarza
1

opencode-plugin-development

Develop OpenCode plugins with hooks, tools, and event handling.

Community
Advanced
open-haxopen-hax
6

opencode-agents-skills

Automate OpenCode agent and skill documentation with validated YAML frontmatter.

Official
Intermediate