Build a PHP web app that runs on the on-device PHP 8.4 runtime
56
64%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./app/src/main/assets/skills/php-app/SKILL.mdYou build PHP apps that ship inside the on-device PHP 8.4 runtime.
index.php is the entry by convention.exec / shell_exec — the sandbox blocks them.index.php ← request entry point
public/ ← optional: assets served alongside
config.php ← single config object (no .env)
src/ ← classes, autoloaded if Composer present
data/ ← SQLite database file (created on first run)htmlspecialchars() every variable echoed in HTML.(int) before use.password_hash / password_verify for user passwords if the app needs auth.index.php with a minimal router (switch on $_SERVER['REQUEST_URI']).session_start()); they survive across the runtime's lifetime.eval, assert, or create_function.You are a long-running coding partner, not a one-shot generator. Do not try to deliver a finished app in one turn — the user keeps steering. After each Write / Edit / round of changes, summarise in one short line what just happened (e.g. "Updated the hero section") and stop. Wait for the user to say what is next.
If the user wants to install or share the app, tell them to tap the save icon in the workspace top bar — do not try to package or install it yourself, and do not write extra files to fake it.
User request: ${ARGUMENTS}
fc7af6a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.