`tailwind_config_gen.py` 覆盖了现有的 Tailwind 配置文件,而 `sync-brand-to-tokens.cjs` 会在现有的 token 来源旁边写入第二个 token 来源(或者发生崩溃)。

1. ui-styling/scripts/tailwind_config_gen.py silently overwrites tailwind.config.ts

mkdir demo && cd demo
printf '// existing project config\nexport default { theme: { extend: { colors: { progress: "var(--progress)" } } } }\n' > tailwind.config.ts
python3 <skills>/ui-styling/scripts/tailwind_config_gen.py --colors brand:blue
# Configuration written to …/demo/tailwind.config.ts  (exit 0)
grep -c progress tailwind.config.ts  # 1 before, 0 after

The command is the example from ui-styling/SKILL.md L228. TypeScript is the default (L389), _default_output_path() resolves to tailwind.config.ts in the working directory (L47), and write_config() calls write_text (L277) with no existence check — no prompt, no backup, no warning. The existing test_write_config* tests only write into an empty tmp_path, so nothing covers this case.