PureYAML/docs/rules
2026-06-06 00:32:53 +02:00
..
code-style.md
colors.md
commits.md
components.md
concurrency.md
cross-platform.md ci: use checkout action with node 24 2026-06-06 00:32:53 +02:00
dependency-injection.md
documentation.md
engineering.md
file-naming.md
folder-grouping.md
fonts.md
git-discipline.md
linux-server.md ci: use checkout action with node 24 2026-06-06 00:32:53 +02:00
mermaid.md docs(roadmap): collapse completed epic diagrams 2026-06-05 10:50:13 +02:00
namespacing.md
package-architecture.md
package-import-contract.md
package-structure.md
README.md fix(ci): prepare 0.1.0 release 2026-06-05 21:20:20 +02:00
research-compatibility.md fix(parser): match block continuation parsing 2026-06-05 22:12:12 +02:00
shared-protocols.md
systematic-debugging.md
testing-discipline.md
testing.md
validation.md Harden parser against real YAML fixtures 2026-06-05 19:34:30 +02:00
verification.md fix(ci): prepare 0.1.0 release 2026-06-05 21:20:20 +02:00
view-models.md
views.md

PureYAML Rules

Load these rules before changing code:

  • code-style.md
  • namespacing.md
  • cross-platform.md
  • testing.md
  • validation.md
  • verification.md
  • commits.md

Project-specific overrides:

  • PureYAML uses a root Package.swift.
  • Sources live directly under Sources.
  • Tests live in Tests/PureYAMLTests.
  • Package.swift must keep dependencies: [].
  • Public API must live under the PureYAML namespace tree.
  • The package must build on macOS, Linux, Windows, and WASI.

The broader rule files are retained for detailed guidance. When they include generic examples, apply the PureYAML-specific overrides above.