weapp-tailwindcss is a build toolchain that generates and adapts Tailwind CSS for web pages, mini-programs, app webviews, React Native, and Lynx applications. It is for developers who want one Tailwind-based styling workflow to produce CSS and styles for multiple platforms.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add sonofmagic/weapp-tailwindcss --skill weapp-tailwindcss-runtimegit clone --depth 1 https://github.com/sonofmagic/weapp-tailwindcssWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sonofmagic/weapp-tailwindcss/weapp-tailwindcss-runtime)<a href="https://agentmods.dev/skills/sonofmagic/weapp-tailwindcss/weapp-tailwindcss-runtime"><img src="https://agentmods.dev/badge/skills/sonofmagic/weapp-tailwindcss/weapp-tailwindcss-runtime/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sonofmagic/weapp-tailwindcss/weapp-tailwindcss-runtime"><img src="https://agentmods.dev/badge/skills/sonofmagic/weapp-tailwindcss/weapp-tailwindcss-runtime.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00118 | $0.00590 |
| Opus 5.5 | $0.00047 | $0.00236 |
| Sonnet 5.5 | $0.00024 | $0.00118 |
| Haiku 4.5 | $0.00012 | $0.00059 |
Grade A, and why
weapp-tailwindcss-runtime scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- weapp-tailwindcss-runtime — 100% identical, 0 lines differ
What it actually says
weapp-tailwindcss runtime
使用项目提供的运行时封装保持 class 合并、转义和构建期精确候选一致。
工作流
- 识别 class 来源：静态模板、完整字面量条件、组件外部覆盖、第三方透传或真正的运行时输入。
- 读取 references/runtime-guide.md，按任务选择最小包和 API。
- 读取各包当前 manifest 与 exports，避免把
merge/slim、merge/lite、UI CSS 或插件入口当成主入口。 - 优先使用完整 class 字面量或枚举；不要拼接
bg-${color}-500这类半截 token。 - 普通组件覆盖使用
@weapp-tailwindcss/merge；单槽 variants 使用@weapp-tailwindcss/cva；多槽 recipes 使用@weapp-tailwindcss/variants。 - 自定义封装名时检查构建期可识别标识符；需要原样透传时使用
weappTwIgnore，不要扩大全局忽略。 - 自定义 runtime factory、escape/unescape 或 rpx transformer 时保持纯函数边界，并验证缓存淘汰前后的等价输出。
关键约束
- 运行时包已经封装小程序 escape/unescape；不要先手动 escape 再交给 merge/cva/variants。
clsx只负责组合，不解决 Tailwind 冲突；需要“调用方最后覆盖”时使用 merge。- 只有会改变冲突分类的自定义 Tailwind token 才同步 merge 配置，并补冲突用例。
weappTwIgnore是精确局部保护，不是让未扫描动态 class 自动生成 CSS 的工具。- 构建期仍遵循
classNameSet精确命中，运行时封装不能补生成缺失的候选。
输出要求
输出包选择理由、可复制实现、构建期配套配置、类型约束，以及冲突、转义和生产压缩验证用例。
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 31 lines · 118 tokens per session scan A 754afa3aa2b9
weapp-tailwindcss-runtime is a skill published in the GitHub repository sonofmagic/weapp-tailwindcss (1,865 stars, last pushed 6d ago), licensed MIT. It adds 118 tokens to every session and 590 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
nuxt-ui
Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.
uniwind
Uniwind — Tailwind CSS v4 styling for React Native. Use when adding, building, or debugging components in a React Native project that uses Uniwind classNames. Covers setup, Metro config, global.css, theming, className props, accent- color props, platform/data/state/responsive variants, CSS variables, custom utilities…
weapp-vite-best-practices
An engineering guide for building small-program projects with weapp-vite, a Vite-based toolchain for compiling mini-apps for several platforms.
Cypress v14 Component Testing
Component testing patterns with Cypress v14 including React, Vue, and Angular component mounting, custom mount commands, interaction testing, visual snapshots, and integration with Vite and Webpack bundlers.
weapp-devtools-e2e-best-practices
A testing workflow for WeChat mini-programs using WeChat DevTools and a headless runtime. WeChat DevTools is the official development environment; end-to-end tests check a feature through its real user flow.
native-to-weapp-vite-wevu-migration
A step-by-step guide for gradually moving native WeChat, Alipay, or Douyin mini-programs to weapp-vite, with an optional later move to Vue single-file components.