Skill on Margrop Blog

Stop Letting Agents Guess UI: Installing and Using UI UX Pro Max the Right Way

Fri, 22 May 2026 22:50:00 +0800

The short version

UI UX Pro Max is not a magic prompt that suddenly gives an agent taste. It is a searchable UI/UX design intelligence Skill for AI coding assistants such as Claude Code, Codex, Cursor, Windsurf, Gemini, OpenCode, and similar tools. It packages product patterns, UI styles, color palettes, typography pairings, landing page structures, chart recommendations, UX guidelines, and stack-specific implementation advice into files and scripts that an agent can actually query.

The right way to use it is not to install it and keep asking for “a beautiful page.” The right way is to make the agent generate a design system first, then query UX, chart, web, or stack-specific guidance, and only then implement the page. That workflow reduces generic AI gradients, weak contrast, crowded mobile layouts, decorative dashboards, missing focus states, and many other common agent-generated UI problems.

This article uses only public references, a public repository, and a clean temporary verification directory. Commands, paths, project names, and examples are generic. No private addresses, credentials, internal project names, account names, or personal configuration are included. Screenshots are taken from public reference pages and sanitized verification work.

Small Models Make Agents Drift. Superpowers Gives Them Rails.

Thu, 07 May 2026 16:43:10 +0800

The short version

When an agent powered by a smaller or weaker model behaves unpredictably, the problem is not always solved by writing a longer prompt. Smaller models often struggle with long-horizon consistency, tool discipline, evidence tracking, and multi-step execution. Superpowers does not turn a weak model into a frontier model. What it does is more practical: it gives the agent an external engineering workflow made of reusable Skills, checkpoints, testing habits, debugging rules, review steps, and completion verification.

For agents such as OpenClaw, HermesAgent, Codex, Claude, Gemini, OpenCode, Droid, Cursor, and similar tools, Superpowers is best understood as an engineering-discipline layer. It makes the agent less dependent on improvisation and more likely to follow a repeatable process.

This article is about a very common failure mode in modern agent workflows: the model can talk fluently, but the agent does not behave reliably once the task becomes long, stateful, tool-heavy, or distributed across multiple agents.

The issue becomes more visible when using smaller domestic models, local models, quantized models, or cost-optimized models. They may answer normal questions well enough, but once they need to read a repository, follow a constraint, modify files, run tests, interpret logs, preserve privacy, and report only verified results, the instability becomes obvious.

All examples in this article are generic. No private hostnames, internal addresses, credentials, project names, or personal paths are included.

Integrating Synology Operations as an OpenClaw / HermesAgent Skill: From One Sentence to Auditable NAS Automation

Tue, 05 May 2026 12:20:00 +0800

I have already written two Synology CLI references on this blog:

Those posts answer the question: “What commands can a human run on a Synology NAS?” This article answers a different question: if I already use OpenClaw / HermesAgent, how can I turn those commands into an operations Skill so that I can ask the agent, in one sentence, to inspect the NAS, summarize evidence, prepare a maintenance plan, and execute approved commands only when the risk is acceptable?

The short answer is: yes, but the Skill must not become an unrestricted root shell. The right design is:

Make Synology SSH access controlled, testable, and revocable.
Put common Synology CLI operations into a Skill, together with command categories, risk levels, and output rules.
Allow read-only diagnostics by default.
Require explicit approval for service restarts, permission changes, user changes, network changes, deletion, and storage operations.
Preserve commands, output, and reasoning so each operation remains auditable.

If you only want the big picture, the diagram below summarizes the whole article.