engineering-conventions

Enforce engineering invariants for opencode-swarm architecture, plugins, and runtime state.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/refernandes/toktrim --skill engineering-conventions-refernandes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-conventions
Source: https://github.com/refernandes/toktrim/tree/main/.opencode/skills/engineering-conventions
Command: npx skills add https://github.com/refernandes/toktrim --skill engineering-conventions-refernandes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures adherence to critical engineering invariants when modifying opencode-swarm, reducing risks and maintaining quality.

Core Features & Use Cases

  • Prevent regressions: Provides guidelines for modifying opencode-swarm to avoid known pitfalls.
  • Ensure compatibility: Validates architecture, plugin initialization, subprocesses, and more for consistency.
  • Quick Start: Load this skill before working on opencode-swarm to ensure invariants are respected.

Quick Start

Load this skill before modifying any opencode-swarm components that could impact architecture, plugins, or runtime state.

Frequently Asked Questions about engineering-conventions

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

FAQPage Schema
How do I enforce engineering invariants when modifying opencode-swarm architecture?▼

Enforce engineering invariants for opencode-swarm by loading this skill before modifying architecture, plugin initialization, subprocesses, or runtime state to ensure adherence to established standards.

What engineering standards should I follow for opencode-swarm plugin initialization?▼

Engineering standards for opencode-swarm plugin initialization require validating architecture and subprocess consistency to prevent regressions and maintain runtime state compatibility.

When do I need to apply engineering conventions for swarm modifications?▼

Apply engineering conventions for swarm modifications whenever changes impact architecture, plugin initialization, subprocess handling, runtime state, or tests to reduce risks and maintain quality.

Can I use quality assurance guidelines to prevent regressions in opencode-swarm?▼

Quality assurance guidelines prevent opencode-swarm regressions by providing established invariants for modifying architecture, plugin initialization, subprocesses, and runtime state to avoid known pitfalls.

What's the best way to validate subprocess handling consistency in opencode-swarm?▼

Validate subprocess handling consistency in opencode-swarm by loading engineering conventions that enforce established invariants and standards before making modifications to runtime state or tests.

Does this skill apply to all opencode-swarm runtime state changes?▼

Yes, this skill applies to all opencode-swarm modifications involving runtime state, architecture, plugin initialization, subprocess handling, and tests, requiring adherence to established engineering invariants.