Tuiweave app builder
Skill ishan5ain/tuiweave-agent-kit/skills/tuiweave-app-builder
Build, migrate, or review Go terminal applications that use tuiweave, with explicit layout, focus, ownership, compatibility, snapshot, scenario, and audit workflows.From its SKILL.md
npx -y skills add ishan5ain/tuiweave-agent-kit --skill tuiweave-app-builderAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.1 KB, 652 tokens by cl100k_base, as published. Nobody here has run it
tuiweave app builder
Use this skill in one of three modes: greenfield, migration, or review. Determine the requested mode from the task; if it is ambiguous, inspect the repository and choose migration when an existing TUI is present, otherwise greenfield.
Before editing, inspect the repository and go.mod, record the exact tuiweave
version or commit, and read the pinned tuiweave repository's
AGENT-CONTRACT.md, COMPATIBILITY.md, AGENT-CATALOG.md, matching AGENTS.md
recipes, closest runnable example, and DESIGN.md only when package ownership
is unclear. Tuiweave is API/design truth; this skill owns workflow, not a
duplicate component rulebook.
Read the matching reference completely:
- greenfield:
references/greenfield.md - migration:
references/migration.md - review:
references/review.md
Always read references/tuiweave-api-compatibility.md before proposing APIs.
Required task contract
Use this shape for every implementation task or migration slice:
Goal:
Reference tuiweave example:
Components:
Application-owned state:
Files allowed:
Behavior to preserve:
Acceptance tests:
Verification commands:
Out of scope:
Universal constraints
- Pin or identify the tuiweave version. A local
replaceis development-only. - Choose a fixed named theme constructor when theme discovery is unnecessary.
When an app exposes built-in choices, enumerate
tuiweave.Presets(), resolve stable IDs withThemeForPreset, and reconstruct themed components while preserving application-owned state. - Use
layout.Len,Min,Max,Percent,Ratio, andFill; do not construct, convert, or store Ultraviolet constraint values. - Respect
layout.SizeModeOf: width-bounded components render at their natural height instead of necessarily filling the assigned height. - Keep product routing, persistence, backends, and lifecycle in the app.
- Report reusable API gaps with a minimal example and acceptance test. Do not create a local tuiweave fork or modify tuiweave without explicit authorization.
- Reassign every component model returned by
Updateand collect every command. - Keep inspection trees, absolute bounds, action routing, and privacy in the app. Validate a qualified action against the current visible tree before forwarding its local suffix.
- Translate global tab-strip mouse coordinates to a local x-coordinate before
calling
tabs.IndexAt. - Review every intentional golden diff; never regenerate goldens during review.
- Run build, vet, tests, and
tuiweave-audit.sh; use--strict --verifyat handoff.
Do not assume APIs from other libraries. In particular, prohibit:
autocomplete.SetSuggestions;dialog.Message;scrollbar.Model;scrollbar.ForViewport;- delegating
/totabs.Updateas though tabs owned global search/focus keys; - synchronizing textarea completion from
Value()alone without cursor/range information.
What ships with it: 4 files
6.0 KB alongside SKILL.md
references/
- greenfield.md868 B
- migration.md798 B
- review.md923 B
- tuiweave-api-compatibility.md3.5 KB