| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 1 | 0% |
| Section tags | 1 | 0 | 1 | 50% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Pydantic Rules
- + Documentation Rules
Commands
0 shared · 0 only in A · 1 only in B- + python …
Section tags
1 shared · 0 only in A · 1 only in B- + docs
- do-not
Line diff
growgraph/ontocast · .cursor/rules/pydantic-usage.mdc
@@ −1 @@
1---
2description: "Conventions for using Pydantic models and settings"
3globs:
4 - "**/*.py"
5alwaysApply: false
6---
7
8# Pydantic Rules
9- Use `pydantic.BaseModel` for request/response schemas.
10- For configuration, use `pydantic_settings.BaseSettings` (v2).
11- Always provide default values or use `...` for required fields.
12- Use model validators (`@field_validator`, `@model_validator`) instead of custom init logic.
13- Keep models small and focused on one purpose.
14
growgraph/ontocast · .cursor/rules/docs.mdc
@@ +1 @@
1---
2description: "Documentation conventions"
3globs:
4 - "docs/**/*.md"
5 - "mkdocs.yaml"
6alwaysApply: false
7---
8
9# Documentation Rules
10- Write docs in Markdown with clear headings and code examples.
11- Update `mkdocs.yaml` navigation when adding new docs.
12- Keep `README.md` concise, and move long explanations to `/docs`.
13- Use Python code fences (```python … ```) in examples.
14
@@ −1 +1 @@
11 ---
2−description: "Conventions for using Pydantic models and settings"
2+description: "Documentation conventions"
33 globs:
4− - "**/*.py"
4+ - "docs/**/*.md"
5+ - "mkdocs.yaml"
56 alwaysApply: false
67 ---
78
8−# Pydantic Rules
9−- Use `pydantic.BaseModel` for request/response schemas.
10−- For configuration, use `pydantic_settings.BaseSettings` (v2).
11−- Always provide default values or use `...` for required fields.
12−- Use model validators (`@field_validator`, `@model_validator`) instead of custom init logic.
13−- Keep models small and focused on one purpose.
9+# Documentation Rules
10+- Write docs in Markdown with clear headings and code examples.
11+- Update `mkdocs.yaml` navigation when adding new docs.
12+- Keep `README.md` concise, and move long explanations to `/docs`.
13+- Use Python code fences (```python … ```) in examples.
1414
