القائمة
Use when creating or updating Zolinga modules, wiring services/events in zolinga.json, handling config access, and following core project structure conventions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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).
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()`.
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.
Use when adding localized strings in PHP or HTML, including gettext usage patterns and context-aware translation strings for Zolinga Intl.
Use when writing or reviewing PHP code in this repository to enforce strict typing, naming, file layout, and listener/service interface conventions.
| name | system-module-development |
| description | Use when creating or updating Zolinga modules, wiring services/events in zolinga.json, handling config access, and following core project structure conventions. |
| argument-hint | <module-name> [goal] |
zolinga.json.modules/<module-name>/ and core code in system/.src/ under the target module.global $api; and $api->serviceName. Do not use dependency injection — just global $api.data/system/api.stub.php.zolinga.json.emits section in zolinga.json.zolinga.json changes, bump minor module version to force cache reload, then run bin/zolinga (no parameters) to trigger manifest rescan and install/update pipeline.config://, module-relative paths) when reading config files.$api->log and stored in data/system/logs/messages.log../tmp/ai-*.* with the ai- prefix. For other folders: ./data/system/tmp/, ./public/data/system/tmp/, ./public/dist/system/tmp/, or ./public/tmp/ (for public URL access). Create tmp/ dirs if needed. Clean up after use.system/define.php)| Constant | Value | Description |
|---|---|---|
Zolinga\System\ROOT_DIR | dirname(__DIR__, 1) | Absolute filesystem path to the project root (parent of system/). Use to build absolute paths to any file in the project without hardcoding. |
zolinga.json.data/system/system.cache.json (autoload section).$api->config[...].data/system/system.cache.json when debugging wiring.Zolinga Core.md, then Module Anatomy.md.Manifest File.md and Events and Listeners.md.Services.md, Configuration.md, and Paths and Zolinga URI.md.modules/<module>/skills/<skill-name>/SKILL.md; the installer auto-symlinks them into .agents/skills/{module}-{skill-name} on every install/update run.system/wiki/Zolinga Core.mdsystem/wiki/Zolinga Core/Module Anatomy.mdsystem/wiki/Zolinga Core/Events and Listeners.mdsystem/wiki/Zolinga Core/Manifest File.mdsystem/wiki/Zolinga Core/Services.mdsystem/wiki/Zolinga Core/Configuration.mdsystem/wiki/Zolinga Core/Paths and Zolinga URI.mdsystem/wiki/ref/event/skeleton/module.md