Skip to content

hashgraph-online/awesome-codex-plugins / plugins/beefiker/superloopy/skills/superloopy-frontend

superloopy-frontend

Verified

Use 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.

FileKindSize
SKILL.mdskill md14.2 KB
agents/openai.yamlconfig505 B
references/anti-slop.mdmarkdown6.4 KB
references/design-system.mdmarkdown7.8 KB
references/design/_INDEX.mdmarkdown9.6 KB
references/design/airbnb.mdmarkdown4.0 KB
references/design/airtable.mdmarkdown3.6 KB
references/design/amazon.mdmarkdown4.3 KB
references/design/apple.mdmarkdown3.8 KB
references/design/binance.mdmarkdown4.1 KB
references/design/bmw.mdmarkdown4.1 KB
references/design/brex.mdmarkdown4.0 KB
references/design/bugatti.mdmarkdown4.2 KB
references/design/cal.mdmarkdown3.7 KB
references/design/canva.mdmarkdown4.0 KB
references/design/claude.mdmarkdown3.5 KB
references/design/clickhouse.mdmarkdown4.0 KB
references/design/cohere.mdmarkdown3.6 KB
references/design/coinbase.mdmarkdown3.8 KB
references/design/cursor.mdmarkdown4.7 KB
references/design/datadog.mdmarkdown4.4 KB
references/design/discord.mdmarkdown4.0 KB
references/design/duolingo.mdmarkdown4.1 KB
references/design/elevenlabs.mdmarkdown3.6 KB
references/design/ferrari.mdmarkdown4.3 KB
references/design/figma.mdmarkdown3.7 KB
references/design/framer.mdmarkdown4.0 KB
references/design/gemini.mdmarkdown4.4 KB
references/design/github.mdmarkdown4.1 KB
references/design/gitlab.mdmarkdown4.1 KB
references/design/google.mdmarkdown4.0 KB
references/design/groq.mdmarkdown4.6 KB
references/design/hashicorp.mdmarkdown4.7 KB
references/design/huggingface.mdmarkdown4.3 KB
references/design/ibm.mdmarkdown4.7 KB
references/design/intercom.mdmarkdown3.7 KB
references/design/kraken.mdmarkdown3.7 KB
references/design/lamborghini.mdmarkdown4.2 KB
references/design/linear.mdmarkdown3.9 KB
references/design/loom.mdmarkdown4.1 KB
references/design/mastercard.mdmarkdown4.5 KB
references/design/mercedes.mdmarkdown4.1 KB
references/design/mercury.mdmarkdown3.9 KB
references/design/meta.mdmarkdown3.9 KB
references/design/microsoft.mdmarkdown4.5 KB
references/design/midjourney.mdmarkdown4.3 KB
references/design/minimax.mdmarkdown4.8 KB
references/design/mintlify.mdmarkdown4.5 KB
references/design/miro.mdmarkdown4.1 KB
references/design/mistral.mdmarkdown3.6 KB
references/design/mongodb.mdmarkdown4.4 KB
references/design/netflix.mdmarkdown4.0 KB
references/design/netlify.mdmarkdown4.4 KB
references/design/nike.mdmarkdown3.9 KB
references/design/notion.mdmarkdown3.9 KB
references/design/nvidia.mdmarkdown4.7 KB
references/design/nytimes.mdmarkdown5.1 KB
references/design/ollama.mdmarkdown4.1 KB
references/design/openai.mdmarkdown3.5 KB
references/design/perplexity.mdmarkdown3.7 KB
references/design/pinterest.mdmarkdown3.8 KB
references/design/plaid.mdmarkdown4.1 KB
references/design/playstation.mdmarkdown4.4 KB
references/design/porsche.mdmarkdown4.0 KB
references/design/posthog.mdmarkdown4.1 KB
references/design/railway.mdmarkdown4.7 KB
references/design/ramp.mdmarkdown3.8 KB
references/design/raycast.mdmarkdown4.6 KB
references/design/renault.mdmarkdown4.5 KB
references/design/replicate.mdmarkdown3.9 KB
references/design/resend.mdmarkdown4.7 KB
references/design/revolut.mdmarkdown3.6 KB
references/design/robinhood.mdmarkdown4.0 KB
references/design/rolex.mdmarkdown4.1 KB
references/design/runwayml.mdmarkdown3.9 KB
references/design/sanity.mdmarkdown4.6 KB
references/design/sentry.mdmarkdown3.8 KB
references/design/shopify.mdmarkdown4.0 KB
references/design/slack.mdmarkdown4.1 KB
references/design/spacex.mdmarkdown4.6 KB
references/design/spotify.mdmarkdown3.7 KB
references/design/starbucks.mdmarkdown4.8 KB
references/design/stripe.mdmarkdown4.0 KB
references/design/substack.mdmarkdown4.6 KB
references/design/supabase.mdmarkdown3.7 KB
references/design/superhuman.mdmarkdown4.2 KB
references/design/tesla.mdmarkdown4.5 KB
references/design/theverge.mdmarkdown4.4 KB
references/design/together.mdmarkdown4.1 KB
references/design/uber.mdmarkdown3.9 KB
references/design/vercel.mdmarkdown4.0 KB
references/design/warp.mdmarkdown4.3 KB
references/design/webflow.mdmarkdown4.0 KB
references/design/wired.mdmarkdown4.5 KB
references/design/wise.mdmarkdown3.8 KB
references/design/xai.mdmarkdown4.1 KB
references/design/zapier.mdmarkdown4.1 KB
references/desktop.mdmarkdown3.3 KB
references/hybrid.mdmarkdown3.1 KB
references/image-first.mdmarkdown5.3 KB
references/impeccable.mdmarkdown5.3 KB
references/layout.mdmarkdown6.3 KB
references/mobile.mdmarkdown3.2 KB
references/motion-core.mdmarkdown4.1 KB
references/motion.mdmarkdown9.9 KB
references/perfection.mdmarkdown8.9 KB
references/qt-qa.mdmarkdown8.0 KB
references/qt-quick.mdmarkdown10.3 KB
references/qt-widgets.mdmarkdown9.4 KB
references/qt.mdmarkdown11.1 KB
references/redesign.mdmarkdown6.9 KB
references/renderer.mdmarkdown2.9 KB
references/system-map.mdmarkdown7.9 KB
references/upstream-notice.mdmarkdown2.8 KB
references/ux.mdmarkdown22.2 KB
references/web.mdmarkdown15.7 KB
scripts/ds-compliance.mjsscript4.4 KB
scripts/evidence-root.mjsscript5.0 KB
scripts/visual-diff.mjsscript9.6 KB

