webdevelopers-eu

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 HTML that needs static translation via gettext attributes. Covers the gettext attribute syntax, gettext-context, nested element translation, meta tag, and translation modes.

Use when writing PHP code that needs localized strings. Covers dgettext, dngettext, context separator, enum label convention, and static analysis constraints.

Use when creating or modifying translated Zolinga web components. Covers importing web-component-intl.js, locale-aware template loading, and gettext in component HTML/JS.

Use when asked to localize a module, add translations, or work with the gettext pipeline. Covers the extract-translate-compile workflow, locale configuration, .po file locations, and troubleshooting.

Use when writing JavaScript code that needs localized strings. Covers the gettext.js import, domain binding via query string, and the gettext/ngettext API.

Use when working with the AI-powered translator service ($api->translator) for synchronous or asynchronous translation between system-supported languages.

Google's content quality guidelines: E-E-A-T, people-first content, helpful content self-assessment, authorship, and avoiding search-engine-first content. Use when writing, editing, or reviewing page content.

Google page experience guidelines: Core Web Vitals, mobile usability, HTTPS, intrusive interstitials, and safe browsing. Use when designing, developing, or reviewing page performance and UX.

Google SEO starter guide fundamentals: how search works, site organization, URLs, content basics, images, videos, promotion, and common myths. Use when building, designing, or reviewing any web page or site structure.

Google Search technical requirements, spam policies, structured data, canonical URLs, and violations to avoid. Use when reviewing technical SEO health or setting up new pages.

Use when submitting URLs to search engines via the seo:submit event, including IndexNow configuration and URL resolution.

How to author CMS pages in data/zolinga-cms/pages/: cms.* meta tags, template resolution, content injection, shuffling, custom elements, content variables, and page structure conventions. Use when creating or editing any .html page in the pages directory.

Use when creating or updating a Zolinga CMS content element listener for cms:content:{tagName}, including ContentElementEvent usage, XPath querying, output fragment handling, and manifest wiring.

Use when editing Zolinga CMS page or template HTML that references design assets, locale-aware links, or revisioned static files.