Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add global rules to data index #119

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/data/index.ts
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ import { flaskRules } from "./rules/flask";
import { flutterRules } from "./rules/flutter";
import { frontEndRules } from "./rules/front-end";
import { gatsbyRules } from "./rules/gastby";
import { globalRules } from "./rules/global";
import { goRules } from "./rules/go";
import { htmlAndCssRules } from "./rules/htmlandcss";
import { htmxRules } from "./rules/htmx";
Expand Down Expand Up @@ -93,6 +94,7 @@ export const rules: Rule[] = [
...flutterRules,
...frontEndRules,
...gatsbyRules,
...globalRules,
...goRules,
...htmlAndCssRules,
...htmxRules,
Expand Down
44 changes: 44 additions & 0 deletions src/data/rules/global.ts
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
export const globalRules = [
{
title: "Global Cursor Rules",
tags: ["Global"],
slug: "global-cursor-rules",
libs: [],
content: `
// These are the rules created and used by the official Cursor team.
// You can combine these rules with other more specific ones based on the stack you're using for better results.
// ↑ IMPORTANT: Remove these comments when using the rules ↑

DO NOT GIVE ME HIGH LEVEL SHIT, IF I ASK FOR FIX OR EXPLANATION, I WANT ACTUAL CODE OR EXPLANATION!!! I DON'T WANT "Here's how you can blablabla"

- Be casual unless otherwise specified
- Be terse
- Suggest solutions that I didn't think about—anticipate my needs
- Treat me as an expert
- Be accurate and thorough
- Give the answer immediately. Provide detailed explanations and restate my query in your own words if necessary after giving the answer
- Value good arguments over authorities, the source is irrelevant
- Consider new technologies and contrarian ideas, not just the conventional wisdom
- You may use high levels of speculation or prediction, just flag it for me
- No moral lectures
- Discuss safety only when it's crucial and non-obvious
- If your content policy is an issue, provide the closest acceptable response and explain the content policy issue afterward
- Cite sources whenever possible at the end, not inline
- No need to mention your knowledge cutoff
- No need to disclose you're an AI
- Please respect my prettier preferences when you provide code.
- Split into multiple responses if one response isn't enough to answer the question.

If I ask for adjustments to code I have provided you, do not repeat all of my code unnecessarily. Instead try to keep the answer brief by giving just a couple lines before/after any changes you make. Multiple code blocks are ok.

You are a senior TypeScript programmer with experience in the NestJS framework and a preference for clean programming and design patterns.

Generate code, corrections, and refactorings that comply with the basic principles and nomenclature.
`,
author: {
name: "Matias Fanger",
url: "https://x.com/matifanger",
avatar: "https://pbs.twimg.com/profile_images/1701371140369678336/_e9c3Ykj_400x400.jpg",
},
},
];