mirror of
https://github.com/simstudioai/sim.git
synced 2026-01-09 15:07:55 -05:00
* feat(kb): emcn alignment; sidebar: popover primary; settings-modal: expand * feat: EMCN breadcrumb; improvement(KB): UI * fix: hydration error * improvement(KB): UI * feat: emcn modal sizing, KB tags; refactor: deleted old sidebar * feat(logs): UI * fix: add documents modal name * feat: logs, emcn, cursorrules; refactor: logs * feat: dashboard * feat: notifications; improvement: logs details * fixed random rectangle on canvas * fixed the name of the file to align * fix build --------- Co-authored-by: waleed <walif6@gmail.com>
48 lines
1.5 KiB
Markdown
48 lines
1.5 KiB
Markdown
# Expert Programming Standards
|
|
|
|
**You are tasked with implementing solutions that follow best practices. You MUST be accurate, elegant, and efficient as an expert programmer.**
|
|
|
|
---
|
|
|
|
# Role
|
|
|
|
You are a professional software engineer. All code you write MUST follow best practices, ensuring accuracy, quality, readability, and cleanliness. You MUST make FOCUSED EDITS that are EFFICIENT and ELEGANT.
|
|
|
|
## Logs
|
|
|
|
ENSURE that you use the logger.info and logger.warn and logger.error instead of the console.log whenever you want to display logs.
|
|
|
|
## Comments
|
|
|
|
You must use TSDOC for comments. Do not use ==== for comments to separate sections. Do not leave any comments that are not TSDOC.
|
|
|
|
## Global Styles
|
|
|
|
You should not update the global styles unless it is absolutely necessary. Keep all styling local to components and files.
|
|
|
|
## Bun
|
|
|
|
Use bun and bunx not npm and npx.
|
|
|
|
## Code Quality
|
|
|
|
- Write clean, maintainable code that follows the project's existing patterns
|
|
- Prefer composition over inheritance
|
|
- Keep functions small and focused on a single responsibility
|
|
- Use meaningful variable and function names
|
|
- Handle errors gracefully and provide useful error messages
|
|
- Write type-safe code with proper TypeScript types
|
|
|
|
## Testing
|
|
|
|
- Write tests for new functionality when appropriate
|
|
- Ensure existing tests pass before completing work
|
|
- Follow the project's testing conventions
|
|
|
|
## Performance
|
|
|
|
- Consider performance implications of your code
|
|
- Avoid unnecessary re-renders in React components
|
|
- Use appropriate data structures and algorithms
|
|
- Profile and optimize when necessary
|