원클릭으로 Manus에서 모든 스킬 실행

helperfunctions

스타3

포크0

업데이트2026년 3월 3일 09:46

Always prefer Laravel's built-in helper classes over native PHP functions. Use `Arr::`, `Str::`, and Collection methods instead of native PHP equivalents.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

codebar-ag

codebar-ag/coding-guidelines

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Helper Functions

When to Apply

When transforming arrays, strings, or iterables in Laravel application code.
When refactoring native PHP utility code to improve readability and consistency.
When chaining multiple transformations on text or data collections.

When NOT to Apply

When no Laravel equivalent exists and native PHP is clearer.
In tight low-level loops where collection wrapping would add unnecessary overhead.
In framework-agnostic packages that should not depend on Laravel helpers.

Preconditions

Import Illuminate\Support\Arr for array helpers.
Import Illuminate\Support\Str for string helpers.
Use collect() only when collection operations improve clarity.

Process

Identify native PHP helper usage (array_*, str_*, manual loops).
Replace with Arr::, Str::, or Collection methods where a direct equivalent exists.
Keep behavior identical (defaults, key handling, casing, null handling).
Prefer fluent chains (Str::of(), collections) for multi-step transformations.
Re-run tests/static analysis for the touched scope.

Examples

use Illuminate\Support\Arr;
use Illuminate\Support\Str;

// Arrays
$city = Arr::get($payload, 'user.address.city', 'Unknown');
$safe = Arr::except($payload, ['password', 'token']);

// Strings
$slug = Str::of($title)->trim()->lower()->slug();

// Collections
$adminEmails = collect($users)
    ->filter(fn (User $user) => $user->isAdmin())
    ->pluck('email')
    ->values();

Anti-Patterns

Mixing native array_*/str_* calls with Laravel helpers in the same transformation flow.
Replacing simple one-liners with collection chains that reduce readability.
Omitting use imports and relying on fully qualified class names repeatedly.
Rewriting code when no Laravel helper exists and native PHP is already explicit.

References

이 저장소의 다른 Skills

같은 저장소

dto

codebar-ag/coding-guidelines

Readonly data containers with typed factory methods (`fromArray`, `fromModel`, `fromCollection`, `fromRequest`) used to pass structured data between application layers — especially for external API responses, Eloquent models, and service boundaries. Use this skill whenever creating, reviewing, or refactoring DTOs, Data Transfer Objects, value objects for inter-layer communication, or mapping payloads from APIs, models, or collections into typed PHP objects. Also trigger when the user mentions spatie/laravel-data alternatives, data mapping, or payload normalization in a Laravel context.

2026-03-043

models

codebar-ag/coding-guidelines

Eloquent model conventions for mass assignment, casts, relationship naming, activity logging, and mandatory model tests (CRUD + relations).

2026-03-043

actions

codebar-ag/coding-guidelines

Single-purpose business logic classes that encapsulate one well-defined business operation. Actions are the primary location for business logic in Laravel applications, invoked from controllers, commands, or jobs.

2026-03-033

albatros

codebar-ag/coding-guidelines

Albatros accounting API integration via Saloon. Use when working with app/Services/Albatros/, AlbatrosConnector, or Albatros DTOs.

2026-03-033

blade

codebar-ag/coding-guidelines

Laravel Blade template conventions covering components, output escaping, security, structure, and formatting.

2026-03-033

commands

codebar-ag/coding-guidelines

Artisan console command classes that serve as the CLI entry point for operations. Commands validate input and delegate all business logic to Actions or Services.

2026-03-033

Helper Functions

When to Apply

When transforming arrays, strings, or iterables in Laravel application code.

When refactoring native PHP utility code to improve readability and consistency.

When chaining multiple transformations on text or data collections.

When NOT to Apply

When no Laravel equivalent exists and native PHP is clearer.

In tight low-level loops where collection wrapping would add unnecessary overhead.

In framework-agnostic packages that should not depend on Laravel helpers.

Preconditions

Import Illuminate\Support\Arr for array helpers.

Import Illuminate\Support\Str for string helpers.

Use collect() only when collection operations improve clarity.

Process

Identify native PHP helper usage (array_*, str_*, manual loops).

Replace with Arr::, Str::, or Collection methods where a direct equivalent exists.

Keep behavior identical (defaults, key handling, casing, null handling).

Prefer fluent chains (Str::of(), collections) for multi-step transformations.

Re-run tests/static analysis for the touched scope.

Examples

use Illuminate\Support\Arr; use Illuminate\Support\Str; // Arrays $city = Arr::get($payload, 'user.address.city', 'Unknown'); $safe = Arr::except($payload, ['password', 'token']); // Strings $slug = Str::of($title)->trim()->lower()->slug(); // Collections $adminEmails = collect($users) ->filter(fn (User $user) => $user->isAdmin()) ->pluck('email') ->values();

Anti-Patterns

Mixing native array_*/str_* calls with Laravel helpers in the same transformation flow.

Replacing simple one-liners with collection chains that reduce readability.

Omitting use imports and relying on fully qualified class names repeatedly.

Rewriting code when no Laravel helper exists and native PHP is already explicit.

References

name	helperfunctions
description	Always prefer Laravel's built-in helper classes over native PHP functions. Use `Arr::`, `Str::`, and Collection methods instead of native PHP equivalents.
compatible_agents	["architect","implement","refactor","review"]