Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Agents
hypecodeteam/backend-ai-rules
claude-code
cursor
security
unit-testing
repository-service-patterns
coding-principles
git-workflow
thin-controllers

Reference: ./vendor/hypecodeteam/backend-ai-rules/rules/codingprinciples.md

Install
php artisan boost:add-skill hypecodeteam/backend-ai-rules

Save this content to: AGENTS.md

# AGENTS.md - API Config Project Guidelines

## ๐Ÿ”’ Security Rules
- **NEVER** read or edit `.env.local` files
- **NEVER** expose or log secrets/API keys
- **NEVER** execute database migrations (`doctrine:migrations:migrate`)
- **ALWAYS** follow security best practices

## ๐Ÿ“‹ Development Guidelines

### ๐Ÿ—๏ธ Coding Principles
**Reference:** `./vendor/hypecodeteam/backend-ai-rules/rules/coding_principles.md`

### ๐Ÿงช Unit Testing Standards
**Reference:** `./vendor/hypecodeteam/backend-ai-rules/rules/unit_testing.md`

### ๐Ÿ“ Git Commit Convention
**Reference:** `./vendor/hypecodeteam/backend-ai-rules/rules/git_workflow_guideline.md`

<!-- If you need to use domain language, uncomment these 2 lines below, then create and fill the file you need with your domain rules-->
<!-- ### ๐Ÿ—ฃ๏ธ Domain Language -->
<!-- **Reference:** `./.rules/ubiquitous_language.md` -->

## ๐Ÿค– AI/LLM Integration

### โš ๏ธ MANDATORY RULES - SYSTEMATIC VERIFICATION

**CRITICAL: Before EVERY code proposal, the AI MUST imperatively:**

1. **Read and apply** `./vendor/hypecodeteam/backend-ai-rules/rules/repository_service_patterns.md` (controller/service logic, constants, OrThrow patterns)
2. **Read and apply** `./vendor/hypecodeteam/backend-ai-rules/rules/coding_principles.md` (PHP 8 patterns, Yoda conditions, defensive programming)
3.  **Read and apply** `./vendor/hypecodeteam/backend-ai-rules/rules/unit_testing.md` (Prophecy, AAA pattern, isolated tests)
4. **Read and apply** `./vendor/hypecodeteam/backend-ai-rules/rules/git_workflow_guideline.md` (commit message format)
<!-- Uncomment the line below if you need to use domain language -->
<!-- 5. **Read and apply** `./.rules/ubiquitous_language.md` (domain language terms and relations) -->
- **Explicitly verify compliance** before responding
- **Display in a bullet point the rules that have been read and loaded in the first answer**

**WITHOUT EXCEPTION:**
- โŒ No business logic in controllers
- โŒ No hardcoded values (use UPPER_SNAKE_CASE constants)
- โŒ No generic methods when a dedicated method is necessary
- โœ… Thin controllers (orchestration only)
- โœ… Private constants in services for static values
- โœ… Dedicated methods in services for special routes

**If these rules are not respected, the response is invalid and must be corrected.**

### Quick-Reference Tables for Agents

| Guideline | Key Rule | Example |
|-----------|----------|---------|
| **Class Declaration** | Final when not extended | `final class Service` |
| **Constructor** | Property promotion | `public function __construct(public readonly string $name)` |
| **Conditions** | Yoda + explicit | `if (false === $obj instanceof Type)` |
| **Testing** | Prophecy + AAA | Arrange โ†’ Act โ†’ Assert |
| **Commits** | type(scope): subject | `fix(service): correct calculation` |
| **Domain Terms** | Use exact terms | Affiliate (not Publisher), Campaign (not Link) |

| When to Use | Pattern | Reference |
|-------------|---------|-----------|
| New feature | feat(scope): add... | `./vendor/hypecodeteam/backend-ai-rules/rules/git_commit_guideline.md` |
| Bug fix | fix(scope): correct... | `./vendor/hypecodeteam/backend-ai-rules/rules/git_commit_guideline.md` |
| Business logic | Service method | `./vendor/hypecodeteam/backend-ai-rules/rules/repository_service_patterns.md` |
| Data access | Repository OrThrow | `./vendor/hypecodeteam/backend-ai-rules/rules/repository_service_patterns.md` |
| Controller input | Deserialize RequestDto + validate | `./vendor/hypecodeteam/backend-ai-rules/rules/repository_service_patterns.md` |
| Entity validation | Rich model methods | `./vendor/hypecodeteam/backend-ai-rules/rules/coding_principles.md` |
| Test setup | ProphecyTrait + setUp() | `./vendor/hypecodeteam/backend-ai-rules/rules/unit_testing.md` |

