Hey everyone! Below are the rules for cursor (.cursorrules file) I have been using for Claude Sonnet 3.5 and 3.7 with Cursor AI and Next.js.

I've been building apps with cursor for a while and have learned a lot over the past few months. Something that's very important is having a good cursorrules file. It will make the difference between building a clean, well-written app and creating a messy codebase.

Below is the .cursorrules file I use. Make sure to adjust this so it works with your own setup / libraries.

App summary:

{{write a summary of your app here}}

Target Audience

{{replace with your target audience}}

Tech stack

• Next.js (app router) 15.1.3
• Tailwind 3.4.1
• Typescript 5
• React-icons 5.3.0
• m3 macbook (important in for cursor to know for generating commands)
• Add any libs you may use

These are your rules, you must read these before every implementation your make and make sure you adhere to them:

- When writing classes, make sure to always use tailwind classes and colors. Make sure to always check that you use the content colors for foreground. Look at the existing components and use similar classes.

- For icons, use the react-icons library. (change if needed)

- Always use best practices and write clean, simple and readable code. Split up in multiple files and components if needed. Aim for readability and maintainability.

- Do not remove any existing code and functionalities unless asked. Only do as asked.

- Do not use the ternary operator unless it's very readable

- I use next.js app router (change if needed), so make sure to use "use client" where needed.

- Design mobile first, and make sure to use the tailwind breakpoints.

- Use the next/image component for images.

- Aim for simplicity and readability. A simpler design is better. Do not add unnecessary complexity or additional divs / components.

- Do not add unnecessary comments

- Reason and think step by step

- Use semantic HTML tags where possible

- Keep Good SEO in mind

- Don't use CDN links for libraries. Use local files

- I work on a mac with an M3 chip (change if needed)

Before generating any code, read ALL these rules again carefully and make sure you adhere to them. Do only as asked and write as little code as possible. Very important! only do as asked!

The Huzzler Launch Arena is finally live 🥳

Hello everyone! I am very excited to announce the release of the Huzzler Launch Arena!

It's a weekly competition where you can submit projects and compete in a week-long battle to get as many votes as possible.

🏆 Why join the Launch Arena?

• Top 3 projects are pinned for a full week at the top of the page (= lots of free traffic to your app)
• A gold / bronze / silver badge
• A Platinum / Diamond / Legendary status badge for 100, 500 or 1000 votes

How it's different from product hunt:

• Competition resets weekly
• Made for smaller startups / indie hackers
• Full integration with Huzzler Community
• I'm adding systems to prevent false votes (will be very strict)
• You can't pay for votes or pay to get to the top of the list, it's a fair competition

Join the Huzzler Launch Arena here: https://huzzler.so/arena

I kindly invite everyone reading this to join. It took a lot of work to create this and any feedback (good or bad) is greatly appreciated!

Thanks a lot guys! 😁

I'm curious to know how much time you guys spend on building your side projects.

I'm curious to know how you guys are handling the marketing of you app(s)? Do you do paid advertisements? Do you contact businesses directly?

Hello everyone. I'd love to hear some of your opinions on this early version of Huzzler.

1. What features would make this most valuable for you as an indie hacker?
2. Would you use this platform to share your projects and get feedback?
3. What's missing that would make you want to join and participate?
4. Any suggestions on how to build a thriving, supportive community?

I will consider all your ideas and feedback! I also want to thank all of our early active members, particularly @harvansh and @samm.

Thank you so much!

I invite all members to join the Huzzler Discord. It will be a positive community where we all provide feedback and help each other grow. You can join here: https://discord.gg/rjyj5hj7cW

Everyone is welcome!

Thanks guys

I can't decide between these two versions of the USPs for huzzler. The first explain Huzzler and are to the point.

The second variant is longer but explains it better.

Thanks for the feedback!

I was recently reading a Google doc called "The $1M MVP" by Pat Walls and just realised how insanely valuable it is for founders. It contains concrete information on what to do and what not to do when building an MVP and takes like 15 minutes to read. It will save you years of time and headache.

Check it out here: https://x.com/thepatwalls/status/1856341863910760727

To just give an example, check out the excerpt from the doc below:

For example, let’s say you want to build an iPhone app. 

Option 1:

- Spend 6 months building an app

- Bang your head against the wall figuring out the tech, authentication, App store approval etc etc

- Take wild guesses at what features to build and hope for the best.

- Launch the app and hope for the best

- No customers, THEN you have to figure out marketing (which could take another 6 months).

- A year later, you MIGHT have a validated idea, but you might not.

Result: 12+ months of work, potentially nothing to show for it.

Option 2:

- In 24 hours create a landing page about your upcoming app. 

- You share that landing page with your network, online, and to potential customers

- The landing page collects emails through a waitlist. 

- You reach out to those customers and ask them about the most important features for them.

- You ask these customers what features they would pay for.

- You know exactly what features to build.

- You build up a strong waitlist

- Then you build the app in 1 month, and potentially have paying customers on Day 1, and you know it’s already validated.

Result: In 24 hours, you got enough information that helped inform your decision to build even further.

The MVR mindset is kind of like a “fake it til you make it” approach.

Sell the dream first, with a super stripped down approach. You don’t need all of the fancy stuff. Fancy logo, growth strategy, all the features, just focus on getting information.

Hey guys. I just added notifications to Huzzler. What do you think about the notification dropdown design? Would you change / improve anything?

Thanks!

For anyone who needs to moderate user generated content: OpenAI offers a free Moderation API. It can can be used to filter out harmful images or content and I'm using it to moderate Huzzler (and it works great).

Thought this may come in handy for some of you.