Download the PHP package mohamed-ashraf-elsaed/claude-kit without Composer

On this page you can find all versions of the php package mohamed-ashraf-elsaed/claude-kit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of mohamed-ashraf-elsaed/claude-kit

Informations about the package claude-kit

claude-kit — one command sets up Claude Code and a quality gate for Laravel

claude-kit

Set up Claude Code — and any AI coding agent — on a Laravel project in one command.
Engineering rules, a quality gate (PHPStan · Pint · Pest), skills, feature-doc scaffolding, and stack-aware frontend tooling.

Latest version Tests Lint PHP version Downloads

claude-kit packages a battle-tested setup so every Laravel project — and every developer — gets the same guardrails instead of hand-copying config between repos: a Stop-hook + pre-commit quality gate, reusable Claude Code skills, PHPStan level 7 + strict-rules, Pint, Pest with an optional coverage floor, an architecture test suite that actually runs, feature-doc scaffolding, and stack-aware frontend tooling (Vue, React, Livewire, Blade, or none).

Who it's for

Table of contents

Requirements

Installation

claude-kit itself depends only on Laravel — it will not pull Pint, PHPStan, or a test runner into your project, and it will not move a version you already have. The installer detects your frontend stack (Inertia + Vue, Inertia + React, Livewire, Blade, or API-only), asks which parts to scaffold, works out the exact tooling your answers need, and offers to install it:

Anything already in your project is left out of that list. Decline it, or run with --no-interaction, and the command is printed for you to run yourself.

[!NOTE] If that command fails on Pest, it is an upstream conflict, not claude-kit. Current Pest releases conflict with phpunit/phpunit newer than 12.5.30, and the Laravel 13 skeleton pins a newer PHPUnit — so composer require --dev pestphp/pest cannot resolve on a fresh Laravel 13 app even with claude-kit uninstalled. Re-running the same command with -W resolves it by letting composer downgrade PHPUnit to 12.5.30. claude-kit never adds -W for you; accepting that downgrade is your decision.

Then:

Not published to Packagist yet? Install straight from GitHub by adding this to your composer.json and running composer require --dev mohamed-ashraf-elsaed/claude-kit:dev-main:

What it installs

Part What lands in your project
.claude core .claude/settings.json (hook wiring + permission allowlist, deep-merged into any existing file), the reusable skills for your stack, and .mcp.json (Laravel Boost).
CLAUDE.md Short and specific: project identity, the quality gate, the feature-doc rule, and an index of the installed rules — inside claude-kit:begin/end markers, so re-running refreshes it without touching your own additions.
Rules .claude/rules/ — one file per selected architecture layer, a clean-code rule (strict / balanced / relaxed), a stack-specific frontend rule, and the always-on anti-overengineering + anti-assumption rules. Path-scoped where it makes sense, so they load only when relevant.
Agents Read-only design-reviewer (output vs the stated design) and docs-reviewer (output vs supplied docs).
Workflow skills /commit, /deploy (both you-only), /dead-code, /codemap.
Quality gate phpstan.neon (your level, Larastan and strict-rules toggles), pint.json, a generated tests/Arch/ArchTest.php matching your layers — plus a tests/Arch testsuite added to your phpunit.xml so it actually runs — .githooks/pre-commit, an edit-time PHPStan hook, and merged composer scripts.
Frontend Stack-matching eslint.config.js / .prettierrc / tsconfig.json, plus merged package.json scripts and devDependencies. Skipped for API-only projects.
Docs features/_TEMPLATE/ + features/README.md, .editorconfig, .gitattributes.
CI Generic GitHub Actions tests.yml and lint.yml.

Nothing is clobbered. An identical file is left alone, a file you have edited is asked about (keep / replace / show diff), settings.json and CLAUDE.md are merged rather than replaced, and composer.json / package.json keep your entries. The conventions claude-kit writes are opinionated defaults — read them and adapt them to how your team actually works.

Choosing what to install

claude-kit:install is a fully interactive configurator — it asks what you want rather than assuming:

Your answers are recorded in .claude/claude-kit.json, which the quality gate and claude-kit:update read.

The hybrid update model

The quality gate

vendor/mohamed-ashraf-elsaed/claude-kit/runtime/quality-checks.sh is the single source of truth. It runs Pint, PHPStan at your level, and your test runner with your coverage floor, then the frontend checks your package.json actually defines. The same script backs the git pre-commit hook, Claude's Stop hook, and CI — so the gate is identical everywhere.

Documentation

Full guides live in the wiki and the docs/ directory:

Contributing

Contributions are welcome! Please read CONTRIBUTING.md and the SemVer; see RELEASING.md.

Security

Please report vulnerabilities privately — see SECURITY.md.

License

The MIT License. See LICENSE.

All versions of claude-kit with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
illuminate/console Version ^11.0 || ^12.0 || ^13.0
illuminate/filesystem Version ^11.0 || ^12.0 || ^13.0
illuminate/support Version ^11.0 || ^12.0 || ^13.0
laravel/prompts Version ^0.1 || ^0.2 || ^0.3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package mohamed-ashraf-elsaed/claude-kit contains the following files

Loading the files please wait ...