All authors
Claude Skills by dotkernel
github.com/dotkernel18 skills0 installs0 views
- Dotkernel Api EndpointUse when adding or changing 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 — and as the end-to-end checklist before calling an API endpoint done. Not for Admin, Frontend, Light or Queue projects.Votes: 0GitHub stars: 9
- Dotkernel Core SubmoduleUse 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 — or when deciding 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.Votes: 0GitHub stars: 9
- Dotkernel Doctrine EntitiesUse when adding or changing 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.Votes: 0GitHub stars: 9
- Dotkernel Dot MakerUse 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.Votes: 0GitHub stars: 9
- Dotkernel Evolution PatternUse whenever a change would break something 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 — or when someone proposes a /v2, a version prefix, a version header, or "versioning the API". Also use when working with ResourceDeprecation, Sunset and Link headers, or the deprecation middleware.Votes: 0GitHub stars: 9
- Dotkernel Feature DocsUse when writing down what a feature does and why in a Dotkernel project — after building or changing a route, module, command or entity, 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 alre...Votes: 0GitHub stars: 9
- Dotkernel Handler NamingUse when naming or reviewing a PSR-15 request handler class, a route URL, a route name, or an authorization key in any Dotkernel project — creating a new endpoint or page, renaming one, adding a route to a RoutesDelegator, wiring a handler into a ConfigProvider, or checking 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.Votes: 0GitHub stars: 9
- Dotkernel Input ValidationUse when handling 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.Votes: 0GitHub stars: 9
- Dotkernel Module StructureUse when creating, moving, renaming or locating any file in a Dotkernel project — 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".Votes: 0GitHub stars: 9
- Dotkernel OpenapiUse when documenting an endpoint in a Dotkernel project that publishes OpenAPI (typically the API) — 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.Votes: 0GitHub stars: 9
- Dotkernel Package StatusChoose, justify and verify PHP/Composer dependencies in Dotkernel projects, and answer whether a Dotkernel package is still maintained. Use this skill ANY time you are about to suggest, add, evaluate or replace a package, edit composer.json, run `composer require`/`composer remove`, or answer "what should I use for X" — including when the user only asks how to implement something a library could solve (mail, queues, caching, logging, validation, pagination, auth, CLI, fixtures, uploads, GeoIP...Votes: 0GitHub stars: 9
- Dotkernel Project VariantsUse at the start of any non-trivial task in a Dotkernel repository, and whenever a convention might differ between projects — to work out whether this is Dotkernel API, Admin, Frontend, Light, Queue or a derived project, and what that implies 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.Votes: 0GitHub stars: 9
- Dotkernel Psr StandardsUse when writing or reviewing any PHP in a Dotkernel project — 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 tempted to type-hint a concrete framework class instead of an interface.Votes: 0GitHub stars: 9
- Dotkernel Qa GateUse when finishing a change in a Dotkernel project and before claiming it is done, when phpcs, phpcbf, phpstan or phpunit fails, when interpreting 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.Votes: 0GitHub stars: 9
- Dotkernel ResponsesUse when shaping 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.Votes: 0GitHub stars: 9
- Dotkernel SecurityUse when touching 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 reviewing a diff for security problems or when asked whether something i...Votes: 0GitHub stars: 9
- Dotkernel TestingUse when writing, running or fixing 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 deciding what coverage a new route needs.Votes: 0GitHub stars: 9
- Dotkernel TroubleshootingUse when something in a Dotkernel project is not working and the cause is unclear — 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.Votes: 0GitHub stars: 9