### AI Usage Guidelines
- **Always reference specific rules** when asking for code changes
- **Request examples** from existing codebase patterns
- **Specify testing requirements** using unit testing standards
- **Use consistent terminology** from domain language section
- **Provide context** from ubiquitous language for domain-specific features

AGENTS.md - API Config Project Guidelines

๐Ÿ”’ Security Rules

  • NEVER read or edit .env.local files
  • NEVER expose or log secrets/API keys
  • NEVER execute database migrations (doctrine:migrations:migrate)
  • ALWAYS follow security best practices

๐Ÿ“‹ Development Guidelines

๐Ÿ—๏ธ Coding Principles

Reference: ./vendor/hypecodeteam/backend-ai-rules/rules/coding_principles.md

๐Ÿงช Unit Testing Standards

Reference: ./vendor/hypecodeteam/backend-ai-rules/rules/unit_testing.md

๐Ÿ“ Git Commit Convention

Reference: ./vendor/hypecodeteam/backend-ai-rules/rules/git_workflow_guideline.md

๐Ÿค– AI/LLM Integration

โš ๏ธ MANDATORY RULES - SYSTEMATIC VERIFICATION

CRITICAL: Before EVERY code proposal, the AI MUST imperatively:

  1. Read and apply ./vendor/hypecodeteam/backend-ai-rules/rules/repository_service_patterns.md (controller/service logic, constants, OrThrow patterns)
  2. Read and apply ./vendor/hypecodeteam/backend-ai-rules/rules/coding_principles.md (PHP 8 patterns, Yoda conditions, defensive programming)
  3. Read and apply ./vendor/hypecodeteam/backend-ai-rules/rules/unit_testing.md (Prophecy, AAA pattern, isolated tests)
  4. Read and apply ./vendor/hypecodeteam/backend-ai-rules/rules/git_workflow_guideline.md (commit message format)
  • Explicitly verify compliance before responding
  • Display in a bullet point the rules that have been read and loaded in the first answer

WITHOUT EXCEPTION:

  • โŒ No business logic in controllers
  • โŒ No hardcoded values (use UPPER_SNAKE_CASE constants)
  • โŒ No generic methods when a dedicated method is necessary
  • โœ… Thin controllers (orchestration only)
  • โœ… Private constants in services for static values
  • โœ… Dedicated methods in services for special routes

If these rules are not respected, the response is invalid and must be corrected.

Quick-Reference Tables for Agents

Guideline Key Rule Example
Class Declaration Final when not extended final class Service
Constructor Property promotion public function __construct(public readonly string $name)
Conditions Yoda + explicit if (false === $obj instanceof Type)
Testing Prophecy + AAA Arrange โ†’ Act โ†’ Assert
Commits type(scope): subject fix(service): correct calculation
Domain Terms Use exact terms Affiliate (not Publisher), Campaign (not Link)
When to Use Pattern Reference
New feature feat(scope): add... ./vendor/hypecodeteam/backend-ai-rules/rules/git_commit_guideline.md
Bug fix fix(scope): correct... ./vendor/hypecodeteam/backend-ai-rules/rules/git_commit_guideline.md
Business logic Service method ./vendor/hypecodeteam/backend-ai-rules/rules/repository_service_patterns.md
Data access Repository OrThrow ./vendor/hypecodeteam/backend-ai-rules/rules/repository_service_patterns.md
Controller input Deserialize RequestDto + validate ./vendor/hypecodeteam/backend-ai-rules/rules/repository_service_patterns.md
Entity validation Rich model methods ./vendor/hypecodeteam/backend-ai-rules/rules/coding_principles.md
Test setup ProphecyTrait + setUp() ./vendor/hypecodeteam/backend-ai-rules/rules/unit_testing.md

AI Usage Guidelines

  • Always reference specific rules when asking for code changes
  • Request examples from existing codebase patterns
  • Specify testing requirements using unit testing standards
  • Use consistent terminology from domain language section
  • Provide context from ubiquitous language for domain-specific features
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
socialdept/atp-orm
cboxdk/laravel-assistant-client
socialdept/atp-resolver
socialdept/tenant-domains
tautvydasr/blade-class-names
socialdept/color-scales
maherelgamil/controller
coleus/widgets
coleus/table
coleus/users
coleus/music
coleus/health
coleus/calendar
coleus/notes
coleus/support
coleus/settings
coleus/apps
seampact/laravel
emmyconceptng/laravel-ng-postcode
jjsquady/round-robin