Installs into .claude/skills of the current project.
Are you the author of Ztu Design Tokens Css Tailwind Bootstrap Output?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/realjustawall-ztu-design-tokens-css-tailwind-bootstrap-output)
---
name: ztu-design-tokens-css-tailwind-bootstrap-output
description: "Implement and verify the css tailwind bootstrap output capability inside DTCG Design Tokens Standard Engine with local evidence and strict fallback."
---
# DTCG Design Tokens Standard Engine: Css Tailwind Bootstrap Output — Perfect_AI VERIFIED ULTIMATE
## Mission / ماموریت
Implement and verify the css tailwind bootstrap output capability inside DTCG Design Tokens Standard Engine with local evidence and strict fallback.
## When to invoke
Invoke whenever the task includes css tailwind bootstrap output, or the parent skill `design-tokens` selects this submodule.
## Exact workflow
1. Read parent `ztu-design-tokens` and `references/design-tokens-implementation.md`.
2. Locate the related component and dependency versions.
3. Construct the smallest deterministic fixture addressing css tailwind bootstrap output.
4. Implement using the parent module tool and preserve unrelated behavior.
5. Run unit, browser and/or hardware evidence appropriate to this feature.
6. Report unsatisfied hardware/browser constraints as **unverified** rather than pass.
7. Attach actual before/after results and test commands.
## Acceptance criteria
- css tailwind bootstrap output implemented with real code and a reproducible example.
- Failure path and mobile/reduced-motion path specified.
- At least one objective assertion passes.
- Existing files remain unchanged unless editing is explicitly approved.
## Evidence contract
Write a machine-readable report with `status` = `pass|fail|unverified`, measured values, runtime/browser/device, changed files, exact command, artifacts and rationale. **Never** claim hardware/browser success from unit tests alone. Preserve original project files unless user explicitly authorizes edits. Avoid MCP; use local CLI and files.
## Compatibility and precautions
Read the installed dependency versions and project conventions first; prefer official APIs. Respect reduced motion, keyboard navigation, privacy, Persian RTL and low-power devices. Do not let two animation engines own the same DOM property. Test fallback modes and undo changes when the same acceptance check regresses.
## Working files
- `../ztu-design-tokens/SKILL.md`
- `../../references/design-tokens-implementation.md`
## Official references
- https://www.w3.org/community/reports/design-tokens/CG-FINAL-format-20251028/