Skip to content
EN

Back to the catalog

webman-development

webman-php/skills · skills.sh

Open source Repository Open in the app JSON README (API)

About

Skill publicada por webman-php/skills no skills.sh. Instale com: npx skills add webman-php/skills@webman-development

Details

Kind
Agent skills
Publisher
webman-php
Origin
skillssh
Category
ferramentas
Stars
22
Forks
4
Last push
2026-08-31T03:07:59Z
Repository state
ativo
Language
PHP
License
MIT
Added
2026-10-07 06:20:03
Updated
2026-10-07 06:20:03
Origin id
webman-php/skills/webman-development

README

# Webman Development Skill

[简体中文](https://github.com/webman-php/skills/blob/HEAD/README.zh-CN.md)

Source-grounded guidance for developing, reviewing, debugging, testing, and deploying [Webman](https://www.workerman.net/doc/webman/) applications. It helps coding agents use Webman's controller, routing, validation, data, process, coroutine, plugin, and production practices without treating a long-lived Workerman process like an ordinary PHP-FPM application.

## Install

Choose **one** of the following methods. Run project-scoped commands from the root of the Webman project that should use the Skill.

### 1. Ask your coding agent (recommended)

Give Codex, Claude Code, or another Skill-aware coding agent this prompt:

```text
Install the webman-development Skill from https://github.com/webman-php/skills
for this project. Keep the complete skill directory, use your native Skill installer
when available, and verify that the installed SKILL.md is discoverable.
```

The agent should use its native Skill installer or one of the explicit methods below.

### 2. Composer

This option needs PHP and Composer, but does not need Node.js, PowerShell, or `webman/console`:

```bash
composer require --dev webman/skills
php vendor/bin/webman-skills install --agents=codex,claude-code
```

Use `--agents=codex` or `--agents=claude-code` to install for only one agent. Add `--global` to install in the current user's Skill directories instead of the current project. The installer refuses to overwrite an unmanaged same-name directory; inspect it first, or use `--force` to preserve it as a backup before installing.

### 3. npx

If Node.js is available:

```bash
npx skills add webman-php/skills --skill webman-development -a codex -a claude-code
```

Keep only the required `-a` option to target one agent. Add `--copy` when independent copied files are preferable to linked entries.

### 4. Manual installation

Clone or download the repository:

```bash
git clone --depth 1 https://github.com/webman-php/skills.git webman-skills
```

Copy the complete `webman-skills/skills/webman-development/` directory to one of these locations:

| Scope | Codex | Claude Code |
|---|---|---|
| Project | `.agents/skills/webman-development/` | `.claude/skills/webman-development/` |
| Current user | `~/.agents/skills/webman-development/` | `~/.claude/skills/webman-development/` |

Do not copy only `SKILL.md`: the on-demand `references/` are part of the Skill.

### Update

Use the update path that matches the chosen installation method:

```bash
# Composer
composer update webman/skills
php vendor/bin/webman-skills update --agents=codex,claude-code

# npx
npx skills update webman-development

# Git clone/manual copy
git -C webman-skills pull --ff-only
```

After a manual source update, replace only the verified `webman-development` copy; never delete an entire `.agents` or `.claude` directory.

## Use

The skill can activate automatically for a matching Webman task. To call it explicitly:

```text
# Codex
$webman-development add a POST endpoint with typed route parameters and validation

# Claude Code
Use the webman-development skill to add a POST endpoint with typed route parameters and validation.
```

## What it covers

- The resident-process model and cross-request state safety.
- Controllers as the primary entry point: typed parameter binding, HTTP method and route attributes, request injection, validation, middleware, and `make:crud` routing.
- Request/response helpers, uploads, routing, CORS/OPTIONS, middleware scopes, and access-control boundaries.
- `webman/validation` plus `webman/console` generators, only after checking the installed packages and command help.
- Eloquent/ThinkORM-compatible data access, transactions, cache and Redis without reproducing their entire upstream manuals.
- Queues, custom processes, coroutines, plugins, deployment, observability, security, and proportionate verification.

The entry point keeps only routing and important invariants. Detailed API recipes live in `references/` and are loaded only for the task that needs them.

## Repository layout

```text
skills/
  webman-development/
    SKILL.md
    agents/openai.yaml       # optional Codex/ChatGPT UI metadata
    references/              # task-specific Webman guidance
```

This follows the open Agent Skills directory convention. The shared `SKILL.md` and references are portable; editors that do not recognize `agents/openai.yaml` can ignore it.

## Contributing and verification

Keep changes scoped to a documented Webman behavior and preserve progressive disclosure: put routing and durable constraints in `SKILL.md`, and put detailed, conditional guidance in a focused reference. Before submitting a change, validate the YAML frontmatter, relative Markdown links, and that an installer discovers exactly one `webman-development` skill.

For the current installation locations and discovery behavior, use the official [Codex Skills documentation](https://developers.openai.com/codex/skills/) and [Claude Code Skills documentation](https://code.claude.com/docs/en/skills).

More