Download the PHP package webminty/boost-webminty-guidelines without Composer

On this page you can find all versions of the php package webminty/boost-webminty-guidelines. 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?

Informations about the package boost-webminty-guidelines

Boost Webminty Guidelines

A Laravel Boost plugin that provides Webminty's Laravel & PHP coding standards as an AI skill. When installed, AI code assistants automatically follow Webminty's conventions for any Laravel or PHP work.

Requirements

Installation

The package auto-discovers via Laravel's package discovery — no additional setup required.

What It Does

This package registers four skills with Laravel Boost:

Skill Activates When
webminty-laravel-standards Writing, editing, or reviewing any Laravel/PHP code
webminty-tailwind-standards Writing or editing Tailwind CSS in Blade, Livewire, Inertia, or the CSS entry file
webminty-livewire-standards Working on Livewire components, form objects, or wire: directives
webminty-inertia-standards Working on controllers returning Inertia responses, shared data, or Inertia testing

Skills activate automatically based on context, ensuring consistent adherence to Webminty's conventions regardless of frontend stack.

Standards Overview

PHP

Laravel

Tailwind CSS

Naming Conventions

What Convention Example
URLs kebab-case /about-us
Route names dot notation tickets.show
Models Singular PascalCase User
Actions Verb-first PascalCase CreateTicket
Tables Plural snake_case mash_items
Columns snake_case is_active
Views kebab-case ticket-list.blade.php
Commands app: prefix, kebab-case app:send-email

Code Quality Tools

Tool Purpose
Laravel Pint Code formatting
PHPStan + Larastan Static analysis (level 5)
Rector Automated refactoring
Pest PHP Testing

Per-Project File Conventions

In addition to coding standards, this package mandates three documentation files at the root of every project that installs it. AI assistants will create and maintain these files automatically as work progresses.

File Purpose Update trigger
features.md Canonical record of what the product does — Status: In Development \| Live, then user-facing features and backend features. Used later for documentation, marketing copy, and build-out planning. End of any feature/PR that adds, changes, or removes a user-facing capability or backend feature.
DECISIONS.md Append-only log of non-obvious technical and architectural decisions (stack picks, package choices, data-model trade-offs, opting out of Laravel defaults). Each entry: ## YYYY-MM-DD — Title, Decision, Why, Alternatives considered. When making a choice another developer would reasonably ask "why did we do it this way?" about. Prior entries are never edited or deleted.
CHANGELOG.md Reverse-chronological log of user-visible changes, grouped by Added / Changed / Fixed / Removed / Deprecated / Security under a date or version heading. Follows Keep a Changelog. When shipping a release, deploy, or user-visible change. Pre-launch projects collect entries under ## Unreleased.

features.md is distinct from README.md: README covers how to install, run, and develop the project; features.md covers what the product does. The full convention details (including what not to put in each file) live in the always-loaded core.blade.php guideline.

Full Reference

The complete guidelines are available: https://github.com/webmintydotcom/standards

For a Laravel Quickstart: https://github.com/webmintydotcom/laravel-quickstart

Changelog

This package follows Semantic Versioning. See CHANGELOG.md for release history.

Thank you

Webminty team

All versions of boost-webminty-guidelines with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
illuminate/support Version ^11.0|^12.0|^13.0
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 webminty/boost-webminty-guidelines contains the following files

Loading the files please wait ...