// Use before making meaningful code changes in HOM to load repository architecture, workflow rules, crate boundaries, feature flags, and verification requirements
| name | hom-workspace-standards |
| description | Use before making meaningful code changes in HOM to load repository architecture, workflow rules, crate boundaries, feature flags, and verification requirements |
This is the Codex-compatible form of the important stable guidance from CLAUDE.md.
<when_to_use> Use this skill for:
<required_reading> Read:
skills/hom-workspace-standards/references/workspace-architecture.mdThen read the relevant domain skill for the part of the codebase you are touching. </required_reading>
Follow this baseline workflow:<success_criteria> This skill is being followed correctly when:
Use this skill when building, reviewing, or refactoring Rust code that requires strong maintainability discipline: SRP, DRY, OCP, explicit dependency injection, TDD/ATDD workflow, architecture review, and clean project structure. Complements the project's Rust CLAUDE.md with process rigor.
Use when adding a new harness adapter or modifying an existing one in hom-adapters
Use when working on terminal emulation, the TerminalBackend trait, libghostty integration, or PTY management
Use when modifying TUI rendering, input routing, layout, command bar, or pane management
Use when creating, modifying, or debugging YAML workflow definitions or the workflow engine
Use when building, reviewing, or refactoring Rust code in HOM that requires strong maintainability, testing discipline, and explicit dependency boundaries