一键在 Manus 中运行任何 Skill

system-run-and-test

星标4

分支0

更新时间2026年5月7日 16:44

Use when running Zolinga locally, triggering CLI-origin events, evaluating scripts, and finding the correct run/test command workflow.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

webdevelopers-eu

webdevelopers-eu/zolinga

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Zolinga Run and Test

Use When

Running local development server or CLI events.
Executing scripts for diagnostics.
Validating behavior after code changes.

Workflow

Always use bin/zolinga — never run php -f or other direct PHP invocations. The bin/zolinga wrapper sets up the full framework environment (autoloading, config, services, error handling). Direct php -f calls will miss framework initialization and fail.
Discover CLI capabilities with bin/zolinga --help.
Trigger CLI-origin events with bin/zolinga <event-name> <params>.
Execute ad hoc scripts with bin/zolinga --execute=\"<path>\".
Evaluate short snippets with bin/zolinga --eval=\"<php-code>\".
Start local web server with bin/zolinga --server[=[HOST:]PORT] and optional --xdebug. Default is 0.0.0.0:8888. Omit the argument to use the default, e.g. bin/zolinga --server. See bin/zolinga --help for details.
Use config/local.json then config/global.json (baseURL) to determine front-end URL defaults.
Create a new module with bin/zolinga skeleton:module --name=<module-name>.
Generate Apache config with bin/zolinga skeleton:apache ... (see system/wiki/ref/event/skeleton/apache.md).
Process HTML/XML content through the CMS pipeline from CLI with bin/zolinga process:content --input=<file> --url=/test/page (see system/wiki/ref/event/process/content.md).

Temporary Scripts

Ad-hoc temporary, debugging, or testing scripts must follow these placement rules:

Default: ./tmp/ai-*.* — always use the ai- prefix (e.g. ai-test-db.php, ai-check-urls.php).
Data folder: ./data/system/tmp/ai-*.*
Public data folder: ./public/data/system/tmp/ai-*.*
Dist folder: ./public/dist/system/tmp/ai-*.*
Public URL access: ./public/tmp/ai-*.* — for scripts that must be reachable via HTTP.

Create the tmp/ directory if it does not exist. Always clean up temporary scripts after use.

Stdout vs Stderr

bin/zolinga writes system logs, warnings, and debug messages to stderr, while the actual event response (JSON) and any listener echo output go to stdout. This lets you separate structured output from diagnostic noise using shell redirection:

# Capture only the JSON response
bin/zolinga my:event > response.json

# Capture response and suppress logs
bin/zolinga my:event > response.json 2> /dev/null

# Capture response and logs separately
bin/zolinga my:event > response.json 2> debug.log

# Pipe response to another tool while still seeing logs in terminal
bin/zolinga my:event | jq '.response.data'

Runtime Constants (defined in `system/define.php`)

Constant	Value	Description
`Zolinga\System\IS_CLI`	`PHP_SAPI === 'cli'`	`true` when running from command line, `false` during web requests. Use to branch CLI-only logic (e.g. skip output buffering, avoid `exit()` in web context).
`Zolinga\System\IS_INTERACTIVE`	`IS_CLI && posix_isatty(STDOUT)` or env `INTERACTIVE`	`true` when running in an interactive terminal (TTY) or when `INTERACTIVE=1` is set. Use to decide whether to show progress bars, prompts, or colored output.

Documentation Abstract

Begin with Running the System.md for execution modes.
Use command-line and custom script docs for CLI workflows.
Use request and AJAX pages for runtime behavior checks after deployment.

References

system/wiki/Zolinga Core/Running the System.md
system/wiki/Zolinga Core/Running the System/Command Line.md
system/wiki/Zolinga Core/Running the System/Custom Scripts.md
system/wiki/Zolinga Core/Running the System/Page Request.md
system/wiki/Zolinga Core/Running the System/AJAX.md
system/wiki/ref/event/skeleton/apache.md
system/wiki/templates/Running the System.md
system/wiki/Zolinga Core/Installing Additional Modules.md

同仓库更多 Skills

同仓库

system-create-mcp-resource

webdevelopers-eu/zolinga

Use when creating or updating MCP resources — static files exposed to MCP clients via `resources/list` and `resources/read`. Covers `.meta.json` descriptors, URI rewriting, dynamic resources via `mcp:resources/list` event hook, and the `mcp-system` scheme.

2026-07-224

system-convert-remote-event-to-mcp-tool

webdevelopers-eu/zolinga

Use when exposing an existing `origin: ["remote"]` listener as an MCP tool without rewriting the handler. Covers the one-line manifest pattern that re-uses the same class+method, plus the minimal schema work needed to satisfy `McpToolsListHandler::collectTools()`. Complements system-create-mcp-tool (which covers the greenfield case).

2026-07-214

system-create-mcp-tool

webdevelopers-eu/zolinga

