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.
huggingface/cadgenbench/.cursor/rules/code-audit.mdc
Pre-launch checklist for shipped code paths. Run before announcing the leaderboard publicly. Style basics (Python 3.12+, type hints, sync only, no fallbacks, no silent exception swallowing) live in style.mdc.
huggingface/cadgenbench/.cursor/rules/project-context.mdc
Fixtures live in two HF dataset repos (cadgenbench-data public, cadgenbench-data-gt private) — resolved at runtime by cadgenbench.common.paths. There is no data/ directory in this repo any more. The set is still shifting (parts get added, removed, or replaced as authoring catches issues), so do not hardcode fixture names or counts anywhere; treat the inputs dataset as the source of truth. Fixtures (inputs + ground truth) and authoring/submitter sanity scripts live in two HF dataset repos (cadgenbench-data, cadgenbench-data-gt), resolved at runtime…
huggingface/cadgenbench/.cursor/rules/prose-audit.mdc
Auditable rules for prose on public-facing surfaces (READMEs, docs/, dataset cards, Space app text). Process docs under space-setup/ are exempt. Style basics (em-dashes, AI tells, lowercase) live in style.mdc, not duplicated here.
huggingface/cadgenbench/.cursor/rules/style.mdc
No summary in the file. Open it to read it.
huggingface/cadgenbench/.cursor/rules/workspace-layout.mdc
Workspace repo layout reminder
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.