smithery/dylantarre

technical-constraints

Use when animation is limited by browser support, platform capabilities, or technical requirements

Installation

$ npx skills add smithery/dylantarre --skill technical-constraints

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/dylantarre · top by installs.

npx skills add smithery/dylantarre

Browse all from smithery/dylantarre

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,673 B
  • docs SUMMARY.md 127 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Technical Constraints

Work within platform limitations while preserving animation intent.

Problem Indicators

  • Animation doesn't work on target browsers
  • Mobile devices can't handle animation
  • Framework limitations block implementation
  • File size constraints (Lottie, sprites)
  • Email/constrained environment needs

Diagnosis by Principle

Straight Ahead vs Pose-to-Pose

Issue: Runtime calculations too expensive Fix: Pre-calculate animations. Use CSS keyframes (pose-to-pose) over JS frame-by-frame (straight ahead).

Solid Drawing

Issue: Complex shapes cause rendering issues Fix: Simplify geometry. Use CSS shapes over SVG paths. Reduce polygon counts in 3D.

Timing

Issue: Consistent timing across devices Fix: Use relative units. Test on slowest target device. Consider requestAnimationFrame for JS.

Secondary Action

Issue: Budget only allows essential animation Fix: Prioritize primary actions. Cut secondary animations first when constrained.

Staging

Issue: Limited screen real estate Fix: Animate in place. Use transforms that don't affect layout. Consider reduce-motion as default on constrained platforms.

Quick Fixes

  1. Use CSS over JavaScript - Better browser optimization
  2. Progressive enhancement - Core function works without animation
  3. Feature detection - Check capability before animating
  4. Fallback states - Static alternative for unsupported browsers
  5. Lazy load animation libraries - Don't block initial render

Troubleshooting Checklist

  • List target browsers/devices
  • Check caniuse.com for feature support
  • Test on oldest supported browser
  • Measure animation impact on bundle size
  • Verify fallback experience is acceptable
  • Test with animation disabled
  • Check framework animation capabilities
  • Consider server-rendered alternatives (GIF, video)

Code Pattern

// Feature detection
const supportsAnimation =
  'animate' in Element.prototype &&
  CSS.supports('transform', 'translateZ(0)');

if (supportsAnimation) {
  element.animate(keyframes, options);
} else {
  element.classList.add('final-state');
}

// Progressive enhancement
@supports (animation: name) {
  .element {
    animation: fadeIn 200ms ease-out;
  }
}

Platform-Specific Tips

  • Email: Use GIF or static images
  • iOS Safari: Test -webkit- prefixes
  • Older Android: Reduce animation complexity
  • Low-end devices: Use prefers-reduced-motion as proxy