data-formulator / rules
microsoft/data-formulator/.cursor/rules/backend-test-conventions.mdc
Backend Python test conventions (pytest)
No other project uses it yet
The rules real projects give Cursor's agent, from .cursor/rules.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
microsoft/data-formulator/.cursor/rules/backend-test-conventions.mdc
Backend Python test conventions (pytest)
No other project uses it yet
microsoft/data-formulator/.cursor/rules/dataframe-serialization.mdc
All DataFrame-to-records conversion for API responses, streaming events, or frontend-visible data MUST use the centralized helpers in data_formulator.datalake.parquet_utils: pandas.DataFrame.to_json(orient='records') defaults to date_format='epoch', which serializes datetime columns as epoch milliseconds (e.g. 1773532800000). The frontend interprets these as plain numbers and renders them with commas (1,773,532,800,000) instead of formatted dates. df_to_safe_records enforces date_format='iso' and default_handler=str, ensuring datetimes become ISO-8601 strings and exotic types degrade gracefully. Internal data processing that never reaches the frontend or JSON serialization (e.g. Kusto SDK metadata parsing, Vega-Lite…
No other project uses it yet
microsoft/data-formulator/.cursor/rules/dev-guides-first.mdc
Require reading dev-guides before development and keeping docs in sync
No other project uses it yet
microsoft/data-formulator/.cursor/rules/error-response-safety.mdc
Prevent information exposure through exception messages in HTTP responses
microsoft/data-formulator/.cursor/rules/frontend-test-conventions.mdc
Frontend TypeScript test conventions (Vitest)
microsoft/data-formulator/.cursor/rules/i18n-no-hardcoded-strings.mdc
No hardcoded UI strings — use i18n translation keys
microsoft/data-formulator/.cursor/rules/implementation-review-checklist.mdc
Require structural code review after implementation before final response
microsoft/data-formulator/.cursor/rules/incremental-development-cadence.mdc
Enforce step-by-step implementation with design-doc checks, tests, and i18n after each step
microsoft/data-formulator/.cursor/rules/language-injection-conventions.mdc
Language injection conventions for LLM Agent prompts
microsoft/data-formulator/.cursor/rules/log-sanitization.mdc
Prevent sensitive data leakage in server-side log messages
microsoft/data-formulator/.cursor/rules/package-manager-conventions.mdc
Use Yarn only, never npm/pnpm
microsoft/data-formulator/.cursor/rules/path-safety.mdc
路径安全编码规范 — 编辑路由/Agent/Loader/Workspace/知识库代码时自动提醒
microsoft/data-formulator/.cursor/rules/test-driven-workflow.mdc
测试优先开发与测试保护规则。确保新功能/Bug 修复必须有测试覆盖,测试失败时先诊断后修改。
microsoft/data-formulator/.cursor/rules/unified-error-protocol.mdc
Unified error handling protocol for backend and frontend
microsoft/rushstack/.cursor/rules/rush.mdc
You are a Rush monorepo development and management expert. Your role is to assist with Rush-related tasks while following these key principles and best practices: The standard directory structure for…
No other project uses it yet
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.