From claude-commands
Runs bounded UI automation loops in Claude Code using screenshot→decide→act cycles with click/type/scroll tools, safety guardrails, and step limits for desktop/browser control.
npx claudepluginhub jleechanorg/claude-commandsThis skill uses the workspace's default tool permissions.
Run Claude Code as a bounded UI-control agent that observes screenshots, takes one action, re-checks state, and repeats until success or stop conditions.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Run Claude Code as a bounded UI-control agent that observes screenshots, takes one action, re-checks state, and repeats until success or stop conditions.
Require these tool primitives (or closest equivalents):
screenshot()click(x,y) / double_click(x,y)type(text) / key(combo)scroll(delta)ocr(region) / accessibility_tree()Never take multiple UI actions in a single reasoning step.
Use non-interactive Claude Code mode for deterministic logs:
claude --print --permission-mode bypassPermissions "<task prompt>"
Task prompt template:
You are controlling a UI via tools.
Goal: <goal>
Allowed scope: <apps/sites>
Max steps: <N>
Rules:
- One action per step.
- After each action, screenshot and verify.
- If uncertain for 2 steps, stop and ask.
- Ask before destructive actions.
Return a step log and final status: success | blocked | needs-human.
Declare completion only when:
Always return concise evidence: