PHPackages                             imagewize/elayne-cli - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [CLI &amp; Console](/categories/cli)
4. /
5. imagewize/elayne-cli

Abandoned → [imagewize/pt-cli](/?search=imagewize%2Fpt-cli)ArchivedLibrary[CLI &amp; Console](/categories/cli)

imagewize/elayne-cli
====================

CLI scaffolding tool for Elayne WordPress block theme patterns

v1.9.0(1mo ago)026GPL-2.0-or-laterPHPPHP &gt;=8.0

Since Apr 12Pushed 1mo agoCompare

[ Source](https://github.com/imagewize/elayne-cli)[ Packagist](https://packagist.org/packages/imagewize/elayne-cli)[ RSS](/packages/imagewize-elayne-cli/feed)WikiDiscussions main Synced 1w ago

READMEChangelog (10)Dependencies (1)Versions (24)Used By (0)

Elayne CLI
==========

[](#elayne-cli)

> **Deprecated** — This package is no longer maintained. All functionality has been absorbed into [`imagewize/pt-cli`](https://github.com/imagewize/pt-cli) v2.0.0.
>
> ```
> composer global remove imagewize/elayne-cli
> composer global require imagewize/pt-cli
> ```
>
>
>
> Commands are identical — `pattern:create`, `layout:create`, `style:create`, `pattern:list` — now alongside `pt-cli check`.

CLI scaffolding tool for [Elayne](https://github.com/imagewize/elayne), a WordPress block theme. Generates WordPress block pattern PHP files, layout patterns, and theme style variation JSON files interactively from pre-built templates.

Requirements
------------

[](#requirements)

- PHP &gt;= 8.0
- Composer

Installation
------------

[](#installation)

```
composer require imagewize/elayne-cli
```

Or clone and install locally:

```
git clone https://github.com/imagewize/elayne-cli.git
cd elayne-cli
composer install
```

Shorter commands (optional)
---------------------------

[](#shorter-commands-optional)

Add these scripts to your theme's `composer.json` to avoid typing `vendor/bin/elayne` every time:

```
"scripts": {
    "pattern:list":   "@php ./vendor/bin/elayne pattern:list",
    "pattern:create": "@php ./vendor/bin/elayne pattern:create",
    "layout:create":  "@php ./vendor/bin/elayne layout:create",
    "style:create":   "@php ./vendor/bin/elayne style:create"
}
```

Then run `composer pattern:list`, `composer pattern:create`, `composer layout:create`, or `composer style:create`.

To use the bare `elayne` command from any project directory, add `./vendor/bin` to your shell PATH:

```
# ~/.zshrc or ~/.bashrc
export PATH="./vendor/bin:$PATH"
```

After reloading your shell (`source ~/.zshrc`) you can run `elayne pattern:list`, `elayne pattern:create`, `elayne layout:create`, and `elayne style:create` directly.

Usage
-----

[](#usage)

### List available templates, snippets, layouts, categories, and style presets

[](#list-available-templates-snippets-layouts-categories-and-style-presets)

```
vendor/bin/elayne pattern:list
```

### Scaffold a new pattern (interactive)

[](#scaffold-a-new-pattern-interactive)

```
vendor/bin/elayne pattern:create
```

You will be prompted for pattern title, slug, category, template, keywords, and output directory. Use `--with-style` to also generate a companion CSS file, and `--shell-only` for an editor-first workflow (PHP header + paste marker only).

### Scaffold a new layout pattern (interactive)

[](#scaffold-a-new-layout-pattern-interactive)

```
vendor/bin/elayne layout:create
```

You will be prompted for pattern title, slug, layout type, category, keywords, and output directory. Use `--shell-only` for an editor-first workflow.

Example non-interactive usage:

```
vendor/bin/elayne layout:create \
  --title="Home Hero" \
  --slug="elayne/home-hero" \
  --layout=hero-image-right \
  --category=elayne/hero \
  --keywords="hero, home" \
  --output-dir=./patterns
```

### Scaffold a new style variation (interactive)

[](#scaffold-a-new-style-variation-interactive)

```
vendor/bin/elayne style:create
```

You will be prompted for style name, vertical preset (or custom colors), and output directory.

Example non-interactive usage:

```
vendor/bin/elayne style:create --name="Ocean Legal" --vertical=legal
```

### Non-interactive pattern creation

[](#non-interactive-pattern-creation)

```
vendor/bin/elayne pattern:create \
  --title="My Pattern" \
  --slug="elayne/my-pattern" \
  --template=hero-cover \
  --category=elayne/hero \
  --keywords="hero, banner" \
  --output-dir=./patterns \
  --with-style \
  --style-dir=./assets/styles/block-styles
```

With `--shell-only` (editor-first workflow):

```
vendor/bin/elayne pattern:create \
  --title="My Pattern" \
  --slug="elayne/my-pattern" \
  --template=hero-cover \
  --category=elayne/hero \
  --shell-only
```

The `--slug` option accepts the full `elayne/` form or just the bare slug — the `elayne/` prefix is stripped automatically.

Documentation
-------------

[](#documentation)

Detailed reference material is available in the [docs/](docs/) directory:

- [📄 Templates](docs/templates.md) — Available pattern templates and descriptions
- [📄 Layouts](docs/layouts.md) — Structural layout patterns for the `layout:create` command
- [📄 Snippets](docs/snippets.md) — Reusable block markup fragments
- [📄 Categories](docs/categories.md) — Available pattern categories
- [📄 CSS Stubs](docs/css-stubs.md) — CSS file generation and custom stubs
- [📄 Style Presets](docs/style-presets.md) — Theme style variation color palettes

Generated pattern file
----------------------

[](#generated-pattern-file)

The command writes a `.php` file to the output directory. Example output for a blank pattern:

```

```

After generation, add your block markup inside the file and flush the WordPress pattern cache.

License
-------

[](#license)

GPL-2.0-or-later — see [LICENSE.md](LICENSE.md) for details.

###  Health Score

41

—

FairBetter than 87% of packages

Maintenance93

Actively maintained with recent releases

Popularity9

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity48

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~1 days

Total

21

Last Release

33d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/01563ca58ee6cd8347183741d139584749756ca5e02cd062915ca0b5edcc8057?d=identicon)[jasperf](/maintainers/jasperf)

---

Top Contributors

[![jasperf](https://avatars.githubusercontent.com/u/344138?v=4)](https://github.com/jasperf "jasperf (74 commits)")

### Embed Badge

![Health badge](/badges/imagewize-elayne-cli/health.svg)

```
[![Health](https://phpackages.com/badges/imagewize-elayne-cli/health.svg)](https://phpackages.com/packages/imagewize-elayne-cli)
```

###  Alternatives

[illuminate/console

The Illuminate Console package.

13045.3M6.1k](/packages/illuminate-console)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
