Build and verify Accessible file upload for Mobile-first interface with Tailwind CSS v4 using a working semantic implementation, responsive RTL/LTR behavior, theme tokens, test plan and design verification.
14 stars
0 votes
0 copies
0 views
Added November 7, 2026
designgoperformancedocumentation
Works with
mcp
Security analysis
A92/100
mediumInstalls packages at runtime which could introduce malicious dependencies
Installs into .claude/skills of the current project.
Are you the author of Ztf Tw File Upload Mobile?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/realjustawall-ztf-tw-file-upload-mobile)
---
name: ztf-tw-file-upload-mobile
description: Build and verify Accessible file upload for Mobile-first interface with Tailwind CSS v4 using a working semantic implementation, responsive RTL/LTR behavior, theme tokens, test plan and design verification.
---
# Accessible file upload — Mobile-first interface (Tailwind CSS v4)
Use this skill when asked to implement, migrate, debug or review the corresponding real interface feature. You MUST implement actual code in the user's repository; do not merely paste advice. Do not request MCP.
## Task and plan
**Goal:** Accessible file upload. **Context:** Mobile-first interface. **Acceptance:** Native input remains available without drag drop. **Product emphasis:** Use touch-first hit regions, soft keyboard resilience and safe-area insets.
1. Inspect lockfile and existing design system. Verify that the correct framework and version is installed.
2. Read `../../frameworks/patterns/tw/file-upload/mobile.md` from this ZIP or, after skill-only installation, use the **embedded recipe below** without depending on external files.
3. Build the semantic structure and wire interactions. Use tokens before choosing visual styling.
4. Test and repair across the acceptance matrix; report actual evidence.
## Embedded implementation
```html
<form id="file-upload-tw-mobile-first-interface" action="/submit" method="post">
<fieldset class="grid gap-3 rounded-xl border p-5"><legend>Accessible file upload: Mobile-first interface</legend>
<label for="file-upload-tw-mobile-first-interface-email">Email</label>
<input id="file-upload-tw-mobile-first-interface-email" name="email" type="email" autocomplete="email" required class="w-full rounded-lg border p-3">
<label for="file-upload-tw-mobile-first-interface-note">Details</label>
<textarea id="file-upload-tw-mobile-first-interface-note" name="note" class="w-full rounded-lg border p-3"></textarea>
<button type="submit" class="rounded-lg bg-zinc-900 px-5 py-3 text-white">Submit</button>
</fieldset>
</form>
```
## Framework and integration rules
- `npm install tailwindcss @tailwindcss/vite` only if necessary and approved in the host project.
- Use top-level @theme to define utility-generating tokens and :root/[data-theme] for semantic alias variables.
- Use ms-*/me-*, text-start/text-end and dir-aware layout with rtl: variants.
- Associate every form control with a real label; native validation is preferable to custom alerts.
- sm 640, md 768, lg 1024, xl 1280, 2xl 1536 default; use @container variants for reusable components.
## Motion / color integration
Choose semantic colors with the original Perfect_AI palette engine and `COLOR-SCIENCE-ULTIMATE.md`. In strict monochrome contexts, do not add colorful gradients. For Anime.js, scope animation, honor reduced motion and dispose on route transitions. For Three.js, provide static fallback, performance caps and resize camera/renderer correctly. Do not animate layout-critical dimensions on every scroll frame.
## Definition of done
- [ ] Native input remains available without drag drop
- [ ] Narrow/wide layout, nested containers, RTL/LTR and 400% zoom pass.
- [ ] Accessible labels, focus, contrast, keyboard/touch, reduced motion pass.
- [ ] Build, tests and targeted browser interaction executed; no uncaught runtime errors.
- [ ] Limitations or unimplemented integration endpoints explicitly disclosed.
**Official reference:** https://tailwindcss.com/docs/. This is original integration documentation, not a vendor's copied component source.