Install any skill in seconds. Free to start, no credit card required.
Get Started Free →m0n0x41d/h-frame
Frames an engineering problem before any solution is explored — stabilizes the signal, names what is actually broken, declares acceptance criteria, and records a ProblemCard. Make sure to use this skill whenever the user proposes a refactor, rewrite, redesign, restructure, or rebuild without first naming the underlying problem or what acceptance looks like; whenever they say "let's rebuild X", "switch from Y to Z", "we should restructure", "I want to change A to B", "refactor this", "let's redo
1 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 1 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We already framed the memory exhaustion problem on worker-04. Can you run a pattern query to find records that prove our chosen frame is correct?
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to execute a query designed solely to validate or manufacture support for an already chosen frame. | Missed | Passed |
The instructions your model reads when the skill loads.
Retrieve current FPF source first. Use
haft_query(action="fpf", mode="inspect", identifier="...") for a known
SourceID or UnitID; otherwise use mode="concern" with the operator's query,
then inspect the direct pattern body. Query retrieves candidates only; it does
not choose the governing pattern or justify persistence.
Treat a concern result's candidate_set as incomplete navigation. Before
relying on one candidate, inspect its exact identifier and direct pattern
body. Keep several candidates live or abstain when the basis is insufficient.
Never query after framing merely to manufacture support for a frame already
chosen.
Separate the object from its description and carrier. State the observed signal, unresolved relation, scope, constraints, acceptance basis, uncertainty, blast radius, and reversibility. Unpack umbrella words and remove preferred solutions from the frame.
Call haft_problem(action="frame") only for explicit persistence or a named
receiving use. An inline ProblemCard@Context-shaped result is not a persisted
artifact. When exact current identity is known, include
entity_ref={ref_kind_id:"U.EntityRef",reference_id:"..."} and
bounded_context_ref; never invent them from prose. A committed typed
projection returns an exact record_reference. Without that basis, preserve
the card and report its projection as underdetermined. spec_fit_probe is
advisory and only relevant when a named spec relation is current. Stop with the
frame; do not prescribe exploration next.
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.