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/motion-core.md
View on GitHub# Cross-Platform Motion Contract
Load this reference only when a motion, transition, gesture-progress, animated continuity, or haptic-feedback claim changes. It defines temporal state truth and evidence without selecting a framework or visual character.
## Activation and proportionality
Add it when app-defined motion is added, removed, or changed; when a journey changes integration with a system or provider transition; when gesture progress, commit, cancellation, reduced-motion behavior, or an app-owned haptic changes; or when comfort, smoothness, continuity, or motion performance is claimed.
Do not add it for unchanged system-controlled animation, a static visual delta, or a behavior change with no temporal claim. Record `Motion impact: unchanged — <reason>` instead.
A narrow change records one compact row in the existing receipt. Expand the record only for custom gestures, frequent or interruptible motion, sensory feedback, broad reach, performance risk, or a high-consequence journey.
## Authority and purpose
Record the purpose, trigger, frequency, affected state, owner, supported input, preference behavior, and observable semantic result. The system or provider remains authoritative for its own transitions, gesture physics, timing, settings, and capability limits. Verify correct integration and avoid adding a second app-owned transition over the provider behavior.
Haptic feedback is optional and never the sole carrier of required information, error, or durable success. Record its semantic event, provider, hardware and settings availability, repeat suppression, synchronization, and a visual, textual, or audible alternative selected by the target contract.
## Temporal state contract
Name the before, intermediate, and after states and the durable owner that commits the result. Exercise repeated input, interruption, reversal, retargeting, and cancellation when the interaction or provider supports them. Mark an unsupported boundary `N/A` with a reason instead of inventing custom behavior.
- Repeated input does not duplicate commands or completion feedback.
- Interruption and retargeting settle on the newest durable truth rather than an animation callback.
- Reversal and cancellation restore a coherent model, surface, focus, selection, and accessible state until a real commit occurs.
- Focus, selection, and assistive-technology continuity remain logical throughout the state change.
- Reduced motion preserves the semantic outcome, status, focus, and spatial comprehension without requiring animation.
Numeric timing, easing, spring, and frame-rate targets come from the system/provider, the approved product motion source, and measured target behavior. Cross-platform equality is not a goal: equivalent semantic outcomes may use different provider-owned timing, physics, and feedback. A toolkit or property name does not prove acceleration, comfort, or performance.
## Evidence
A resting screenshot does not prove motion. Exercise the actual interaction in every applicable default, repeated, interrupted, reversed, retargeted, cancelled, and preference state. Build a representative target-and-state matrix from changed ownership, provider differences, reach, uncertainty, and consequence; do not demand a full device-by-state Cartesian product when attributable evidence establishes the same behavior. Record real-target interaction evidence for user-visible continuity; add a trace or measurement only for the performance claim it can support. Unit tests can prove state transitions and cleanup but cannot substitute for rendered timing, device integration, comfort, or haptic behavior.
Use existing owner-scoped interaction, visual, accessibility, target, adversarial-case, and contract-coverage records to bind the claim. An artifact label or non-empty note is not temporal or haptic proof: distinguish a provider call, observed physical output, measured behavior, and what remains unverified. Do not invent a motion or haptic artifact kind until its validator can verify structure, producer and provenance, target/build binding, and the claim-specific result; a new filename alone would create false confidence.
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: 198k | 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 |