Skip to content

Rules Hardening — Improve 11 rule files with examples and anti-patterns #39

@striderZA

Description

@striderZA

Summary

Each of the 11 rule files in .opencode/rules/ should include concrete examples, anti-pattern checklists, and enforceability criteria. Godot rules as priority.

Current Rules

ai-code.md, data-files.md, design-docs.md, engine-code.md, gameplay-code.md, narrative.md, network-code.md, prototype-code.md, shader-code.md, test-standards.md, ui-code.md

Per-Rule Requirements

  • Examples: At least 1 good + 1 bad example per rule
  • Anti-pattern checklist: Bulleted list of things to explicitly avoid
  • Enforceability: Code-review criteria that can be mechanically checked
  • Cross-references: Link to related agents and skills

Godot Priority

  • engine-code.md — ensure Godot-specific patterns (signals, autoloads, resources)
  • shader-code.md — Godot shading language examples
  • gameplay-code.md — Godot node/scene patterns

Acceptance Criteria

  • All 11 rule files have examples section
  • All 11 rule files have anti-pattern checklist
  • Godot-specific content in engine-code, shader-code, gameplay-code
  • Cross-references added to related agents/skills

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requestgood first issueGood for newcomers

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions