一键在 Manus 中运行任何 Skill

开始使用

hima-forge

星标1

分支0

更新时间2026年7月2日 18:59

Implement the minimum code to satisfy the charter's RED tests, one logical change per commit.

安装

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

在 Manus 中运行

来源

momomuchu

momomuchu/hima

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

下载

在 Manus 中运行

Purpose

Cover the cycle's impl stage: write the minimum code that turns the charter's RED tests green, guided by the blueprint's contracts. This is the strongest gate in the system — no write to an implementation file without a loaded charter and (when required) a loaded blueprint.

When to use

A sealed charter exists, RED tests are in place (or about to be written by hima-trial), and it is time to write or edit implementation code.
Never invoke this skill to "just fix it quickly" ahead of a charter — that is precisely the case this gate exists to stop.

Steps

Confirm a sealed charter is loaded; confirm a blueprint is loaded when the change is M+ or touches ≥2 files, a schema, or a public interface.
Write the minimum code that satisfies the charter's scenarios — no speculative scope.
Keep each commit either S (structural) or B (behavioral) per Tidy First — never mixed.
One logical change per commit; reference the charter in the commit message.
Re-run the RED tests continuously; stop as soon as they go GREEN, then hand off to hima-verdict rather than gold-plating.

Done when

All of the charter's RED tests are GREEN with no unrelated scope added.
Every commit in the change is cleanly S or B, never both.
The implementation is traceable back to its charter and (if used) its blueprint.

同仓库更多 Skills

同仓库

hima-admit

momomuchu/hima

Bootstrap a new project or catch up an agent on an existing one in minutes by reading vision/goals/state and scaffolding the minimum brain files.

2026-07-021

hima-blueprint

momomuchu/hima

Produce the structural plan — component boundaries, contracts, data flow — plus a lightweight decision record, from a sealed charter.

2026-07-021

hima-charter

momomuchu/hima

Formalize intent into a spec artifact (Gherkin scenarios, acceptance criteria, criticality tags) before any non-md file may change.

2026-07-021

hima-covenant

momomuchu/hima

Declare and audit the per-project disciplines (cadence, branching, testing, architecture, methodology) that the pluggable StageSkillMap resolves against.

2026-07-021

hima-lookout

momomuchu/hima

Cited, multi-source research pass for H/C decisions or true blockers — converts findings into requirements, risks, and rejected alternatives.

2026-07-021

hima-muster

momomuchu/hima

Bridge blueprint to forge — break an approved charter+blueprint into atomic, sequenced or explicitly-parallel steps, cross-critiqued once before trust.

2026-07-021

name	hima-forge
description	Implement the minimum code to satisfy the charter's RED tests, one logical change per commit.
stage	impl
source	base
mode	force

Purpose

When to use

A sealed charter exists, RED tests are in place (or about to be written by hima-trial), and it is time to write or edit implementation code.
Never invoke this skill to "just fix it quickly" ahead of a charter — that is precisely the case this gate exists to stop.

Steps

Confirm a sealed charter is loaded; confirm a blueprint is loaded when the change is M+ or touches ≥2 files, a schema, or a public interface.
Write the minimum code that satisfies the charter's scenarios — no speculative scope.
Keep each commit either S (structural) or B (behavioral) per Tidy First — never mixed.
One logical change per commit; reference the charter in the commit message.
Re-run the RED tests continuously; stop as soon as they go GREEN, then hand off to hima-verdict rather than gold-plating.

Done when

All of the charter's RED tests are GREEN with no unrelated scope added.
Every commit in the change is cleanly S or B, never both.
The implementation is traceable back to its charter and (if used) its blueprint.