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.

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.

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.

Use when creating or wiring a Zolinga service exposed on global $api via system:service events, including manifest sugar, naming, initialization, and special service/listener combinations.

Use when writing or updating user-facing wiki documentation for features, modules, events, or content tags. Guides a user-oriented writing style focused on tasks and outcomes rather than internal implementation.

Use when creating, dispatching, or handling PHP server-side events in Zolinga. Covers event class hierarchy, status/message access, origin types, stoppable events, authorization, manifest wiring, and common pitfalls.

How to query the Zolinga system's runtime state — merged manifest cache, API service stubs, configuration layers, and log files — using jq, grep, tail, and PHP.

Use when serving JSON, plain text, or other non-HTML content from a URL path that goes through the Zolinga content pipeline (public/index.php). Covers the PreflightEvent + ContentEvent two-listener pattern for switching MIME type and generating the response body.

Use when you need to inspect database schema, list tables, view table structure, or run read-only SELECT queries for debugging purposes using the mysql CLI.

Use when creating, updating, or consolidating Agent Skills in this repository, including canonical placement, naming, and AGENTS.md alignment.

Use when creating or modifying module installation scripts, update migration scripts, or initial file assets (dist/). Covers the install-vs-update lifecycle, naming, ordering, and the rule that install scripts must stay complete while update scripts must only be added.

Guidance preparing a release of the system core or any module, including updating the changelog and version number.

Use when creating or modifying code in Zolinga modules, especially for following established coding standards and best practices.

Use when writing localizable PHP code in Zolinga modules — dgettext/dngettext usage, domain naming, and context separators.

Use when creating or updating Zolinga modules, wiring services/events in zolinga.json, handling config access, and following core project structure conventions.

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

Use when setting up a basic Zolinga installation, checking prerequisites, fixing writable-path problems, configuring the local URL, and starting the framework for the first time.

Use when implementing inter-process locking or concurrency control in Zolinga modules. Covers the registry-based MySQL lock API.

Use when creating or updating CHANGELOG.md files in Zolinga modules. Covers Keep a Changelog format, SemVer versioning, and the rule that every zolinga.json version bump must be accompanied by a CHANGELOG.md entry.

Use when creating or editing module zolinga.json manifests, including listen/emit/autoload/config/webComponents/dependencies conventions and validation-oriented authoring.

Use when creating or modifying database schema in Zolinga modules, including install SQL and update migration scripts with naming conventions.

Use before implementing any new feature — check existing services, events, content tags, and installable modules first. Avoid duplicating functionality that already exists in the system.

Use when creating or modifying Zolinga web components in install/dist, registering them through module zolinga.json, and documenting them correctly.

Use when placing static files (favicon, robots, verification files, etc.) into the virtual web-root overlay so they are served from root URLs without modifying public/.

Use when implementing CMS content tag handlers (cms:content:tagName), including listener contracts, DOM manipulation rules, and required wiki docs.

Use when implementing sensitive actions or reviewing Zolinga code for authorization gaps, unsafe request handling, and common security mistakes.

Use when: working with this module. Replace this description with specific trigger phrases describing what the skill helps accomplish and when to invoke it.

Use when creating module-specific API endpoints in install/dist and wiring them to load the Zolinga system correctly.