Run the agent release gate — a portable, wire-level QA harness for the agent runtime. Drives the same product endpoint the playground drives and asserts on the SSE frame stream and real side effects, never on model prose, so it works against any deployment (cloud or self-hosted) from three env vars. Use before an agent-workflows release, or after changing the runner, the SDK agent adapters, the runner Docker images, or the agent service. Triggers: "run the release gate", "QA the agent runtime", "does the agent still work end to end", "pre-release agent QA".
Pick and record the names of a new concept in every layer (database table and column, ORM model, DTO, route, JSON field, UI label), and give every stored item kind the same resource shape and the same actions. Holds the glossary format with an Avoid list, the per-layer name table, the resource template, standard and custom actions, field, enum, state and owner rules, the Agenta convention table, the folder naming rule, and the spec naming checklist. Use when writing or changing a spec, design or plan that adds or renames a table, column, index, route, DTO field, enum value, config field or UI label, when asked "what should this be called", "is this name consistent", "fill the naming section", or when another skill asks for the per-layer names. It applies even when the word "naming" never appears. Do not use it for field grouping by role (use design-interfaces), for migration errors, or for a rated review (use review-naming).