Install
$ agentstack add skill-undertone0809-rudder-rudder-ui-polish-maintainer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Rudder UI Polish Maintainer
Overview
Turn concrete Rudder UI feedback into a scoped, implemented, visually verified, and committed change.
When to Use
Use this skill when:
- the user points at a Rudder screen or screenshot and asks for polish
- density, spacing, alignment, labels, badges, icons, menus, hover, empty states, onboarding, or small workflow UI is wrong
- the user asks for a screenshot after a local UI change
- the likely answer is CSS/layout/data layering for a visible surface
Do not use this skill when:
- pure advice with no implementation request; use build-advisor
- high-stakes proposal plus reviewer gates; use advisor-review-loop-maintainer
- missing-data root cause; use data-path diagnostician
- broad redesign not anchored to a visible Rudder surface
Core Pattern
intent -> evidence packet -> smallest UI change -> contract alignment -> browser/screenshot proof -> scoped commit
Quick Reference
| Situation | Action | | --- | --- | | Screenshot supplied | Match the visible issue and viewport | | User says “先说说” | Clarify direction before edits | | Visible function changes | Update E2E/contract as needed | | Layout-sensitive change | Verify rendered result |
Implementation
- Resolve whether the user wants discussion or implementation.
- Build a small evidence packet from screenshot, route, component, and product contract.
- Make the smallest coherent UI change consistent with Rudder design rules.
- Keep routes/nav/API contracts aligned for visible behavior.
- Validate in browser or screenshot and run focused tests.
- Commit only this task.
Reference files are part of this skill contract. Before executing high-risk actions or final judgments, load references/runbook.md for the detailed legacy workflow, examples, validation cases, and command-level guidance.
Use evals/ when the route needs that detail; keep the entrypoint thin.
Common Mistakes
| Mistake | Fix | | --- | --- | | Turning polish into a redesign | Stay scoped to the noticed problem. | | Relying on typecheck for layout | Inspect rendered UI. | | Ignoring product contracts for visible workflow changes | Sync behavior and tests. | | Staging unrelated dirty files | Commit only UI task files. |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Undertone0809
- Source: Undertone0809/rudder
- License: Apache-2.0
- Homepage: https://rudder.zeeland.studio
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.