一键在 Manus 中运行任何 Skill

system-php-coding-style

星标4

分支0

更新时间2026年6月27日 15:55

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

安装

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

在 Manus 中运行

来源

webdevelopers-eu

webdevelopers-eu/zolinga

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

下载

在 Manus 中运行

Zolinga PHP Coding Style

Use When

Implementing new PHP classes, listeners, services, or models.
Refactoring PHP for repository style compliance.

Rules

Add declare(strict_types=1); at file top.
Target PHP 8.4 compatibility.
Place PHP code under modules/<module-name>/src/.
Keep function parameters typed and declare return types.
Add concise PHPDoc; include usage examples when useful.
Split long functions into smaller units.
Use naming conventions:

camelCase for variables/methods.
PascalCase for classes.
Up to 4 consecutive uppercase initials stay uppercased, e.g. XMLHttpRequest, HTTPClient, getURL().
kebab-case for filenames (except wiki article titles and PHP class files — see rule 8).

PHP class files must mirror the namespace path after the autoload prefix, using the exact class name as filename. Given "Zolinga\\Seo\\": "src/" in zolinga.json autoload, the class Zolinga\Seo\Listeners\IndexNowListener must be at <module>/src/Listeners/IndexNowListener.php. This is not kebab-case — class files use PascalCase filenames matching the class name. Without this the autoloader won't find the class.
Put DB model classes under src/Model.
Put enum-like keyword sets in src/Types where useful.
Listeners implement Zolinga\System\Events\ListenerInterface.
Services implement Zolinga\System\Events\ServiceInterface.
Provide a complete class example and brief comments explaining each public or protected property and/or accessor.
Use $event::STATUS_* constants (e.g. $event::STATUS_OK, $event::STATUS_ERROR, $event::STATUS_BAD_REQUEST) when calling $event->setStatus(). Never pass raw integers — setStatus() accepts StatusEnum. For dynamic HTTP codes use StatusEnum::tryFrom($code) ?? $event::STATUS_ERROR.
Methods and functions must not be longer than 50 lines. If they are, break them into smaller private methods or separate class helpers.
Do not do one-line method wrappers, inline them instead.
If there is a method that is only used in one place, consider inlining it unless it increases the function's complexity, size or decreases significantly the readability of the code.

Documentation Abstract

Use Module Anatomy.md for source placement conventions.
Use Services.md and Events and Listeners.md to align service/listener implementation style.
Use API class references when matching method/event typing patterns.

References

system/wiki/Zolinga Core/Module Anatomy.md
system/wiki/Zolinga Core/Services.md
system/wiki/Zolinga Core/Events and Listeners.md
system/wiki/Zolinga Core/Manifest File.md
system/wiki/ref/class/Zolinga/System/Events/Event.md
system/wiki/ref/class/Zolinga/System/Events/AuthorizeEvent.md
system/wiki/ref/class/Zolinga/System/Events/ContentEvent.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-create-handler

webdevelopers-eu/zolinga

Use when creating a new event handler/listener in a Zolinga module, including event naming, class placement, origin filtering, rights checks, and event object selection.

2026-06-274

Zolinga PHP Coding Style

Use When

Implementing new PHP classes, listeners, services, or models.

Refactoring PHP for repository style compliance.

Rules

Add declare(strict_types=1); at file top.

Target PHP 8.4 compatibility.

Place PHP code under modules/<module-name>/src/.

Keep function parameters typed and declare return types.

Add concise PHPDoc; include usage examples when useful.

Split long functions into smaller units.

Use naming conventions:

camelCase for variables/methods.

PascalCase for classes.

Up to 4 consecutive uppercase initials stay uppercased, e.g. XMLHttpRequest, HTTPClient, getURL().

kebab-case for filenames (except wiki article titles and PHP class files — see rule 8).

PHP class files must mirror the namespace path after the autoload prefix, using the exact class name as filename. Given "Zolinga\\Seo\\": "src/" in zolinga.json autoload, the class Zolinga\Seo\Listeners\IndexNowListener must be at <module>/src/Listeners/IndexNowListener.php. This is not kebab-case — class files use PascalCase filenames matching the class name. Without this the autoloader won't find the class.

Put DB model classes under src/Model.

Put enum-like keyword sets in src/Types where useful.

Listeners implement Zolinga\System\Events\ListenerInterface.

Services implement Zolinga\System\Events\ServiceInterface.

Provide a complete class example and brief comments explaining each public or protected property and/or accessor.

Use $event::STATUS_* constants (e.g. $event::STATUS_OK, $event::STATUS_ERROR, $event::STATUS_BAD_REQUEST) when calling $event->setStatus(). Never pass raw integers — setStatus() accepts StatusEnum. For dynamic HTTP codes use StatusEnum::tryFrom($code) ?? $event::STATUS_ERROR.

Methods and functions must not be longer than 50 lines. If they are, break them into smaller private methods or separate class helpers.

Do not do one-line method wrappers, inline them instead.

If there is a method that is only used in one place, consider inlining it unless it increases the function's complexity, size or decreases significantly the readability of the code.

Documentation Abstract

Use Module Anatomy.md for source placement conventions.

Use Services.md and Events and Listeners.md to align service/listener implementation style.

Use API class references when matching method/event typing patterns.

References

system/wiki/Zolinga Core/Module Anatomy.md

system/wiki/Zolinga Core/Services.md

system/wiki/Zolinga Core/Events and Listeners.md

system/wiki/Zolinga Core/Manifest File.md

system/wiki/ref/class/Zolinga/System/Events/Event.md

system/wiki/ref/class/Zolinga/System/Events/AuthorizeEvent.md

system/wiki/ref/class/Zolinga/System/Events/ContentEvent.md

name	system-php-coding-style
description	Use when writing or reviewing PHP code in this repository to enforce strict typing, naming, file layout, and listener/service interface conventions.
argument-hint	<module-name> [class-or-file]