voyager67/Pixelcraft / skills/effects-overuse-repair
effects-overuse-repair
VerifiedReduces gratuitous gradients, glows, blur, glassmorphism, shadows, borders, and decorative effects while preserving intentional brand expression.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
| agents/openai.yaml | config | 333 B |
SKILL.md
View on GitHub---
name: effects-overuse-repair
description: "Reduces gratuitous gradients, glows, blur, glassmorphism, shadows, borders, and decorative effects while preserving intentional brand expression."
license: CC-BY-NC-4.0
---
# Effects Overuse Repair
## Workflow
1. Inventory every effect and record where it appears and what role it claims to serve.
2. Test whether the effect adds hierarchy, depth, state feedback, grouping, or brand recognition.
3. Remove stacked effects that compete with content: colored glows, neon borders, multiple shadows, gradient text, background blobs, and blur behind ordinary controls.
4. Rebuild depth using surface steps, spacing, alignment, and restrained neutral elevation.
5. Keep a strong effect only where it marks a meaningful focal moment or real interaction state.
6. Check contrast, rendering performance, and dark/light theme consistency after changes.
## Output
Effect inventory, keep/remove decisions, tokens changed, visual checks, and any brand exceptions.
## Non-negotiable rules
- Judge the interface that exists, not assumptions about who or what produced it. AI authorship cannot be reliably inferred from generic visual patterns alone.
- Treat “AI slop” as a shorthand for observable quality problems: generic patterns, weak hierarchy, arbitrary decoration, vague copy, fabricated-looking content, inconsistent systems, or incomplete states.
- A pattern is a signal, not proof. Record evidence, confidence, and plausible benign explanations. Do not label a screen “AI-generated” as a factual finding.
- Preserve user goals, factual content, product behavior, existing brand assets, and working accessibility unless the evidence supports a change.
- Never invent metrics, reviews, customer logos, endorsements, product claims, features, integrations, or data to make a screen look more convincing.
- Inspect rendered output when tools allow it. If you only inspect source code or a screenshot, state that limitation.
- Make the smallest effective change first. Do not replace an existing coherent visual language just to make the result look different.
- Never expose secrets or private information found in a repository. If a secret is detected, do not repeat its value; report only the file and line, stop short of publishing it, and recommend revocation/rotation.
## Completion report
State the signals found, evidence and confidence, fixes made, files changed, checks actually run, and unresolved issues. Distinguish visual review, code review, and runtime testing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |