adonis0123/tailwindcss-next-init
skills/tailwindcss-next-init/SKILL.md
Initialize Tailwind CSS v4 and Iconify for Next.js App Router projects with script-driven templates. Use when you need a fast setup or migration with consistent style-entry conventions.
$ install --global
skillsauthnpx skillsauth add adonis0123/adonis-skills tailwindcss-next-initInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 30, 2026, 6:20 PM57.8s11 files scanned
SKILL.md
- name:
- tailwindcss-next-init
- description:
- Initialize Tailwind CSS v4 and Iconify for Next.js App Router projects with script-driven templates. Use when you need a fast setup or migration with consistent style-entry conventions.
- author:
- adonis
Tailwindcss Next Init
概览
用本 skill 为目标仓库生成 Tailwind v4 初始化骨架，并给出可复制的依赖安装命令、布局导入检查结果、@source 与 @reference 使用建议。
优先运行脚本完成标准化输出，避免手工遗漏。
标准流程
- 识别目标项目结构。
- 检查
<project-root>/package.json是否存在。 - 检查
src/app/layout.tsx或app/layout.tsx是否存在。 - 检查
src/styles/与styles/目录状态。
- 先做 dry-run 预览。
- 运行：
python3 scripts/init_tailwind_v4.py --project-root /abs/path/to/project --dry-run
- 先确认将创建/覆盖的文件，再决定是否执行真实写入。
- 执行初始化写入。
- 默认最小模板：
python3 scripts/init_tailwind_v4.py --project-root /abs/path/to/project
- 贴近本仓库模板：
python3 scripts/init_tailwind_v4.py --project-root /abs/path/to/project --preset project-like
- 已有文件需覆盖时显式加
--force。
- 处理依赖安装。
- 按脚本输出的包管理器命令安装依赖（脚本只生成命令，不直接执行安装）。
- 默认图标策略是
--icons all，安装lucide/mdi/tabler三套图标集。
- 检查导入与扫描边界。
- 若脚本提示缺少全局样式导入，在目标
layout.tsx增加：
import "@/styles/globals.css";
import "@/styles/custom.css";
- 若类名来自
node_modules或扫描盲区，按提示在tailwind-core.css增加@source。
- 进行项目验证。
- 至少执行一次构建链路检查（如
pnpm typecheck、pnpm dev）。 - 确认页面样式生效、Iconify 图标类可渲染。
脚本参数契约
scripts/init_tailwind_v4.py 支持以下参数：
--project-root <path>：目标项目根目录（必填）--preset minimal|project-like：模板风格，默认minimal--icons all|lucide|none：图标策略，默认all--package-manager auto|pnpm|npm|yarn|bun：包管理器，默认auto--dry-run：仅预览，不写文件--force：覆盖已存在文件
资源说明
references/repo-tailwind-audit.md- 记录当前仓库 Tailwind 链路与历史演进，供“项目同款”策略参考。
references/tailwind-v4-best-practices.md- 记录 Tailwind v4 / Next.js / Iconify 的最佳实践与官方链接。
assets/templates/minimal/*- 通用最小模板，适合跨项目快速落地。模板源文件使用
.tpl后缀。
- 通用最小模板，适合跨项目快速落地。模板源文件使用
assets/templates/project-like/*- 贴近本仓库风格，包含 safe-area、reduced-motion、theme token bridge。模板源文件使用
.tpl后缀。 project-like模板中的@layer ... antd ...为仓库同款特化项；非 Ant Design 项目可按需移除该 layer。
- 贴近本仓库风格，包含 safe-area、reduced-motion、theme token bridge。模板源文件使用
模板后缀约定：
- 模板源：
*.tpl - 目标产物：
src/styles/*.css或styles/*.css（脚本自动判定） init_tailwind_v4.py严格读取.tpl，不会回退读取.css模板。
输出约束
执行本 skill 时，始终输出：
- 目标项目识别结果（layout、styles、package manager）
- 将写入/已写入文件列表
- 依赖安装命令（按所选包管理器）
@source与@reference的建议片段- 验证清单（至少 3 条可执行检查项）
Related Skills
adonis0123/code-plugin-architecture
tools
VerifiedTrustedCommunity
Use when the user's pain is "adding/removing one more X means editing N files" and X is a recurring variant kind: popup, banner, modal, ad slot, payment method, AI model/tool, form field type, connector, sub-site, command, menu item, agent, extension point, or data source. Use when they want to design, refactor, review, name, or explain a pluggable mechanism using registry, interface/trait contract, runtime core, and convention folders; mention pluginize, pluggable, plugin architecture, extension point, registry pattern, or extensibility. Use when explaining the first-principles rationale, DDD/SOLID/OCP mapping, or industry analogies behind that structure. Use for cross-stack mapping to VSCode contributes, Webpack/Vite plugins, Rust/Tauri connectors, Python entry_points, or cargo features. Skip one variant's internals/styles/hooks/copy/bugs, and skip register/registry meaning DI container, user signup, or package registry.
2SKILL.mdUpdated May 30, 2026
adonis0123/workflow-gate
development
VerifiedTrustedCommunity
Use BEFORE heavier workflow skills when route choice matters. Route creative work without a design doc/spec to Brainstorm; destructive or hard-to-reverse work to Discuss; unresolved decisions, Plan/Full fan-out, ship checks, unclear bugs, and fresh-eyes fix-then-re-review need this gate. Skip single-line read-only lookups, pure typo/formatting edits, trivial safe one-line fixes, and clearly safe named-skill requests. Outputs Route, Runtime skill, Fallback alias, and Execution path.
2SKILL.mdUpdated May 17, 2026
adonis0123/agentic-review-handoff
development
VerifiedTrustedCommunity
Cross-agent code review handoff and review-fix-re-review loop with persistent packet artifacts. Requires a git repo because packet addressing uses git rev-parse --show-toplevel. Use when the user asks for an independent, read-only second pair of eyes on a diff/branch/PR another agent or teammate implemented; asks to verify reviewer feedback before fixing; says a fix is done and wants scoped re-review; asks to continue the latest review packet; or asks for first-principles, DDD, high-cohesion/low-coupling review. Persists each loop under $repo_root/.review-handoff/active/ so agents can resume without copy-paste. Do NOT use for ordinary implementation, generic staged-change review, review-comment copy editing, non-git folders/zips/tarballs/temp dirs, or when the user names a different review skill.
2SKILL.mdUpdated May 16, 2026
adonis0123/discuss-before-plan
testing
VerifiedTrustedCommunity
Enforces 'decide then plan' discipline - the pre-planning decision gate. Use when the user asks for a plan or starts a change while key decisions are unresolved: architecture tradeoffs, data flow, public interfaces, unclear requirements, multi-module scope, or roughly 5+ files affected. Also triggers when the user explicitly wants to discuss, compare options, or review architecture before committing. Core job: reduce incorrect-execution cost by confirming decisions before producing executable plans.
2SKILL.mdUpdated Mar 27, 2026