artiframe add
The artiframe add command allows you to integrate pre-configured and officially supported extensions (packages) into your project in seconds.
It is not merely a composer require trigger; for "Integrated" packages, it copies ready-to-use service classes into your project and automatically injects the necessary environment variables into your .env file.
Usage
$ artiframe add [package_code]
Parameterless Usage (List)
If you run the command without specifying a package name, you will see a list and the types of all available extensions.
$ artiframe add
ArtiFrame Package Registry
─────────────────────────────────────────────────────────────
⚡ Integrated Packages (Composer + Stub + ENV)
add iyzico iyzico/iyzipay-php → src/Service/Iyzico.php
add stripe stripe/stripe-php → src/Service/Stripe.php
add jwt firebase/php-jwt → src/Auth/JwtAuth.php
...
📦 Direct Packages (Composer Only)
add mpdf mpdf/mpdf
add uuid ramsey/uuid
...
Package Types
1. Integrated Packages
These packages are ready to run the moment they are added to the system.
For example, when you execute artiframe add stripe, the following operations occur in the background:
- The
stripe/stripe-phppackage is installed via Composer. - The
stripe.stubfile from the CLI templates is copied into your project'ssrc/Service/Stripe.phpdirectory. This class contains ready-made payment methods. - Variables like
STRIPE_SECRET_KEYandSTRIPE_PUBLISHABLE_KEYare automatically appended to your project's.envand.env.examplefiles.
2. Direct Packages
These are packages that do not require any special configuration or wrapper classes, and are intended for developers to use directly with their own business logic (e.g., carbon, uuid, mpdf). Only the Composer installation is performed.