nanotron / rules
huggingface/nanotron/.cursor/rules/performance-optimization.mdc
Better pattern:
The rules real projects give Cursor's agent, from .cursor/rules.
huggingface/nanotron/.cursor/rules/performance-optimization.mdc
Better pattern:
huggingface/nanotron/.cursor/rules/philosophy.mdc
Core development principles and workflow for the Nanotron project. Apply when discussing project architecture, planning new features, or reviewing code structure.
huggingface/nanotron/.cursor/rules/pipeline-parallelism.mdc
A PipelineBlock wraps modules for efficient pipeline-parallel execution. Each block operates on a specific device and communicates with other pipeline stages through P2P. When passing data between pipeline stages: Design modules with clean interfaces for pipeline parallelism: Use TensorPointer to reference tensors across pipeline stages without copying: In pipeline parallelism, different tensors are only available on specific pipeline ranks (see src/nanotron/data/dataloader.py):
huggingface/nanotron/.cursor/rules/project-overview.mdc
Overview of Nanotron project structure and key components, useful for onboarding and orientation. Apply when discussing project architecture or organization.
huggingface/nanotron/.cursor/rules/tensor-parallelism.mdc
No summary in the file. Open it to read it.
huggingface/nanotron/.cursor/rules/troubleshooting.mdc
Common issues and solutions for Nanotron development. Apply when debugging performance, memory, or training problems.
openlit/openlit/.cursor/rules/coding-agents-convention.mdc
Canonical coding-agent telemetry schema, inbound mappings, and data contracts. Applies to semantic conventions, emission, processing, and readers—not hook implementation mechanics.
openlit/openlit/.cursor/rules/coding-agents-hook.mdc
Authoring and testing coding-agent hook adapters, including payload probing, session state, capture modes, and plugin manifests. Consult the telemetry convention when changing canonical attributes.
openlit/openlit/.cursor/rules/controller-design.mdc
Design principles and invariants for the OpenLIT controller (Go agent that discovers and instruments LLM workloads) and the Agents-page server layer that consumes its data.
openlit/openlit/.cursor/rules/documentation.mdc
Standards for OpenLIT documentation, MDX structure, navigation, examples, and terminology.
openlit/openlit/.cursor/rules/frontend.mdc
UI, messaging, project hierarchy, and CE/enterprise-boundary guidance for OpenLIT client presentation code.
openlit/openlit/.cursor/rules/js-sdk-genai-framework-instrumentation.mdc
Guide for implementing JS SDK agent and framework instrumentations, such as LangChain, LangGraph, OpenAI Agents, Claude Agent SDK, Google ADK, and Vercel AI.
openlit/openlit/.cursor/rules/js-sdk-genai-instrumentation.mdc
Guide for aligning JS SDK GenAI provider instrumentations with OTel semantic conventions and the Python SDK reference implementation.
openlit/openlit/.cursor/rules/security-testing.mdc
Authorization, input validation, CE boundary, secrets, and test guidance for OpenLIT server code.
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/cursor-rules.mdc
Follow these rules when the user's request involves creating, modifying, organizing, or structuring Cursor rules within the project
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/capitalization.mdc
Capitalize proper names of products, features, pages, and tools. In step-by-step instructions, match the exact capitalization of UI elements. Don't capitalize words that are not proper nouns solely for emphasis. Don't capitalize: - Articles: a, an, the (unless first word) - Conjunctions: and, but, or (unless >5 letters or first word) - Prepositions: of, in, to, for (unless >5 letters or first word)
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/categories.mdc
Guidelines for placing documentation in the correct category within the docs/source directory
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/formatting.mdc
Use consistent formatting to help convey meaning and improve readability. All formatting should be consistent throughout technical content.
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/general.mdc
Follow these rules when working with any documentation in the NeMo Agent Toolkit project.
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/latinisms.mdc
Guidelines for avoiding Latin phrases in documentation to simplify content for a global audience
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.