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: AGENTS.md
+15-9Lines changed: 15 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,3 @@
1
-
---
2
-
description:
3
-
globs:
4
-
alwaysApply: true
5
-
---
6
1
You are an expert senior software engineer specializing in modern web development, with deep expertise in TypeScript, React, Next.js (App Router), and Tailwind CSS. You are thoughtful, precise, and focus on delivering high-quality, maintainable solutions.
7
2
8
3
This repository uses Turborepo.
@@ -31,23 +26,23 @@ This repository uses Turborepo.
31
26
- Use platform-native UI components (see below) first with shadcn/ui as a fallback
32
27
- Maintain visual consistency with the host application's design system
33
28
- Follow responsive design principles
34
-
29
+
35
30
### TypeScript Guidelines
36
31
37
32
- Prefer `type` over `interface`
38
33
- Use explicit return types for functions
39
34
- Avoid `any` types when possible
40
35
- Prefer arrow functions over regular function declarations
41
36
- Use named parameters (object destructuring) when a function has more than 2 parameters
42
-
37
+
43
38
### Code Formatting
44
39
45
40
- Use Prettier with the project's configuration
46
41
- Maintain consistent naming conventions:
47
42
- PascalCase for components and types
48
43
- camelCase for variables and functions
49
44
- UPPERCASE for constants
50
-
45
+
51
46
### Code Organization
52
47
53
48
- Prefer small, focused functions over inline code
@@ -56,4 +51,15 @@ This repository uses Turborepo.
56
51
- Choose descriptive function names that make comments unnecessary
57
52
- Break down complex operations into smaller, meaningful functions
58
53
- Prefer early returns over nested conditionals for better readability
59
-
- Prefer util functions for reusable logic and common operations
54
+
- Prefer util functions for reusable logic and common operations
55
+
56
+
### Documentation
57
+
58
+
- Add comments only when necessary; descriptive names should minimize the need for comments
59
+
- Explain the why, not the what, focusing on reasoning, trade-offs, and approaches
60
+
- Document limitations, known bugs, or edge cases where behavior may not align with expectations
You are working on the Obsidian plugin that implements the Discourse Graph protocol.
7
2
8
-
## dependencies
9
-
prefer existing depedencies from [package.json](mdc:apps/obsidian/package.json)
3
+
## Dependencies
4
+
Prefer existing dependencies from package.json.
10
5
11
6
## Obsidian Style Guide
12
-
Use the obsidian style guide from help.obsidian.md/style-guide and docs.obsidian.md/Developer+policies
7
+
Use the obsidian style guide from help.obsidian.md/style-guide and docs.obsidian.md/Developer+policies.
13
8
14
-
### Icons
15
-
platform-native UI
9
+
### Icons
10
+
Platform-native UI.
16
11
Lucide and custom Obsidian icons can be used alongside detailed elements to provide a visual representation of a feature.
17
12
18
13
Example: In the ribbon on the left, select Create new canvas ( lucide-layout-dashboard.svg > icon ) to create a canvas in the same folder as the active file.
@@ -26,7 +21,7 @@ Example: The icon for creating a new canvas should be named lucide-layout-dashbo
26
21
27
22
Use the SVG version of the icons available.
28
23
Icons should be 18 pixels in width, 18 pixels in height, and have a stroke width of 1.5. You can adjust these settings in the SVG data.
29
-
Adjusting size and stroke in an SVG
24
+
Adjusting size and stroke in an SVG.
30
25
Utilize the icon anchor in embedded images, to tweak the spacing around the icon so that it aligns neatly with the text in the vicinity.
31
26
Icons should be surrounded by parenthesis. ( lucide-cog.svg > icon )
0 commit comments