本文へ移動
cccskills

Dotkernel

@dotkernel

組織

19 スキル1 リポジトリ 9

スキル(19)

検索で絞り込む

Use when writing any prose in a Dotkernel project or package — a chat answer, a commit message, a tag message, an MR or PR description, a Markdown file (README, feature doc, release notes, CHANGELOG), a code comment, a docblock description, an exception or error message, CLI command output, or an OpenAPI summary or description. Applies ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one instruction per sentence, one meaning per word. Also use when reviewing text for clarity, or when asked to rewrite, simplify or disambiguate text, or to write it in STE, "simple English" or "plain English".

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年11月16日 更新

Use at the start of any non-trivial task in a Dotkernel repository, and whenever a convention might differ between projects. It finds whether this is Dotkernel API, Admin, Frontend, Light, Queue or a derived project, and what that means for handler naming, authorization config, responses, forms, templates, documentation and tests. Also use when a skill's guidance does not match what the repo actually contains, or when the same feature has to be built in more than one Dotkernel project.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年11月17日 更新

Use when you touch anything security-relevant in a Dotkernel project: authentication, OAuth2 or session login, authorization config and role permissions or guards, CORS, content negotiation, session and cookie settings, error handling and error-reporting endpoints, documentation exposure, secrets and *.local.php versus *.global.php, demo credentials, ownership checks, raw DQL or SQL, or adding a dependency. Also use when you review a diff for security problems, or when the user asks whether something is safe to commit.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年11月17日 更新

Use when you write, run or fix tests in a Dotkernel project: unit tests, functional route tests, mocking repositories and services, authenticating a test request, seeding data, or diagnosing failures inside setUp such as "test mode is NOT enabled" or "non in-memory database". Also use when you decide what coverage a new route needs.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年11月17日 更新

Use when something in a Dotkernel project does not work and the cause is not clear: a route returns 403, 404, 406, 415 or 500 unexpectedly, a service is not found in the container, a handler throws while building a response, config changes have no effect, routes are missing, tests fail in setUp, autoloading fails, a form silently rejects a submit, or CORS preflight fails. Start here before reading code at random.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年11月17日 更新

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/dotboost92026年11月17日 更新

Use whenever a change touches the Core layer of a Dotkernel project: adding or editing a Doctrine entity, repository, enum, DBAL type, fixture, migration or shared service. Also use when you decide whether code belongs in Core versus an application module. Also use for git submodule mechanics (.gitmodules, git submodule add/init/update, committing from inside src/Core) and for questions about sharing code between Dotkernel projects on one database.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年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/dotboost92026年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/dotboost92026年11月17日 更新

Use when you document an endpoint in a Dotkernel project that publishes OpenAPI (usually the API). This includes: adding or editing a module's OpenAPI.php, describing request bodies, responses, parameters, security schemes or schemas, marking an operation deprecated, or regenerating the interactive documentation. Also use when an endpoint exists but is missing from the docs, or when checking whether this project publishes OpenAPI at all.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年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/dotboost92026年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/dotboost92026年11月17日 更新

Use when you handle incoming data in a Dotkernel project: writing or changing an InputFilter, an Input class, or a laminas-form Form, wiring validators, filters and error messages, handling CSRF on a templated project, validating uploads, or deciding where a value should be checked. Also use when a write endpoint accepts data it should reject, when validation messages are inconsistent, or when a form redisplays without its errors.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年11月17日 更新

Use when you create, move, rename or locate any file in a Dotkernel project. This includes: deciding whether code belongs in an application module or the shared Core layer, adding a Handler, Service, Collection, Form, InputFilter, Input, Entity, Repository, Enum, DBAL type, Command, Middleware, ConfigProvider or RoutesDelegator, registering a module in config/config.php and composer.json autoload, or answering "where does this go" and "why is this class not found".

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年11月17日 更新

Select, justify and verify PHP/Composer dependencies in Dotkernel projects, and tell whether a Dotkernel package is still maintained. Use this skill ANY time before you suggest, add, evaluate or replace a package, edit composer.json, run `composer require`/`composer remove`, or answer "what should I use for X". Also use it when the user only asks how to implement something that a library can solve (mail, queues, caching, logging, validation, pagination, auth, CLI, fixtures, uploads, GeoIP, error handling, HTTP client). Also use when asked whether a Dotkernel package is still maintained, what a package does, which PHP versions it supports, whether it is safe for a new project, or what the state of the Dotkernel open-source portfolio is. Enforces this order: already installed, then dotkernel/*, then laminas & mezzio, then a vetted community package, then hand-rolled code. Answers from the published dotkernel.com listing, not from memory. Also use each time that you find yourself naming a package from memory.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年11月17日 更新

Use when you write or review any PHP in a Dotkernel project. It tells which PSR applies, how to type handlers and middleware (PSR-7/PSR-15), how to obtain services (PSR-11, no service locator), logging (PSR-3), caching (PSR-6/PSR-16), building responses (PSR-17), autoloading (PSR-4), and coding style (PSR-1/PSR-12 via the Laminas Coding Standard). Also use when phpcs or phpstan complains, or when you are tempted to type-hint a concrete framework class instead of an interface.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年11月17日 更新

Use when you finish a change in a Dotkernel project and before you say that it is done, when phpcs, phpcbf, phpstan or phpunit fails, when you interpret CI results, or when asked to "run the checks" or "fix the build". Also use when tempted to add a phpcs exclusion, a @phpstan-ignore, or to skip a test.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年11月17日 更新

Use when you shape what a Dotkernel handler returns: HAL resources and collections and the MetadataMap for API-style projects, or templates, redirects and flash messages for templated projects, plus pagination, content negotiation, and the error body. Also use when a response is missing links, a list is not paginated, a resource exposes the wrong fields, or an error leaks internal detail.

日本語の概要は準備中です。原文の説明を表示しています。

dotkernel/dotboost92026年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/dotboost92026年11月17日 更新

あなたのアカウントですか? GitHub 連携でクリエイターページにまとめられます