メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| 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. |
| metadata | {"author":"adonis"} |
用本 skill 为目标仓库生成 Tailwind v4 初始化骨架，并给出可复制的依赖安装命令、布局导入检查结果、@source 与 @reference 使用建议。
优先运行脚本完成标准化输出，避免手工遗漏。
<project-root>/package.json 是否存在。src/app/layout.tsx 或 app/layout.tsx 是否存在。src/styles/ 与 styles/ 目录状态。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）。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
references/tailwind-v4-best-practices.md
assets/templates/minimal/*
.tpl 后缀。assets/templates/project-like/*
.tpl 后缀。project-like 模板中的 @layer ... antd ... 为仓库同款特化项；非 Ant Design 项目可按需移除该 layer。模板后缀约定：
*.tplsrc/styles/*.css 或 styles/*.css（脚本自动判定）init_tailwind_v4.py 严格读取 .tpl，不会回退读取 .css 模板。执行本 skill 时，始终输出：
@source 与 @reference 的建议片段Generate emoji-prefixed Conventional Commit messages and focused local commits from staged changes or a single clear unstaged change.
Commit a focused local change set with an emoji Conventional Commit message, safely stage a clear unstaged scope when needed, then push the current branch to its remote. Use when the user asks to "commit and push", "commit push", "submit and push", "push my committed change", or wants a local commit finalized on the remote. Do not create pull requests, merge requests, releases, tags, rebases, or deployment changes.
Use this skill when the user wants to decide, set, write, or use a durable coding-agent goal or /goal prompt that keeps Codex, Claude Code, or another agent working until a verifiable done condition is met. It gates autonomy, handles runtime differences, and writes copy-ready goal contracts with outcome, verification, constraints, write boundaries, iteration policy, completion evidence, and pause/ask conditions. Trigger on requests like 'should I set a goal?', 'set up a durable goal', 'give me a /goal prompt', 'turn this vague app idea into a goal', 'keep refactoring until tests pass', 'I am stepping away, have the agent finish this', migrations, refactors, ports, spec implementations, eval loops, backlog cleanup, or multi-checkpoint work. Do not use for single quick edits, running tests once, OKR/scrum goal questions, recurring reminders, or token-budget settings.
Create safe Git feature or hotfix branches with concise names. Use this whenever the user asks to create a branch, start work on a new feature or fix, wants a `feat/...` or `hotfix/...` branch name, asks for a short branch slug from a task description, or wants help before beginning local Git work. Default to recommending the branch name and command first, then create only after user confirmation. Do not push, commit, rebase, or create PRs.
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.
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.