|
29 | 29 | 10. **Respect .editorconfig**: Adhere to the `.editorconfig` file for consistent code style across all IDEs. |
30 | 30 | 11. **Prefer razor.cs code-behind files**: Use `.razor.cs` files for component logic instead of @code blocks in `.razor` files. |
31 | 31 | 12. **Prefer razor.scss files**: Use `.razor.scss` files for component styles instead of inline styles in `.razor` files. |
| 32 | +13. **After applying changes, make sure project builds successfully**: Always verify that the project builds without errors after making changes. |
32 | 33 |
|
33 | | -### Rules for Using DeepWiki |
| 34 | +### Rules for Using MCP |
34 | 35 |
|
35 | | -The deepwiki's `ask_question` mcp tool is essential for this project. Use it not only to answer questions but also to guide **code modifications**. |
36 | | -For the topics below, you **MUST** consult `deepwiki` to find correct implementations and usage patterns before writing or changing any code. |
37 | | - |
38 | | -**RULE 1:** If a task (which includes answering a question or performing a code modification) involves the use of bit BlazorUI components (e.g., `BitButton`, `BitTooltip`, `BitTextField`), or refers to `bitplatform`, `bit Bswup`, `bit Butil`, `bit Besql`, or `bit Boilerplate`, |
39 | | -you **MUST** use the deepwiki's `ask_question` mcp tool to find the correct implementation and usage patterns before writing or changing any code. |
40 | | - |
41 | | -**RULE 1 Command:** |
42 | | -`deepwiki fetch bitfoundation/bitplatform` |
| 36 | +**RULE 1:** If a task (question or code modification) involves the use of bit BlazorUI components (e.g., `BitButton`, `BitTooltip`, `BitTextField`), |
| 37 | +or refers to `bitplatform`, `bit Bswup`, `bit Butil`, `bit Besql`, or `bit Boilerplate`, or involves UI components without explicitly specifying their UI toolkit, |
| 38 | +you **MUST** use the deepwiki's `ask_question` mcp tool to find the correct implementation and usage patterns of `bitfoundation/bitplatform` deep wiki before writing or changing any code. |
43 | 39 |
|
44 | 40 | **End of RULE 1** |
45 | 41 |
|
46 | | -**RULE 2:** If a task (question or code modification) involves mappers, or refers to `mapperly`, `map`, `project`, or `patch`, you **MUST** use the deepwiki's `ask_question` mcp tool to find the correct implementation before writing or changing any code. |
47 | | - |
48 | 42 | **RULE 2 Command:** |
49 | | -`deepwiki fetch riok/mapperly` |
50 | | - |
51 | | -**End of RULE 2** |
52 | | - |
53 | | -**RULE 3:** If a task (question or code modification) involves .NET MAUI, or refers to `xaml`, `Android`, `iOS`, or `Windows`, you **MUST** use the deepwiki's `ask_question` mcp tool to find the correct implementation before writing or changing any code. |
54 | | - |
55 | | -**RULE 3 Command:** |
56 | | -`deepwiki fetch dotnet/maui` |
57 | | - |
58 | | -**End of RULE 3** |
59 | | - |
60 | | -**RULE 4:** If a task (question or code modification) involves Hangfire, or refers to `background job` or `recurring jobs`, you **MUST** use the deepwiki's `ask_question` mcp tool to find the correct implementation before writing or changing any code. |
61 | | - |
62 | | -**RULE 4 Command:** |
63 | | -`deepwiki fetch HangfireIO/Hangfire` |
64 | | - |
65 | | -**End of RULE 4** |
66 | | - |
67 | | -**RULE 5:** If a task (question or code modification) involves file storage, or refers to `fluent storage` or `S3`, you **MUST** use the deepwiki's `ask_question` mcp tool to find the correct implementation before writing or changing any code. |
68 | | - |
69 | | -**RULE 5 Command:** |
70 | | -`deepwiki fetch robinrodricks/FluentStorage` |
71 | | - |
72 | | -**End of RULE 5** |
73 | | - |
74 | | -**RULE 6 Command:** |
75 | 43 | Use Playwright MCP tools like browser_navigate for URLs, browser_click for interactions, and browser_snapshot for page analysis. |
76 | 44 |
|
77 | | -**End of RULE 6** |
| 45 | +**End of RULE 2** |
0 commit comments