@sylphx/flow 3.0.1 → 3.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +6 -0
- package/assets/slash-commands/review.md +65 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# @sylphx/flow
|
|
2
2
|
|
|
3
|
+
## 3.1.0 (2026-01-26)
|
|
4
|
+
|
|
5
|
+
### ✨ Features
|
|
6
|
+
|
|
7
|
+
- add /review slash command for ruthless self-critique ([1c4f35c](https://github.com/SylphxAI/flow/commit/1c4f35c6e5ac755921f44b04f53dbac306fab9cc))
|
|
8
|
+
|
|
3
9
|
## 3.0.1 (2026-01-26)
|
|
4
10
|
|
|
5
11
|
### 🐛 Bug Fixes
|
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: review
|
|
3
|
+
description: Challenge your work - is it truly state-of-the-art?
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Review: Ruthless Self-Critique
|
|
7
|
+
|
|
8
|
+
Stop. Step back. Challenge everything you just did.
|
|
9
|
+
|
|
10
|
+
## Questions to Answer
|
|
11
|
+
|
|
12
|
+
### 1. State of the Art?
|
|
13
|
+
- Would industry experts approve this implementation?
|
|
14
|
+
- Does it follow current best practices (2024+)?
|
|
15
|
+
- Is this how top engineers at FAANG would solve it?
|
|
16
|
+
- Are you using modern APIs, patterns, and approaches?
|
|
17
|
+
|
|
18
|
+
### 2. Correct Approach or Workaround?
|
|
19
|
+
- Does this solve the ROOT CAUSE or just the symptom?
|
|
20
|
+
- Is this a proper fix or a hack that will break later?
|
|
21
|
+
- Would you be embarrassed if a senior engineer reviewed this?
|
|
22
|
+
- Is there technical debt being created?
|
|
23
|
+
|
|
24
|
+
### 3. Clean & Complete?
|
|
25
|
+
- Zero dead code?
|
|
26
|
+
- Zero unused imports?
|
|
27
|
+
- Zero TODOs left behind?
|
|
28
|
+
- Zero console.logs or debug code?
|
|
29
|
+
- All edge cases handled?
|
|
30
|
+
- Error handling complete?
|
|
31
|
+
|
|
32
|
+
### 4. Human Experience?
|
|
33
|
+
- Is the UX intuitive? Would a user understand without explanation?
|
|
34
|
+
- Are error messages helpful and actionable?
|
|
35
|
+
- Is the UI responsive and accessible?
|
|
36
|
+
- Does it feel polished, not janky?
|
|
37
|
+
|
|
38
|
+
### 5. Better Way?
|
|
39
|
+
- What would you do differently with unlimited time?
|
|
40
|
+
- Is there a simpler solution you overlooked?
|
|
41
|
+
- Could this be more elegant?
|
|
42
|
+
- What would 10x improvement look like?
|
|
43
|
+
|
|
44
|
+
## Process
|
|
45
|
+
|
|
46
|
+
1. **List** all changes made in this session
|
|
47
|
+
2. **Audit** each change against the questions above
|
|
48
|
+
3. **Identify** anything that's not truly excellent
|
|
49
|
+
4. **Fix** or **flag** issues found
|
|
50
|
+
5. **Report** your findings honestly
|
|
51
|
+
|
|
52
|
+
## Standards
|
|
53
|
+
|
|
54
|
+
* "Good enough" is NOT acceptable
|
|
55
|
+
* If you wouldn't stake your reputation on it, fix it
|
|
56
|
+
* Perfection is the goal, not completion
|
|
57
|
+
* Clean code > working code > fast code
|
|
58
|
+
|
|
59
|
+
## Output
|
|
60
|
+
|
|
61
|
+
After review, report:
|
|
62
|
+
- ✅ What meets the bar
|
|
63
|
+
- ⚠️ What could be better (and how)
|
|
64
|
+
- ❌ What needs immediate fixing
|
|
65
|
+
- 🎯 Actions taken or recommended
|
package/package.json
CHANGED