Skip to content
Back to skills

Dhpk Php 8x Features

ASecurity

Use when the project''s PHP floor permits 8.x syntax, when reviewing whether a 7.4-and-up library can adopt an 8.x idiom conditionally, or when designing an API with attributes, enums, readonly, or newer types. Not for everyday business logic, 7.4 baseline guidance, or legacy 5.6 code. Output: a feature recommendation or migration decision with its minimum PHP version and library-floor rule.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
ai-agentsphpapi

Works with

  • api

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 2, 2026

npx -y skills add hmj1026/dhpk --skill dhpk-php-8x-features --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dhpk Php 8x Features?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dhpk Php 8x Features
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hmj1026-dhpk-php-8x-features/badge)](https://www.skillsdirectory.com/skills/hmj1026-dhpk-php-8x-features)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dhpk-php-8x-features
description: 'Use when the project''s PHP floor permits 8.x syntax, when reviewing whether a 7.4-and-up library can adopt an 8.x idiom conditionally, or when designing an API with attributes, enums, readonly, or newer types. Not for everyday business logic, 7.4 baseline guidance, or legacy 5.6 code. Output: a feature recommendation or migration decision with its minimum PHP version and library-floor rule.'
metadata:
  dhpk-invocation-class: implicit-eligible
---

# PHP 8.x features — routing entrypoint

Use this skill to decide whether a PHP 8.0–8.3 language feature is legal for
the actual runtime and package floor. Start with the feature catalog before
editing code; PHP 8.x syntax has no runtime polyfill.

## Working sequence

1. Read `composer.json`, CI matrices, and deployment metadata to identify the
   lowest supported PHP version.
2. Open the relevant version section in
   `references/feature-catalog.md`.
3. Apply the catalog's library rule: attributes may be inert on 7.4, while
   the other listed 8.x syntax requires a compatible parser.
4. If the floor changes, run the composer-package-hygiene checks and record
   the semver consequence.
5. Verify with the project's parser, static-analysis, and focused-test gates.

## Decision branches

- Choosing a language idiom: use the feature's minimum-version entry and
  compare it with the declared floor.
- Supporting `^7.4 || ^8.0`: use the mixed-floor decision table; do not hide
  parse errors behind runtime checks.
- Designing public API: inspect named-argument stability, attributes read by
  frameworks, and serialization or reflection consequences.
- Raising `composer.json`'s PHP floor: hand off to
  `skills/dhpk-composer-package-hygiene/SKILL.md` for semver and release review.

## When NOT to Use

- Everyday business logic where no PHP-version decision is involved.
- PHP 7.4 baseline or dual-floor patterns; use `dhpk-php-modern-pro`.
- Legacy PHP 5.6 compatibility work; use `dhpk-php-runtime-router`.

## Output

Return one of:

- a feature recommendation with its minimum PHP version and compatibility
  caveat; or
- a migration decision listing the required floor bump, affected matrix
  cells, and verification evidence.

Do not report a feature as compatible until the lowest declared floor and the
framework/tooling that consumes it have been checked.

## Verification

- [ ] The selected feature's minimum PHP version is at or below the declared
      project floor.
- [ ] A `^7.4 || ^8.0` library uses only attributes without a deliberate
      gated branch; all other 8.x syntax is excluded or the floor is raised.
- [ ] Composer constraints and CI matrix cells agree with the decision.
- [ ] Parser, static-analysis, and focused tests pass for the affected cells.
- [ ] A floor bump is treated as a semver-major release decision.

## References

- `references/feature-catalog.md` — feature examples, caveats, and mixed-floor
  decision tables.
- `skills/dhpk-php-modern-pro/SKILL.md` — 7.4 baseline and
  dual-version-floor patterns.
- `modules/php-7.4/references/static-checks.md` — lint and analysis pipeline.
- `skills/dhpk-composer-package-hygiene/SKILL.md` — package-floor and release flow.

Files in this skill

  • SKILL.md3.2 KB
  • agents/openai.yaml239 B
  • references/feature-catalog.md5.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.