跳转到内容
PHP Ecosystem
Explore

AI assistance

此内容尚不支持你的语言。

The canonical package skill is ui-awesome-html-core. It covers HTML base elements and application-scoped configuration. The checkout’s .agents/skills/ and .claude/skills/ links point to that single source; no client-specific copies are maintained.

Use the one-time Composer setup for llm/skills, explicitly trust ui-awesome/html-core, and configure auto-sync before expecting dependency updates to synchronize skills. Composer metadata alone does not install a synchronizer or activate a skill. Inspect the installed plugin version, permitted donor and synchronization result.

Terminal window
composer install
composer skills:show

With manual synchronization configured, run composer skills:update. These commands assume the application setup is already authorized and complete. Installing a package under vendor/ alone does not expose a skill at the application root.

For optional project-scoped installation, list the local source first:

Terminal window
npx skills@1.7.2 add /absolute/path/to/html-core --list
npx skills@1.7.2 add /absolute/path/to/html-core --skill ui-awesome-html-core --agent claude-code codex opencode

Use an installed vendor/ui-awesome/html-core source only if that release contains this skill. A copied skill must be refreshed on upgrades. Local changes do not prove availability from a published GitHub or Composer release.

Open a fresh session at the project root. Codex uses .agents/skills/ui-awesome-html-core/ and explicit $ui-awesome-html-core; Claude Code uses .claude/skills/ui-awesome-html-core/ and /ui-awesome-html-core. OpenCode can load the named skill through its native skill tool. Verify the installed client’s actual discovery paths and avoid duplicate/global same-name fallbacks. Installer --list checks source discovery, not native activation. Capture a real load event and execute the task before calling it tested.

Explicit Codex invocation (adapt the first line to the other client’s native mechanism):

$ui-awesome-html-core
Create a minimal ThemeInterface and application-scoped Config applying one immutable call. Test a matching context, an unknown context and Config::create() without a factory.
Use the installed source, show executable checks, and do not install dependencies or alter unrelated code.

Natural selection, without naming the skill:

How do I configure UI Awesome components with ordered recipes while keeping strict failures and avoiding global mutable theme state?
Include a runnable normal case, a boundary case and a deliberate invalid-input or unsupported-capability case.

Expected verification: inspect the referenced source contracts, execute the generated PHP with independent assertions, and record exact output or exceptions. Check state isolation and encoding where applicable. A correct answer without a native load trace is not evidence of native activation. In a separate unrelated task, ensure this skill is not forced into scope; do not change the real checkout to run a negative control.

Run this package’s configured checks and the consuming application’s relevant integration tests. Mark PHP versions, client activation, browser behavior and published artifacts separately when not exercised. Keep raw model evaluations, fixtures and provider traces in ignored maintainer storage, not the distributable skill. The examples above are prompts, not a claim that a particular provider has executed them.

Back to documentation