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/image-first.md
View on GitHub# Visual Reference Discipline
Use this reference for an approved new/redesigned direction or another materially changed visual claim when a generated, captured, sketched, or supplied visual reference will influence implementation. Do not use this reference to expand a narrow nonvisual change into visual work.
Inspect the project's current design source and representative surface first; they remain authoritative. A generated image, captured inspiration, or layout sketch is a scoped reference, never permission to replace existing brand, component, token, content, platform, accessibility, or behavior contracts. Ask the minimum necessary questions only when material unknowns would change the result, and batch independent unknowns. This reference does not make anti-slop or SEO applicable; SEO remains limited to the current crawlable public Web target or a distinct deployed public Web target in scope.
## Authority modes
Classify the reference before using it:
- **Current-surface delta:** the existing product, implemented surface, and authoritative design source resolve the direction. Use the current state plus the changed visual claim as the target; do not generate replacement concepts merely to restyle a narrow delta.
- **Exploratory direction:** concepts may explore hierarchy, density, atmosphere, and composition, but remain explicitly non-authoritative and cannot direct production implementation or count as quality evidence.
- **Approved implementation reference:** a user, design owner, or established product source has approved the reference for a named target, state, and visual claim. Fidelity is an acceptance claim, subject to documented platform, content, accessibility, adaptive-layout, interaction, and performance changes.
When a material visual-direction unknown cannot be resolved from existing evidence, exploration may precede implementation approval. Do not mistake producing an image for approving it.
## Promotion to implementation authority
Before an exploratory or external reference becomes an approved implementation reference, reconcile and record the task, audience, authoritative content and states, semantic order, spatial owners and constraints, target platform and inputs, accessibility boundaries, and the project's existing design authority. If layout is material, also apply `references/layout.md` before committing production visual implementation.
Write a scoped implement-versus-ignore handoff:
- implement: approved hierarchy, composition, spacing relationships, media treatment, component emphasis, and state-specific visual intent;
- adapt explicitly: platform conventions, real content, localization, text scaling, accessibility, interaction, performance, and supported target behavior; and
- ignore: invented controls or data, unsupported claims, fake metrics, decorative artifacts, and details outside the approved visual claim.
Use `DESIGN.md` only when already established as the source or as a synchronized scoped mapping/receipt linked to the real owner; never create a competing source.
## Reference composition
Choose the artifact shape that makes the claim inspectable. A full-surface reference can preserve overall relationships; section or component references can add detail; a labelled state or responsive board can compare several individually legible panels. Do not crop away spatial context required by the claim, and request a clearer source when text, state, or geometry cannot be read reliably.
Generated-image text is not content or copy authority. Use approved product strings, localization keys, legal text, and content-owner decisions; otherwise label generated wording provisional and exclude it from fidelity scoring.
For an external capture, record the actual representative target-derived viewport or window, environment, state, content, date, source, and permission. For native or embedded work, a browser reference never becomes native-behavior proof.
## Implementation and evidence
Implement against the approved handoff rather than an undefined impression. Record every intentional deviation and its owner. Compare the production result with the applicable target across the target-derived matrix, then separately prove behavior, accessibility, content, and performance claims.
A generated image or screenshot is not proof of usability, accessibility, brand correctness, semantic order, or implementation correctness. Pixel similarity may locate differences but cannot decide whether task behavior, platform integration, reflow, localization, focus, or state truth is correct.
A pixel-exact claim is meaningful only after recording the approved reference, named target and build, rendering environment, state and content, fonts and assets, comparison method, and project-specific tolerance. Without those criteria, treat the artifact as visual direction, not exactness acceptance. Do not invent one universal tolerance; accessibility, platform, content, and adaptive deviations remain separately owned even when the scoped fidelity comparison passes.
## Degrade path
No image-generation tool is required. Use the approved current surface, user-provided mock, authorized capture, authored sketch, or a low-fidelity prototype suited to the uncertainty. Store a visual artifact under the active evidence root only when the changed visual claim and proportional visual-QA gate require it.
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 |