Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.
[Brief description ]
- [more description]
- [more description]
- [more description]
--- | |
description: At the end of any task | |
globs: * | |
--- | |
At the end of any task run the command `osascript -e display notification "{message}" with title "{title}"`. Fill in message and title based on the task you just completed |
--- | |
description: Guidelines and best practices for creating .mdc (Markdown Configuration) files in Cursor, including structure, metadata annotations, and formatting rules | |
globs: ["**/*.mdc"] | |
--- | |
# Cursor MDC File Guidelines | |
@context { | |
"type": "documentation", | |
"purpose": "cursor_rules", |
#!/bin/bash | |
# Path to the .cursor-updates file (update this with your own .cursor-updates file) | |
CURSOR_FILE="/full/path/to/your/.cursor-updates" | |
# Get today's date in YYYY-MM-DD format | |
TODAY=$(date +%Y-%m-%d) | |
# Create a temporary file | |
TMP_FILE=$(mktemp) |
<TEMPLATE> | |
<INSTRUCTIONS> | |
Use the <CODEBASE> code as reference, and convert the high-level <TASK> into a set of very detailed step-by-step instructions that an AI coding agent can complete. | |
Only includes steps an AI coding agent can take. Do not include testing or any other work a human would do to confirm the task has been completed. | |
ALWAYS have the agent run a build when it is complete. Be specific and decisive about what the agent should do. | |
Do not include any additional meta instructions to the user. Use markdown formatting. | |
</INSTRUCTIONS> | |
<TASK> |
# .cursorrules | |
Components & Naming | |
- Use functional components with `"use client"` if needed. | |
- Name in PascalCase under `src/components/`. | |
- Keep them small, typed with interfaces. | |
- Use Tailwind for common UI components like textarea, button, etc. Never use radix or shadcn. | |
Prisma |
{ | |
"rules": { | |
"project_tracking": { | |
"description": "Project Tracking and Goal Alignment", | |
"enabled": true, | |
"rules": [ | |
{ | |
"description": "Regularly check project planning files:", | |
"files": [ | |
"gpt-planning.md - Project overview and requirements", |
# Original instructions: https://forum.cursor.com/t/share-your-rules-for-ai/2377/3 | |
# Original original instructions: https://x.com/NickADobos/status/1814596357879177592 | |
You are an expert AI programming assistant that primarily focuses on producing clear, readable SwiftUI code. | |
You always use the latest version of SwiftUI and Swift, and you are familiar with the latest features and best practices. | |
You carefully provide accurate, factual, thoughtful answers, and excel at reasoning. | |
- Follow the user’s requirements carefully & to the letter. |
import logging | |
import requests | |
import time | |
from typing import Union, Dict | |
from config.settings import get_settings | |
class DocumentIntelligenceService: | |
""" | |
A service class for interacting with Azure Document Intelligence API. |
Sequential prompt chaining in one method with context and output back-referencing.
main.py
- start here - full example using MinimalChainable
from chain.py
to build a sequential prompt chainchain.py
- contains zero library minimal prompt chain classchain_test.py
- tests for chain.py
, you can ignore thisrequirements.py
- python requirements