Skip to content

Commit b99d11f

Browse files
committed
Fix DiagramFrame JSX in skills-and-procedures doc
1 parent 5325b44 commit b99d11f

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎website/docs/skills-and-procedures.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,9 @@ narration="Skills cost the same to advertise either way: the discovery metadata
2121
caption={
2222
'Both paths pay the same discovery metadata. Manual invocation loads one procedure; a near match loads a second one it never uses — and never removes.'
2323
}
24-
25-
> <SkillsInvocationDiagram />
26-
> </DiagramFrame>
24+
>
25+
<SkillsInvocationDiagram />
26+
</DiagramFrame>
2727
2828
Drag the catalog control: it grows the discovery metadata carried by both prefixes, pushing the prompt deeper into the attention valley, while every procedure body stays out of the window until something activates it. The AUTO panel always shows a near match, because that is the only outcome worth drawing — a lucky direct match reproduces the manual trace exactly. The wrong procedure body and the false-start turn it produced load before the correct skill and then sit at the bottom of the valley for the rest of the run. Everything separating the two panels is the price of one bad pick, and manual invocation never pays it.
2929

0 commit comments

Comments
 (0)