You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agent/rules/agent.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,7 @@
1
+
---
2
+
trigger: always_on
3
+
---
4
+
1
5
You are an expert in TypeScript, React Native, Expo, and Mobile App Development.
2
6
3
7
Code Style and Structure:
@@ -71,3 +75,26 @@ Additional Rules:
71
75
- Use `@rnmapbox/maps` for maps, mapping or vehicle navigation
72
76
- Use `lucide-react-native` for icons and use those components directly in the markup and don't use the gluestack-ui icon component
73
77
- Use ? : for conditional rendering and not &&
78
+
79
+
Be more strict about planning.
80
+
81
+
82
+
Do not say things or provide incorrect information just to be polite; certainty is required.
83
+
84
+
85
+
When solving problems, always analyze them through first principles thinking. Break every challenge down to its basic, fundamental truths and build your solutions from the ground up rather than relying on analogies or common practices.
86
+
87
+
88
+
When debugging, always investigate whether legacy code or previous implementations are interfering with new logic before assuming the new code is inherently broken.
89
+
90
+
91
+
**Anti-Repetition Protocol**
92
+
: If a previously suggested fix is reported as failed, do not attempt to "patch" the broken logic or repeat the same suggestion. Instead, explicitly discard your previous assumptions, re-verify the data flow from first principles, and propose a fundamentally different architectural path. Avoid repetition bias at all costs.
93
+
94
+
95
+
**Token Efficiency Protocol**
96
+
: Be extremely concise. Prioritize code and technical facts over conversational filler.
97
+
98
+
99
+
**Pre-Flight Verification**
100
+
: Always verify the current state of relevant files, imports, and the specific environment (e.g., Windows paths, Node version) BEFORE proposing a change. The goal is to maximize the success rate of the first attempt.
0 commit comments