[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HQ4VSZRNHWXN6HR1D2DBWD":3,"skill-same:01M6HQ4VSZRNHWXN6HR1D2DBWD":100},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":80,"commitSha":81,"skillDirectory":82,"forksCount":83,"repositoryHtmlUrl":84,"repositoryHomepageUrl":6,"ownerHtmlUrl":85,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":86,"install":87,"resources":99},"01M6HQ4VSZRNHWXN6HR1D2DBWD","godot-sync-static-positions",null,"当 Godot 节点的位置同时在 .tscn（编辑器）和 _ready()（代码）中设置时使用， 这会导致实际运行时位置产生混乱。检测与编辑器值冲突的静态位置赋值。 同步到单一事实来源，使编辑器预览与游戏行为一致（所见即所得）。","welflau\u002Fai-dev-system","welflau","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7010385?v=4","01M6HPTDGF18RFY07M229P8CTM","01M6HPTDMRMZCJPYBFEA9XVVYT",3,"MIT","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgodot-dev\u002Fclaude\u002Fskills\u002Fgodot-sync-static-positions\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"static","sync","godot sync static positions","godot","positions","superpowers","true","文件","wysiwyg","preview","clean","files","design","ready","fix","README","tool","game","development","windows","linux","2026-11-10 10:12:30",false,"---\nname: godot-sync-static-positions\nversion: 3.0.0\ndisplayName: 同步静态位置\ndescription: >\n  当 Godot 节点的位置同时在 .tscn（编辑器）和 _ready()（代码）中设置时使用，\n  这会导致实际运行时位置产生混乱。检测与编辑器值冲突的静态位置赋值。\n  同步到单一事实来源，使编辑器预览与游戏行为一致（所见即所得）。\nauthor: Asreonn\nlicense: MIT\ncategory: game-development\ntype: tool\ndifficulty: beginner\naudience: [developers]\nkeywords:\n  - godot\n  - position-sync\n  - editor-preview\n  - wysiwyg\n  - static-positions\n  - node-position\n  - level-design\n  - tscn-files\nplatforms: [macos, linux, windows]\nrepository: https:\u002F\u002Fgithub.com\u002Fasreonn\u002Fgodot-superpowers\nhomepage: https:\u002F\u002Fgithub.com\u002Fasreonn\u002Fgodot-superpowers#readme\n\npermissions:\n  filesystem:\n    read: [\".gd\", \".tscn\"]\n    write: [\".gd\", \".tscn\"]\n  git: true\n\nbehavior:\n  auto_rollback: true\n  validation: true\n  git_commits: true\n\noutputs: \"同步后的位置、更新的 .tscn 或 .gd 文件、清晰的归属文档、git 提交\"\nrequirements: \"Git 仓库、Godot 4.x\"\nexecution: \"自动检测，用户审批同步策略\"\nintegration: \"godot-fix-positions 编排器的一部分，与 godot-clean-conflicts 协作\"\n---\n\n# 同步静态位置\n\n## 核心原则\n\n**所见即所得。** 对于静态位置，编辑器预览应与游戏行为一致。\n\n## 此技能的功能\n\n查找如下冲突：\n```gdscript\n# enemy.gd\nfunc _ready():\n    position = Vector2(500, 300)  # 代码设置在这里\n\n# enemy.tscn\n[node name=\"Enemy\" type=\"CharacterBody2D\"]\nposition = Vector2(100, 100)  # 编辑器设置在这里\n\n# 结果：令人困惑！编辑器显示错误的位置\n```\n\n解决为：\n```gdscript\n# enemy.gd\nfunc _ready():\n    # 位置已在场景文件中设置，以便在编辑器中可见\n    pass\n\n# enemy.tscn\n[node name=\"Enemy\" type=\"CharacterBody2D\"]\nposition = Vector2(500, 300)  # 更新为匹配预期位置\n\n# 结果：编辑器预览与游戏一致\n```\n\n## 检测模式\n\n识别以下情况：\n\n### _ready() 中的直接位置赋值\n```gdscript\nfunc _ready():\n    position = Vector2(100, 150)  # 静态冲突\n    global_position = Vector2(500, 300)  # 静态冲突\n```\n\n### Node 属性赋值\n```gdscript\nfunc _ready():\n    $Sprite.position = Vector2(10, 20)  # 子节点位置冲突\n    get_node(\"CollisionShape2D\").position = Vector2(0, 0)\n```\n\n### 多属性冲突\n```gdscript\nfunc _ready():\n    position = Vector2(100, 100)\n    rotation = deg_to_rad(45)  # 也是位置相关的\n    scale = Vector2(2, 2)\n```\n\n## 何时使用\n\n### 关卡设计工作流\n在编辑器中放置物体，但代码覆盖了位置。\n\n### 调试位置问题\n\"为什么这个节点在错误的位置？\"\n\n### 维护所见即所得\n希望编辑器预览是准确的。\n\n### 为协作做准备\n关卡设计师需要准确的编辑器预览。\n\n## 流程\n\n1. **扫描** - 查找 _ready() 中的位置赋值\n2. **对比** - 与 .tscn 值进行比较\n3. **检测冲突** - 识别静态冲突（非动态）\n4. **选择策略** - 用户选择同步方向\n5. **应用** - 更新 .tscn 或 .gd 文件\n6. **记录** - 添加注释说明归属关系\n7. **验证** - 确保编辑器\u002F游戏之间的位置一致\n8. **提交** - 每次冲突解决后进行 git 提交\n\n## 同步策略\n\n### 策略 1：编辑器优先（推荐用于静态位置）\n将代码中的值移到 .tscn，从代码中移除。\n\n**何时使用：**\n- 位置应在编辑器中可见\n- 设计师控制的布局\n- 静态物体定位\n\n**示例：**\n```gdscript\n# 修改前\nfunc _ready():\n    position = Vector2(500, 300)\n\n# 修改后\nfunc _ready():\n    # 位置已在场景文件中设置\n    pass\n```\n```ini\n# enemy.tscn 已更新\nposition = Vector2(500, 300)\n```\n\n### 策略 2：代码优先（保持动态）\n移除编辑器中的值，保留代码赋值。\n\n**何时使用：**\n- 位置在运行时计算\n- 依赖于其他节点\u002F数据\n- 程序化定位\n\n**示例：**\n```gdscript\n# 修改前\nfunc _ready():\n    position = spawn_point.position + offset  # 动态的！\n\n# 修改后\nfunc _ready():\n    # 位置是动态计算的（参见 spawn_point）\n    position = spawn_point.position + offset\n```\n```ini\n# enemy.tscn - 位置已移除或设置为 (0,0) 作为占位符\n```\n\n### 策略 3：记录意图\n保留两者，但添加清晰的注释。\n\n**何时使用：**\n- 编辑器中的初始位置，被有意覆盖\n- 默认位置带有代码覆盖\n- 两个值都有意义\n\n**示例：**\n```gdscript\n# 修改前\nfunc _ready():\n    position = start_position\n\n# 修改后\nfunc _ready():\n    # 编辑器位置是默认出生点，被覆盖为 start_position\n    position = start_position\n```\n\n## 智能检测\n\n**识别静态冲突（修复这些）：**\n```gdscript\nfunc _ready():\n    position = Vector2(100, 100)  # 字面量常数 - 静态\n    position = Vector2(CONSTANT_X, CONSTANT_Y)  # 常量 - 静态\n    $Child.position = Vector2(10, 10)  # 字面量 - 静态\n```\n\n**跳过动态定位（属于有意设计）：**\n```gdscript\nfunc _ready():\n    position = player.position  # 变量引用 - 动态\n    position = get_spawn_point()  # 函数调用 - 动态\n    if some_condition:\n        position = Vector2(100, 100)  # 条件性 - 动态\n\nfunc _process(delta):\n    position = target  # 每帧 - 动态（跳过）\n```\n\n**关键区别：静态 = 每次都相同，动态 = 运行时变化**\n\n## 生成内容\n\n- 同步后的 .tscn 文件，包含正确的位置\n- 更新或清理后的代码文件\n- 记录位置归属的注释\n- 确保同步成功的验证\n- 每次同步操作的 git 提交\n\n## 常见冲突\n\n### 冲突 1：出生位置\n```gdscript\n# 修改前：代码设置 (500, 300)，编辑器设置 (0, 0)\nfunc _ready():\n    position = Vector2(500, 300)\n\n# 修改后：编辑器已更新，代码已移除\n# enemy.tscn: position = Vector2(500, 300)\n```\n\n### 冲突 2：子节点偏移\n```gdscript\n# 修改前：子节点偏移在代码中，不在编辑器中\nfunc _ready():\n    $Sprite.position = Vector2(0, -10)\n\n# 修改后：Sprite 位置已移入 .tscn\n# enemy.tscn: [node name=\"Sprite\"] position = Vector2(0, -10)\n```\n\n### 冲突 3：多属性\n```gdscript\n# 修改前：位置、旋转、缩放都在代码中\nfunc _ready():\n    position = Vector2(100, 100)\n    rotation = deg_to_rad(45)\n    scale = Vector2(1.5, 1.5)\n\n# 修改后：所有属性都在 .tscn 中，代码干净\n# enemy.tscn 已设置所有三个属性\n```\n\n## 集成\n\n与以下技能协作：\n- **godot-sync-camera-positions** - 跟随相机的元素\n- **godot-sync-parallax** - 视差层专用同步\n- **godot-clean-conflicts** - 通用冲突解决\n- **godot-fix-positions**（编排器）- 所有位置同步操作\n\n## 安全性\n\n- 原始位置保留在 git 中\n- 验证确保同步正确性\n- 验证失败时自动回滚\n- .tscn 格式精确保留\n\n## 何时不应使用\n\n以下情况不要同步：\n- 位置是动态计算的\n- 位置根据游戏状态变化\n- 有意的位置覆盖模式\n- 位置在 _process() 中设置（每帧）\n\n**合法的代码控制位置：**\n```gdscript\n# 这些不应该同步到 .tscn\nfunc _ready():\n    position = get_spawn_location_from_data()  # 数据驱动\n    position = player.position + offset  # 相对于玩家\n    position = area.get_random_point()  # 程序化\n```\n\n## 好处\n\n- **所见即所得** - 编辑器显示准确的位置\n- **设计师友好** - 在编辑器中进行关卡设计，而非代码\n- **便于调试** - 位置来源一目了然\n- **一致性** - 清晰的归属模式\n- **可视化** - 预览与游戏完全一致\n\n## 位置归属模式\n\n同步后，清晰的模式会浮现：\n\n| 位置类型 | 归属方 | 示例 |\n|---------|--------|------|\n| 静态出生点 | 编辑器 (.tscn) | 敌人出生位置 |\n| 子节点偏移 | 编辑器 (.tscn) | Sprite 相对于父节点 |\n| 动态位置 | 代码 (_ready, _process) | 跟随玩家、程序化 |\n| 动画位置 | AnimationPlayer | 动画运动 |\n| 物理位置 | 物理引擎 | RigidBody2D |\n\n## 验证\n\n同步后验证：\n- .tscn 文件正确解析\n- 位置值与预期目标一致\n- 引用（@onready）仍然有效\n- 场景无错误加载\n- 视觉位置与代码位置一致\n\n## 添加的文档\n\n```gdscript\n# 位置在场景文件中设置为 (500, 300)\n# 旋转由 AnimationPlayer \"rotate\" 控制\n# 缩放由代码控制（基于生命值的动态缩放）\n```\n\n清晰的归属 = 清晰的代码 = 更少的 bug。\n","# 同步静态位置\n\n## 核心原则\n\n**所见即所得。** 对于静态位置，编辑器预览应与游戏行为一致。\n\n## 此技能的功能\n\n查找如下冲突：\n```gdscript\n# enemy.gd\nfunc _ready():\n    position = Vector2(500, 300)  # 代码设置在这里\n\n# enemy.tscn\n[node name=\"Enemy\" type=\"CharacterBody2D\"]\nposition = Vector2(100, 100)  # 编辑器设置在这里\n\n# 结果：令人困惑！编辑器显示错误的位置\n```\n\n解决为：\n```gdscript\n# enemy.gd\nfunc _ready():\n    # 位置已在场景文件中设置，以便在编辑器中可见\n    pass\n\n# enemy.tscn\n[node name=\"Enemy\" type=\"CharacterBody2D\"]\nposition = Vector2(500, 300)  # 更新为匹配预期位置\n\n# 结果：编辑器预览与游戏一致\n```\n\n## 检测模式\n\n识别以下情况：\n\n### _ready() 中的直接位置赋值\n```gdscript\nfunc _ready():\n    position = Vector2(100, 150)  # 静态冲突\n    global_position = Vector2(500, 300)  # 静态冲突\n```\n\n### Node 属性赋值\n```gdscript\nfunc _ready():\n    $Sprite.position = Vector2(10, 20)  # 子节点位置冲突\n    get_node(\"CollisionShape2D\").position = Vector2(0, 0)\n```\n\n### 多属性冲突\n```gdscript\nfunc _ready():\n    position = Vector2(100, 100)\n    rotation = deg_to_rad(45)  # 也是位置相关的\n    scale = Vector2(2, 2)\n```\n\n## 何时使用\n\n### 关卡设计工作流\n在编辑器中放置物体，但代码覆盖了位置。\n\n### 调试位置问题\n\"为什么这个节点在错误的位置？\"\n\n### 维护所见即所得\n希望编辑器预览是准确的。\n\n### 为协作做准备\n关卡设计师需要准确的编辑器预览。\n\n## 流程\n\n1. **扫描** - 查找 _ready() 中的位置赋值\n2. **对比** - 与 .tscn 值进行比较\n3. **检测冲突** - 识别静态冲突（非动态）\n4. **选择策略** - 用户选择同步方向\n5. **应用** - 更新 .tscn 或 .gd 文件\n6. **记录** - 添加注释说明归属关系\n7. **验证** - 确保编辑器\u002F游戏之间的位置一致\n8. **提交** - 每次冲突解决后进行 git 提交\n\n## 同步策略\n\n### 策略 1：编辑器优先（推荐用于静态位置）\n将代码中的值移到 .tscn，从代码中移除。\n\n**何时使用：**\n- 位置应在编辑器中可见\n- 设计师控制的布局\n- 静态物体定位\n\n**示例：**\n```gdscript\n# 修改前\nfunc _ready():\n    position = Vector2(500, 300)\n\n# 修改后\nfunc _ready():\n    # 位置已在场景文件中设置\n    pass\n```\n```ini\n# enemy.tscn 已更新\nposition = Vector2(500, 300)\n```\n\n### 策略 2：代码优先（保持动态）\n移除编辑器中的值，保留代码赋值。\n\n**何时使用：**\n- 位置在运行时计算\n- 依赖于其他节点\u002F数据\n- 程序化定位\n\n**示例：**\n```gdscript\n# 修改前\nfunc _ready():\n    position = spawn_point.position + offset  # 动态的！\n\n# 修改后\nfunc _ready():\n    # 位置是动态计算的（参见 spawn_point）\n    position = spawn_point.position + offset\n```\n```ini\n# enemy.tscn - 位置已移除或设置为 (0,0) 作为占位符\n```\n\n### 策略 3：记录意图\n保留两者，但添加清晰的注释。\n\n**何时使用：**\n- 编辑器中的初始位置，被有意覆盖\n- 默认位置带有代码覆盖\n- 两个值都有意义\n\n**示例：**\n```gdscript\n# 修改前\nfunc _ready():\n    position = start_position\n\n# 修改后\nfunc _ready():\n    # 编辑器位置是默认出生点，被覆盖为 start_position\n    position = start_position\n```\n\n## 智能检测\n\n**识别静态冲突（修复这些）：**\n```gdscript\nfunc _ready():\n    position = Vector2(100, 100)  # 字面量常数 - 静态\n    position = Vector2(CONSTANT_X, CONSTANT_Y)  # 常量 - 静态\n    $Child.position = Vector2(10, 10)  # 字面量 - 静态\n```\n\n**跳过动态定位（属于有意设计）：**\n```gdscript\nfunc _ready():\n    position = player.position  # 变量引用 - 动态\n    position = get_spawn_point()  # 函数调用 - 动态\n    if some_condition:\n        position = Vector2(100, 100)  # 条件性 - 动态\n\nfunc _process(delta):\n    position = target  # 每帧 - 动态（跳过）\n```\n\n**关键区别：静态 = 每次都相同，动态 = 运行时变化**\n\n## 生成内容\n\n- 同步后的 .tscn 文件，包含正确的位置\n- 更新或清理后的代码文件\n- 记录位置归属的注释\n- 确保同步成功的验证\n- 每次同步操作的 git 提交\n\n## 常见冲突\n\n### 冲突 1：出生位置\n```gdscript\n# 修改前：代码设置 (500, 300)，编辑器设置 (0, 0)\nfunc _ready():\n    position = Vector2(500, 300)\n\n# 修改后：编辑器已更新，代码已移除\n# enemy.tscn: position = Vector2(500, 300)\n```\n\n### 冲突 2：子节点偏移\n```gdscript\n# 修改前：子节点偏移在代码中，不在编辑器中\nfunc _ready():\n    $Sprite.position = Vector2(0, -10)\n\n# 修改后：Sprite 位置已移入 .tscn\n# enemy.tscn: [node name=\"Sprite\"] position = Vector2(0, -10)\n```\n\n### 冲突 3：多属性\n```gdscript\n# 修改前：位置、旋转、缩放都在代码中\nfunc _ready():\n    position = Vector2(100, 100)\n    rotation = deg_to_rad(45)\n    scale = Vector2(1.5, 1.5)\n\n# 修改后：所有属性都在 .tscn 中，代码干净\n# enemy.tscn 已设置所有三个属性\n```\n\n## 集成\n\n与以下技能协作：\n- **godot-sync-camera-positions** - 跟随相机的元素\n- **godot-sync-parallax** - 视差层专用同步\n- **godot-clean-conflicts** - 通用冲突解决\n- **godot-fix-positions**（编排器）- 所有位置同步操作\n\n## 安全性\n\n- 原始位置保留在 git 中\n- 验证确保同步正确性\n- 验证失败时自动回滚\n- .tscn 格式精确保留\n\n## 何时不应使用\n\n以下情况不要同步：\n- 位置是动态计算的\n- 位置根据游戏状态变化\n- 有意的位置覆盖模式\n- 位置在 _process() 中设置（每帧）\n\n**合法的代码控制位置：**\n```gdscript\n# 这些不应该同步到 .tscn\nfunc _ready():\n    position = get_spawn_location_from_data()  # 数据驱动\n    position = player.position + offset  # 相对于玩家\n    position = area.get_random_point()  # 程序化\n```\n\n## 好处\n\n- **所见即所得** - 编辑器显示准确的位置\n- **设计师友好** - 在编辑器中进行关卡设计，而非代码\n- **便于调试** - 位置来源一目了然\n- **一致性** - 清晰的归属模式\n- **可视化** - 预览与游戏完全一致\n\n## 位置归属模式\n\n同步后，清晰的模式会浮现：\n\n| 位置类型 | 归属方 | 示例 |\n|---------|--------|------|\n| 静态出生点 | 编辑器 (.tscn) | 敌人出生位置 |\n| 子节点偏移 | 编辑器 (.tscn) | Sprite 相对于父节点 |\n| 动态位置 | 代码 (_ready, _process) | 跟随玩家、程序化 |\n| 动画位置 | AnimationPlayer | 动画运动 |\n| 物理位置 | 物理引擎 | RigidBody2D |\n\n## 验证\n\n同步后验证：\n- .tscn 文件正确解析\n- 位置值与预期目标一致\n- 引用（@onready）仍然有效\n- 场景无错误加载\n- 视觉位置与代码位置一致\n\n## 添加的文档\n\n```gdscript\n# 位置在场景文件中设置为 (500, 300)\n# 旋转由 AnimationPlayer \"rotate\" 控制\n# 缩放由代码控制（基于生命值的动态缩放）\n```\n\n清晰的归属 = 清晰的代码 = 更少的 bug。\n",{"name":5,"type":39,"author":49,"license":14,"outputs":50,"version":51,"audience":52,"behavior":54,"category":56,"homepage":57,"keywords":58,"execution":65,"platforms":66,"difficulty":68,"repository":69,"description":70,"displayName":71,"integration":72,"permissions":73,"requirements":79},"Asreonn","同步后的位置、更新的 .tscn 或 .gd 文件、清晰的归属文档、git 提交","3.0.0",[53],"developers",{"validation":55,"git_commits":55,"auto_rollback":55},true,"game-development","https:\u002F\u002Fgithub.com\u002Fasreonn\u002Fgodot-superpowers#readme",[26,59,60,31,61,62,63,64],"position-sync","editor-preview","static-positions","node-position","level-design","tscn-files","自动检测，用户审批同步策略",[67,43,42],"macos","beginner","https:\u002F\u002Fgithub.com\u002Fasreonn\u002Fgodot-superpowers","当 Godot 节点的位置同时在 .tscn（编辑器）和 _ready()（代码）中设置时使用， 这会导致实际运行时位置产生混乱。检测与编辑器值冲突的静态位置赋值。 同步到单一事实来源，使编辑器预览与游戏行为一致（所见即所得）。\n","同步静态位置","godot-fix-positions 编排器的一部分，与 godot-clean-conflicts 协作",{"git":55,"filesystem":74},{"read":75,"write":78},[76,77],".gd",".tscn",[76,77],"Git 仓库、Godot 4.x","main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fconfig_packs\u002Fgodot-dev\u002Fclaude\u002Fskills\u002Fgodot-sync-static-positions",1,"https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system","https:\u002F\u002Fgithub.com\u002Fwelflau","2026-11-12 14:55:20",{"source":8,"skillName":5,"commands":88,"prompt":98,"zipAvailable":55},[89,92,95],{"tool":90,"command":91},"npx","npx skills add welflau\u002Fai-dev-system --skill godot-sync-static-positions",{"tool":93,"command":94},"bunx","bunx skills add welflau\u002Fai-dev-system --skill godot-sync-static-positions",{"tool":96,"command":97},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill godot-sync-static-positions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgodot-dev\u002Fclaude\u002Fskills\u002Fgodot-sync-static-positions\u002FSKILL.md",[],[101,134,164,190,217,242],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":115,"publishedAt":133},"01M6HS9Z4B0YA8CJCS2Y2F04Y3","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fwebapp-testing\u002FSKILL.md",[109,112],{"categoryNo":110,"categoryName":111,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":113,"categoryName":114,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"testing","webapp testing","webapp","frontend","screenshots","playwright","web","debugging","toolkit","browser","ui","logs","applications","behavior","local","with","for","2026-11-11 15:11:14",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":144,"publishedAt":133},"01M6HRAGMG7JF0HXYHMA5QHS8A","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Finternal-comms\u002FSKILL.md",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通",[145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163],"internal comms","comms","status","help","SET","write","use","reports","me","incident","leadership","project","resources","communications","internal communications","formats","sort","my","updates",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":44},"01M6HSTDP4M3JFXEBK91VFB4PA","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FSKILL.md",[171],{"categoryNo":113,"categoryName":114,"taxonomyType":20,"taxonomyTypeDesc":21},[173,122,174,175,176,119,177,178,179,180,181,182,183,184,151,185,186,187,188,132,189],"web artifacts builder","artifacts","artifacts builder","builder","css","components","react","routing","state management","state","file","Tailwind","single-file","simple","ui components","multi","single",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":194,"sourceHtmlUrl":195,"categories":196,"keywords":204,"publishedAt":44},"01M6HSDXH0JSP8R3QTNY9XZ8HN","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FSKILL.md",[197,198,199],{"categoryNo":113,"categoryName":114,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":200,"categoryName":201,"taxonomyType":202,"taxonomyTypeDesc":203},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[119,35,205,177,122,178,179,206,207,208,174,209,128,210,151,211,212,213,214,131,215,216],"frontend design","react components","create","code","examples","landing","ui design","pages","aesthetics","web ui","generic","when",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":221,"sourceHtmlUrl":222,"categories":223,"keywords":225,"publishedAt":44},"01M6HSA77QYVP7A72HREGTDN2C","algorithmic-art","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FSKILL.md",[224],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[226,227,228,207,208,229,230,231,232,151,233,234,235,236,131,237,238,239,240,241,216],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","exploration","systems","users","Existing","request","generative","copyright","fields",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":246,"sourceHtmlUrl":247,"categories":248,"keywords":250,"publishedAt":44},"01M6HS9HE0X390Y6RQKTY1YNGJ","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FSKILL.md",[249],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[251,252,253,254,124,255,174,149,256,257,210,258,259,212,260,131,261,262,263,132,264,265],"theme factory","factory","theme","docs","generate","fly","slides","styling","artifact","themes","you","fonts","can","apply","new"]