| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 3 | 23 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 3 | 6 | 0% |
What each file covers
Sections
0 shared · 3 only in A · 23 only in B- − Code Style
- − Services
- − CI/CD - build pipleline
- + Twenty Development Rules
- + Rules Overview
- + Core Guidelines
- + Code Quality
- + React Development
- + Testing & Quality
- + Internationalization
- + How Rules Work
- + Automatic Attachment
- + Manual Reference
- + Rule Types Used
- + Development Commands
- + Frontend Commands
- + Backend Commands
- + Usage Guidelines
- + For Developers
- + For AI Assistants
- + Contributing to Rules
- + Adding New Rules
- + Updating Existing Rules
- + Rule Format Reference
- + Rule Title
- + Migration from Legacy Format
Commands
neither file has anySection tags
0 shared · 3 only in A · 6 only in B- − build
- − code-style
- − deployment
- + test
- + lint-format
- + architecture
- + types
- + database
- + do-not
Line diff
nowtec/nowCRM · CLAUDE.md
@@ −1 @@
1# Code Style
2Read coding guidelines completed
3.cursor/rules
4
5
6# Services
7See all the services under **apps** directory
8
9
10# CI/CD - build pipleline
11.github/workflows/main.yaml - creates release, builds services, pushed to Github registry, sends notification to Telegram
nowtec/nowCRM · .cursor/rules/readme.mdc
@@ +1 @@
1---
2description: NOWCRM development rules and best practices
3globs: []
4alwaysApply: true
5---
6# Twenty Development Rules
7
8This directory contains NOWCRM's development guidelines and best practices in the modern Cursor Rules format (MDC). These rules are automatically applied based on file patterns and provide context-aware guidance to AI assistants.
9
10## Rules Overview
11
12### Core Guidelines
13- **architecture.mdc** - Project overview, technology stack, and infrastructure setup (Always Applied)
14
15### Code Quality
16- **typescript-guidelines.mdc** - TypeScript best practices and conventions (Auto-attached to .ts/.tsx files)
17- **code-style.mdc** - General coding standards and style guide (Auto-attached to code files)
18- **file-structure.mdc** - File and directory organization patterns (Auto-attached to config files)
19
20### React Development
21- **react-general-guidelines.mdc** - Core React development principles (Auto-attached to React files)
22
23### Testing & Quality
24- **testing-guidelines.mdc** - Testing strategies and best practices (Auto-attached to test files)
25
26### Internationalization
27- **translations.mdc** - Translation workflow and i18n setup (Auto-attached to locale files)
28
29## How Rules Work
30
31### Automatic Attachment
32Rules are automatically included in your AI context based on file patterns (globs). When you work on TypeScript files, the TypeScript guidelines are automatically loaded.
33
34### Manual Reference
35You can manually reference any rule using the `@ruleName` syntax:
36- `@react-general-guidelines` - Load React best practices
37- `@testing-guidelines` - Get testing recommendations
38
39### Rule Types Used
40- **Always Applied** - Loaded in every context (architecture.mdc, README.mdc)
41- **Auto Attached** - Loaded when matching file patterns are referenced
42- **Agent Requested** - Available for AI to include when relevant
43- **Manual** - Only included when explicitly mentioned
44
45## Development Commands
46
47### Frontend Commands
48
49todo:
50
51### Backend Commands
52
53todo:
54
55## Usage Guidelines
56
57### For Developers
58- Rules are automatically applied based on file context
59- Check rule descriptions to understand when they're activated
60- Use manual references (`@ruleName`) for additional context
61- Keep rules updated as the codebase evolves
62
63### For AI Assistants
64- Rules provide consistent guidance across conversations
65- Use rule context to maintain coding standards
66- Reference specific rules when making recommendations
67- Apply rule principles in code suggestions and reviews
68
69## Contributing to Rules
70
71### Adding New Rules
721. Create a new `.mdc` file in this directory
732. Include proper metadata headers with description and globs
743. Write clear, actionable guidelines with examples
754. Test the rule with relevant file patterns
765. Update this README if needed
77
78### Updating Existing Rules
791. Modify the rule content while preserving metadata
802. Test changes with affected file patterns
813. Ensure consistency with other rules
824. Update examples and best practices as needed
83
84## Rule Format Reference
85
86Each rule file uses the MDC format with metadata:
87
88```markdown
89---
90description: Brief description of the rule's purpose
91globs: ["**/*.ts", "**/*.tsx"] # File patterns for auto-attachment
92alwaysApply: false # Whether to always include this rule
93---
94
95# Rule Title
96
97Rule content in Markdown format...
98```
99
100## Migration from Legacy Format
101
102The rules have been migrated from the legacy `.md` format to the modern `.mdc` format, providing:
103- Better context awareness through file pattern matching
104- Improved organization with metadata headers
105- More flexible rule application strategies
106- Enhanced integration with Cursor's AI features
107
108For the most up-to-date version of these guidelines, always refer to the files in this directory.
@@ −1 +1 @@
1−# Code Style
2−Read coding guidelines completed
3−.cursor/rules
1+---
2+description: NOWCRM development rules and best practices
3+globs: []
4+alwaysApply: true
5+---
6+# Twenty Development Rules
47
8+This directory contains NOWCRM's development guidelines and best practices in the modern Cursor Rules format (MDC). These rules are automatically applied based on file patterns and provide context-aware guidance to AI assistants.
59
6−# Services
7−See all the services under **apps** directory
10+## Rules Overview
811
12+### Core Guidelines
13+- **architecture.mdc** - Project overview, technology stack, and infrastructure setup (Always Applied)
914
10−# CI/CD - build pipleline
11−.github/workflows/main.yaml - creates release, builds services, pushed to Github registry, sends notification to Telegram
15+### Code Quality
16+- **typescript-guidelines.mdc** - TypeScript best practices and conventions (Auto-attached to .ts/.tsx files)
17+- **code-style.mdc** - General coding standards and style guide (Auto-attached to code files)
18+- **file-structure.mdc** - File and directory organization patterns (Auto-attached to config files)
19+
20+### React Development
21+- **react-general-guidelines.mdc** - Core React development principles (Auto-attached to React files)
22+
23+### Testing & Quality
24+- **testing-guidelines.mdc** - Testing strategies and best practices (Auto-attached to test files)
25+
26+### Internationalization
27+- **translations.mdc** - Translation workflow and i18n setup (Auto-attached to locale files)
28+
29+## How Rules Work
30+
31+### Automatic Attachment
32+Rules are automatically included in your AI context based on file patterns (globs). When you work on TypeScript files, the TypeScript guidelines are automatically loaded.
33+
34+### Manual Reference
35+You can manually reference any rule using the `@ruleName` syntax:
36+- `@react-general-guidelines` - Load React best practices
37+- `@testing-guidelines` - Get testing recommendations
38+
39+### Rule Types Used
40+- **Always Applied** - Loaded in every context (architecture.mdc, README.mdc)
41+- **Auto Attached** - Loaded when matching file patterns are referenced
42+- **Agent Requested** - Available for AI to include when relevant
43+- **Manual** - Only included when explicitly mentioned
44+
45+## Development Commands
46+
47+### Frontend Commands
48+
49+todo:
50+
51+### Backend Commands
52+
53+todo:
54+
55+## Usage Guidelines
56+
57+### For Developers
58+- Rules are automatically applied based on file context
59+- Check rule descriptions to understand when they're activated
60+- Use manual references (`@ruleName`) for additional context
61+- Keep rules updated as the codebase evolves
62+
63+### For AI Assistants
64+- Rules provide consistent guidance across conversations
65+- Use rule context to maintain coding standards
66+- Reference specific rules when making recommendations
67+- Apply rule principles in code suggestions and reviews
68+
69+## Contributing to Rules
70+
71+### Adding New Rules
72+1. Create a new `.mdc` file in this directory
73+2. Include proper metadata headers with description and globs
74+3. Write clear, actionable guidelines with examples
75+4. Test the rule with relevant file patterns
76+5. Update this README if needed
77+
78+### Updating Existing Rules
79+1. Modify the rule content while preserving metadata
80+2. Test changes with affected file patterns
81+3. Ensure consistency with other rules
82+4. Update examples and best practices as needed
83+
84+## Rule Format Reference
85+
86+Each rule file uses the MDC format with metadata:
87+
88+```markdown
89+---
90+description: Brief description of the rule's purpose
91+globs: ["**/*.ts", "**/*.tsx"] # File patterns for auto-attachment
92+alwaysApply: false # Whether to always include this rule
93+---
94+
95+# Rule Title
96+
97+Rule content in Markdown format...
98+```
99+
100+## Migration from Legacy Format
101+
102+The rules have been migrated from the legacy `.md` format to the modern `.mdc` format, providing:
103+- Better context awareness through file pattern matching
104+- Improved organization with metadata headers
105+- More flexible rule application strategies
106+- Enhanced integration with Cursor's AI features
107+
108+For the most up-to-date version of these guidelines, always refer to the files in this directory.
