Use when you add or change an endpoint in a Dotkernel API project (or a project derived from it): a new route, handler, request or response contract, resource loading by id, a caller-scoped /account route, an action segment like /activate, an upload, a guest grant, or an operationId. Also use it as the end-to-end checklist before you call an API endpoint done. Not for Admin, Frontend, Light or Queue projects.
日本語の概要は準備中です。原文の説明を表示しています。
dotkernel/dotboost☆ 92026年11月17日 更新
Use when you add or change anything persisted in a Dotkernel project: a Doctrine entity, column, relation, index, repository, backed enum with its DBAL type, fixture, or migration. Also use for questions about UUID versus numeric identifiers, timestamps, the table prefix, why doctrine-migrations diff produces an unexpected diff, or why a schema-validation CI job is failing.
日本語の概要は準備中です。原文の説明を表示しています。
dotkernel/dotboost☆ 92026年11月17日 更新
Use before hand-writing any new scaffolding in a Dotkernel project: a module, entity, repository, service, service interface, handler, collection, form, input, input filter, middleware or CLI command. dot-maker (dotkernel/dot-maker, "composer make …") generates these to the Dotkernel file structure and naming pattern. Also use when asked how to create a new module, what "composer make" can do, or why generated boilerplate looks a certain way.
日本語の概要は準備中です。原文の説明を表示しています。
dotkernel/dotboost☆ 92026年11月17日 更新
Use whenever a change would break something that a client already depends on in a Dotkernel project: renaming or removing a field, parameter, route or template variable, changing a type, status code or response shape, making an optional field required, deprecating or deleting an endpoint. Also use when someone proposes a /v2, a version prefix, a version header, or "versioning the API". Also use when you work with ResourceDeprecation, Sunset and Link headers, or the deprecation middleware.
日本語の概要は準備中です。原文の説明を表示しています。
dotkernel/dotboost☆ 92026年11月17日 更新
Use when you write down what a feature does and why in a Dotkernel project. This includes after building or changing a route, module, command or entity, and when asked to document a feature, write release notes, record a decision, explain an endpoint to another developer, or bring an existing feature doc back in line with the code. Also use when a feature exists but nothing outside the code explains it, when a doc still describes behaviour that has since changed, and before adding behaviour to an area that already has a feature doc.
日本語の概要は準備中です。原文の説明を表示しています。
dotkernel/dotboost☆ 92026年11月17日 更新
Use when you name or review a PSR-15 request handler class, a route URL, a route name, or an authorization key in any Dotkernel project. This includes when you create a new endpoint or page, rename one, add a route to a RoutesDelegator, wire a handler into a ConfigProvider, or check that a handler follows the Dotkernel naming pattern. Also use when a route returns 403 or 404 unexpectedly, when choosing between PATCH and POST, or when deciding whether a handler needs a Form suffix.
日本語の概要は準備中です。原文の説明を表示しています。
dotkernel/dotboost☆ 92026年11月17日 更新