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
smartest-project-addition
smartest-project-addition
pekral/ai-olympus
claude-code
project-assessment
prioritization
recommendations
risk-analysis
php-standards
rollout-planning

Use when you want exactly one high-impact, concrete proposal for the next project addition.

Install
php artisan boost:add-skill pekral/ai-olympus

Save this content to: .claude/skills/smartest-project-addition/SKILL.md

## Constraints
- Apply `@rules/php/core-standards.md` **only once it is established that the project is a PHP project (PHP stack in `composer.json`) and the proposed addition touches PHP code** — skip it for a non-PHP project or a non-code proposal; do not load the PHP standards when the addition does not touch PHP.
- Recommend exactly one addition
- Do not include alternative proposals in the final answer
- Do not implement code unless explicitly requested

## Use when
- You want the single most valuable next addition to the project
- You want a concrete recommendation, not a list of ideas

## Required approach
- Inspect the current repository and identify the strongest leverage point across architecture, DX, reliability, performance, security, or delivery speed
- Evaluate candidate ideas by:
    - impact
    - implementation complexity
    - risk
    - reversibility
- Select exactly one proposal with the best overall leverage

## Output
Provide:
- a concise proposal statement
- why this is the best next addition now
- expected business and technical benefits
- key risks and mitigations
- smallest safe implementation plan
- test/validation strategy
- rollout and rollback notes

## Done when
- The recommendation is concrete, measurable, and actionable
- The final answer contains exactly one proposal
- The proposal is justified by impact relative to complexity and risk

Constraints

  • Apply @rules/php/core-standards.md only once it is established that the project is a PHP project (PHP stack in composer.json) and the proposed addition touches PHP code — skip it for a non-PHP project or a non-code proposal; do not load the PHP standards when the addition does not touch PHP.
  • Recommend exactly one addition
  • Do not include alternative proposals in the final answer
  • Do not implement code unless explicitly requested

Use when

  • You want the single most valuable next addition to the project
  • You want a concrete recommendation, not a list of ideas

Required approach

  • Inspect the current repository and identify the strongest leverage point across architecture, DX, reliability, performance, security, or delivery speed
  • Evaluate candidate ideas by:
    • impact
    • implementation complexity
    • risk
    • reversibility
  • Select exactly one proposal with the best overall leverage

Output

Provide:

  • a concise proposal statement
  • why this is the best next addition now
  • expected business and technical benefits
  • key risks and mitigations
  • smallest safe implementation plan
  • test/validation strategy
  • rollout and rollback notes

Done when

  • The recommendation is concrete, measurable, and actionable
  • The final answer contains exactly one proposal
  • The proposal is justified by impact relative to complexity and risk
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.
uni-method/symfony-lib
tacticmedia/scim-server-bundle
neika-ai/symfony-bundle
mattleads/agent-publishing-bundle
glavweb/framework-bundle
glavweb/extra-bundle
glavweb/api-bundle
glavweb/admin-bundle
adachsoft/api-version-bundle
elsayed85/laravel-api-exceptions
ouhssini/laravel-demo-mode
daworks/ncloud-outbound-mailer-driver
gp247/cms
ignibyte/aic-gates
nexa-merchant/blog
novasa/laravel-language-center
opencage/geocode
adolfoholzer/parameters
livenetworks/ln-starter
cgv/localized-resource