38 tagged php framework, measured the same way as everything else here.
Browse within: php 38content-management-system 35databaseless 35php-widgets 35web-components 35
Skill Claude CodeCodex
Cut a new Marko release. Reads every PR merged since the last tag, audits their release-notes labels, recommends the next version number with reasoning, and — only after you confirm or override it — runs ./bin/release.sh. Use this skill whenever the user types /release or asks to cut, ship, publish, or tag a release.…
Skill Claude CodeCodex
Scaffold a new Marko module — a self-contained Composer package with composer.json, namespaced src/, and Pest tests. Use this skill whenever the user asks to create, add, or scaffold a new Marko module or package. Concrete triggers: 'create a module named payment', 'scaffold an acme/blog package', 'add a new module…
Skill Claude CodeCodex
Create a Marko plugin — a class that intercepts methods on another class to modify behavior without subclassing. Use this skill whenever the user wants to add a plugin, intercept a method, or extend a class's behavior. Concrete triggers: "add a plugin for the OrderService", "intercept the save method on User", "extend…
Skill Claude CodeCodex
Use when creating or updating MCP resources — static files exposed to MCP clients via resources/list and resources/read. Covers .meta.json descriptors, tenant filtering, URI rewriting, dynamic resources via mcp:resources/list event hook, and the mcp-system scheme.
Skill Claude CodeCodex
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().
Skill Claude CodeCodex
ALWAYS use when creating, modifying, or reviewing ANY front-end web components, widgets, or custom elements in this repository. Mandatory for all web component work — creating new components, modifying existing ones, registering in zolinga.json, writing component docs, or debugging component…