Just develop to master

.claude/skills/abstract-seeder/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: abstract-seeder
+description: Provides structured seeding workflow for module data initialization
+---
+
+# Abstract Seeder
+
+## Purpose
+
+Provides a structured way to seed database data per module.
+
+---
+
+## Scope
+
+Seeders are responsible for:
+
+- creating initial dataset for a company
+- using factories to generate valid records
+- orchestrating dependency order between models
+
+---
+
+## Ownership Boundary
+
+Seeders MUST NOT:
+
+- define validation rules
+- define factory structure
+- enforce schema constraints
+- contain business logic
+
+---
+
+## Factory Dependency Rule
+
+Seeders MUST rely on factories for object creation.
+
+Factories are the source of truth for valid model state.
+
+---
+
+## Dependency Resolution
+
+Seeders MAY resolve dependencies using helper methods:
+
+- findOrCreateClient
+- findOrCreateProject
+- findOrCreateUser
+
+These helpers are convenience utilities, not business logic.
+
+---
+
+## Execution Hooks
+
+- beforeSeed(): setup state
+- afterSeed(): cleanup or summary
+
+---
+
+## Principle
+
+Seeders assemble data. They do not define data correctness.

.claude/skills/application-architecture-standard/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: application-architecture-standard
+description: Defines structural rules for Laravel architecture, layering, and code organization
+---
+
+# Purpose
+
+Single source of truth for application structure and architectural boundaries.
+
+---
+
+# 1. Layering Rules
+
+## Presentation Layer
+- Controllers
+- Filament Pages
+- Form Requests (validation only)
+
+No business logic allowed.
+
+## Application Layer
+- Services
+- DTOs
+- Transformers
+
+Holds all business logic orchestration.
+
+## Domain Layer
+- Models
+Represents state and invariants only.
+
+## Infrastructure Layer
+- API clients
+- External services
+
+Must be replaceable and contain no business logic.
+
+---
+
+## 2. Service Rules
+
+- Business logic lives in services.
+- Services must remain framework-agnostic except for Laravel infrastructure (Eloquent, DB transactions, HTTP client, logging).
+- No Filament classes or UI concerns inside services.
+- DTOs are used for structured data transfer where transformation, validation, or reuse is required.
+- They are optional for internal service calls when validated arrays are sufficient.
+
+---
+
+# 3. Dependency Rules
+
+- Constructor injection only
+- No service locators
+- No hidden dependencies
+
+---
+
+# 4. Architecture Integrity
+
+- No cross-layer leakage
+- Strict separation of concerns
+- Refactoring must preserve behavior

.claude/skills/autonomous-coding-workflow/SKILL.md

@@ -0,0 +1,137 @@
+---
+name: autonomous-coding-workflow
+description: Governs safe, incremental, repository-wide development workflow with continuous validation gates
+---
+
+# Autonomous Coding Workflow
+
+## Goal
+
+Perform repository-wide modifications safely, incrementally, and with continuous validation.
+
+---
+
+## 1. Instruction Precedence
+
+Before doing anything:
+
+- Check for repository-level instruction files:
+  - `.github/copilot-instructions.md`
+  - `AGENTS.md`
+  - `.junie/*.md`
+  - `CLAUDE.md`
+
+If they exist:
+- Treat them as higher precedence for architecture and conventions.
+- Avoid duplicating rules already defined there.
+
+---
+
+## 2. Preparation
+
+Before modifying code:
+
+1. Read existing implementation.
+2. Understand current behavior.
+3. Identify existing abstractions and reuse them:
+   - Traits
+   - Base test cases
+   - Base resources
+   - Base seeders
+   - Services
+   - DTOs
+   - Transformers
+4. Search explicitly for duplication before introducing new abstractions.
+5. Preserve existing architectural patterns.
+
+Do not modify code that has not been understood.
+
+---
+
+## 3. Refactoring Heuristics
+
+Apply only when relevant:
+
+- If repeated patterns exist across many test classes, models, or resources, evaluate abstraction opportunities.
+- Prefer centralizing duplicated logic into:
+  - Traits
+  - Base classes
+  - Services
+- Do not introduce abstraction unless duplication is confirmed.
+
+---
+
+## 4. Incremental Development
+
+Work in small, verifiable steps.
+
+After each change:
+
+1. Verify syntax:
+   ```bash
+   php -l
+   ```
+2. Run targeted tests.
+3. Fix failures immediately.
+4. Run code style checks:
+   ```bash
+   vendor/bin/pint --dirty --format agent
+   ```
+5. Continue only if repository is clean.
+
+---
+
+## 5. Validation Gates
+
+Never proceed if any of the following fail:
+
+- PHPUnit tests
+- Static analysis
+- PHP syntax check (php -l)
+- Code style (Pint)
+
+Before completion, additionally ensure:
+
+- migrate:fresh --seed passes
+- smoke tests pass
+- targeted tests pass
+- full suite passes (unless explicitly excluded)
+
+---
+
+## 6. Module Completion
+
+After completing a module:
+
+1. Run targeted test suite.
+2. Run `php -l`.
+3. Run Pint.
+4. Confirm no unintended changes.
+5. Commit with clear module description.
+
+Do not start the next module until the current one is fully stable.
+
+---
+
+## 7. Uncertainty Handling
+
+If behavior is unclear:
+
+- Stop immediately.
+- Describe ambiguity.
+- Request clarification.
+- Do not infer or guess missing business rules.
+
+---
+
+## 8. Success Criteria
+
+The task is complete only when:
+
+- Behavior is preserved.
+- No duplicate logic introduced.
+- Changes are idempotent.
+- All tests pass.
+- Full suite passes.
+- Formatting is clean.
+- No unintended architectural drift occurred.

.claude/skills/ci-schema-invariant-gate/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: ci-schema-invariant-gate
+description: Ensures correct execution order of migrations, seeders, and tests in CI
+---
+
+# CI Schema Gate
+
+## Purpose
+
+Enforces correct execution order of database setup and test execution in CI.
+
+---
+
+# 1. Execution Order (Strict)
+
+CI MUST run in this order:
+
+```bash
+php artisan migrate:fresh --seed
+php artisan test
+```
+
+No deviations allowed.
+
+---
+
+# 2. Responsibility
+
+This skill ONLY controls:
+
+- execution sequencing
+- CI pipeline ordering
+- ensuring seed runs before tests
+
+It does NOT validate:
+- schema correctness
+- factory correctness
+- business logic correctness
+
+These are handled by other skills.
+
+---
+
+# 3. Failure Behavior
+
+If CI fails:
+
+- migrations failing → schema issue (handled by test-honesty)
+- seed failing → factory/data issue (handled by test-honesty)
+- tests failing → behavior issue (handled by test layer)
+
+CI does NOT interpret or classify failures.
+
+---
+
+# 4. Determinism Requirement
+
+Test execution MUST always run on a fresh database state created by:
+
+```bash
+migrate:fresh --seed
+```
+
+No cached or partial state is allowed.
+
+---
+
+# 5. Core Principle
+
+CI defines execution order only.
+
+It does not define correctness of the system.