add-cursor-prompt #25
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kemborah
requested changes
Dec 10, 2024
CURSOR.md
Outdated
| You are an expert in JavaScript, ReactJS, Node.js, MongoDB, mongoose, and TailwindCSS. | ||
|
|
||
| Code Style and Structure | ||
| - Write Clear and Functional JavaScript: Use functional programming patterns, React hooks, and modular, reusable code structures. Avoid object-oriented programming when possible. |
There was a problem hiding this comment.
no hooks except for useEffect, useState
| - Modern Frontend Standards: Use Tailwind CSS for styling and React functional components for UI. Default to responsive design using grids and embrace modern layout principles. | ||
| - Backend Consistency: Ensure APIs have a single responsibility per endpoint. Use flat data structures and standardize API responses in {ok, data, error} format. | ||
| - Optimize Collaboration: Keep pull requests (PRs) small and focused to ensure seamless deployments with minimal conflicts. | ||
| - Leverage Monorepo: Use a single repository for related codebases to improve code reuse and reduce overhead. |
There was a problem hiding this comment.
dont think this will be useful for cursor
| - Focus on Simplicity (KIS): Break complex logic into smaller, readable pieces. Use early returns and avoid unnecessary abstractions. | ||
| - Encourage Consistent Practices: Write code that looks authored by a single person across projects. Prioritize clarity, maintainability, and adherence to shared conventions. | ||
| - Descriptive Naming: Use meaningful and precise names for variables and functions (e.g., fetchUsers, isLoading, handleDelete). | ||
| - Scalable File Structures: Organize projects into predictable folders like components, scenes, services, and utils for a consistent architecture. |
There was a problem hiding this comment.
also this not sure it can organise files
| - Constants: Use UPPER_CASE_WITH_UNDERSCORES for constants (e.g., API_BASE_URL, DEFAULT_PAGE_SIZE). | ||
| - React Components: Use PascalCase for component names (e.g., UserProfile, LoginButton). | ||
| - CSS/Tailwind Utilities: Follow kebab-case for Tailwind utility classes (e.g., text-gray-700, max-w-7xl). | ||
| - Route Parameters: Use snake_case for dynamic route parameters (e.g., /users/:user_id). |
There was a problem hiding this comment.
i wouldn't say user_id , just :id since we are already saying user on the first part of the sentence
|
the most important is that it works |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.