## 단계 1-4: 크레딧 관리 컴포넌트

### MCP 확인 단계

- 명령어: `기존 UserCredit, CreditRequest, CreditTransaction 모델과 필라멘트 리소스 확인`

- 확인할 대상: app/Models/UserCredit.php, app/Models/CreditRequest.php, app/Models/CreditTransaction.php

- 확인 결과: 기존 크레딧 관련 모델 구조 그대로 활용

### Laravel 명령어

- 실행: `php artisan make:livewire VIP/CreditPurchase --no-interaction`

- 실행: `php artisan make:livewire VIP/CreditUsage --no-interaction`

- 실행: `php artisan make:livewire VIP/CreditTransactions --no-interaction`

- 파일 위치: `app/Livewire/VIP/` 디렉토리

- 기존 모델 참조: `use App\Models\UserCredit; use App\Models\CreditRequest;`

### 백엔드 로직 명세 (기존 크레딧 모델들 활용)

- 참조 모델: UserCredit::class, CreditRequest::class, CreditTransaction::class (기존 완벽한 모델들)

- 기존 모델들의 User 관계 메서드 그대로 활용

- 기존 필라멘트 크레딧 관련 로직 그대로 적용

### 프론트엔드 렌더링 명세

- 크레딧 구매 신청 폼 (수량 선택)

- 크레딧 잔액 및 사용 내역 표시

- 거래 내역 테이블 (날짜/금액/상태)

위는 dev2.md의 일부내용입니다.

1요청당 이 행동으로 프롬프트를 설정하였고, 맥락에는 오직 라라벨 mcp로 생성한 규칙만 존재합니다.

우분투25.04 에서 작업하였을때, 반자동식으로 결과물 보고 다음 넘어가고 work2.md라는곳에 내역 남기도록하고 

이런 절차로 진행중입니다.

라라벨 12.x 로 프로젝트 생성. 관리자패널은 필라멘트 v4로 구성

프론트는 TALL스택으로 타일윈드 4.1 vite , Alpine , Livewire  구성으로 

1. 필요한 라이브러리 설치 / 실행 

2. 프론트앤드 타일윈드 vite, livewire 설치 (alpine은 자동설정됩니다.)

3. bost 설치 및 vscode나 claude code 나 커서나 윈드서퍼 등으로 초기파일 생성 명령어 실행시 알아서 mcp 설정 + 지시 rule 및 참조 코드를 프로젝트 의존성에 맞추어서 생성해줍니다.

라라벨 docs 나 타일윈드 docs 들의 기본 공식 권장 코딩스타일 이런게 포함됩니다.

그러므로 환각증세라고하죠  자기 마음대로 판단하고 생성하고 메롱해지는 것.

그런걸 좀 방지를 정말 해주더라구요.

윈도우11프로랑 우분투 25.04에서 왔다갔다 하면서 깃클론으로 작업해봤는데 탄탄하게 잘 만들어주네요.

아래는 명령어 한줄로 생성된 claude code 용 맥락 문서인 claude.md 의 내용 일부입니다.

[code]

<laravel-boost-guidelines>

=== foundation rules ===

# Laravel Boost Guidelines

The Laravel Boost guidelines are specifically curated by Laravel maintainers for this application. These guidelines should be followed closely to enhance the user's satisfaction building Laravel applications.

## Foundational Context

This application is a Laravel application and its main Laravel ecosystems package & versions are below. You are an expert with them all. Ensure you abide by these specific packages & versions.

- php - 8.4.5

- filament/filament (FILAMENT) - v4

- laravel/fortify (FORTIFY) - v1

- laravel/framework (LARAVEL) - v12

- laravel/prompts (PROMPTS) - v0

- laravel/reverb (REVERB) - v1

- laravel/sanctum (SANCTUM) - v4

- livewire/livewire (LIVEWIRE) - v3

- laravel/pint (PINT) - v1

- laravel/sail (SAIL) - v1

- phpunit/phpunit (PHPUNIT) - v11

- alpinejs (ALPINEJS) - v3

- laravel-echo (ECHO) - v2

- tailwindcss (TAILWINDCSS) - v3

## Conventions

- You must follow all existing code conventions used in this application. When creating or editing a file, check sibling files for the correct structure, approach, naming.

- Use descriptive names for variables and methods. For example, `isRegisteredForDiscounts`, not `discount()`.

- Check for existing components to reuse before writing a new one.

## Verification Scripts

- Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit and feature tests are more important.

## Application Structure & Architecture

- Stick to existing directory structure - don't create new base folders without approval.

- Do not change the application's dependencies without approval.

## Frontend Bundling

- If the user doesn't see a frontend change reflected in the UI, it could mean they need to run `npm run build`, `npm run dev`, or `composer run dev`. Ask them.

## Replies

- Be concise in your explanations - focus on what's important rather than explaining obvious details.

## Documentation Files

- You must only create documentation files if explicitly requested by the user.

=== boost rules ===

## Laravel Boost

- Laravel Boost is an MCP server that comes with powerful tools designed specifically for this application. Use them.

## Artisan

- Use the `list-artisan-commands` tool when you need to call an Artisan command to double check the available parameters.

## URLs

- Whenever you share a project URL with the user you should use the `get-absolute-url` tool to ensure you're using the correct scheme, domain / IP, and port.

## Tinker / Debugging

- You should use the `tinker` tool when you need to execute PHP to debug code or query Eloquent models directly.

- Use the `database-query` tool when you only need to read from the database.

## Reading Browser Logs With the `browser-logs` Tool

- You can read browser logs, errors, and exceptions using the `browser-logs` tool from Boost.

- Only recent browser logs will be useful - ignore old logs.

## Searching Documentation (Critically Important)

- Boost comes with a powerful `search-docs` tool you should use before any other approaches. This tool automatically passes a list of installed packages and their versions to the remote Boost API, so it returns only version-specific documentation specific for the user's circumstance. You should pass an array of packages to filter on if you know you need docs for particular packages.

- The 'search-docs' tool is perfect for all Laravel related packages, including Laravel, Inertia, Livewire, Filament, Tailwind, Pest, Nova, Nightwatch, etc.

- You must use this tool to search for Laravel-ecosystem documentation before falling back to other approaches.

- Search the documentation before making code changes to ensure we are taking the correct approach.

- Use multiple, broad, simple, topic based queries to start. For example: `['rate limiting', 'routing rate limiting', 'routing']`.

- Do not add package names to queries - package information is already shared. For example, use `test resource table`, not `filament 4 test resource table`.

### Available Search Syntax

- You can and should pass multiple queries at once. The most relevant results will be returned first.

1. Simple Word Searches with auto-stemming - query=authentication - finds 'authenticate' and 'auth'

2. Multiple Words (AND Logic) - query=rate limit - finds knowledge containing both "rate" AND "limit"

3. Quoted Phrases (Exact Position) - query="infinite scroll" - Words must be adjacent and in that order

4. Mixed Queries - query=middleware "rate limit" - "middleware" AND exact phrase "rate limit"

5. Multiple Queries - queries=["authentication", "middleware"] - ANY of these terms

=== php rules ===

## PHP

- Always use curly braces for control structures, even if it has one line.

### Constructors

- Use PHP 8 constructor property promotion in `__construct()`.

- <code-snippet>public function __construct(public GitHub $github) { }</code-snippet>

- Do not allow empty `__construct()` methods with zero parameters.

### Type Declarations

- Always use explicit return type declarations for methods and functions.

- Use appropriate PHP type hints for method parameters.

<code-snippet name="Explicit Return Types and Method Params" lang="php">

protected function isAccessible(User $user, ?string $path = null): bool

{

...

}

</code-snippet>

## Comments

- Prefer PHPDoc blocks over comments. Never use comments within the code itself unless there is something _very_ complex going on.

## PHPDoc Blocks

- Add useful array shape type definitions for arrays when appropriate.

## Enums

- Typically, keys in an Enum should be TitleCase. For example: `FavoritePerson`, `BestLake`, `Monthly`.

=== filament/core rules ===

[/code]

테스트의 목적: 비싼 구독 요금제 IDE보다 

똥물리에, 구림의 정석 이라 소리듣는 카피롯으로 싼마이 10달러로 얼마나 효율을 얻어낼 수 있는가

를 중점으로 두고 에이전트 모드 / claude 4 sonnet 으로 고정하고 작업돌려봤습니다.