// Development workflow for UnoPim. Activates when running tests, linting code, building assets, or debugging; or when the user mentions test, lint, pint, build, npm, pest, format, style, quality, coverage, or needs to verify code works.
Backend PHP development for UnoPim. Activates when writing PHP code, creating classes, models, repositories, events, listeners, or tests; or when the user mentions model, repository, controller, service, event, listener, observer, Concord, proxy, or needs to write backend code. MUST be invoked before writing any PHP tests.
Code review for UnoPim. Activates when reviewing code changes, checking standards compliance, flagging violations, or performing PR reviews; or when the user mentions review, standards, conventions, best practices, violations, or code quality.
Handle module attribute mapping and mapping history management in Unopim. Use this skill when creating module attribute mapping UI, mapping controller, mapping history, or restricting fields to module structure. Only Attribute Mapping and History tabs are allowed. Covers DB_PREFIX (auto-added by Laravel), Migration/ singular folder, HistoryTrait on models, flat ACL, cURL HTTP client, and JsonResponse controller pattern.
Day-1 checklist and step-by-step guide to build a complete Unopim third-party connector (WooCommerce, Shopify, Shopware, module, or any REST API) within one working day. Use this skill when starting a new Unopim integration, planning a connector from scratch, or needing the full ordered sequence of steps to create a production-ready connector module. Covers all required files, patterns, and critical checkpoints verified against the WooCommerce connector reference implementation.
Implement credential storage, API connection testing, secure field handling, history tracking, and full CRUD for Unopim third-party connector modules. Covers Credential model with HistoryTrait and extras JSON, Contract interface, CredentialRepository, CredentialController with JsonResponse, FormRequest validation, DataGrid, and migration with DB_PREFIX. Use this skill when building the credentials section of any Unopim connector (WooCommerce, Shopify, Shopware, module, etc.).
Implement Unopim DataGrid classes for listing records in admin panels with search, filter, sort, actions (edit/delete), and mass actions. Covers DataGrid subdirectory structure (DataGrids/Section/), prepareQueryBuilder with DB::table (prefix added by Laravel), addColumn with correct closure patterns, addAction with function callbacks for url, addMassAction, bouncer() permission checks, and Blade integration. Use this skill when creating a DataGrid for credentials, mappings, export history, or any Unopim module listing page.
| name | unopim-dev-cycle |
| description | Development workflow for UnoPim. Activates when running tests, linting code, building assets, or debugging; or when the user mentions test, lint, pint, build, npm, pest, format, style, quality, coverage, or needs to verify code works. |
| license | MIT |
| metadata | {"author":"unopim"} |
This skill provides guidance for the UnoPim development workflow, including running tests, code quality checks, building assets, and troubleshooting.
Follow these guidelines for UnoPim development workflow:
The standard development workflow:
./vendor/bin/pint./vendor/bin/pest --filter YourTestpackages/Webkul/Admin/src/Resources/assets/): cd packages/Webkul/Admin && npx vite buildresources/): npm run buildnpm run build does NOT build Admin package assets — they have separate Vite configsphp artisan optimize:clear# Format PHP code
./vendor/bin/pint
# Run all tests
./vendor/bin/pest
# Run specific test suite
./vendor/bin/pest --testsuite="Admin Feature Test"
# Build frontend assets
npm run build
# Clear all caches
php artisan optimize:clear
# Start dev server
php artisan serve
# Start queue worker (for import/export)
php artisan queue:work --queue="default,system"
Before considering ANY feature or fix complete, you MUST run and pass ALL applicable checks. GitHub Actions will fail if these are skipped.
# Auto-fix style on changed files
./vendor/bin/pint --dirty
# Verify no violations remain (dry run)
./vendor/bin/pint --test --dirty
See code-quality.md for common Pint pitfalls.
# Run tests for the package you changed
./vendor/bin/pest packages/Webkul/{Package}/tests/
# Run specific test file
./vendor/bin/pest path/to/YourTest.php
See running-tests.md for common Pest pitfalls.
Playwright tests (tests/e2e-pw/) run in CI but not locally. You MUST keep them in sync when changing:
Resources/lang/*/app.php): Search tests/e2e-pw/ for the old text and update assertionstests/e2e-pw/ for affected selectorstests/e2e-pw/tests/04-datatransfer/$.uid-based IDs in tests (e.g., id="36_dropzone-file") — use stable selectors like input[type="file"][name="file"]# Search Playwright tests for text you changed
grep -r "OLD TEXT" tests/e2e-pw/
./vendor/bin/pint before committing PHP changes