references/design-system.md

View on GitHub
# Design-system contract and `DESIGN.md` schema

Use this reference when a changed visual claim needs new or updated app-defined semantics, or when an approved new/redesigned direction needs a coherent token contract. It does not expand a narrow nonvisual change into design work: that path may record `Design impact: unchanged` and `Visual evidence: not applicable` with behavioral, accessibility, and regression evidence.

## Choose the authority before the format

Inspect the repository's existing tokens, theme, style layer, component library, platform conventions, and representative UI before writing a design artifact. The project's current design source of truth remains authoritative.

- If `DESIGN.md` is already the established source, update it directly.
- If another source owns the system, update that source first. Use `DESIGN.md` only as a scoped mapping/receipt that links every changed app-defined semantic back to, and stays synchronized with, that owner.
- If the repository has no equivalent and a visual claim genuinely needs app-defined semantics, a scoped `DESIGN.md` may establish those affected decisions without requiring a repository-wide redesign.
- The absence of a formal design-system document is not a blocker and never means “no UI work.” Preserve working conventions and introduce only the minimum coherent contract required by the changed visual claim.

When material unknowns would change the visual direction or source of truth, ask the minimum necessary questions and batch independent unknowns. Otherwise document the evidence, assumption, and confidence and continue within the existing authority.

Loading this schema does not by itself select anti-slop, SEO, measured-quality, or a universal visual matrix. Anti-slop stays limited to its declared marketing/editorial or approved new-direction scope. SEO stays limited to the current crawlable public Web target or a distinct deployed public Web target in scope. Verify changed visual semantics across the target-derived browser/OS/input and breakpoint matrix, and create visual artifacts only for changed visual claims or interactions with a visible-state/layout consequence.

## Seven-section schema for a new or redesigned direction

Use the complete schema for an approved new or redesigned visual direction. For a visual delta inside an existing system, document only the affected sections and roles. Every new app-owned visual value traces to one authoritative token or an explicitly synchronized platform value; do not move runtime-owned native values into product tokens.

1. **Atmosphere / signature** — one paragraph naming how it *feels* (the one recognizable idea), not what it does. e.g. "weight-300 elegance, shadows tinted toward twilight" or "dark-native, content emerges from black, one signature heading weight". The signature is the compression key that makes every later token cohere.
2. **Color** — record each project-native color token, its resolved value or dynamic-value rule, and semantic role. Preserve the authoritative representation: CSS custom properties and CSS color syntax on Web, Android resources or Compose tokens, Apple asset catalogs or Swift values, Qt palette/QColor roles, or the repository's equivalent. Define only the roles the product needs, including state and dynamic light/dark/high-contrast variants where applicable. Pre-check contrast for the target's applicable text and non-text criteria and note adjusted values.
3. **Typography** — define a ramp per semantic role using the project's native units and APIs: CSS `rem`/`px`, Android `sp`, Apple points and text styles, Qt logical pixels or inherited platform fonts, or the repository equivalent. Record weight, line height, tracking, fallback, scaling behavior, and platform text-style ownership where applicable.
4. **Spacing** — preserve or establish a project-native base and named scale in the authoritative unit system (`rem`, logical px, dp, points, toolkit metrics, or equivalent). Values should follow that scale unless a platform metric, content constraint, or documented optical correction owns the exception; 4 px is an example, not a universal base.
5. **Components** — per component, define structure, semantic roles, content behavior, geometry, and every target-supported state and input path. Use the platform's native state and styling vocabulary rather than importing hover, radius, border, or CSS concepts where they do not apply.
6. **Motion** — define duration or spring behavior, continuity, interruption, and reduced-motion behavior. Prefer compositor-friendly or platform-native mechanisms appropriate to the actual renderer; do not impose Web-only transform/opacity/filter rules on native toolkits.
7. **Depth** — choose a coherent strategy supported by the platform and product, such as tonal hierarchy, material/elevation, borders, shadows, or native grouping. Do not mix unrelated systems without an explicit ownership reason.

## Authoring loopy-native token sets

Write your own token references — do not copy third-party design files. Two ways in:

- **From an existing UI**: inspect ground-truth values with the appropriate rendered-surface and repository tools rather than estimating. Keep the existing source authoritative; when a receipt is needed, map only the affected values into the schema and link them back to that source.
- **From a direction**: pick a committed aesthetic from the Design Read, then define exact tokens in the project's native representation. Record each color token, resolved value or dynamic rule, and role; add a short Do/Don't list that names the wrong instinct (for example, “Don't use a heavy display weight when the established voice is light”); and provide buildable examples using the target's real token names, units, and APIs rather than vague color or spacing language.

Keep the system lean. Add a token only when a component needs it, and add it to the authoritative design source first; synchronize any scoped `DESIGN.md` mapping in the same change.

## Web-oriented example token sets (loopy-native, illustrative)

Author your own only when a new or redesigned direction requires it. These examples intentionally use Web syntax to show shape and altitude; they are never defaults and their CSS variables, hex colors, pixel values, and interaction states must not be copied into a native target. Translate semantic roles into that target's authoritative tokens, units, platform states, and APIs.

### Calm SaaS (light, trustworthy)
- **Signature**: quiet confidence; generous whitespace, one restrained accent, content over chrome.
- **Color**: bg `#FBFCFD --bg`, fg `#0F1729 --fg` (near-black, not #000), primary `#2563EB --primary`, on-primary `#FFFFFF`, muted `#5B6472 --muted`, border `#E6E9EE --border`, card `#FFFFFF --card`. Accent used once per view.
- **Type**: stack Geist/General Sans. Display 48/600/1.05/-0.8px · H2 30/600/1.1 · body 16/400/1.6 · label 13/500/0.2px.
- **Spacing**: base 4; section padding `--space-20` (80px); card padding `--space-6`.
- **Depth**: borders-only + one soft tonal shadow `0 1px 2px rgba(15,23,41,.06), 0 8px 24px rgba(15,23,41,.06)`.
- **Motion**: 160-220ms ease-out; press scale 0.98.

### Editorial Dark (premium, content-faith)
- **Signature**: dark-native; text emerges from near-black; one signature heading weight; color used sparingly as punctuation.
- **Color**: bg `#0A0B0D --bg`, fg `#F2F3F5 --fg` (not pure white), surface `#141619 --surface`, primary `#E8533F --primary`, muted `#8A9099 --muted`, border `rgba(255,255,255,.08) --border`.
- **Type**: stack Cabinet Grotesk + a real serif for display. Display 72/510/1.0/-1.5px · H2 36/510/1.05 · body 17/400/1.65.
- **Spacing**: base 4; large rhythm (`--space-24` between sections); tight inside cards.
- **Depth**: tonal luminance stacking on dark surfaces; inset hairlines, no heavy drop shadows.
- **Motion**: 200-300ms; subtle reveal on scroll via IntersectionObserver; reduced-motion disables transforms.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall