Skill Claude CodeCodex
Use when creating, reviewing, or debugging SPIP CVT forms — canonical HTML wrappers, field/global errors, charger/verifier/traiter/identifier, or when deciding whether Saisies or Verifier are appropriate.
Skill Claude CodeCodex
Use when creating, reviewing, or debugging SPIP CVT forms — canonical HTML wrappers, field/global errors, charger/verifier/traiter/identifier, or when deciding whether Saisies or Verifier are appropriate.
Skill Claude CodeCodex
Use for SPIP translation/i18n work — creating, editing, or auditing language files (lang/prefixXX.php, lang/paquet-prefixXX.php), naming keys, adding translations, using T() / , or debugging missing/untranslated strings.
Skill Claude CodeCodex
Use when writing, reading, or debugging SPIP logs — spiplog(), journal(), log constants, log file location, gravité levels, or log rotation. For SPIP 4.1+.
Skill Claude CodeCodex
Use when developing a SPIP plugin (paquet.xml present, pipelines.php, spip table references in PHP) or when the user asks about plugin architecture, pipelines, hooks, or the SPIP PHP/SQL API. SPIP 4.1+. Not for template/squelettes work — use the spip-squelettes skill for that.
Skill Claude CodeCodex
Use when working with the SPIP Saisies plugin — declaring fields in formulaires saisies(), writing a custom field type in saisies/ or saisies-vues/, using #SAISIE / #GENERERSAISIES / #VOIRSAISIES, hooking a saisies pipeline, or manipulating a field array with the inc/saisies PHP API.
Skill Claude CodeCodex
Use for any SPIP template question — BOUCLE loops, balises, critères, filtres, INCLURE, pagination, image filters, recursive trees, AJAX reloads. Covers public squelettes and plugin squelettes (espace privé, modèles). Trigger even when the user doesn't say "squelette". Not for PHP hooks/pipelines → use spip-plugins.
Skill Claude CodeCodex
Guides automated testing of SPIP plugins and squelettes using PHPUnit — the standard test tool for SPIP. Covers the full self-contained setup (composer, spip-cli), unit tests with lightweight mocks, and integration tests against a real SPIP instance. Use whenever the user wants to test, verify, or validate a SPIP…