agentsclimarketplace

Frontend for openclaw

Skill LeoYeAI/openclaw-coding-skills/skills/frontend-for-openclaw

Production-grade coding workflow, execution scaffolding, and tuning skills for OpenClaw agents, part of the MyClaw.ai ecosystem.

Install
npx -y skills add LeoYeAI/openclaw-coding-skills --skill frontend-for-openclaw

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 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.

What its author says it does

Copied from the file, not written here

Build or modify user-facing interfaces inside an OpenClaw workspace with strong interaction, responsiveness, and verification discipline. Use when the request sounds like "build this UI", "fix this page", "this interaction is broken", "make this responsive", "update this component", or any browser-facing change users will directly see, click, type into, or depend on visually.

SKILL.md

1.8 KB, as published. Nobody here has run it

Frontend For OpenClaw

Ship interfaces that hold up in real use, not just static screenshots.

Process

  1. Identify the user flow being changed.
  2. Respect the existing design language unless the task explicitly changes it.
  3. Build the smallest complete interaction slice first.
  4. Verify layout, state changes, and edge conditions.
  5. Check the result in a browser when practical.
  6. Confirm mobile and desktop sanity for changed surfaces.

Interface Rules

  • Prefer clear hierarchy over decorative complexity.
  • Make loading, empty, error, and success states explicit when they matter.
  • Preserve accessibility basics: focus order, labels, semantics, and readable contrast.
  • Avoid introducing visual churn unrelated to the request.

Reference Files

Read references/ui-verification-checklist.md before closing out user-facing changes.

Read references/state-surface-checklist.md when a UI flow adds or changes loading, error, empty, success, or recovery behavior.

Read references/interaction-regression-checks.md when the surface looks visually correct but interaction regressions are plausible.

OpenClaw Guidance

  • Use browser-based verification for interaction-heavy changes.
  • If a design task is exploratory, keep options structured rather than mixing several directions into one output.
  • Separate design judgment from implementation proof: something can look good and still be broken.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.