Suggestion: change the way expressions are used in the docs to make it easier to understand

[dkarlovi]

In the README, you're using each expression FQCN directly.

What I've done is add an alias to the ForClasses namespace, allowing me to use expressions without cluttering up the import map, this convention is used in Symfony for attributes from Doctrine, Validator, Serializer, etc.

My config file

<?php

declare(strict_types=1);

use Arkitect\ClassSet;
use Arkitect\CLI\Config;
use Arkitect\Expression\ForClasses as Assert;
use Arkitect\Rules\Rule;

return static function (Config $config): void {
    $src = ClassSet::fromDir(__DIR__.'/src');
    $naming = [
        Rule::allClasses()
            ->that(new Assert\IsInterface())
            ->should(new Assert\NotHaveNameMatching('*Interface'))
            ->because('we do not use the Interface suffix for interfaces'),
        Rule::allClasses()
            ->that(new Assert\IsAbstract())
            ->should(new Assert\HaveNameMatching('Abstract*'))
            ->because('we want abstract classes to have a Abstract prefix'),
        Rule::allClasses()
            ->that(new Assert\IsTrait())
            ->should(new Assert\HaveNameMatching('*Trait'))
            ->because('we want traits to have a Trait suffix'),
        Rule::allClasses()
            ->that(new Assert\ResideInOneOfTheseNamespaces('App'))
            ->should(new Assert\NotHaveNameMatching('*Manager'))
            ->because('*Manager is too vague in naming classes'),
    ];

    $config->add($src, ...$naming);
};