Weave Code
Bundle Ai Kit Laravel Package
symkit/bundle-ai-kit
Symkit Bundle AI Kit is a Laravel/PHP package for adding AI features to applications. It offers ready-to-use services, configuration, and utilities that simplify model calls, prompt handling, and AI-powered workflows, helping developers reduce boilerplate in Laravel projects.
AI rules and optional skills for building Symfony bundles (best practices, SOLID, AbstractBundle, quality tooling)
Frequently asked questions about Bundle Ai Kit
- What is symkit/bundle-ai-kit used for in a Laravel project?
- It is a dev-time Composer plugin that renders versioned AI coding rules into editor-specific paths such as .cursor/rules, .cursor/skills, .cursor/agents, and AGENTS.md at the Composer root. For Laravel teams, the valuable part is the transferable quality-gate configuration and rule content; the plugin ships no runtime application code. Treat it as tooling for AI-assisted development, not as a runtime AI feature package.
- How do I install symkit/bundle-ai-kit with Composer 2.2 or later?
- Install it as a dev dependency with composer require --dev symkit/bundle-ai-kit, then add the plugin to config.allow-plugins in composer.json because Composer 2.2+ blocks plugins by default. The plugin runs on install and writes rules into the Composer root. Commit the generated files only if your team wants to review and track rule changes.
- Does symkit/bundle-ai-kit add runtime AI provider support to Laravel?
- No. The technical assessment describes it as a dev-time tooling dependency with no runtime surface, meaning none of its classes are loaded by your Laravel application. The overview language about AI provider configuration and prompt abstractions should not be read as a runtime SDK. If you need provider calls, model routing, or prompt execution at runtime, evaluate a separate package.
- Which PHP, Composer, and Laravel versions does symkit/bundle-ai-kit support?
- CI asserts PHP 8.2, 8.3, and 8.4 across Composer 2 and Composer 3, which fits a modern Laravel estate. The assessment does not state a Laravel version constraint because the mechanism is framework-agnostic and works in any Composer 2 project. Check the repository before assuming support for older Laravel or PHP versions.
- Which files does symkit/bundle-ai-kit write, and does it support Cursor only?
- It writes into .cursor/rules/, .cursor/skills/*, .cursor/agents/, and AGENTS.md at the Composer root. There is deliberately no editor abstraction, so the paths are fixed inside AiRulesInstaller. Claude Code, Codex, and Copilot users get AGENTS.md and must wire the remaining editor integration by hand.
- Is it safe to run symkit/bundle-ai-kit during composer install in CI?
- Be cautious. A Composer plugin executes arbitrary PHP on every developer install and every CI job, and sync-on-install mutates tracked files, which can create diff noise or trip clean-checkout assertions. Pin the package exactly or vendor it, and decide whether require-dev is installed in staging or production builds. There is no external review surface at 3 stars and 0 dependents.
- How do I update or remove outdated AI rules synced by symkit/bundle-ai-kit?
- The plugin is merge-only and follows a never-delete-user-files default, and the assessment notes no documented prune or manifest of synced files. That means a version bump cannot reliably remove superseded rules, so the ruleset can drift silently and agents may follow obsolete conventions. Ask for a dry-run/diff mode and a manifest-based prune before relying on updates.
- How much of the symkit/bundle-ai-kit rule corpus applies to Laravel?
- Expect roughly 20–30% of the rule corpus to apply directly to Laravel work. The content is Symfony-bundle specific, covering AbstractBundle, bundle extension/prepend conventions, and bundle test patterns. The reusable parts are the quality bar and CI patterns, not the framework-specific rules.
- Is symkit/bundle-ai-kit production-ready despite having only 3 stars?
- The code-quality instrumentation is credible: PHPStan level 9 with no baselines, GrumPHP pre-commit mirroring CI, Infection with a covered-MSI floor, Deptrac layer enforcement, and a PHP × Composer CI matrix. That makes it a useful reference implementation for a Laravel team's quality gate. It does not prove ecosystem health or long-term maintenance.
- What is the recommended way to evaluate symkit/bundle-ai-kit before adopting it?
- Start read-only: clone the repository and read ai/cursor/rules/*.mdc and ai/skills/*/SKILL.mdc directly to extract transferable rules. Adopt the delivery mechanism only if Cursor is your team's standardized editor; otherwise the plugin is dead weight and only the content is valuable. Confirm the rule corpus license and fork permissions before creating an internal ruleset, and plan for sole-maintainer risk.
Weaver
How can I help you explore Laravel packages today?