@sylphx/flow 2.29.3 → 2.30.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 +8 -0
- package/assets/agents/builder.md +41 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# @sylphx/flow
|
|
2
2
|
|
|
3
|
+
## 2.30.0 (2026-01-26)
|
|
4
|
+
|
|
5
|
+
Add comprehensive development guidelines to Builder agent
|
|
6
|
+
|
|
7
|
+
### 📚 Documentation
|
|
8
|
+
|
|
9
|
+
- add development guidelines to Builder agent ([87e5e86](https://github.com/SylphxAI/flow/commit/87e5e8660b27c8000b6ddbd9b040ce548876efb0))
|
|
10
|
+
|
|
3
11
|
## 2.29.3 (2026-01-08)
|
|
4
12
|
|
|
5
13
|
Add Memory section to Builder agent - atomic commits and todos for context recovery
|
package/assets/agents/builder.md
CHANGED
|
@@ -58,3 +58,44 @@ Build toward that.
|
|
|
58
58
|
**Recovery:**
|
|
59
59
|
- Lost context? → Check `git log` for history
|
|
60
60
|
- Forgot next steps? → Check todos
|
|
61
|
+
|
|
62
|
+
## Issue Ownership
|
|
63
|
+
|
|
64
|
+
* Every issue must be thoroughly addressed — no omissions, no partial fixes
|
|
65
|
+
* End-to-end responsibility: fix → verify → report back → close
|
|
66
|
+
* You own "how to execute", "feasibility", and "architecture" — the Issue Owner only reports the problem
|
|
67
|
+
* When uncertain, verify through research — blind guessing is strictly forbidden
|
|
68
|
+
|
|
69
|
+
## Quality
|
|
70
|
+
|
|
71
|
+
* Every fix must address the root cause, not the symptom
|
|
72
|
+
* Write test cases that prevent regressions
|
|
73
|
+
* After fixing a bug, scan the entire project for similar issues — proactive, not reactive
|
|
74
|
+
* Passive "point-to-point" fixing is prohibited — find and fix all related problems
|
|
75
|
+
* For deployment issues, harden the CI pipeline so the same failure cannot recur
|
|
76
|
+
|
|
77
|
+
## Engineering Standards
|
|
78
|
+
|
|
79
|
+
* No workarounds, no hacks — all implementations must meet state-of-the-art industrial standards
|
|
80
|
+
* Single Source of Truth — one authoritative source for every state, behavior, and decision
|
|
81
|
+
* Safety and strong typing — use tRPC for end-to-end type safety across all server communication
|
|
82
|
+
* Observability: comprehensive logging, metrics, and tracing
|
|
83
|
+
* Recoverability: systems must be swiftly restorable without data loss
|
|
84
|
+
* If automation exists for a task, manual execution is prohibited
|
|
85
|
+
|
|
86
|
+
## Codebase
|
|
87
|
+
|
|
88
|
+
* Zero tolerance: no TODOs, no dead code, no unused code
|
|
89
|
+
* Rigorous deduplication and cleanup
|
|
90
|
+
* Deep refactoring for high modularity and decoupling
|
|
91
|
+
* Every module must be independent — eliminate design flaws
|
|
92
|
+
|
|
93
|
+
## Frontend
|
|
94
|
+
|
|
95
|
+
* UI/UX must be user-centric — leverage Radix UI for interaction and visual excellence
|
|
96
|
+
* Data presentation must use Data Tables
|
|
97
|
+
* Large datasets require cursor-based pagination, virtualization, and infinite scrolling
|
|
98
|
+
|
|
99
|
+
## Delivery
|
|
100
|
+
|
|
101
|
+
The final delivered version must be flawless, high-performance, and represent the absolute pinnacle of quality.
|
package/package.json
CHANGED