Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

$pwd:

hom-workspace-standards

Name: Hom Workspace Standards
Author: mudrii

// Use before making meaningful code changes in HOM to load repository architecture, workflow rules, crate boundaries, feature flags, and verification requirements

Ejecutar en Manus

$ git log --oneline --stat

stars:1

forks:0

updated:11 de abril de 2026, 15:18

Explorador de archivos

2 archivos

SKILL.md

readonly

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

Load the repository-specific rules that apply across the HOM workspace.

This is the Codex-compatible form of the important stable guidance from CLAUDE.md.

<when_to_use> Use this skill for:

any feature work
any bugfix
any refactor
any architecture review
any change that crosses crate boundaries </when_to_use>

<required_reading> Read:

skills/hom-workspace-standards/references/workspace-architecture.md

Then read the relevant domain skill for the part of the codebase you are touching. </required_reading>

Follow this baseline workflow:

Inspect the workspace root, relevant crate layout, feature flags, and tests before editing.
Match existing patterns and prefer the smallest coherent change.
Keep behavior changes, tests, and docs in the same change.
Pass dependencies explicitly; do not hardcode ports, paths, URLs, credentials, or feature switches.
Verify locally before handing off.

<success_criteria> This skill is being followed correctly when:

crate boundaries remain intact
project-specific architecture constraints are preserved
feature flag boundaries remain clean
tests and verification match the affected scope
the change does not quietly bypass existing configuration or runtime wiring </success_criteria>

related-skills.json

mismo repositorio

rust-rig.md

from "mudrii/hom"

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.

2026-04-111

hom-adapter-development.md

from "mudrii/hom"

Use when adding a new harness adapter or modifying an existing one in hom-adapters

2026-04-111

hom-terminal-integration.md

from "mudrii/hom"

Use when working on terminal emulation, the TerminalBackend trait, libghostty integration, or PTY management

2026-04-111

hom-tui-testing.md

from "mudrii/hom"

Use when modifying TUI rendering, input routing, layout, command bar, or pane management

2026-04-111

hom-workflow-authoring.md

from "mudrii/hom"

Use when creating, modifying, or debugging YAML workflow definitions or the workflow engine

2026-04-111

rust-rig.md

from "mudrii/hom"

Use when building, reviewing, or refactoring Rust code in HOM that requires strong maintainability, testing discipline, and explicit dependency boundaries

2026-04-111

package.json

"author": "mudrii"

"repository": "mudrii/hom"

Abrir repositorio de GitHub Ver repositorios del creador

$ install --global

$ download --local

Ejecutar en Manus

$ useful --forSOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas15-1252L4

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

Load the repository-specific rules that apply across the HOM workspace.

This is the Codex-compatible form of the important stable guidance from CLAUDE.md.

<when_to_use> Use this skill for:

any feature work
any bugfix
any refactor
any architecture review
any change that crosses crate boundaries </when_to_use>

<required_reading> Read:

skills/hom-workspace-standards/references/workspace-architecture.md

Then read the relevant domain skill for the part of the codebase you are touching. </required_reading>

Follow this baseline workflow:

Inspect the workspace root, relevant crate layout, feature flags, and tests before editing.
Match existing patterns and prefer the smallest coherent change.
Keep behavior changes, tests, and docs in the same change.
Pass dependencies explicitly; do not hardcode ports, paths, URLs, credentials, or feature switches.
Verify locally before handing off.

<success_criteria> This skill is being followed correctly when:

crate boundaries remain intact
project-specific architecture constraints are preserved
feature flag boundaries remain clean
tests and verification match the affected scope
the change does not quietly bypass existing configuration or runtime wiring </success_criteria>

hom-workspace-standards

Más de este repositorio

Más de este repositorio