Scaffold Workbench

Name: Scaffold Workbench
Author: mwguerra

ASecurity

Add Orchestra Workbench (testbench.yaml + workbench/) to an existing Laravel package

35 stars
0 votes
0 copies
1 view
Added September 7, 2026

developmentpythonphpbashtestingdatabase

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 7, 2026

npx -y skills add mwguerra/claude-code-plugins --skill scaffold-workbench --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Scaffold Workbench?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Scaffold Workbench

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mwguerra-scaffold-workbench/badge)](https://www.skillsdirectory.com/skills/mwguerra-scaffold-workbench)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
description: Add Orchestra Workbench (testbench.yaml + workbench/) to an existing Laravel package
allowed-tools: Bash(python3:*), Bash(composer:*), Write, Read, Glob
---

# Workbench Scaffold Skill

Adds Orchestra Workbench to an existing Laravel package for interactive development.

## Usage

When the user wants to add workbench to an existing package:

```bash
python3 ${SKILL_DIR}/scripts/scaffold_workbench.py <vendor/package-name> [options]
```

## Options

- `--project-root` - Specify project root directory

## Examples

```bash
python3 ${SKILL_DIR}/scripts/scaffold_workbench.py mwguerra/my-package
```

## What Gets Created

### Files

1. **testbench.yaml** — Testbench + Workbench configuration
2. **workbench/app/Providers/WorkbenchServiceProvider.php** — Workbench provider
3. **workbench/database/seeders/DatabaseSeeder.php** — Workbench seeder
4. **workbench/resources/views/welcome.blade.php** — Welcome page
5. **workbench/routes/web.php** — Workbench routes

### Directories

- `workbench/app/Models/`
- `workbench/database/factories/`
- `workbench/database/migrations/`

### composer.json Updates

Adds workbench autoload namespaces and serve/build scripts.

## Using Workbench

```bash
cd packages/vendor/package-name
composer update
composer serve
```

This starts a real Laravel application at `http://127.0.0.1:8000` with your package loaded, powered by [Orchestra Workbench](https://packages.tools/workbench).

## Testbench vs Workbench

- **Testbench** = automated testing framework (boots Laravel for PHPUnit/Pest tests)
- **Workbench** = interactive development environment (serves a real Laravel app)
- Both share `testbench.yaml` for configuration
- The `WithWorkbench` trait in TestCase bridges both worlds