starwards-debugging

仓库创建 2019年3月17日最近提交 23 天前SkillHot 收录 22 天前

▸ 精选理由

避免盲目修补，适合排查复杂复现与竞态问题

这个 Skill 做什么

四阶段系统化调试流程，涵盖根因、验证与实装，含多人同步问题定位

一套四阶段的 Starwards 专用调试流程：定位根因、找出模式、验证假设并落地修复，覆盖 Colyseus 状态检查、Tweakpane 调试和多人同步问题。遇到多人同步、装饰器问题或 UI/服务器不一致等难查错误时用。核心原则是不打临时补丁先找根因，并包含针对 monorepo 和竞态条件的实战技巧。

▸ 展开 SKILL.md 英文原文

Systematic debugging for Starwards - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) with Colyseus state inspection, Tweakpane debugging, multiplayer sync issues, and monorepo-specific troubleshooting

开发编程系统化调试根因分析单体仓库通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/starwards/starwards/master/.claude/skills/starwards-debugging/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/starwards/starwards/master/.claude/skills/starwards-debugging/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Systematic Debugging for Starwards

## Overview

Random fixes waste time. Quick patches mask underlying issues.

**Core principle:** ALWAYS find root cause before attempting fixes.

**Starwards-specific:** Debug state sync issues, decorator problems, UI/server mismatches, and multiplayer race conditions.

## The Iron Law

```
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
```

If you haven't completed Phase 1, you cannot propose fixes.

## When to Use

**Any technical issue:**
- Test failures (Jest, Playwright)
- State sync problems (Colyseus)
- UI not updating (Tweakpane, React)
- Build failures (webpack, tsup, tsc)
- Decorator issues (@gameField, @range, @tweakable)
- Multiplayer race c

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有