this repo has no description
Add AGENTS.md and prune .gitignore
+38
-24
-24
.gitignore
-24
.gitignore
···
11
11
# Editor directories
12
12
.vscode/
13
13
.idea/
14
-
15
-
16
-
# START Ruler Generated Files
17
-
/.agent/rules/ruler.md
18
-
/.agent/rules/ruler.md.bak
19
-
/.agent/skills
20
-
/.claude/skills
21
-
/.gemini/settings.json
22
-
/.gemini/settings.json.bak
23
-
/.gemini/skills
24
-
/.mcp.json
25
-
/.mcp.json.bak
26
-
/.opencode/skills
27
-
/.vscode/mcp.json
28
-
/.vscode/mcp.json.bak
29
-
/.zed/settings.json
30
-
/.zed/settings.json.bak
31
-
/AGENTS.md
32
-
/AGENTS.md.bak
33
-
/CLAUDE.md
34
-
/CLAUDE.md.bak
35
-
/opencode.json
36
-
/opencode.json.bak
37
-
# END Ruler Generated Files
+38
AGENTS.md
+38
AGENTS.md
···
1
+
## Interaction Guidelines
2
+
3
+
Direct, succinct, and objective. Favor headings over lists; use nested lists only for specific details.
4
+
**No em dashes**; restructure sentences to avoid them.
5
+
6
+
## Response Architecture
7
+
8
+
Use multi-section responses for complex inquiries; provide brief, direct answers for simple requests.
9
+
10
+
## Research and Knowledge
11
+
12
+
- **Trust User Knowledge**: Research unfamiliar concepts thoroughly for context.
13
+
- **Documentation Retrieval**: Use documentation fetching tools (context7), and web search tools to access current documentation.
14
+
- **Proactive Context**: Verify latest library features, breaking changes, tools before implementation.
15
+
16
+
## Coding Standards
17
+
18
+
Produce minimal, readable, and performant code.
19
+
20
+
### Architectural Integrity
21
+
22
+
- **Zero Redundancy**: Do not create redundant logic. Always remove redundancy to ensure code is reusable and organized.
23
+
24
+
### Documentation and Readability
25
+
26
+
- **Self-Documenting Logic**: Use descriptive naming; avoid comments unless logic is cryptographic or mathematical.
27
+
- **JSDoc/JavaDoc and equivalents**: Use for public APIs/functions, complex functions, and non-obvious logic.
28
+
- **No Magic Numbers**: Use constants for all numeric or string literals.
29
+
30
+
### API Design Patterns
31
+
32
+
- **Dual Getter-Setter Functions**: Use overloaded functions for state: `fn()` to get, `fn(val)` to set.
33
+
- **Interface Quality**: Prioritize high-fidelity UI/UX and seamless DX.
34
+
35
+
### Performance and Scale
36
+
37
+
- **Efficiency**: Favor built-in language features and efficient algorithms.
38
+
- **Consistency**: Maintain unified style for predictability.