skills.rest
RamonsDka
RamonsDkaCOMMUNITY
Explore all skills by this author →
GitHub

opencode-rules

Codify governance rules for Opencode projects with modular rule loading and naming conventions.

1|1|Updated Apr 19, 2026
Search Tags:#architecture#patterns#governance#best-practices#naming-conventions#opencode
One-click install
npx skills add https://github.com/RamonsDka/the-architect-overlay --skill opencode-rules
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opencode-rules
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/opencode
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill opencode-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide codifies the core governance rules for the Opencode ecosystem, helping teams align on architecture, naming, and workflow standards to reduce ambiguity and entropy.

Core Features & Use Cases

  • Modular rule sets: Distill best practices into independent, reusable rules that can be loaded per project or task phase.
  • Architectural discipline: Enforce patterns like independent operations, research-first approaches, minimal invasive edits, and robust root cause debugging to improve maintainability.
  • Naming and structure conventions: Standardize semantic names, design tokens, and small, focused components to ease onboarding and collaboration.
  • State and data governance: Encourage server-component style data flows and prudent handling of secrets to improve security.

Quick Start

Review the Opencode rules and start applying the architectural patterns to your project structure.

Frequently Asked Questions about opencode-rules

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

FAQPage Schema
How do I enforce architecture and naming conventions across an OpenCode project?▼

Architectural governance rules enforce independent operations, research-first approaches, minimal invasive edits, and root cause debugging to standardize development practices and improve maintainability across engineering teams.

Can I load governance rules modularly for different project phases?▼

Yes, you can load modular rule sets independently per project or task phase, distilling best practices into reusable rules that apply specific architectural patterns and naming conventions exactly when needed.

What is the best way to standardize data flow and handle secrets in OpenCode?▼

You should follow state and data governance rules that encourage server-component style data flows and prudent handling of secrets to improve security and maintainability across your engineering team.

Does the opencode-rules skill require external dependencies or scripts to function?▼

No, the opencode-rules skill operates with zero dependencies and enables optional resources like scripts, references, and assets for extensible guidance without requiring external components.

When should I not use modular rule sets for architecture governance?▼

You should avoid using modular rule sets when your project lacks OpenCode ecosystem integration, as the governance rules specifically codify modular rule loading, naming conventions, and pattern-driven workflows for OpenCode projects.

Related Skills

Explore More Software Engineering Skills→
CharitablebusinessroninCharitablebusinessronin

plugin-creator

Create OpenCode plugins and configure their project/global load locations.

Community
Intermediate
markwang2658markwang2658
31

systematic-debugging

Apply a four-phase debugging workflow to identify and eliminate root causes.

Community
Advanced
Charles5277Charles5277
45

vue

Reference Vue 3 Composition API patterns, component architecture, and testing practices.

Community
Intermediate
matlockxmatlockx

coding-standards

Enforce universal coding standards across Go, Rust, Swift, TypeScript, JavaScript, React, and Node.js.

Community
Advanced