Frontend UI Engineer for Openclaw

Prerequisites

• An AI agent platform that supports SKILL.md, such as Claude Code, Cursor, Codex, or Gemini CLI.
• Windows, macOS, or Linux.
• Access to an LLM API supplied by the agent platform.
• Required source data or project files, potentially from GitHub.
• API credentials or access tokens when the selected workflow requires external API access.

Installation

The source document does not specify a package manager, registry command, or standalone runtime installer. Install the skill by adding its SKILL.md definition to the skills directory supported by your AI coding agent, then restart or reload the agent.

A generic project-local setup can be prepared as follows:

mkdir -p .agent/skills/frontend-ui-engineering
cp SKILL.md .agent/skills/frontend-ui-engineering/SKILL.md

Use the equivalent skills path required by your agent if it differs. Do not commit API keys to the repository; configure them through the agent or operating-system environment.

First run

1. Confirm that the agent can discover frontend-ui-engineering.
2. Provide a non-empty content input.
3. Set format to json, text, or markdown when needed.
4. Add options for output style, batch size, or other supported advanced configuration.
5. Inspect the returned success, data, and error fields before using the result.

Request schema

Response schema

{
  "success": true,
  "data": {
    "result": "frontend-ui-engineer processing result",
    "metadata": {
      "skill": "frontend-ui-engineering",
      "version": "1.0.0",
      "pricing_tier": "L2-advanced"
    }
  },
  "error": null
}

Metadata taxonomy

• Skill identity: frontend-ui-engineering.
• Version: 1.0.0.
• Pricing tier: L2-advanced, with the source listing a per-use pricing model.
• Execution state: success indicates whether processing completed.
• Payload: data.result contains the generated or processed output.
• Failure information: error contains error details when processing does not complete.

The workflow may read project files and source data, but the source document does not define a fixed generated-file directory or additional artifact naming convention. Treat returned results and any agent-created project files as implementation-specific outputs.