Installs into .claude/skills of the current project.
Are you the author of Ztx3 Adaptive Responsive Zoom Reflow 400?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/realjustawall-ztx3-adaptive-responsive-zoom-reflow-400)
---
name: ztx3-adaptive-responsive-zoom-reflow-400
description: "Adaptive Responsive Engine 3.0 focused task: zoom reflow 400. Use when the requested frontend feature or review involves zoom reflow 400."
---
# Zoom Reflow 400
## Why and when
Test 1280 CSS viewport at 400% zoom equivalent 320px and no 2D scrolling for body. Work under the project's actual framework and browser constraints; do not assert this is implemented merely because a recipe exists.
## Implementation procedure
1. Inspect the current component and data flow; record constraints, user journey and existing integration.
2. Describe the mechanism: Test 1280 CSS viewport at 400% zoom equivalent 320px and no 2D scrolling for body. Choose the smallest API with well-defined ownership.
3. Create real code and testable state transitions; document dependencies, cleanup and errors.
4. Handle mobile and container width changes, reduced motion, RTL/LTR and keyboard where applicable.
5. Record a runnable example or a reproducible browser test in the target project.
## Specific pitfalls
Allow data tables to scroll independently. Version-pin relevant APIs and do not silently override old behavior.
## Parent engine acceptance protocol
Implement intrinsic layout, container-level rules and input modality handling; measure actual content and 3D fit at each breakpoint.
Test 320/360/390/768/1024/1440, 400% zoom, 600px height, touch, RTL and reduced motion.
## Definition of done
- [ ] Mechanism present in production code and demonstrable.
- [ ] Test at real narrow viewport and at least one wide viewport.
- [ ] No inaccessible keyboard/pointer-only workflows.
- [ ] Reduced-motion/static fallback as relevant.
- [ ] Source/license provenance included for reused upstream code.
- [ ] Error/empty/unsupported state is visible and usable.
- [ ] Report tests actually run and any unverified claim.
See `$ztx3-adaptive-responsive` for full handbook; do not use MCP.