hashgraph-online/awesome-codex-plugins / plugins/beefiker/superloopy/skills/superloopy-frontend
superloopy-frontend
VerifiedUse only after explicit Codex `$superloopy:superloopy-frontend` or Claude Code `/superloopy:superloopy-frontend` invocation for supported screen-based application UI across browser-hosted Web, interactive deployed content-led Web, desktop, mobile/tablet, embedded/hybrid, Qt, custom-rendered, or mixed targets, such a task started with a leading `loopy` or `루피`, or an active Superloopy loop explicitly routing it here. Do not activate from UI, frontend, desktop, mobile, or framework vocabulary alone, or for TV, wearable, XR, automotive, game UI, TUI, static media/document artifacts, or non-UI work.
references/impeccable.md
View on GitHub# Impeccable-informed visual direction
Load this reference only for marketing, editorial, campaign, or an explicitly new visual direction after the target route, shared UX, layout when selected, and `anti-slop.md`. It sharpens presentation decisions without creating another routing, product, design-system, or evidence authority.
## Ownership boundary
**Superloopy owns** activation, target and renderer routing, existing-stack preservation, user and product truth, platform behavior, dependency approval, accessibility, responsive proof, evidence proportionality, and completion.
**Impeccable informs** visitor mode, visual thesis, typography, composition, hierarchy, interaction character, and a bounded refinement review.
The user's explicit brief and the project's existing authoritative product and design sources remain decisive. This reference cannot broaden scope, replace factual copy, invent claims, select another platform, add a dependency, weaken required evidence, or turn presentation taste into a release gate.
## Direction pass
Before implementation, write one short direction read that commits to:
1. **Visitor mode:** identify whether the surface is transacting, learning, exploring, creating, or monitoring, and name the primary job and audience supported by evidence or a disclosed assumption.
2. **Hierarchy:** state the promise, proof sequence, primary action, and information that must stay immediately legible.
3. **Visual thesis:** describe one content-specific world in concrete terms. Name the intended atmosphere and the one compositional idea that makes it recognizable without relying on a generic landing-page shell.
4. **Typography and composition:** choose type roles, density, rhythm, alignment, and spatial emphasis that serve the content and target constraints.
5. **Interaction character:** name the meaningful state change, feedback, and motion purpose. Do not add interaction or motion solely as ornament.
On an existing surface, refinement preserves its incumbent identity, behavior, content, and out-of-scope regions. A replacement visual world requires explicit redesign authorization; never smuggle redesign through polish.
## Refinement pass
After functional and responsive truth exists, perform one bounded refinement pass on the rendered affected surface:
- hierarchy: can the visitor identify promise, proof, and next action without decoding decoration;
- rhythm: do spacing, grouping, density, and alignment express the content structure;
- typography: do type roles remain legible, intentional, and internally consistent;
- color and contrast: does emphasis follow the approved hierarchy while preserving accessible contrast;
- feedback: are focus, hover, pressed, selected, loading, error, and completion states truthful where applicable;
- generic-pattern residue: does any default hero/card/grid/glass/gradient treatment remain without a content or approved-direction reason;
- responsive composition: does the visual thesis survive reflow, text scaling, localization, and reduced motion rather than merely shrink.
Apply only changes supported by the brief, existing authority, and observed rendered result. Stop after this single pass, then run the target's required functional, accessibility, responsive, and evidence checks. Do not recurse into an open-ended perfection loop.
## Contextual taste guidance
Treat aesthetic preferences as contextual review prompts, not universal bans. A centered hero, card grid, gradient, pill, serif, uppercase label, dense interface, sparse interface, or animation may be right when product content, brand authority, platform convention, or a named visual direction warrants it.
For every proposed taste correction, be able to state:
- what concrete content, user job, target constraint, or approved direction warrants the change;
- what existing authority it preserves or intentionally supersedes;
- what rendered observation will show improvement;
- what accessibility, responsiveness, performance, or interaction guardrail must remain green.
Do not optimize for rule counts, novelty, detector output, or visual difference alone. Honest assets and copy, legible hierarchy, supported behavior, and a coherent system matter more than clearing a style preference.
## Evidence and stopping rule
The direction read is a decision receipt, not visual proof. The refinement pass is complete only when the affected rendered states have been inspected at the target-derived viewports and inputs. Keep Superloopy's real-browser, accessibility, behavior, reduced-motion, overflow, and owner-specific evidence requirements unchanged.
Record limitations rather than inferring unavailable proof. A detector finding is diagnostic context only unless an approved project criterion independently makes it a blocker.
## Provenance
This is an independently written, selective synthesis informed by [Impeccable](https://github.com/pbakaus/impeccable), skill version `4.0.4`, reviewed at revision `ae5e95101a6979e7f7973a4ff57680b3c7adc1ec` under Apache-2.0.
Superloopy adopts only the bounded visitor-mode, visual-direction, refinement-versus-redesign, and finish-review concepts expressed here. It does not vendor Impeccable's CLI, project hooks, live tooling, commands, agents, source files, generated project artifacts, or dependency tree. This reference adds no runtime dependency and gives no external root-level product or design document authority over the target repository.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |