create-fullstack-scaffold 0.1.0

package/template/.claude/scripts/pre-tool-use-check.sh

@@ -0,0 +1,86 @@
+#!/bin/bash
+
+# Claude Code Pre-Tool-Use Check Script
+# 在执行 Bash 命令前检查是否包含禁止的操作
+
+set -e
+
+# 读取工具输入（从 stdin）
+TOOL_INPUT=$(cat)
+
+# 检查是否是 Bash 工具
+TOOL_NAME=$(echo "$TOOL_INPUT" | jq -r '.tool_name // empty')
+
+if [ "$TOOL_NAME" != "Bash" ]; then
+  # 不是 Bash 工具，直接通过
+  exit 0
+fi
+
+# 提取命令
+COMMAND=$(echo "$TOOL_INPUT" | jq -r '.tool_input.command // empty')
+
+if [ -z "$COMMAND" ]; then
+  # 没有命令，直接通过
+  exit 0
+fi
+
+# 检查是否包含 --no-verify 或 -n
+if echo "$COMMAND" | grep -qE 'git\s+commit.*(--no-verify|-n)'; then
+  echo ""
+  echo "❌ 检测到禁止的命令！"
+  echo ""
+  echo "🚫 禁止使用 'git commit --no-verify' 或 'git commit -n'"
+  echo ""
+  echo "原因："
+  echo "  • Pre-commit hooks 确保代码质量（格式检查、测试运行）"
+  echo "  • 跳过 hooks 会将低质量代码提交到仓库"
+  echo "  • 影响团队协作和代码审查"
+  echo ""
+  echo "正确做法："
+  echo "  ✅ git commit -m \"your message\""
+  echo ""
+  echo "如果 hooks 失败："
+  echo "  1. 运行测试失败 → 修复测试后再提交"
+  echo "  2. 格式检查失败 → 运行 npm run format 修复"
+  echo "  3. 验证器失败 → 修复验证问题"
+  echo ""
+  echo "📖 详细说明: .claude/rules/git-workflow.md"
+  echo ""
+  exit 1
+fi
+
+# 检查其他禁止的 git 操作
+# 先检查是否包含 --force-with-lease（允许）
+if echo "$COMMAND" | grep -qE 'git\s+push.*--force-with-lease'; then
+  # --force-with-lease 是安全的，允许通过
+  :
+elif echo "$COMMAND" | grep -qE 'git\s+push.*--force'; then
+  echo ""
+  echo "❌ 检测到禁止的命令！"
+  echo ""
+  echo "🚫 禁止使用 'git push --force'"
+  echo ""
+  echo "原因："
+  echo "  • 强制推送会覆盖远程仓库的历史"
+  echo "  • 可能导致其他开发者的工作丢失"
+  echo "  • 破坏团队协作"
+  echo ""
+  echo "替代方案："
+  echo "  ✅ git push --force-with-lease (更安全的强制推送)"
+  echo "  ✅ 先 pull 再 push"
+  echo ""
+  exit 1
+fi
+
+# 检查是否直接修改 .husky 目录
+if echo "$COMMAND" | grep -qE '(rm|mv|chmod|chown).*\.husky'; then
+  echo ""
+  echo "⚠️  警告：正在修改 .husky 目录"
+  echo ""
+  echo "这可能会影响 Git hooks 的正常运行。"
+  echo "请确保你知道自己在做什么。"
+  echo ""
+fi
+
+# 所有检查通过
+exit 0

package/template/.claude/scripts/test-pre-tool-use.sh

@@ -0,0 +1,73 @@
+#!/bin/bash
+
+# 测试 pre-tool-use-check.sh 脚本
+
+set -e
+
+SCRIPT_PATH=".claude/scripts/pre-tool-use-check.sh"
+
+echo "🧪 测试 pre-tool-use-check.sh 脚本"
+echo "=================================================="
+echo ""
+
+# 测试 1: 正常的 git commit 命令（应该通过）
+echo "📋 测试 1: 正常的 git commit 命令"
+echo "--------------------------------------------------"
+echo '{"tool_name": "Bash", "tool_input": {"command": "git commit -m \"test message\""}}' | bash "$SCRIPT_PATH"
+if [ $? -eq 0 ]; then
+  echo "✅ 测试通过：正常命令被允许"
+else
+  echo "❌ 测试失败：正常命令被拒绝"
+  exit 1
+fi
+echo ""
+
+# 测试 2: git commit --no-verify 命令（应该被拒绝）
+echo "📋 测试 2: git commit --no-verify 命令"
+echo "--------------------------------------------------"
+if echo '{"tool_name": "Bash", "tool_input": {"command": "git commit --no-verify -m \"test\""}}' | bash "$SCRIPT_PATH" 2>&1; then
+  echo "❌ 测试失败：--no-verify 命令被允许"
+  exit 1
+else
+  echo "✅ 测试通过：--no-verify 命令被拒绝"
+fi
+echo ""
+
+# 测试 3: git push --force 命令（应该被拒绝）
+echo "📋 测试 3: git push --force 命令"
+echo "--------------------------------------------------"
+if echo '{"tool_name": "Bash", "tool_input": {"command": "git push --force origin main"}}' | bash "$SCRIPT_PATH" 2>&1; then
+  echo "❌ 测试失败：--force 命令被允许"
+  exit 1
+else
+  echo "✅ 测试通过：--force 命令被拒绝"
+fi
+echo ""
+
+# 测试 4: 非 Bash 工具（应该通过）
+echo "📋 测试 4: 非 Bash 工具"
+echo "--------------------------------------------------"
+echo '{"tool_name": "Write", "tool_input": {"file_path": "/tmp/test.txt"}}' | bash "$SCRIPT_PATH"
+if [ $? -eq 0 ]; then
+  echo "✅ 测试通过：非 Bash 工具被允许"
+else
+  echo "❌ 测试失败：非 Bash 工具被拒绝"
+  exit 1
+fi
+echo ""
+
+# 测试 5: git push --force-with-lease（应该通过）
+echo "📋 测试 5: git push --force-with-lease 命令"
+echo "--------------------------------------------------"
+echo '{"tool_name": "Bash", "tool_input": {"command": "git push --force-with-lease origin main"}}' | bash "$SCRIPT_PATH"
+if [ $? -eq 0 ]; then
+  echo "✅ 测试通过：--force-with-lease 命令被允许"
+else
+  echo "❌ 测试失败：--force-with-lease 命令被拒绝"
+  exit 1
+fi
+echo ""
+
+echo "=================================================="
+echo "✅ 所有测试通过！"
+echo "=================================================="

package/template/.claude/scripts/validate-git-changes.sh

@@ -0,0 +1,38 @@
+#!/bin/bash
+
+# 增量校验脚本 - 只针对 git 修改的文件
+
+set -e
+
+echo "🚀 Running incremental validation for git staged files..."
+echo ""
+
+# 获取所有修改的 ts/tsx 文件（移除 template/ 前缀）
+STAGED_FILES=$(git diff --cached --name-only --diff-filter=ACM | grep -E '\.(ts|tsx)$' | sed 's|^template/||' || true)
+MODIFIED_FILES=$(git diff --name-only --diff-filter=ACM | grep -E '\.(ts|tsx)$' | sed 's|^template/||' || true)
+
+ALL_FILES="$STAGED_FILES $MODIFIED_FILES"
+
+if [ -z "$ALL_FILES" ]; then
+  echo "✅ No TypeScript files to validate"
+  exit 0
+fi
+
+echo "📁 Files to validate:"
+for file in $ALL_FILES; do
+  echo "  - $file"
+done
+echo ""
+
+# 运行 ESLint 只针对修改的文件
+echo "🔍 Running ESLint on modified files..."
+if [ -n "$STAGED_FILES" ]; then
+  npx eslint $STAGED_FILES --max-warnings=0 || true
+fi
+
+if [ -n "$MODIFIED_FILES" ]; then
+  npx eslint $MODIFIED_FILES --max-warnings=0 || true
+fi
+
+echo ""
+echo "✅ Incremental validation completed!"

package/template/.claude/settings.json

