@sylphx/flow 3.2.0 → 3.3.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 +10 -0
- package/assets/agents/builder.md +12 -7
- package/assets/slash-commands/catchup.md +119 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# @sylphx/flow
|
|
2
2
|
|
|
3
|
+
## 3.3.0 (2026-01-26)
|
|
4
|
+
|
|
5
|
+
### ✨ Features
|
|
6
|
+
|
|
7
|
+
- add /catchup command and architecture principles ([f5d6cd9](https://github.com/SylphxAI/flow/commit/f5d6cd9475aba40094f5c434fb962b7451632f1d))
|
|
8
|
+
|
|
9
|
+
### 🐛 Bug Fixes
|
|
10
|
+
|
|
11
|
+
- **builder:** simplify CLAUDE.md memory instructions ([fedd464](https://github.com/SylphxAI/flow/commit/fedd46482dc01ef5988d5552b9f7a7c8675c6240))
|
|
12
|
+
|
|
3
13
|
## 3.2.0 (2026-01-26)
|
|
4
14
|
|
|
5
15
|
### ✨ Features
|
package/assets/agents/builder.md
CHANGED
|
@@ -86,7 +86,7 @@ Vercel CLI, Neon CLI, GitHub CLI
|
|
|
86
86
|
|
|
87
87
|
**Todos.** Track what needs to be done next. This is your memory of what to do.
|
|
88
88
|
|
|
89
|
-
**CLAUDE.md** — Your persistent memory file.
|
|
89
|
+
**CLAUDE.md** — Your persistent memory file. Write to it when you discover:
|
|
90
90
|
- Project-specific commands (build, test, deploy, lint)
|
|
91
91
|
- Environment setup (env vars, prerequisites, dependencies)
|
|
92
92
|
- Architecture decisions and their reasoning
|
|
@@ -94,10 +94,8 @@ Vercel CLI, Neon CLI, GitHub CLI
|
|
|
94
94
|
- Gotchas, workarounds, or non-obvious behaviors
|
|
95
95
|
- Frequently referenced paths, configs, or resources
|
|
96
96
|
|
|
97
|
-
This file is auto-attached every session. If you learn something important that future sessions should know, write it to CLAUDE.md immediately.
|
|
98
|
-
|
|
99
97
|
**Recovery:**
|
|
100
|
-
- Lost context? → Check `git log` for history
|
|
98
|
+
- Lost context? → Check `git log` for history
|
|
101
99
|
- Forgot next steps? → Check todos
|
|
102
100
|
|
|
103
101
|
## Issue Ownership
|
|
@@ -119,11 +117,18 @@ This file is auto-attached every session. If you learn something important that
|
|
|
119
117
|
|
|
120
118
|
* No workarounds, no hacks — all implementations must meet state-of-the-art industrial standards
|
|
121
119
|
* Single Source of Truth — one authoritative source for every state, behavior, and decision
|
|
122
|
-
*
|
|
123
|
-
* Observability
|
|
124
|
-
* Recoverability
|
|
120
|
+
* Type safety — end-to-end type safety across all boundaries (tRPC, Zod, strict TypeScript)
|
|
121
|
+
* Observability — logging, metrics, tracing; platform code must be observable by design
|
|
122
|
+
* Recoverability — systems must be swiftly restorable without data loss
|
|
125
123
|
* If automation exists for a task, manual execution is prohibited
|
|
126
124
|
|
|
125
|
+
## Architecture Principles
|
|
126
|
+
|
|
127
|
+
* **Pure functions** — no side effects, deterministic output; isolate impure code at boundaries
|
|
128
|
+
* **Decoupling** — minimize dependencies between modules, use interfaces and dependency injection
|
|
129
|
+
* **Modularisation** — single responsibility, clear boundaries, independent deployability
|
|
130
|
+
* **Reusable composition** — build primitives that compose; prefer composition over inheritance
|
|
131
|
+
|
|
127
132
|
## Codebase
|
|
128
133
|
|
|
129
134
|
* Zero tolerance: no TODOs, no dead code, no unused code
|
|
@@ -0,0 +1,119 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: catchup
|
|
3
|
+
description: Deep dive into project history, direction, and implementation details
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Catchup: Understand the Project Deeply
|
|
7
|
+
|
|
8
|
+
Get up to speed with the entire project — history, direction, and details.
|
|
9
|
+
|
|
10
|
+
## Phase 1: Git History Analysis
|
|
11
|
+
|
|
12
|
+
### Recent Commits
|
|
13
|
+
```bash
|
|
14
|
+
git log --oneline -50
|
|
15
|
+
git log --oneline --since="1 week ago"
|
|
16
|
+
git log --oneline --since="1 month ago" --until="1 week ago"
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
### Commit Patterns
|
|
20
|
+
- What areas are being actively worked on?
|
|
21
|
+
- What types of changes dominate? (feat, fix, refactor, docs)
|
|
22
|
+
- Who are the contributors and what do they focus on?
|
|
23
|
+
- Are there any recurring issues being fixed?
|
|
24
|
+
|
|
25
|
+
### Recent Activity by Area
|
|
26
|
+
```bash
|
|
27
|
+
git log --oneline --all -- "src/components/*" | head -20
|
|
28
|
+
git log --oneline --all -- "src/api/*" | head -20
|
|
29
|
+
git log --oneline --all -- "src/lib/*" | head -20
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
## Phase 2: Development Direction
|
|
33
|
+
|
|
34
|
+
### Read Project Documentation
|
|
35
|
+
1. **PRODUCT.md** — Vision, goals, target users, success metrics
|
|
36
|
+
2. **ARCHITECTURE.md** — Tech decisions, patterns, system design
|
|
37
|
+
3. **CLAUDE.md** — Project-specific knowledge, commands, gotchas
|
|
38
|
+
4. **README.md** — Setup, usage, contribution guidelines
|
|
39
|
+
5. **CHANGELOG.md** — Release history, breaking changes
|
|
40
|
+
|
|
41
|
+
### Identify Current Focus
|
|
42
|
+
- What features are in progress?
|
|
43
|
+
- What's the roadmap or next milestones?
|
|
44
|
+
- Are there open issues or PRs that indicate direction?
|
|
45
|
+
|
|
46
|
+
```bash
|
|
47
|
+
gh issue list --state open --limit 20
|
|
48
|
+
gh pr list --state open --limit 10
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
### Branch Analysis
|
|
52
|
+
```bash
|
|
53
|
+
git branch -a
|
|
54
|
+
git log main..HEAD --oneline # if on feature branch
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
## Phase 3: Deep Implementation Research
|
|
58
|
+
|
|
59
|
+
### Codebase Structure
|
|
60
|
+
```bash
|
|
61
|
+
tree -L 2 -d src/ # or relevant directories
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
### Key Files to Understand
|
|
65
|
+
- Entry points (main, index, app)
|
|
66
|
+
- Configuration files (config, env, settings)
|
|
67
|
+
- Core business logic
|
|
68
|
+
- Database schema and migrations
|
|
69
|
+
- API routes and handlers
|
|
70
|
+
- Shared utilities and helpers
|
|
71
|
+
|
|
72
|
+
### Dependency Analysis
|
|
73
|
+
- What are the major dependencies?
|
|
74
|
+
- Are there any custom abstractions worth understanding?
|
|
75
|
+
- What patterns are consistently used?
|
|
76
|
+
|
|
77
|
+
### Test Coverage
|
|
78
|
+
- Where are tests located?
|
|
79
|
+
- What's tested, what's not?
|
|
80
|
+
- What do test failures tell us about the system?
|
|
81
|
+
|
|
82
|
+
## Output
|
|
83
|
+
|
|
84
|
+
### Executive Summary
|
|
85
|
+
```
|
|
86
|
+
Project: [name]
|
|
87
|
+
Stage: [MVP / Growth / Mature]
|
|
88
|
+
Focus: [current development focus]
|
|
89
|
+
Health: [assessment based on commits, issues, code quality]
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
### Recent Activity (Last 2 Weeks)
|
|
93
|
+
| Date | Area | Changes | Impact |
|
|
94
|
+
|------|------|---------|--------|
|
|
95
|
+
| ... | ... | ... | H/M/L |
|
|
96
|
+
|
|
97
|
+
### Development Direction
|
|
98
|
+
- **Current sprint/focus:** ...
|
|
99
|
+
- **Next milestones:** ...
|
|
100
|
+
- **Technical debt:** ...
|
|
101
|
+
- **Opportunities:** ...
|
|
102
|
+
|
|
103
|
+
### Key Findings
|
|
104
|
+
1. ...
|
|
105
|
+
2. ...
|
|
106
|
+
3. ...
|
|
107
|
+
|
|
108
|
+
### Recommendations
|
|
109
|
+
- **Immediate:** ...
|
|
110
|
+
- **Short-term:** ...
|
|
111
|
+
- **Consider:** ...
|
|
112
|
+
|
|
113
|
+
## Mindset
|
|
114
|
+
|
|
115
|
+
* Be thorough — read everything, assume nothing
|
|
116
|
+
* Connect the dots — understand WHY decisions were made
|
|
117
|
+
* Think forward — where is this project heading?
|
|
118
|
+
* Be critical — identify risks, gaps, opportunities
|
|
119
|
+
* Document discoveries — update CLAUDE.md with important findings
|
package/package.json
CHANGED