tailwind-reference-adapter
Use when the user provides a local TailwindUI or Tailwind Plus folder as visual reference material for a HeroUI React/Tailwind v4 implementation.
它会碰到什么
扫了多少1 个文本文件,2 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
Tailwind Reference Adapter
This skill treats TailwindUI v4.1 and Tailwind Plus content as licensed local reference-only material, not as plugin source.
Input Artifacts
- Local TailwindUI/Tailwind Plus root path
- Product, IA, interaction, visual, and HeroUI component contracts
10-visual-confirmation-plan.md
Output Artifact
docs/full-stack-development/requirements/<feature-slug>/04-visual/tailwind-reference-index.md
Required MCP Tool
inspect_tailwind_ui_referenceplan_tailwind_hero_ui_adoptionselect_hero_ui_components
Hard Stops
- Do not copy TailwindUI source code into the plugin or generated project.
- Do not bundle TailwindUI templates, assets, previews, Catalyst UI Kit source, or screenshots into the plugin.
- Do not use Catalyst, Headless UI, or TailwindUI primitives when HeroUI has an official component.
- Do not let TailwindUI override HeroUI Official Component First.
Pressure Test Responsibility
- Missing local reference path must block only TailwindUI enrichment, not the base HeroUI workflow.
- Direct source-copy requests must block.
- Catalyst primitive adoption must block when HeroUI has an official component.
- Tailwind v4 class usage must remain layout/supportive around HeroUI components.
Next Gate
visual-design-orchestratormay consume the reference index as inspiration for Pencil/Figma boards, while implementation still uses HeroUI official components.
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
它属于哪个仓库
星标★ 1,027
本站分层T1
该仓技能数1910
原文件路径
plugins/kevin592/codex-full-stack-workflow/skills/tailwind-reference-adapter/SKILL.md