Analyze, lint, and safely fix Ultiorganizer CSS changes. Use when Codex edits or reviews CSS files under cust/, mobile app styling, skin overrides, or shared stylesheet rules; when checking style/color consistency; or when deciding whether duplicated selectors and utility classes should be consolidated. Run Stylelint on changed CSS and apply only low-risk fixes unless the user asks for broader visual refactoring.
Verify Ultiorganizer UI and CSS changes by taking screenshots and measuring element layout using Chromium inside the dev Docker container. Use whenever a visual or layout change needs confirmation — responsive CSS, header alignment, table widths, mobile vs desktop rendering. Don't skip this just because the code looks right; run it to get actual pixel evidence.
Fix Ultiorganizer user-facing language for project spelling, grammar, gettext-backed wording, and terminology correctness. Use for either a single page sweep or a single-term sweep across user-facing surfaces. Default to one page or module when the caller is not explicit. Do not rename internal identifiers unless the user asks for that broader scope.
Read-only review skill for Ultiorganizer user-facing language. Use after adding or changing a page, page module, or other code with user-facing text. Review changed content for project spelling, grammar, gettext-backed wording, database-backed U_() translation usage, terminology correctness, and on-page terminology consistency. Prioritize user-modified files first, then check the surrounding page or module for consistency warnings. Do not apply fixes.
Analyze PHP function declarations and usage in Ultiorganizer lib files. Use when asked to inventory functions in lib/*.php, count direct or callback-style usages across the repository, identify dead-code candidates, compare usage for a specific lib file, or prepare safe cleanup work around unused PHP helpers.
Run PHP formatter and static analyser on Ultiorganizer changes, then fix or report findings. Use after editing PHP files to apply PER-CS 2.0 formatting via PHP-CS-Fixer and to surface PHPStan findings against the project baseline. Apply auto-fixable formatting; for static-analysis findings, fix when the cause is obvious in the changed code, otherwise report and leave the baseline untouched.
Read-only review skill for Ultiorganizer database access boundaries. Use after adding or changing PHP functionality that calls the database or changes DB access structure. Review changed PHP for page-layer DB usage, misplaced SQL outside `lib/`, low-level DB wrapper calls in routed files, or legacy cursor-style helper APIs in `lib/`. Run the bundled checker first, then report findings without editing files.
Read-only review skill for Ultiorganizer playoff bracket layouts. Use after adding or changing a `cust/<id>/layouts/<N>_teams_<R>_rounds.html` template, after editing the `PlayoffTemplate()` placeholder contract in `lib/pool.functions.php`, or after editing the move-comment parser in `GeneratePlayoffPools()`. Run the bundled checker first, then report findings without editing files.