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/redesign.md

View on GitHub
# Web Site Redesign Protocol

This is the Web-only protocol for redesigning a living site. Native and embedded-shell redesigns use the shared UX and claim-triggered visual/spatial overlays plus their platform and composition references; they do not inherit the browser, SEO, analytics, or real-browser rules below.

Greenfield rules applied to a living site are how redesigns go wrong: the model overwrites a working brand with its own taste, breaks applicable discovery contracts, and silently renames things analytics depends on. A redesign is evidence-first work — audit what exists, classify the mode, then change the least that satisfies the brief. Apply this protocol only when a visual Web redesign is actually in scope; a narrow nonvisual change does not require a redesign audit, design artifact, anti-slop pass, or visual capture.

## Mode detection (first action)

- **Greenfield** — no existing site, or a full restart is explicitly approved. Normal skill flow applies.
- **Preserve** — modernize without breaking the brand. Audit the existing authoritative design source first and evolve it gradually; do not move ownership into a new file.
- **Overhaul** — new visual language over existing content. Treat visuals as greenfield; preserve content and information architecture unless a separate IA change is actually in scope and explicitly approved from the recorded audit.

If the mode is a material unknown that cannot be resolved from the brief, repository, and current surface, ask whether to preserve the existing brand or start visually from scratch. Ask the minimum necessary questions and batch independent material unknowns instead of forcing a separate one-question round trip. Otherwise state the evidence-based mode, assumption, and confidence.

## Audit before touching (recorded as evidence)

Write `REDESIGN_AUDIT.md` under the evidence root before proposing changes, covering:

- **Brand tokens** — primary/accent colors, type stack, logo treatment, radii, and their authoritative repository owner. In preserve mode that existing owner remains the starting contract; `DESIGN.md` is used only when already established or as a synchronized scoped mapping/receipt.
- **Information architecture** — page tree, primary nav, key conversion paths.
- **Content blocks** — what exists, what is doing work, what is filler.
- **Patterns to preserve** — signature interactions, a recognizable hero, the copy voice.
- **Patterns to retire** — anti-slop tells, broken layouts, dead links, generic stock imagery, performance traps.
- **Visual-direction reading of the existing site** — record how far its visual language departs from the established system, the quantity and complexity of motion, and its information and spacing density. Ground each description in concrete evidence such as component variation, transition count and duration, content per viewport, and whitespace rhythm; this observed reading, not a greenfield preset, is the starting point.
- **Discovery baseline** — for the current crawlable public Web target, or a distinct deployed public Web target in scope, record ranking pages, meta titles, structured data, and share metadata. For authenticated, private, native-only, or embedded-only delivery without a distinct public deployment, record `SEO: N/A` with the concrete deployment reason; visual Web technology alone does not make SEO applicable.

Evidence availability is part of the audit. When analytics, Search Console, ranking history, or another source is unavailable, mark that field **unavailable and unverified, never guessed**. State whether the missing source blocks a named success criterion; otherwise continue with the observable repository/browser evidence and preserve the unknown contract conservatively.

## Preservation rules

- **Information architecture stays by default.** Page slugs, anchor IDs, primary nav labels, and conversion paths remain stable for discovery and muscle memory. Change broken IA only when information architecture is actually in scope, the audit identifies the concrete failure and downstream impact, and the user explicitly approves that IA change; a visual overhaul alone is not approval.
- **Extract brand colors before applying the anti-slop palette bans.** A brand that is already purple stays purple — that is the named override path, not a violation.
- **Copy voice is preserved** unless a rewrite is requested; visual modernization is not a content rewrite.
- **Existing accessibility wins never regress** — focus states, alt text, keyboard nav, contrast.
- **Analytics contracts hold** — do not rename tracked buttons, form field names, or section IDs without locating and updating the downstream contract.

## Never change silently (explicit user approval required)

URL structure and route slugs; primary nav labels; form field names; the brand logo or wordmark; legal, consent, and cookie copy. Treat field order separately: inspect analytics, autofill, validation, and task flow, then get approval when reordering changes one of those contracts.

## Modernization levers (apply in order, stop when the brief is satisfied)

1. **Typography refresh** — the biggest visual lift per unit of risk.
2. **Spacing and rhythm** — section padding, vertical rhythm.
3. **Color recalibration** — desaturate, unify neutrals, keep the brand accent.
4. **Motion layer** — evidence-backed micro-interactions that fit the preserved visual direction and existing components (`references/motion-core.md`, plus `references/motion.md` only for Web implementation).
5. **Hero and key-section recomposition** — restructure the top of the funnel.
6. **Full block replacement** — only when a block is unsalvageable.

## Decision tree

- IA, content, and SEO are sound → **targeted evolution** (levers 1–4): most of the value at a fraction of the risk.
- Visual debt is structural (for example incoherent or unowned visual semantics or broken supported-target adaptation) → **full visual redesign** with strict content and information-architecture preservation. Broken IA is a separate change: include it only when it is actually in scope and explicitly approved from the audit. The absence of a formal design-system document alone is not structural failure.
- The brand itself is changing → treat as **greenfield**.

For an actual redesign, completion preserves the project's authoritative design source and uses `DESIGN.md` only when it is established or a synchronized scoped mapping. Run anti-slop only for its declared marketing/editorial or approved new-visual-direction scope. Capture real-browser visual QA across the target-derived browser/OS/input and breakpoint matrix, exercise the affected and adjacent journeys, and retain the evidence record plus `REDESIGN_AUDIT.md` proving the before-state was read rather than guessed. SEO proof remains limited to the current crawlable public Web target or a distinct deployed public Web target in scope.

Selected redesign mechanisms were adapted under MIT from Taste Skill; see `references/upstream-notice.md`.
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