hawk skill

Use this skill when editing Hawk applications or explaining Hawk behavior.

Quick workflow

Identify the page path, expected card shape, and whether this is a plain page, a template, or a composed page.
Prefer simple manx output first. Only reach for richer load composition when behavior clearly needs it.
Read card data through c and file/tree data through f.
Use Feather classes and semantic Sail before adding custom CSS or JS.
Check metadata early, especially /title, /pulse, /peek/public, and /poke/public.
Put !: at the top of Hawk-500 pages while debugging.

For Hawk's types, compile subject, loads, forms, event loop, and utility doors, read references/core-model.md.
For Feather, Spine, templates, auth/public access, URL behavior, configuration, and debugging guidance, read references/ui-and-ops.md.

Treat Hawk as a tree of programmable pages: file -> page -> {meta, code, data}.
Keep the root dime at / as the command kind for non-empty cards.
Prefer %manx for straightforward pages.
Use %twin for shared code, %call for shared code with initialization data, %view for mirroring another page's data, %lens for subtree reductions, and %shed only as a final asynchronous load.
Do not hand-walk info or file trees unless the utility doors are insufficient.
Do not put secrets in public page code. A public page exposes its code.page too.

If a form behaves oddly, verify card path names and whether values are being parsed as dimes instead of plain strings.
If a page does not update as expected, check whether it depends on the changed subtree through %view, %twin, %call, or %lens.
If a page is meant to be internet-visible or form-submittable, verify /peek/public and /poke/public.
If styling drifts, prefer Feather classes or head-extras overrides before custom one-off CSS.

Manual root: https://hawk.computer/~~/~/manual/
Some utilities are underdocumented in the manual. Inspect /lib/hawk/hoon and /lib/html-utils/hoon when needed.