posthog / rules
PostHog/posthog/.cursor/rules/django-python.mdc
Rules for writing Python services at PostHog (Python servers powered by the Django framework)
The rules real projects give Cursor's agent, from .cursor/rules.
PostHog/posthog/.cursor/rules/django-python.mdc
Rules for writing Python services at PostHog (Python servers powered by the Django framework)
PostHog/posthog/.cursor/rules/rust.mdc
Rules for writing Rust services at PostHog. Focuses on writing async Rust with Tokio and encoding general Rust best practices from the Rust book and docs.
vercel/chatbot/.cursor/rules/ultracite.mdc
Ultracite Rules - AI-Ready Formatter and Linter
microsoft/data-formulator/.cursor/rules/dev-guides-first.mdc
Require reading dev-guides before development and keeping docs in sync
triggerdotdev/trigger.dev/.cursor/rules/repo.mdc
understanding the structure of the monorepo
0xJacky/nginx-ui/.cursor/rules/backend.mdc
Follow consistent coding standards and formatting rules across the project to enhance clarity. ## 5. Documentation and Comments - **English Language:** All code comments and documentation should be written in English
refly-ai/refly/.cursor/rules/00-language-priority.mdc
variable names, function names, class names, and other identifiers MUST use English words** - **ALL documentation (READMEs, API docs, inline documentation) MUST be in English** - **ALL Git commit messages MUST
refly-ai/refly/.cursor/rules/04-code-formatting.mdc
description: globs: alwaysApply: true --- # Code Formatting Guidelines This document defines the code formatting standards to ensure consistency and readability. ## Formatting Tools The project uses Biome for code formatting and linting
refly-ai/refly/.cursor/rules/05-code-organization.mdc
components - Avoid overusing global state - Consider adopting a predictable state container for complex applications - Document the structure of shared state
refly-ai/refly/.cursor/rules/06-api-structure.mdc
functionality ## Best Practices - Follow NestJS module structure - Use dependency injection - Implement proper error handling - Document APIs with OpenAPI - Schema-First Development - All API contracts must be defined in [schema.yml
airweave-ai/airweave/.cursor/rules/airweave-overview.mdc
General overview of Airweave.
airweave-ai/airweave/.cursor/rules/connector-development-end-to-end.mdc
backend/airweave/platform/auth/yaml/dev.integrations.yaml` - ✅ Monke authentication configured in `monke/configs/{short_name}.yaml` (Composio or direct) - ✅ API documentation loaded into context Your task is to write the code. The human will handle testing
airweave-ai/airweave/.cursor/rules/fern-docs-generation.mdc
globs: **/fern/** alwaysApply: false --- # Fern Documentation Generation System - Internal Guide ## Overview The custom internal Fern documentation generator automatically creates MDX documentation for Airweave connectors by introspecting Python source code using
airweave-ai/airweave/.cursor/rules/integrations-yaml.mdc
Description of how the integrations yaml works.
airweave-ai/airweave/.cursor/rules/monke-testing-guide.mdc
bytes, filename) """ llm = LLMClient(model_override=model) instruction = ( f"Generate content for a technical document or specification. " f"You MUST include the literal token '{token}' in the content. " f"Make
airweave-ai/airweave/.cursor/rules/search-module.mdc
/search.py,**/domains/search/** alwaysApply: false --- # Airweave Search Rules > **WARNING — PARTIALLY OUTDATED (March 2026)** > > This file documents the **legacy V1 search module** (`airweave/search/`), which > uses an operation-based pipeline with Qdrant, Cerebras/OpenAI/Groq
airweave-ai/airweave/.cursor/rules/source-connector-implementation.mdc
Types There are two base entity types: 1. **ChunkEntity** - Text-based entities (tasks, messages, documents, etc.) 2. **FileEntity** - File attachments (PDFs, images, etc.) ### Basic Structure ```python """Entity schemas for {Connector
microsoft/rushstack/.cursor/rules/rush.mdc
Execute operations affecting the entire repository or multiple projects - Features: - Strict parameter validation and documentation - Support for global and batch commands - Suitable for standardized workflows - Use cases: Dependency installation, building
vercel/streamdown/apps/website/.cursor/.cursor/rules/ultracite.mdc
Ultracite Rules - AI-Ready Formatter and Linter
vercel/streamdown/apps/website/.cursor/rules/ultracite.mdc
Ultracite Rules - AI-Ready Formatter and Linter
Instruction files for Cursor's agent, kept in .cursor/rules/ as .mdc files.
A rule can apply only to files matching a pattern, or only when the agent asks for it. AGENTS.md always applies.
Copy the .mdc file into your project's .cursor/rules/ directory and adjust its globs.
Open a rule to see its discussion. Reports from people and their agents are coming.