@sylphx/flow 2.24.0 → 2.26.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
CHANGED
|
@@ -1,5 +1,17 @@
|
|
|
1
1
|
# @sylphx/flow
|
|
2
2
|
|
|
3
|
+
## 2.26.0 (2025-12-18)
|
|
4
|
+
|
|
5
|
+
### ✨ Features
|
|
6
|
+
|
|
7
|
+
- **rules:** add Project Context - PRODUCT.md and ARCHITECTURE.md ([cf7383f](https://github.com/SylphxAI/flow/commit/cf7383f1d8d4176dc605bc01e9ac3da6d3750af4))
|
|
8
|
+
|
|
9
|
+
## 2.25.0 (2025-12-18)
|
|
10
|
+
|
|
11
|
+
### ✨ Features
|
|
12
|
+
|
|
13
|
+
- **rules:** add Git Workflow - all commits must be atomic ([17ebcbf](https://github.com/SylphxAI/flow/commit/17ebcbfa630b0a14961e88fcacca996b73634e5a))
|
|
14
|
+
|
|
3
15
|
## 2.24.0 (2025-12-18)
|
|
4
16
|
|
|
5
17
|
### ✨ Features
|
|
@@ -145,3 +145,32 @@ Storage → Domain Model → Transform → API Response
|
|
|
145
145
|
```
|
|
146
146
|
|
|
147
147
|
Never skip validation at boundaries.
|
|
148
|
+
|
|
149
|
+
---
|
|
150
|
+
|
|
151
|
+
## Git Workflow
|
|
152
|
+
|
|
153
|
+
**All commits are atomic.** One logical change per commit. Commit immediately after each unit of work.
|
|
154
|
+
|
|
155
|
+
**Never batch. Never wait.** Don't accumulate changes. Don't wait for user to say "commit".
|
|
156
|
+
|
|
157
|
+
**Commit triggers** — commit immediately when any of these complete:
|
|
158
|
+
- Feature added
|
|
159
|
+
- Bug fixed
|
|
160
|
+
- Refactor done
|
|
161
|
+
- Config changed
|
|
162
|
+
- Docs updated
|
|
163
|
+
|
|
164
|
+
**Format**: `<type>(<scope>): <description>`
|
|
165
|
+
|
|
166
|
+
Types: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`
|
|
167
|
+
|
|
168
|
+
<example>
|
|
169
|
+
✅ Edit file → Commit → Edit next file → Commit
|
|
170
|
+
✅ feat(auth): add login endpoint
|
|
171
|
+
✅ fix(billing): handle webhook retry
|
|
172
|
+
|
|
173
|
+
❌ Edit 5 files → Commit all together
|
|
174
|
+
❌ Wait for user to say "commit"
|
|
175
|
+
❌ "WIP" commits
|
|
176
|
+
</example>
|
package/assets/rules/core.md
CHANGED
|
@@ -120,6 +120,14 @@ Before accepting any approach:
|
|
|
120
120
|
|
|
121
121
|
**These actions are AUTOMATIC. Do without being asked.**
|
|
122
122
|
|
|
123
|
+
### Project Context
|
|
124
|
+
- **Before significant work**, read:
|
|
125
|
+
- `PRODUCT.md` — Vision, goals, features, target users, success metrics
|
|
126
|
+
- `ARCHITECTURE.md` — Tech stack, patterns, decisions, system design
|
|
127
|
+
- **Update immediately** when relevant changes happen
|
|
128
|
+
- Product doc = WHAT and WHY. Architecture doc = HOW.
|
|
129
|
+
- These docs are SSOT. Code is implementation detail.
|
|
130
|
+
|
|
123
131
|
### Task Management
|
|
124
132
|
- Complex task (3+ steps) → Write todos immediately, update as you progress
|
|
125
133
|
- Long conversation → Check git log + todos before continuing
|
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
# ARCHITECTURE
|
|
2
|
+
|
|
3
|
+
## Tech Stack
|
|
4
|
+
|
|
5
|
+
| Layer | Technology | Why |
|
|
6
|
+
|-------|------------|-----|
|
|
7
|
+
| Frontend | ... | ... |
|
|
8
|
+
| Backend | ... | ... |
|
|
9
|
+
| Database | ... | ... |
|
|
10
|
+
| Auth | ... | ... |
|
|
11
|
+
| Payments | ... | ... |
|
|
12
|
+
| Hosting | ... | ... |
|
|
13
|
+
|
|
14
|
+
## System Design
|
|
15
|
+
|
|
16
|
+
High-level architecture overview.
|
|
17
|
+
|
|
18
|
+
```
|
|
19
|
+
[Diagram or description]
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
## Key Patterns
|
|
23
|
+
|
|
24
|
+
What patterns and conventions do we follow?
|
|
25
|
+
|
|
26
|
+
- **State management**: ...
|
|
27
|
+
- **API design**: ...
|
|
28
|
+
- **Error handling**: ...
|
|
29
|
+
- **Testing**: ...
|
|
30
|
+
|
|
31
|
+
## Data Models
|
|
32
|
+
|
|
33
|
+
Core entities and relationships.
|
|
34
|
+
|
|
35
|
+
## Integrations
|
|
36
|
+
|
|
37
|
+
External services and APIs.
|
|
38
|
+
|
|
39
|
+
| Service | Purpose | Notes |
|
|
40
|
+
|---------|---------|-------|
|
|
41
|
+
| ... | ... | ... |
|
|
42
|
+
|
|
43
|
+
## Technical Decisions
|
|
44
|
+
|
|
45
|
+
Key decisions and rationale (ADRs).
|
|
46
|
+
|
|
47
|
+
### Decision: [Title]
|
|
48
|
+
- **Context**: ...
|
|
49
|
+
- **Decision**: ...
|
|
50
|
+
- **Rationale**: ...
|
|
51
|
+
- **Consequences**: ...
|
|
52
|
+
|
|
53
|
+
## Known Limitations
|
|
54
|
+
|
|
55
|
+
Technical debt, constraints, areas for improvement.
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
*Last updated: YYYY-MM-DD*
|
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
# PRODUCT
|
|
2
|
+
|
|
3
|
+
## Vision
|
|
4
|
+
|
|
5
|
+
What is this product? Why does it exist? What problem does it solve?
|
|
6
|
+
|
|
7
|
+
## Success Metrics
|
|
8
|
+
|
|
9
|
+
How do we know we're winning?
|
|
10
|
+
|
|
11
|
+
- Revenue target?
|
|
12
|
+
- User growth?
|
|
13
|
+
- Engagement?
|
|
14
|
+
- Market position?
|
|
15
|
+
|
|
16
|
+
## Target Users
|
|
17
|
+
|
|
18
|
+
Who are we building for? What are their pain points?
|
|
19
|
+
|
|
20
|
+
## Value Propositions
|
|
21
|
+
|
|
22
|
+
Why would users choose this over alternatives?
|
|
23
|
+
|
|
24
|
+
## Key Features
|
|
25
|
+
|
|
26
|
+
What are the core capabilities?
|
|
27
|
+
|
|
28
|
+
| Feature | Status | Priority |
|
|
29
|
+
|---------|--------|----------|
|
|
30
|
+
| ... | ... | ... |
|
|
31
|
+
|
|
32
|
+
## Competitive Landscape
|
|
33
|
+
|
|
34
|
+
Who are the competitors? What's our differentiation?
|
|
35
|
+
|
|
36
|
+
## Roadmap
|
|
37
|
+
|
|
38
|
+
What's next? What's the priority order?
|
|
39
|
+
|
|
40
|
+
### Now
|
|
41
|
+
- ...
|
|
42
|
+
|
|
43
|
+
### Next
|
|
44
|
+
- ...
|
|
45
|
+
|
|
46
|
+
### Later
|
|
47
|
+
- ...
|
|
48
|
+
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
*Last updated: YYYY-MM-DD*
|
package/package.json
CHANGED