New 5 stack packs: Next.js, React, Node, FastAPI, Full-stack TS →

Make Cursor code
your way. From day one.

Describe your project in 60 seconds. Get a production-grade .cursor/ pack — rules, skills and a prompt library — tuned to your stack, your team and your style.

Free early access — no card needed Runs 100% in your browser 14-day refund
acme-invoices — Cursor
Explorer
.cursor
rules
00-project-core.mdc
05-code-style.mdc
10-nextjs.mdc
11-typescript.mdc
skills
code-review
new-page
write-tests
app
page.tsx
PROMPTS.md
10-nextjs.mdc05-code-style.mdcPROMPTS.md
---description: Next.js App Router conventionsglobs: "app/**/*,**/*.tsx"alwaysApply: false--- # Next.js (App Router) ## Server vs client- Components are Server Components by default.  Add "use client" only for state, effects or events.- Never import DB clients or secrets into client code. ## Data- Fetch in Server Components, not in useEffect.- Mutations → Server Actions, validated with zod,  then revalidatePath().- Be explicit about caching on every fetch. ## Env- Only NEXT_PUBLIC_ vars reach the browser.
Agent 4 rules applied
Add a settings page where users can update their billing email.
Cursor
Following your project rules:
00-project-core05-code-style10-nextjs02-security
  • app/settings/page.tsx as a Server Component
  • Server Action with zod validation + auth check
  • loading.tsx & error.tsx states
  • Vitest test for the action
Ask, plan, or build… ⌘ L

Tuned packs for the stacks developers actually ship with

NNext.js RReact + Vite JSNode · Express · Fastify · NestJS · Hono PyPython / FastAPI TSFull-stack TypeScript
The problem

Cursor is brilliant.
Without rules, it's guessing.

Out of the box the agent doesn't know your stack, your conventions or how your team ships. So you repeat yourself — and clean up after it.

Without VibeRules
Add a page to edit the billing email.
→ Creates pages/settings.tsx (wrong router), fetches in useEffect, no validation, no tests.
No — we use the App Router. And zod. And Vitest. Again.
With VibeRules
Add a page to edit the billing email.
→ app/settings/page.tsx as a Server Component, Server Action with zod + auth check, loading/error states, and a Vitest test. Summarizes what to verify.
Perfect. Ship it.

Same corrections every day

"Use the App Router." "No any." "Tests next to the file." Typed again and again.

Inconsistent code

Every generated file follows a different pattern. Reviews take longer, the codebase drifts.

Good rules take hours

Writing solid .mdc rules is research and trial-and-error. Most devs never get to it.

How it works

Three steps. Two minutes.

No account, no install, no API keys. Your description never leaves your browser.

01

Describe your project

Stack, framework, team size, testing and style preferences — plus a sentence about what you're building.

stackNext.js
team2–5
testingtest-first
stylingTailwind
02

Preview every file

Read each rule, skill and prompt in full right in the browser. What you see is exactly what you get.

---
alwaysApply: true
---
# Code style
- Work test-first…
03

Drop it into your repo

Download the zip, copy .cursor/ to your repo root. Cursor follows your conventions from the next prompt.

.zip
viberules-acme.zip
12 files · 38 KB
✓ ready
What's in the pack

Everything Cursor needs to
work like a senior teammate.

Opinionated where it matters, editable everywhere. Plain Markdown you own.

6–8 tailored rules

Proper .mdc files with descriptions, globs and alwaysApply — so the right rule loads at the right time.

00-project-core.mdccontext & definition of done
05-code-style.mdcyour testing, typing & tone choices
10-nextjs.mdcframework conventions
02-security.mdc · 01-workflow.mdcsecurity & git

3 starter skills

Step-by-step playbooks the agent follows on request.

code-review
write-tests
new-page / endpoint

Prompt library

10–15 copy-paste prompts for planning, debugging, refactoring and PRs.

CopyFind the root cause (not just the symptom), explain it in 2–3 sentences, apply the fix and add a regression test.

Private by design

Generated entirely in your browser. No upload, no tracking of your project, no API keys. Works offline.

✓ Zero data leaves your machine
✓ Unlimited packs, every project
Pricing

Pay once. Use it everywhere.

No subscription. Less than an hour of your time — saved in the first afternoon.

VibeRules Lifetime

● Early-bird price
$29$49one-time
  • Unlimited packs — every stack, every project
  • 6–8 rules + 3 skills + prompt library per pack
  • All 5 stacks — Next.js, React, Node, FastAPI, Full-stack TS
  • Template updates as we add stacks
Get VibeRules →

Secure checkout · Instant access by email · Taxes handled for you

14-day refund, no questions

Not useful? Reply to your receipt and get your money back.

Preview before you pay

Every file is visible in the generator. No surprises.

Real human support

A rule doesn't fit your setup? Email us — we'll help you adapt it.

FAQ

Straight answers.

Can I see what I get before buying?

Yes. The generator shows every file in full, in your browser, before you pay. What you preview is exactly what you download.

Does it use Cursor's current rules format?

Yes — .mdc files in .cursor/rules/ with description, globs and alwaysApply frontmatter, plus skills in .cursor/skills/. All plain text you can edit anytime.

Is my project description sent anywhere?

No. The pack is generated entirely in your browser. Nothing you type is uploaded.

My stack isn't listed.

Pick the closest one — the core, style, security and workflow rules fit any project. Tell us what you use and we'll prioritize it.

What if it's not for me?

Email us within 14 days for a full refund. No forms, no hoops.

Stop re-explaining your stack.

Build your pack in two minutes. Preview it free.