一键在 Manus 中运行任何 Skill

hom-workspace-standards

星标1

分支0

更新时间2026年4月11日 15:18

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

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

mudrii

mudrii/hom

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

相关职业SOC

基于 SOC 职业分类

软件开发工程师计算机与数学类职业·SOC 15-1252

文件资源管理器

2 个文件

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>

同仓库更多 Skills

同仓库

rust-rig

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

mudrii/hom

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

2026-04-111

hom-terminal-integration

mudrii/hom

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

2026-04-111

hom-tui-testing

mudrii/hom

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

2026-04-111

hom-workflow-authoring

mudrii/hom

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

2026-04-111

rust-rig

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

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>