@@ -0,0 +1,32 @@
+{
+  "PreToolUse": [
+    {
+      "matcher": {
+        "tools": ["*"]
+      },
+      "hooks": [
+        {
+          "type": "command",
+          "command": "bash .claude/scripts/pre-tool-use-check.sh"
+        }
+      ]
+    }
+  ],
+  "PostToolUse": [
+    {
+      "matcher": {
+        "tools": ["Write", "Edit"]
+      },
+      "hooks": [
+        {
+          "type": "command",
+          "command": "bash .claude/scripts/post-edit-check.sh"
+        },
+        {
+          "type": "command",
+          "command": "npx tsx .claude/scripts/check-duplicate-types.ts"
+        }
+      ]
+    }
+  ]
+}

package/template/.claude/skills/writing-hookify-rules/SKILL.md

@@ -0,0 +1,408 @@
+---
+name: Writing Hookify Rules
+description: This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
+version: 0.1.0
+---
+
+# Writing Hookify Rules
+
+## Overview
+
+Hookify rules are markdown files with YAML frontmatter that define patterns to watch for and messages to show when those patterns match. Rules are stored in `.claude/hookify.{rule-name}.local.md` files.
+
+## Rule File Format
+
+### Basic Structure
+
+```markdown
+---
+name: rule-identifier
+enabled: true
+event: bash|file|stop|prompt|all
+pattern: regex-pattern-here
+---
+
+Message to show Claude when this rule triggers.
+Can include markdown formatting, warnings, suggestions, etc.
+```
+
+### Frontmatter Fields
+
+**name** (required): Unique identifier for the rule
+
+- Use kebab-case: `warn-dangerous-rm`, `block-console-log`
+- Be descriptive and action-oriented
+- Start with verb: warn, prevent, block, require, check
+
+**enabled** (required): Boolean to activate/deactivate
+
+- `true`: Rule is active
+- `false`: Rule is disabled (won't trigger)
+- Can toggle without deleting rule
+
+**event** (required): Which hook event to trigger on
+
+- `bash`: Bash tool commands
+- `file`: Edit, Write, MultiEdit tools
+- `stop`: When agent wants to stop
+- `prompt`: When user submits a prompt
+- `all`: All events
+
+**action** (optional): What to do when rule matches
+
+- `warn`: Show message but allow operation (default)
+- `block`: Prevent operation (PreToolUse) or stop session (Stop events)
+- If omitted, defaults to `warn`
+
+**pattern** (simple format): Regex pattern to match
+
+- Used for simple single-condition rules
+- Matches against command (bash) or new_text (file)
+- Python regex syntax
+
+**Example:**
+
+```yaml
+event: bash
+pattern: rm\s+-rf
+```
+
+### Advanced Format (Multiple Conditions)
+
+For complex rules with multiple conditions:
+
+```markdown
+---
+name: warn-env-file-edits
+enabled: true
+event: file
+conditions:
+  - field: file_path
+    operator: regex_match
+    pattern: \.env$
+  - field: new_text
+    operator: contains
+    pattern: API_KEY
+---
+
+You're adding an API key to a .env file. Ensure this file is in .gitignore!
+```
+
+**Condition fields:**
+
+- `field`: Which field to check
+  - For bash: `command`
+  - For file: `file_path`, `new_text`, `old_text`, `content`
+- `operator`: How to match
+  - `regex_match`: Regex pattern matching
+  - `contains`: Substring check
+  - `equals`: Exact match
+  - `not_contains`: Substring must NOT be present
+  - `starts_with`: Prefix check
+  - `ends_with`: Suffix check
+- `pattern`: Pattern or string to match
+
+**All conditions must match for rule to trigger.**
+
+## Message Body
+
+The markdown content after frontmatter is shown to Claude when the rule triggers.
+
+**Good messages:**
+
+- Explain what was detected
+- Explain why it's problematic
+- Suggest alternatives or best practices
+- Use formatting for clarity (bold, lists, etc.)
+
+**Example:**
+
+```markdown
+⚠️ **Console.log detected!**
+
+You're adding console.log to production code.
+
+**Why this matters:**
+
+- Debug logs shouldn't ship to production
+- Console.log can expose sensitive data
+- Impacts browser performance
+
+**Alternatives:**
+
+- Use a proper logging library
+- Remove before committing
+- Use conditional debug builds
+```
+
+## Event Type Guide
+
+### bash Events
+
+Match Bash command patterns:
+
+```markdown
+---
+event: bash
+pattern: sudo\s+|rm\s+-rf|chmod\s+777
+---
+
+Dangerous command detected!
+```
+
+**Common patterns:**
+
+- Dangerous commands: `rm\s+-rf`, `dd\s+if=`, `mkfs`
+- Privilege escalation: `sudo\s+`, `su\s+`
+- Permission issues: `chmod\s+777`, `chown\s+root`
+
+### file Events
+
+Match Edit/Write/MultiEdit operations:
+
+```markdown
+---
+event: file
+pattern: console\.log\(|eval\(|innerHTML\s*=
+---
+
+Potentially problematic code pattern detected!
+```
+
+**Match on different fields:**
+
+```markdown
+---
+event: file
+conditions:
+  - field: file_path
+    operator: regex_match
+    pattern: \.tsx?$
+  - field: new_text
+    operator: regex_match
+    pattern: console\.log\(
+---
+
+Console.log in TypeScript file!
+```
+
+**Common patterns:**
+
+- Debug code: `console\.log\(`, `debugger`, `print\(`
+- Security risks: `eval\(`, `innerHTML\s*=`, `dangerouslySetInnerHTML`
+- Sensitive files: `\.env$`, `credentials`, `\.pem$`
+- Generated files: `node_modules/`, `dist/`, `build/`
+
+### stop Events
+
+Match when agent wants to stop (completion checks):
+
+```markdown
+---
+event: stop
+pattern: .*
+---
+
+Before stopping, verify:
+
+- [ ] Tests were run
+- [ ] Build succeeded
+- [ ] Documentation updated
+```
+
+**Use for:**
+
+- Reminders about required steps
+- Completion checklists
+- Process enforcement
+
+### prompt Events
+
+Match user prompt content (advanced):
+
+```markdown
+---
+event: prompt
+conditions:
+  - field: user_prompt
+    operator: contains
+    pattern: deploy to production
+---
+
+Production deployment checklist:
+
+- [ ] Tests passing?
+- [ ] Reviewed by team?
+- [ ] Monitoring ready?
+```
+
+## Pattern Writing Tips
+
+### Regex Basics
+
+**Literal characters:** Most characters match themselves
+
+- `rm` matches "rm"
+- `console.log` matches "console.log"
+
+**Special characters need escaping:**
+
+- `.` (any char) → `\.` (literal dot)
+- `(` `)` → `\(` `\)` (literal parens)
+- `[` `]` → `\[` `\]` (literal brackets)
+
+**Common metacharacters:**
+
+- `\s` - whitespace (space, tab, newline)
+- `\d` - digit (0-9)
+- `\w` - word character (a-z, A-Z, 0-9, \_)
+- `.` - any character
+- `+` - one or more
+- `*` - zero or more
+- `?` - zero or one
+- `|` - OR
+
+**Examples:**
+
+```
+rm\s+-rf         Matches: rm -rf, rm  -rf
+console\.log\(   Matches: console.log(
+(eval|exec)\(    Matches: eval( or exec(
+chmod\s+777      Matches: chmod 777, chmod  777
+API_KEY\s*=      Matches: API_KEY=, API_KEY =
+```
+
+### Testing Patterns
+
+Test regex patterns before using:
+
+```bash
+python3 -c "import re; print(re.search(r'your_pattern', 'test text'))"
+```
+
+Or use online regex testers (regex101.com with Python flavor).
+
+### Common Pitfalls
+
+**Too broad:**
+
+```yaml
+pattern: log # Matches "log", "login", "dialog", "catalog"
+```
+
+Better: `console\.log\(|logger\.`
+
+**Too specific:**
+
+```yaml
+pattern: rm -rf /tmp # Only matches exact path
+```
+
+Better: `rm\s+-rf`
+
+**Escaping issues:**
+
+- YAML quoted strings: `"pattern"` requires double backslashes `\\s`
+- YAML unquoted: `pattern: \s` works as-is
+- **Recommendation**: Use unquoted patterns in YAML
+
+## File Organization
+
+**Location:** All rules in `.claude/` directory
+**Naming:** `.claude/hookify.{descriptive-name}.local.md`
+**Gitignore:** Add `.claude/*.local.md` to `.gitignore`
+
+**Good names:**
+
+- `hookify.dangerous-rm.local.md`
+- `hookify.console-log.local.md`
+- `hookify.require-tests.local.md`
+- `hookify.sensitive-files.local.md`
+
+**Bad names:**
+
+- `hookify.rule1.local.md` (not descriptive)
+- `hookify.md` (missing .local)
+- `danger.local.md` (missing hookify prefix)
+
+## Workflow
+
+### Creating a Rule
+
+1. Identify unwanted behavior
+2. Determine which tool is involved (Bash, Edit, etc.)
+3. Choose event type (bash, file, stop, etc.)
+4. Write regex pattern
+5. Create `.claude/hookify.{name}.local.md` file in project root
+6. Test immediately - rules are read dynamically on next tool use
+
+### Refining a Rule
+
+1. Edit the `.local.md` file
+2. Adjust pattern or message
+3. Test immediately - changes take effect on next tool use
+
+### Disabling a Rule
+
+**Temporary:** Set `enabled: false` in frontmatter
+**Permanent:** Delete the `.local.md` file
+
+## Examples
+
+See `${CLAUDE_PLUGIN_ROOT}/examples/` for complete examples:
+
+- `dangerous-rm.local.md` - Block dangerous rm commands
+- `console-log-warning.local.md` - Warn about console.log
+- `sensitive-files-warning.local.md` - Warn about editing .env files
+
+## Quick Reference
+
+**Minimum viable rule:**
+
+```markdown
+---
+name: my-rule
+enabled: true
+event: bash
+pattern: dangerous_command
+---
+
+Warning message here
+```
+
+**Rule with conditions:**
+
+```markdown
+---
+name: my-rule
+enabled: true
+event: file
+conditions:
+  - field: file_path
+    operator: regex_match
+    pattern: \.ts$
+  - field: new_text
+    operator: contains
+    pattern: any
+---
+
+Warning message
+```
+
+**Event types:**
+
+- `bash` - Bash commands
+- `file` - File edits
+- `stop` - Completion checks
+- `prompt` - User input
+- `all` - All events
+
+**Field options:**
+
+- Bash: `command`
+- File: `file_path`, `new_text`, `old_text`, `content`
+- Prompt: `user_prompt`
+
+**Operators:**
+
+- `regex_match`, `contains`, `equals`, `not_contains`, `starts_with`, `ends_with`

package/template/.dev-context-compact.md

@@ -0,0 +1,54 @@
+# 项目紧凑上下文（用于 AI 会话）
+
+## 架构概览
+
+- **模块数量**: 10
+- **中间件**: 7
+- **数据库表**: 3
+- **API 端点**: 74
+
+## 模块列表
+
+- **admin**: 8 路由, 8 服务
+- **captcha**: 4 路由, 4 服务
+- **chat**: 5 路由, 5 服务
+- **content**: 4 路由, 4 服务
+- **dispute**: 4 路由, 4 服务
+- **notifications**: 5 路由, 5 服务
+- **order**: 4 路由, 4 服务
+- **permission**: 4 路由, 4 服务
+- **ticket**: 4 路由, 4 服务
+- **todos**: 4 路由, 4 服务
+
+## 关键文件路径
+
+### 服务端
+
+```
+src/server/
+├── app.ts                 # 应用入口
+├── middleware/            # 中间件
+├── module-{feature}/      # 业务模块
+│   ├── routes/            # API 路由
+│   ├── services/          # 业务逻辑
+│   └── __tests__/         # 测试
+└── db/schema/             # 数据库表定义
+```
+
+### 客户端
+
+```
+src/client/
+├── App.tsx                # 应用入口
+├── components/            # UI 组件
+├── stores/                # Zustand 状态
+└── services/              # API 客户端
+```
+
+### 共享类型
+
+```
+src/shared/
+├── core/                  # 框架层（不可修改）
+└── modules/               # 业务层 Schema
+```