Use when exposing a Zolinga event handler as an MCP (Model Context Protocol) tool — i.e. a method clients can invoke via JSON-RPC `tools/call`. Covers handler class, manifest binding, JSON Schemas, the `Tools\CallEvent` contract, and the `schema.response` requirement enforced by `McpToolsListHandler::collectTools()`.

2026-07-214

system-events-client

webdevelopers-eu/zolinga

Use when working with the JavaScript client-side event system in Zolinga. Covers the Event class, Api gateway, dispatching events from JS to PHP, receiving broadcastBack responses, inter-component communication via BroadcastChannel, and web component integration.

2026-07-154

system-translations

webdevelopers-eu/zolinga

Use when adding localized strings in PHP or HTML, including gettext usage patterns and context-aware translation strings for Zolinga Intl.

2026-07-064

system-php-coding-style

webdevelopers-eu/zolinga

Use when writing or reviewing PHP code in this repository to enforce strict typing, naming, file layout, and listener/service interface conventions.

2026-06-274

Zolinga Run and Test

Use When

Running local development server or CLI events.

Executing scripts for diagnostics.

Validating behavior after code changes.

Workflow

Always use bin/zolinga — never run php -f or other direct PHP invocations. The bin/zolinga wrapper sets up the full framework environment (autoloading, config, services, error handling). Direct php -f calls will miss framework initialization and fail.

Discover CLI capabilities with bin/zolinga --help.

Trigger CLI-origin events with bin/zolinga <event-name> <params>.

Execute ad hoc scripts with bin/zolinga --execute=\"<path>\".

Evaluate short snippets with bin/zolinga --eval=\"<php-code>\".

Start local web server with bin/zolinga --server[=[HOST:]PORT] and optional --xdebug. Default is 0.0.0.0:8888. Omit the argument to use the default, e.g. bin/zolinga --server. See bin/zolinga --help for details.

Use config/local.json then config/global.json (baseURL) to determine front-end URL defaults.

Create a new module with bin/zolinga skeleton:module --name=<module-name>.

Generate Apache config with bin/zolinga skeleton:apache ... (see system/wiki/ref/event/skeleton/apache.md).

Process HTML/XML content through the CMS pipeline from CLI with bin/zolinga process:content --input=<file> --url=/test/page (see system/wiki/ref/event/process/content.md).

Temporary Scripts

Ad-hoc temporary, debugging, or testing scripts must follow these placement rules:

Default: ./tmp/ai-*.* — always use the ai- prefix (e.g. ai-test-db.php, ai-check-urls.php).

Data folder: ./data/system/tmp/ai-*.*

Public data folder: ./public/data/system/tmp/ai-*.*

Dist folder: ./public/dist/system/tmp/ai-*.*

Public URL access: ./public/tmp/ai-*.* — for scripts that must be reachable via HTTP.

Create the tmp/ directory if it does not exist. Always clean up temporary scripts after use.

Stdout vs Stderr

# Capture only the JSON response bin/zolinga my:event > response.json # Capture response and suppress logs bin/zolinga my:event > response.json 2> /dev/null # Capture response and logs separately bin/zolinga my:event > response.json 2> debug.log # Pipe response to another tool while still seeing logs in terminal bin/zolinga my:event | jq '.response.data'

Runtime Constants (defined in system/define.php)

Constant

Value

Description

Zolinga\System\IS_CLI

PHP_SAPI === 'cli'

true when running from command line, false during web requests. Use to branch CLI-only logic (e.g. skip output buffering, avoid exit() in web context).

Zolinga\System\IS_INTERACTIVE

IS_CLI && posix_isatty(STDOUT) or env INTERACTIVE

true when running in an interactive terminal (TTY) or when INTERACTIVE=1 is set. Use to decide whether to show progress bars, prompts, or colored output.

Documentation Abstract

Begin with Running the System.md for execution modes.

Use command-line and custom script docs for CLI workflows.

Use request and AJAX pages for runtime behavior checks after deployment.

References

system/wiki/Zolinga Core/Running the System.md

system/wiki/Zolinga Core/Running the System/Command Line.md

system/wiki/Zolinga Core/Running the System/Custom Scripts.md

system/wiki/Zolinga Core/Running the System/Page Request.md

system/wiki/Zolinga Core/Running the System/AJAX.md

system/wiki/ref/event/skeleton/apache.md

system/wiki/templates/Running the System.md

system/wiki/Zolinga Core/Installing Additional Modules.md

name	system-run-and-test
description	Use when running Zolinga locally, triggering CLI-origin events, evaluating scripts, and finding the correct run/test command workflow.
argument-hint	[event-name] [params]

system-run-and-test

Zolinga Run and Test

Use When

Workflow

Temporary Scripts

Stdout vs Stderr

Runtime Constants (defined in system/define.php)

Documentation Abstract

References

同仓库更多 Skills

同仓库更多 Skills

Zolinga Run and Test

Use When

Workflow

Temporary Scripts

Stdout vs Stderr

Runtime Constants (defined in system/define.php)

Documentation Abstract

References

Runtime Constants (defined in `system/define.php`)

Runtime Constants (defined in `system/define.php`)