LLM Cursor Rules
Welcome to my repository of go-to rules for using Cursor and LLMs in software development!
Loading actions...
Skill content
Main instructions and any bundled files for this skill.
LLM Cursor Rules
Welcome to my repository of go-to rules for using Cursor and LLMs in software development!
About
This repository contains my opinionated rules and best practices for leveraging Large Language Models (LLMs) and the Cursor editor in software development workflows. The rules are designed to enhance productivity and code quality when working with AI-assisted coding tools.
Rules
Currently, the repository includes two sets of rules:
- Swift and SwiftUI Development Rules
- Next.js 14 Development Rules
These rules cover best practices, code structure, state management, performance optimization, and more for their respective domains.
Usage
Feel free to use these rules in your own projects or as a starting point for developing your own set of best practices. If you find them helpful, I'd appreciate attribution (see below).
Contributing
Contributions are welcome! If you have suggestions for improvements or additional rules, please feel free to open an issue or submit a pull request.
Attribution
If you use parts of this work in your own projects or writings, please provide attribution by referencing this repository and my X (formerly Twitter) account: @RayFernando1337
Live Coding
I regularly livestream coding sessions where I use Cursor and apply these rules. You can watch these streams on my YouTube channel: Ray Fernando
Connect
- Follow me on X: @RayFernando1337
- Subscribe to my YouTube channel: Ray Fernando
License
This project is open source. While I welcome sharing and usage of this work, I kindly request that you provide attribution as mentioned above.
Related Skills
Frontend Typescript Linting.mdc
TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...
2. Apply Deepthink Protocol (reason about dependencies
risks