attention-management
Use when wrong elements get attention, important content is missed, or visual hierarchy is broken by animation
What this skill does
# Attention Management
Direct user focus correctly using Disney's principles.
## Problem Indicators
- Users miss important content
- Decorative elements steal focus
- CTAs don't stand out
- Users look at wrong things first
- Information hierarchy is unclear
## Diagnosis by Principle
### Staging
**Issue**: Multiple elements compete for attention
**Fix**: One thing moves at a time. Animate the most important element; keep others still.
### Timing
**Issue**: Everything animates at same speed
**Fix**: Primary content: faster animation. Secondary: slower or delayed. Speed implies importance.
### Exaggeration
**Issue**: Uniform motion across hierarchy
**Fix**: Important elements get more dramatic animation. Background elements get subtle motion.
### Anticipation
**Issue**: No buildup directs eyes
**Fix**: Use anticipation to guide attention. A small movement can draw eyes before the main action.
### Appeal
**Issue**: Wrong elements are visually interesting
**Fix**: Make important elements the most visually appealing. Animation should enhance hierarchy, not fight it.
## Quick Fixes
1. **One animation at a time** - Sequence, don't parallelize
2. **Stagger by importance** - Most important animates first
3. **Reduce decorative motion** - Background should be calm
4. **Increase CTA animation contrast** - Stands out from surroundings
5. **Use motion to guide reading order** - Top-to-bottom, left-to-right
## Troubleshooting Checklist
- [ ] What do users look at first? (Eye tracking or testing)
- [ ] Does animation sequence match importance hierarchy?
- [ ] Are decorative animations subtle enough?
- [ ] Does primary CTA have strongest motion?
- [ ] Count simultaneous animations (should be 1-2)
- [ ] Test: Hide animation—does hierarchy still work?
- [ ] Is motion guiding or distracting?
- [ ] Does stillness create emphasis where needed?
## Code Pattern
```css
/* Stagger by importance */
.hero-title {
animation: fadeInUp 400ms ease-out;
}
.hero-subtitle {
animation: fadeInUp 400ms ease-out 100ms backwards;
}
.hero-cta {
animation: fadeInUp 400ms ease-out 200ms backwards,
pulse 2s ease-in-out 1s infinite;
}
/* De-emphasize background */
.background-element {
animation: subtleDrift 20s linear infinite;
opacity: 0.3;
}
```
## Hierarchy Through Motion
| Priority | Animation Style |
|----------|----------------|
| Primary | Fast, prominent, potentially looping |
| Secondary | Medium speed, one-time |
| Tertiary | Slow, subtle, or static |
| Background | Very slow or no animation |
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.