/SKILL.md
# Known Issues & Solutions - Zariah Construction Project ## WOW.js Animation Classes Causing Invisible Images ### Problem Description When converting HTML templates to React + Vite, images with `wow` animation classes (specifically `img-custom-anim-left`, `img-custom-anim-right`, `img-custom-anim-top`) were not visible on the page. The images appeared in the DOM but had `opacity: 0`, making them invisible to users. ### Root Cause The custom CSS animation classes set `opacity: 0` initially: ``
npx skillsauth add saseklab/zariah-construction zariah-constructionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When converting HTML templates to React + Vite, images with wow animation classes (specifically img-custom-anim-left, img-custom-anim-right, img-custom-anim-top) were not visible on the page. The images appeared in the DOM but had opacity: 0, making them invisible to users.
The custom CSS animation classes set opacity: 0 initially:
.img-custom-anim-left {
animation: img-anim-left 1.3s forwards cubic-bezier(0.645, 0.045, 0.355, 1) 0.4s;
opacity: 0; /* <-- This causes the issue */
}
The animations rely on WOW.js to trigger and set the opacity back to 1. However, when elements are already in the viewport on page load (common in SPA routing), WOW.js doesn't trigger the animation, leaving elements with opacity: 0.
src/components/sections/Faq.jsx - FAQ imagesrc/components/sections/About.jsx - About section images (2 images)src/components/sections/Purposes.jsx - Purposes imagesrc/components/sections/Cta.jsx - CTA imageRemove the problematic animation classes from image elements:
Before:
<div className="faq-image wow img-custom-anim-left">
<img src={faqImage} alt="FAQ" />
</div>
After:
<div className="faq-image">
<img src={faqImage} alt="FAQ" />
</div>
If you want to keep the animations:
Use different animation classes that don't set opacity: 0:
wow fadeInUp (from animate.css) - only animates transformManually trigger WOW.js after component mount:
useEffect(() => {
if (window.WOW) {
new window.WOW().init()
}
}, [])
Use CSS-in-JS or styled-components to conditionally apply animations
The FAQ image also needed a z-index fix to appear above the orange overlay:
/* In src/styles/main.css around line 3320 */
.faq-wrapper-new .faq-image {
max-width: 570px;
position: relative; /* Added */
z-index: 9; /* Added - places image above ::before overlay */
}
After fixing animation issues, verify:
Run this in browser console to check image opacity:
document.querySelectorAll('img').forEach(img => {
const opacity = window.getComputedStyle(img).opacity;
if (opacity === '0') {
console.log('Hidden image:', img.src, img.parentElement);
}
});
Problem: Images not loading - Failed to resolve import errors
Solution: Use correct relative paths from src/components/sections/:
// CORRECT (2 levels up to src, then into assets)
import heroBg from '../../assets/img/home-1/hero/hero-bg.jpg'
// WRONG (only 1 level up)
import heroBg from '../assets/img/home-1/hero/hero-bg.jpg'
Problem: SourceMap warnings for CSS files
Solution: Remove sourceMappingURL comments from CSS files:
/* Remove this line: */
/*# sourceMappingURL=bootstrap.min.css.map */
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.