engineering-conventions

Enforce engineering invariants for opencode-swarm modifications and PR workflows.

1|Updated May 17, 2026

Search Tags:#audit trail #code compliance #invariant verification #opencode-swarm #engineering invariants

Ready to run

npx skills add https://github.com/djimit/djimitflo --skill engineering-conventions-djimit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: engineering-conventions
Source: https://github.com/djimit/djimitflo/tree/main/.opencode/skills/engineering-conventions
Command: npx skills add https://github.com/djimit/djimitflo --skill engineering-conventions-djimit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining adherence to engineering invariants crucial for modifying the opencode-swarm system, preventing potential regressions and system issues.

Core Features & Use Cases

Invariant Verification: Validates compliance with essential engineering principles and practices before system modification.
Preventive Guardrails: Provides guidelines for bounded operations, subprocess handling, and runtime portability.
Auditable Workflow: Enforces a clear, auditable process for Pull Requests (PRs) that touch sensitive areas.

Quick Start

Load this skill before any implementation that modifies the opencode-swarm, ensuring you're adhering to the defined engineering invariants.

Frequently Asked Questions about engineering-conventions

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

FAQPage Schema

How do I verify engineering invariants before modifying opencode-swarm?▼

Invariant verification validates compliance with critical engineering principles before modifying opencode-swarm. It checks bounded operations, subprocess handling, and runtime portability to prevent regressions and system instability during implementation.

What engineering conventions should I follow for secure Pull Request workflows in opencode-swarm?▼

Engineering conventions for secure PR workflows in opencode-swarm require enforcing a clear, auditable process for modifications touching sensitive areas. This includes maintaining an audit trail and verifying invariants across plugin initialization and subprocess handling before approval.

Why does opencode-swarm regress after plugin initialization or subprocess modifications?▼

opencode-swarm regressions occur after plugin initialization or subprocess modifications when engineering invariants are violated. Bypassing bounded operations and runtime portability guidelines introduces system instability that invariant verification is designed to prevent.

Do I need to check code compliance manually for every opencode-swarm modification?▼

You do not need to check code compliance manually for every opencode-swarm modification. Loading this skill automates invariant verification across all implementation phases, applying preventive guardrails to subprocess handling and runtime portability automatically.

Can I use automated invariant verification for runtime portability checks in opencode-swarm?▼

Yes, you can use automated invariant verification for runtime portability checks in opencode-swarm. The skill enforces runtime portability guidelines alongside bounded operations and subprocess handling during all modification phases without requiring external dependencies.