Find agent skills by outcome

- Error states must be first-class UI states

not plain text dumps: use a dedicated error container/card/banner that is consistent with the current design system.

- Build a clear hierarchy: header

control strip

- Distinguish states clearly: idle

- When path-dependent behavior exists

display active working directory in UI/help text.

- For mutating commands (kill process

delete file

- Use CSS variables for tokens: color

spacing

Creative

- Every error must be rendered in-design: error UI must follow the widget's visual language (color tokens

typography

Creative

- If truncation is reported

show partial output status and avoid false-success messaging.

- If stdout is empty

return `{}` or `[]` consistently based on expected shape.

- In `parseJson` mode

ensure script returns exactly one JSON payload.

- Validate and normalize user inputs (path

hostname

- Prefer allow-list style validation for sensitive parameters (e.g.

command mode

- For user text interpolated into PowerShell single-quoted literals

always escape `'` -> `''`.

- `setStatus(message

tone)` where `tone` supports at least: `info`

- `runPs(script

parseJson = false

- `await window.HTWind.invoke(powershell.exec

{ script

- `pick(obj

camelKey

Coding & Debugging

- One fenced `html` code block containing the full

self-contained single file.

- Brief bullets: commands

safety decisions

- Quick edits: palette

refresh cadence

- If the user asks for a specific language

follow that explicit instruction.

- Default rule: if the user does not explicitly specify language

generate visible widget text in the same language as the user's prompt.

- Keep accessibility semantics aligned with UI language (for example `aria-label`

`title`

- If external URLs are used (for example fonts/icons)

include graceful fallbacks so the widget still functions as one deliverable HTML file.