Valinor PHP

Use this skill to write production-quality code against Valinor's public API. Favor the smallest correct Valinor configuration and keep the code on the public surface.

Core stance

1. Default to strict mapping. Relax rules only when the input contract actually requires it.
2. Prefer precise PHP and PHPDoc types over mixed or object.
3. Prefer public entrypoints such as MapperBuilder, NormalizerBuilder, Mapper\Source\Source, Normalizer\Format, HttpRequest, AsConverter, AsTransformer, and Object\Constructor.
4. Treat builders as immutable configuration objects. Chain or reassign them; do not assume in-place mutation.
5. Prefer reusable configurators for shared application policy.
6. Avoid internal classes under areas like Library, Compiler, Definition, or concrete mapper internals.