[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71EQAR89QD5PCEHGY1GVQN6":3,"skill-same:01M71EQAR89QD5PCEHGY1GVQN6":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M71EQAR89QD5PCEHGY1GVQN6","laravel-patterns",null,"Laravel architecture patterns, routing\u002Fcontrollers, Eloquent ORM, service layers, queues, events, caching, and API resources for production apps.","ViewWay\u002Fhermes-by-everythings","ViewWay","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F57283862?v=4","01M71ENR60K309MXA64A23SEW5","01M71ENR6QYM7NQHP29W53HSXT",3,"MIT","https:\u002F\u002Fgithub.com\u002FViewWay\u002Fhermes-by-everythings\u002Fblob\u002Fmain\u002Fskills\u002Flaravel-patterns\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"laravel patterns","patterns","laravel","service","Production","routing","production apps","layers","for","orm","events","architecture patterns","eloquent","queues","api","architecture","laravel architecture","caching","apps","resources","2026-11-10 10:12:30",false,"---\nname: laravel-patterns\ndescription: Laravel architecture patterns, routing\u002Fcontrollers, Eloquent ORM, service layers, queues, events, caching, and API resources for production apps.\norigin: ECC\n---\n\n# Laravel Development Patterns\n\nProduction-grade Laravel architecture patterns for scalable, maintainable applications.\n\n## When to Use\n\n- Building Laravel web applications or APIs\n- Structuring controllers, services, and domain logic\n- Working with Eloquent models and relationships\n- Designing APIs with resources and pagination\n- Adding queues, events, caching, and background jobs\n\n## How It Works\n\n- Structure the app around clear boundaries (controllers -> services\u002Factions -> models).\n- Use explicit bindings and scoped bindings to keep routing predictable; still enforce authorization for access control.\n- Favor typed models, casts, and scopes to keep domain logic consistent.\n- Keep IO-heavy work in queues and cache expensive reads.\n- Centralize config in `config\u002F*` and keep environments explicit.\n\n## Examples\n\n### Project Structure\n\nUse a conventional Laravel layout with clear layer boundaries (HTTP, services\u002Factions, models).\n\n### Recommended Layout\n\n```\napp\u002F\n├── Actions\u002F            # Single-purpose use cases\n├── Console\u002F\n├── Events\u002F\n├── Exceptions\u002F\n├── Http\u002F\n│   ├── Controllers\u002F\n│   ├── Middleware\u002F\n│   ├── Requests\u002F       # Form request validation\n│   └── Resources\u002F      # API resources\n├── Jobs\u002F\n├── Models\u002F\n├── Policies\u002F\n├── Providers\u002F\n├── Services\u002F           # Coordinating domain services\n└── Support\u002F\nconfig\u002F\ndatabase\u002F\n├── factories\u002F\n├── migrations\u002F\n└── seeders\u002F\nresources\u002F\n├── views\u002F\n└── lang\u002F\nroutes\u002F\n├── api.php\n├── web.php\n└── console.php\n```\n\n### Controllers -> Services -> Actions\n\nKeep controllers thin. Put orchestration in services and single-purpose logic in actions.\n\n```php\nfinal class CreateOrderAction\n{\n    public function __construct(private OrderRepository $orders) {}\n\n    public function handle(CreateOrderData $data): Order\n    {\n        return $this->orders->create($data);\n    }\n}\n\nfinal class OrdersController extends Controller\n{\n    public function __construct(private CreateOrderAction $createOrder) {}\n\n    public function store(StoreOrderRequest $request): JsonResponse\n    {\n        $order = $this->createOrder->handle($request->toDto());\n\n        return response()->json([\n            'success' => true,\n            'data' => OrderResource::make($order),\n            'error' => null,\n            'meta' => null,\n        ], 201);\n    }\n}\n```\n\n### Routing and Controllers\n\nPrefer route-model binding and resource controllers for clarity.\n\n```php\nuse Illuminate\\Support\\Facades\\Route;\n\nRoute::middleware('auth:sanctum')->group(function () {\n    Route::apiResource('projects', ProjectController::class);\n});\n```\n\n### Route Model Binding (Scoped)\n\nUse scoped bindings to prevent cross-tenant access.\n\n```php\nRoute::scopeBindings()->group(function () {\n    Route::get('\u002Faccounts\u002F{account}\u002Fprojects\u002F{project}', [ProjectController::class, 'show']);\n});\n```\n\n### Nested Routes and Binding Names\n\n- Keep prefixes and paths consistent to avoid double nesting (e.g., `conversation` vs `conversations`).\n- Use a single parameter name that matches the bound model (e.g., `{conversation}` for `Conversation`).\n- Prefer scoped bindings when nesting to enforce parent-child relationships.\n\n```php\nuse App\\Http\\Controllers\\Api\\ConversationController;\nuse App\\Http\\Controllers\\Api\\MessageController;\nuse Illuminate\\Support\\Facades\\Route;\n\nRoute::middleware('auth:sanctum')->prefix('conversations')->group(function () {\n    Route::post('\u002F', [ConversationController::class, 'store'])->name('conversations.store');\n\n    Route::scopeBindings()->group(function () {\n        Route::get('\u002F{conversation}', [ConversationController::class, 'show'])\n            ->name('conversations.show');\n\n        Route::post('\u002F{conversation}\u002Fmessages', [MessageController::class, 'store'])\n            ->name('conversation-messages.store');\n\n        Route::get('\u002F{conversation}\u002Fmessages\u002F{message}', [MessageController::class, 'show'])\n            ->name('conversation-messages.show');\n    });\n});\n```\n\nIf you want a parameter to resolve to a different model class, define explicit binding. For custom binding logic, use `Route::bind()` or implement `resolveRouteBinding()` on the model.\n\n```php\nuse App\\Models\\AiConversation;\nuse Illuminate\\Support\\Facades\\Route;\n\nRoute::model('conversation', AiConversation::class);\n```\n\n### Service Container Bindings\n\nBind interfaces to implementations in a service provider for clear dependency wiring.\n\n```php\nuse App\\Repositories\\EloquentOrderRepository;\nuse App\\Repositories\\OrderRepository;\nuse Illuminate\\Support\\ServiceProvider;\n\nfinal class AppServiceProvider extends ServiceProvider\n{\n    public function register(): void\n    {\n        $this->app->bind(OrderRepository::class, EloquentOrderRepository::class);\n    }\n}\n```\n\n### Eloquent Model Patterns\n\n### Model Configuration\n\n```php\nfinal class Project extends Model\n{\n    use HasFactory;\n\n    protected $fillable = ['name', 'owner_id', 'status'];\n\n    protected $casts = [\n        'status' => ProjectStatus::class,\n        'archived_at' => 'datetime',\n    ];\n\n    public function owner(): BelongsTo\n    {\n        return $this->belongsTo(User::class, 'owner_id');\n    }\n\n    public function scopeActive(Builder $query): Builder\n    {\n        return $query->whereNull('archived_at');\n    }\n}\n```\n\n### Custom Casts and Value Objects\n\nUse enums or value objects for strict typing.\n\n```php\nuse Illuminate\\Database\\Eloquent\\Casts\\Attribute;\n\nprotected $casts = [\n    'status' => ProjectStatus::class,\n];\n```\n\n```php\nprotected function budgetCents(): Attribute\n{\n    return Attribute::make(\n        get: fn (int $value) => Money::fromCents($value),\n        set: fn (Money $money) => $money->toCents(),\n    );\n}\n```\n\n### Eager Loading to Avoid N+1\n\n```php\n$orders = Order::query()\n    ->with(['customer', 'items.product'])\n    ->latest()\n    ->paginate(25);\n```\n\n### Query Objects for Complex Filters\n\n```php\nfinal class ProjectQuery\n{\n    public function __construct(private Builder $query) {}\n\n    public function ownedBy(int $userId): self\n    {\n        $query = clone $this->query;\n\n        return new self($query->where('owner_id', $userId));\n    }\n\n    public function active(): self\n    {\n        $query = clone $this->query;\n\n        return new self($query->whereNull('archived_at'));\n    }\n\n    public function builder(): Builder\n    {\n        return $this->query;\n    }\n}\n```\n\n### Global Scopes and Soft Deletes\n\nUse global scopes for default filtering and `SoftDeletes` for recoverable records.\nUse either a global scope or a named scope for the same filter, not both, unless you intend layered behavior.\n\n```php\nuse Illuminate\\Database\\Eloquent\\SoftDeletes;\nuse Illuminate\\Database\\Eloquent\\Builder;\n\nfinal class Project extends Model\n{\n    use SoftDeletes;\n\n    protected static function booted(): void\n    {\n        static::addGlobalScope('active', function (Builder $builder): void {\n            $builder->whereNull('archived_at');\n        });\n    }\n}\n```\n\n### Query Scopes for Reusable Filters\n\n```php\nuse Illuminate\\Database\\Eloquent\\Builder;\n\nfinal class Project extends Model\n{\n    public function scopeOwnedBy(Builder $query, int $userId): Builder\n    {\n        return $query->where('owner_id', $userId);\n    }\n}\n\n\u002F\u002F In service, repository etc.\n$projects = Project::ownedBy($user->id)->get();\n```\n\n### Transactions for Multi-Step Updates\n\n```php\nuse Illuminate\\Support\\Facades\\DB;\n\nDB::transaction(function (): void {\n    $order->update(['status' => 'paid']);\n    $order->items()->update(['paid_at' => now()]);\n});\n```\n\n### Migrations\n\n### Naming Convention\n\n- File names use timestamps: `YYYY_MM_DD_HHMMSS_create_users_table.php`\n- Migrations use anonymous classes (no named class); the filename communicates intent\n- Table names are `snake_case` and plural by default\n\n### Example Migration\n\n```php\nuse Illuminate\\Database\\Migrations\\Migration;\nuse Illuminate\\Database\\Schema\\Blueprint;\nuse Illuminate\\Support\\Facades\\Schema;\n\nreturn new class extends Migration\n{\n    public function up(): void\n    {\n        Schema::create('orders', function (Blueprint $table): void {\n            $table->id();\n            $table->foreignId('customer_id')->constrained()->cascadeOnDelete();\n            $table->string('status', 32)->index();\n            $table->unsignedInteger('total_cents');\n            $table->timestamps();\n        });\n    }\n\n    public function down(): void\n    {\n        Schema::dropIfExists('orders');\n    }\n};\n```\n\n### Form Requests and Validation\n\nKeep validation in form requests and transform inputs to DTOs.\n\n```php\nuse App\\Models\\Order;\n\nfinal class StoreOrderRequest extends FormRequest\n{\n    public function authorize(): bool\n    {\n        return $this->user()?->can('create', Order::class) ?? false;\n    }\n\n    public function rules(): array\n    {\n        return [\n            'customer_id' => ['required', 'integer', 'exists:customers,id'],\n            'items' => ['required', 'array', 'min:1'],\n            'items.*.sku' => ['required', 'string'],\n            'items.*.quantity' => ['required', 'integer', 'min:1'],\n        ];\n    }\n\n    public function toDto(): CreateOrderData\n    {\n        return new CreateOrderData(\n            customerId: (int) $this->validated('customer_id'),\n            items: $this->validated('items'),\n        );\n    }\n}\n```\n\n### API Resources\n\nKeep API responses consistent with resources and pagination.\n\n```php\n$projects = Project::query()->active()->paginate(25);\n\nreturn response()->json([\n    'success' => true,\n    'data' => ProjectResource::collection($projects->items()),\n    'error' => null,\n    'meta' => [\n        'page' => $projects->currentPage(),\n        'per_page' => $projects->perPage(),\n        'total' => $projects->total(),\n    ],\n]);\n```\n\n### Events, Jobs, and Queues\n\n- Emit domain events for side effects (emails, analytics)\n- Use queued jobs for slow work (reports, exports, webhooks)\n- Prefer idempotent handlers with retries and backoff\n\n### Caching\n\n- Cache read-heavy endpoints and expensive queries\n- Invalidate caches on model events (created\u002Fupdated\u002Fdeleted)\n- Use tags when caching related data for easy invalidation\n\n### Configuration and Environments\n\n- Keep secrets in `.env` and config in `config\u002F*.php`\n- Use per-environment config overrides and `config:cache` in production\n","# Laravel Development Patterns\n\nProduction-grade Laravel architecture patterns for scalable, maintainable applications.\n\n## When to Use\n\n- Building Laravel web applications or APIs\n- Structuring controllers, services, and domain logic\n- Working with Eloquent models and relationships\n- Designing APIs with resources and pagination\n- Adding queues, events, caching, and background jobs\n\n## How It Works\n\n- Structure the app around clear boundaries (controllers -> services\u002Factions -> models).\n- Use explicit bindings and scoped bindings to keep routing predictable; still enforce authorization for access control.\n- Favor typed models, casts, and scopes to keep domain logic consistent.\n- Keep IO-heavy work in queues and cache expensive reads.\n- Centralize config in `config\u002F*` and keep environments explicit.\n\n## Examples\n\n### Project Structure\n\nUse a conventional Laravel layout with clear layer boundaries (HTTP, services\u002Factions, models).\n\n### Recommended Layout\n\n```\napp\u002F\n├── Actions\u002F            # Single-purpose use cases\n├── Console\u002F\n├── Events\u002F\n├── Exceptions\u002F\n├── Http\u002F\n│   ├── Controllers\u002F\n│   ├── Middleware\u002F\n│   ├── Requests\u002F       # Form request validation\n│   └── Resources\u002F      # API resources\n├── Jobs\u002F\n├── Models\u002F\n├── Policies\u002F\n├── Providers\u002F\n├── Services\u002F           # Coordinating domain services\n└── Support\u002F\nconfig\u002F\ndatabase\u002F\n├── factories\u002F\n├── migrations\u002F\n└── seeders\u002F\nresources\u002F\n├── views\u002F\n└── lang\u002F\nroutes\u002F\n├── api.php\n├── web.php\n└── console.php\n```\n\n### Controllers -> Services -> Actions\n\nKeep controllers thin. Put orchestration in services and single-purpose logic in actions.\n\n```php\nfinal class CreateOrderAction\n{\n    public function __construct(private OrderRepository $orders) {}\n\n    public function handle(CreateOrderData $data): Order\n    {\n        return $this->orders->create($data);\n    }\n}\n\nfinal class OrdersController extends Controller\n{\n    public function __construct(private CreateOrderAction $createOrder) {}\n\n    public function store(StoreOrderRequest $request): JsonResponse\n    {\n        $order = $this->createOrder->handle($request->toDto());\n\n        return response()->json([\n            'success' => true,\n            'data' => OrderResource::make($order),\n            'error' => null,\n            'meta' => null,\n        ], 201);\n    }\n}\n```\n\n### Routing and Controllers\n\nPrefer route-model binding and resource controllers for clarity.\n\n```php\nuse Illuminate\\Support\\Facades\\Route;\n\nRoute::middleware('auth:sanctum')->group(function () {\n    Route::apiResource('projects', ProjectController::class);\n});\n```\n\n### Route Model Binding (Scoped)\n\nUse scoped bindings to prevent cross-tenant access.\n\n```php\nRoute::scopeBindings()->group(function () {\n    Route::get('\u002Faccounts\u002F{account}\u002Fprojects\u002F{project}', [ProjectController::class, 'show']);\n});\n```\n\n### Nested Routes and Binding Names\n\n- Keep prefixes and paths consistent to avoid double nesting (e.g., `conversation` vs `conversations`).\n- Use a single parameter name that matches the bound model (e.g., `{conversation}` for `Conversation`).\n- Prefer scoped bindings when nesting to enforce parent-child relationships.\n\n```php\nuse App\\Http\\Controllers\\Api\\ConversationController;\nuse App\\Http\\Controllers\\Api\\MessageController;\nuse Illuminate\\Support\\Facades\\Route;\n\nRoute::middleware('auth:sanctum')->prefix('conversations')->group(function () {\n    Route::post('\u002F', [ConversationController::class, 'store'])->name('conversations.store');\n\n    Route::scopeBindings()->group(function () {\n        Route::get('\u002F{conversation}', [ConversationController::class, 'show'])\n            ->name('conversations.show');\n\n        Route::post('\u002F{conversation}\u002Fmessages', [MessageController::class, 'store'])\n            ->name('conversation-messages.store');\n\n        Route::get('\u002F{conversation}\u002Fmessages\u002F{message}', [MessageController::class, 'show'])\n            ->name('conversation-messages.show');\n    });\n});\n```\n\nIf you want a parameter to resolve to a different model class, define explicit binding. For custom binding logic, use `Route::bind()` or implement `resolveRouteBinding()` on the model.\n\n```php\nuse App\\Models\\AiConversation;\nuse Illuminate\\Support\\Facades\\Route;\n\nRoute::model('conversation', AiConversation::class);\n```\n\n### Service Container Bindings\n\nBind interfaces to implementations in a service provider for clear dependency wiring.\n\n```php\nuse App\\Repositories\\EloquentOrderRepository;\nuse App\\Repositories\\OrderRepository;\nuse Illuminate\\Support\\ServiceProvider;\n\nfinal class AppServiceProvider extends ServiceProvider\n{\n    public function register(): void\n    {\n        $this->app->bind(OrderRepository::class, EloquentOrderRepository::class);\n    }\n}\n```\n\n### Eloquent Model Patterns\n\n### Model Configuration\n\n```php\nfinal class Project extends Model\n{\n    use HasFactory;\n\n    protected $fillable = ['name', 'owner_id', 'status'];\n\n    protected $casts = [\n        'status' => ProjectStatus::class,\n        'archived_at' => 'datetime',\n    ];\n\n    public function owner(): BelongsTo\n    {\n        return $this->belongsTo(User::class, 'owner_id');\n    }\n\n    public function scopeActive(Builder $query): Builder\n    {\n        return $query->whereNull('archived_at');\n    }\n}\n```\n\n### Custom Casts and Value Objects\n\nUse enums or value objects for strict typing.\n\n```php\nuse Illuminate\\Database\\Eloquent\\Casts\\Attribute;\n\nprotected $casts = [\n    'status' => ProjectStatus::class,\n];\n```\n\n```php\nprotected function budgetCents(): Attribute\n{\n    return Attribute::make(\n        get: fn (int $value) => Money::fromCents($value),\n        set: fn (Money $money) => $money->toCents(),\n    );\n}\n```\n\n### Eager Loading to Avoid N+1\n\n```php\n$orders = Order::query()\n    ->with(['customer', 'items.product'])\n    ->latest()\n    ->paginate(25);\n```\n\n### Query Objects for Complex Filters\n\n```php\nfinal class ProjectQuery\n{\n    public function __construct(private Builder $query) {}\n\n    public function ownedBy(int $userId): self\n    {\n        $query = clone $this->query;\n\n        return new self($query->where('owner_id', $userId));\n    }\n\n    public function active(): self\n    {\n        $query = clone $this->query;\n\n        return new self($query->whereNull('archived_at'));\n    }\n\n    public function builder(): Builder\n    {\n        return $this->query;\n    }\n}\n```\n\n### Global Scopes and Soft Deletes\n\nUse global scopes for default filtering and `SoftDeletes` for recoverable records.\nUse either a global scope or a named scope for the same filter, not both, unless you intend layered behavior.\n\n```php\nuse Illuminate\\Database\\Eloquent\\SoftDeletes;\nuse Illuminate\\Database\\Eloquent\\Builder;\n\nfinal class Project extends Model\n{\n    use SoftDeletes;\n\n    protected static function booted(): void\n    {\n        static::addGlobalScope('active', function (Builder $builder): void {\n            $builder->whereNull('archived_at');\n        });\n    }\n}\n```\n\n### Query Scopes for Reusable Filters\n\n```php\nuse Illuminate\\Database\\Eloquent\\Builder;\n\nfinal class Project extends Model\n{\n    public function scopeOwnedBy(Builder $query, int $userId): Builder\n    {\n        return $query->where('owner_id', $userId);\n    }\n}\n\n\u002F\u002F In service, repository etc.\n$projects = Project::ownedBy($user->id)->get();\n```\n\n### Transactions for Multi-Step Updates\n\n```php\nuse Illuminate\\Support\\Facades\\DB;\n\nDB::transaction(function (): void {\n    $order->update(['status' => 'paid']);\n    $order->items()->update(['paid_at' => now()]);\n});\n```\n\n### Migrations\n\n### Naming Convention\n\n- File names use timestamps: `YYYY_MM_DD_HHMMSS_create_users_table.php`\n- Migrations use anonymous classes (no named class); the filename communicates intent\n- Table names are `snake_case` and plural by default\n\n### Example Migration\n\n```php\nuse Illuminate\\Database\\Migrations\\Migration;\nuse Illuminate\\Database\\Schema\\Blueprint;\nuse Illuminate\\Support\\Facades\\Schema;\n\nreturn new class extends Migration\n{\n    public function up(): void\n    {\n        Schema::create('orders', function (Blueprint $table): void {\n            $table->id();\n            $table->foreignId('customer_id')->constrained()->cascadeOnDelete();\n            $table->string('status', 32)->index();\n            $table->unsignedInteger('total_cents');\n            $table->timestamps();\n        });\n    }\n\n    public function down(): void\n    {\n        Schema::dropIfExists('orders');\n    }\n};\n```\n\n### Form Requests and Validation\n\nKeep validation in form requests and transform inputs to DTOs.\n\n```php\nuse App\\Models\\Order;\n\nfinal class StoreOrderRequest extends FormRequest\n{\n    public function authorize(): bool\n    {\n        return $this->user()?->can('create', Order::class) ?? false;\n    }\n\n    public function rules(): array\n    {\n        return [\n            'customer_id' => ['required', 'integer', 'exists:customers,id'],\n            'items' => ['required', 'array', 'min:1'],\n            'items.*.sku' => ['required', 'string'],\n            'items.*.quantity' => ['required', 'integer', 'min:1'],\n        ];\n    }\n\n    public function toDto(): CreateOrderData\n    {\n        return new CreateOrderData(\n            customerId: (int) $this->validated('customer_id'),\n            items: $this->validated('items'),\n        );\n    }\n}\n```\n\n### API Resources\n\nKeep API responses consistent with resources and pagination.\n\n```php\n$projects = Project::query()->active()->paginate(25);\n\nreturn response()->json([\n    'success' => true,\n    'data' => ProjectResource::collection($projects->items()),\n    'error' => null,\n    'meta' => [\n        'page' => $projects->currentPage(),\n        'per_page' => $projects->perPage(),\n        'total' => $projects->total(),\n    ],\n]);\n```\n\n### Events, Jobs, and Queues\n\n- Emit domain events for side effects (emails, analytics)\n- Use queued jobs for slow work (reports, exports, webhooks)\n- Prefer idempotent handlers with retries and backoff\n\n### Caching\n\n- Cache read-heavy endpoints and expensive queries\n- Invalidate caches on model events (created\u002Fupdated\u002Fdeleted)\n- Use tags when caching related data for easy invalidation\n\n### Configuration and Environments\n\n- Keep secrets in `.env` and config in `config\u002F*.php`\n- Use per-environment config overrides and `config:cache` in production\n",{"name":5,"origin":43,"description":7},"ECC","main","0446e11613ad1942de249b12f7deea3889c25af4","skills\u002Flaravel-patterns",0,"https:\u002F\u002Fgithub.com\u002FViewWay\u002Fhermes-by-everythings","https:\u002F\u002Fgithub.com\u002FViewWay","rust can do everything","2026-06-19 23:27:05",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add ViewWay\u002Fhermes-by-everythings --skill laravel-patterns",{"tool":58,"command":59},"bunx","bunx skills add ViewWay\u002Fhermes-by-everythings --skill laravel-patterns",{"tool":61,"command":62},"pnpm","pnpm dlx skills add ViewWay\u002Fhermes-by-everythings --skill laravel-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FViewWay\u002Fhermes-by-everythings\u002Fblob\u002Fmain\u002Fskills\u002Flaravel-patterns\u002FSKILL.md",true,[],[67,107,133,154,185,206],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":86,"publishedAt":38},"01M71EREGWXCCGBGDZ969RZQA7","ui-ux-pro-max","UI\u002FUX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems\u002Ftokens, component specs, copy\u002Fmicrocopy, accessibility, or to generate\u002Fcritique\u002Frefine frontend UI (HTML\u002FCSS\u002FJS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI\u002FUX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.","https:\u002F\u002Fgithub.com\u002FViewWay\u002Fhermes-by-everythings\u002Fblob\u002Fmain\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[73,78,81],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":79,"categoryName":80,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"ux","max","ui ux","ui","ui ux pro max","pro","information architecture","css","microcopy","direction","Tailwind","flows","frontend","design","new","svelte","design systems","information","workflows","when",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":38},"01M71ERBY797MAY4HTFMSHPXMY","springboot-verification","Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.","https:\u002F\u002Fgithub.com\u002FViewWay\u002Fhermes-by-everythings\u002Fblob\u002Fmain\u002Fskills\u002Fspringboot-verification\u002FSKILL.md",[],[114,115,116,117,118,119,120,26,121,122,123,124,125,126,127,128,129,130,131,132],"springboot verification","verification","coverage","projects","verification loop","pr","diff","static","tests","spring boot","diff review","spring","loop","boot","analysis","review","with","build","release",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":142,"publishedAt":38},"01M71ER9TQGK9Y00JEEM6RW9RY","springboot-patterns","Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.","https:\u002F\u002Fgithub.com\u002FViewWay\u002Fhermes-by-everythings\u002Fblob\u002Fmain\u002Fskills\u002Fspringboot-patterns\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000010","后端与接口",[19,143,144,145,123,100,146,35,33,32,147,148,149,29,150,26,151,152,153,125],"springboot patterns","processing","rest api design","access","spring boot architecture","work","data","logging","async","java spring","use",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":167,"publishedAt":38},"01M71ER6XTWDJ0NVE5RFY28RE7","security-auditor","Use when reviewing code for security vulnerabilities, implementing authentication flows, auditing OWASP Top 10, configuring CORS\u002FCSP headers, handling secrets, input validation, SQL injection prevention, XSS protection, or any security-related code review.","https:\u002F\u002Fgithub.com\u002FViewWay\u002Fhermes-by-everythings\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-auditor\u002FSKILL.md",[160,163,164],{"categoryNo":161,"categoryName":162,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":140,"categoryName":141,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":165,"categoryName":166,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000033","数据分析师",[168,169,170,171,172,98,173,174,175,106,176,177,178,179,129,180,181,182,183,184],"security","security auditor","auditor","authentication","code review","implementing","csrf","Input Validation","encryption","code","vulnerability","xss","top","owasp top 10","audit","sql","secrets",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":194,"publishedAt":38},"01M71ER4PHRJ1EKXQTQPEPYQ6J","rust-testing","Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.","https:\u002F\u002Fgithub.com\u002FViewWay\u002Fhermes-by-everythings\u002Fblob\u002Fmain\u002Fskills\u002Frust-testing\u002FSKILL.md",[191],{"categoryNo":192,"categoryName":193,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000008","测试与质量",[195,196,197,116,198,199,19,200,151,201,122,202,203,204,205],"rust","testing","rust testing","unit","testing patterns","integration tests","mocking","unit tests","tdd","integration","methodology",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":212,"publishedAt":38},"01M71ER0XW3N4K7YTQSXXWW3M3","rust-patterns","Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.","https:\u002F\u002Fgithub.com\u002FViewWay\u002Fhermes-by-everythings\u002Fblob\u002Fmain\u002Fskills\u002Frust-patterns\u002FSKILL.md",[],[195,19,213,214,215,216,217,218,26,219,220,221,222],"rust patterns","error","traits","concurrency","safe","idiomatic","applications","best practices","error handling","ownership"]