Skill Claude Code
Use when: working with this module. Replace this description with specific trigger phrases describing what the skill helps accomplish and when to invoke it.
not rated 5 9d ago A 31 tokens
Skill Claude Code
Use when creating actionable, trackable plan documents in the /TODO folder — reviews, audits, new features, refactors, migrations, any multi-step work. Covers the TOC-with-progress-counters format, atomic checkbox steps each followed by one reasoning paragraph, a mandatory validation step per block, heading hierarchy…
not rated 5
changed 8d ago A 73 tokens
Skill Claude Code
Use when creating or editing module zolinga.json manifests, including listen/emit/autoload/config/webComponents/dependencies conventions and validation-oriented authoring.
not rated 5 9d ago A 35 tokens
Skill Claude Code
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.
not rated 5 9d ago A 51 tokens
Skill Claude Code
Use BEFORE building any new feature, page, or capability. The Zolinga core ships alone — official modules (CMS, DB, Intl, Commons, Cron, RMS, AI) provide most common features. Install them instead of hand-rolling a custom module. Always read README.md "Pre-Loaded Modules" first.
not rated 5 9d ago A 70 tokens
Skill Claude Code
Use when creating or modifying code in Zolinga modules, especially for following established coding standards and best practices.
not rated 5
changed 1mo ago C 29 tokens
Skill Claude Code
Use when implementing inter-process locking or concurrency control in Zolinga modules. Covers the registry-based MySQL lock API.
not rated 5 9d ago A 28 tokens
Skill Claude Code
Use when implementing CMS content tag handlers (cms:content:tagName), including listener contracts, DOM manipulation rules, and required wiki docs.
not rated 5 9d ago A 32 tokens
Skill Claude CodeCodex
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…
not rated 5
changed 1mo ago A 0 tokens
Skill Claude Code
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.
not rated 5 9d ago A 38 tokens
Skill Claude Code
Use when creating or updating MCP prompts — reusable prompt templates exposed to MCP clients via prompts/list and prompts/get. Covers .meta.json definitions, content.uri file references, {{arg}} substitution, and the mcp-system scheme.
not rated 5
changed 1mo ago A 64 tokens
Skill Claude Code
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.
not rated 5
changed 1mo ago A 62 tokens
Skill Claude Code
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().
not rated 5
changed 1mo ago A 82 tokens
Skill Claude Code
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.
not rated 5
changed 1mo ago A 40 tokens
Skill Claude Code
Use when creating, updating, or consolidating Agent Skills in this repository, including canonical placement, naming, and AGENTS.md alignment.
not rated 5 9d ago A 32 tokens
Skill Claude Code
Use when creating module-specific API endpoints in install/dist and wiring them to load the Zolinga system correctly.
not rated 5 9d ago A 28 tokens
Skill Claude Code
Use when creating or modifying database schema in Zolinga modules, including install SQL and update migration scripts with naming conventions.
not rated 5 9d ago A 31 tokens
Skill Claude Code
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.
not rated 5 9d ago B 35 tokens
Skill Claude Code
ALWAYS use when writing or updating ANY wiki documentation in this repository. Mandatory for all wiki changes. Guides a user-oriented writing style focused on tasks and outcomes. Enforces the no-duplication rule: reference existing content rather than repeating it.
not rated 5 9d ago A 0 tokens
Skill Claude Code
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.
not rated 5 9d ago A 53 tokens
Skill Claude Code
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.
not rated 5 9d ago A 47 tokens
Skill Claude Code
Use when writing localizable PHP code in Zolinga modules — dgettext/dngettext usage, domain naming, and context separators.
not rated 5 9d ago A 34 tokens
Skill Claude Code
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.
not rated 5 9d ago A 42 tokens
Skill Claude Code
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.
not rated 5 9d ago A 55 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: