arkade-product-ui

Installation
SKILL.md

Arkade contract UI

The screen follows the covenant-viz picture. It shows one next action, the next step that picture names. It does not invent a second protocol beside that picture. Hide a function the user cannot satisfy. Do not show a witness, a txid, or a control asset on that path. Connect and send open in a new tab and return to the same standing address the picture funded.

The design sources are separate repositories. Use them when those skills are installed. Otherwise clone emilkowalski/skills and pbakaus/impeccable and read the skill files named below. They are not application dependencies. Emil's skills are for motion after the flow is right. They are not a substitute for the flow.

A contract surface is Operate in Impeccable (skill/SKILL.src.md): the user completes a task. A landing page on the same product is Persuade. If the skill is installed, run its context command once, use shape before a new surface, and read the craft floor immediately before editing. A narrow fix stays on the existing screen. Verify once at desktop and mobile, fix what that pass shows, confirm once, and stop.

Polish and motion come from emilkowalski/skills, emil-design-eng. Load prototype while the flow is still fake, and animate only after that skill's decision framework says the motion should exist. An action the user repeats does not animate. A press uses transform only, ease-out, and scale(0.97) on :active. Review notes go in one table with Before, After, and Why.

Match the artifact

The one next action is the operation the picture's current coin allows. Funding the standing address pays that address. It is not a function on contract.functions. A covenant spend is one function on contract.functions, named as in the .ark file, and only when this user can satisfy it and the picture draws that spend. Constructor fields that pin the outputs were collected when the address was funded. That spend sends the witnesses and outputs that function checks, and nothing else. A payment, a witness, or a second contract the picture does not draw is a second protocol. Leave it out.

A direct send creates a second coin beside the one the contract continues. The screen must say which of those two the user just did. Only a spend that pays the continuation script changes the position the contract tracks.

Numbers the user sees are the integers the covenant computes, in the units the contract uses. A display format is applied after that result. A preview that rounds in floating point and then spends the rounded value will disagree with the script.

Say when the page does not broadcast. A hash of the form fields is not a script, an address, or a payment.

Installs
7
GitHub Stars
7
First Seen
Oct 8, 2026