From inspiration to implementation

Work in my existing project. First inspect its structure and the relevant page. Preserve its approved visual identity, working interactions and content. Ask for the page URL, screenshots or device information only when needed to reproduce the problem. Explain findings with evidence before changing code. Make focused changes, then report what changed, what you tested and what remains unverified.

Task: Diagnose loading speed. Separate document response, JavaScript, fonts, hero imagery, card images and video first-frame waits. Measure cold and repeat visits at the actual target viewport. Check real request sizes, caching headers, duplicate requests and resource priorities. Preserve the initial background and avoid layout shifts. Use appropriately sized images, defer offscreen media and pause videos when hidden. Do not reduce image quality or remove interactions without showing the tradeoff. Compare before and after under the same conditions; distinguish local observations from real mobile-network measurements.

Work in my existing project. First inspect its structure and the relevant page. Preserve its approved visual identity, working interactions and content. Ask for the page URL, screenshots or device information only when needed to reproduce the problem. Explain findings with evidence before changing code. Make focused changes, then report what changed, what you tested and what remains unverified.

Task: Reproduce the responsive defect. Start with the reported device, browser and screenshot. Check viewport metadata, browser text scaling, font loading, fixed widths, flex/grid minimum sizes, safe areas and long text. Verify 320, 390, 430, 768 and desktop widths, plus large text and landscape where relevant. Keep important actions readable and reachable, preserve complete media and avoid horizontal document scrolling. Do not hide content or shrink all text to make a screenshot fit. Explain which checks used a resized browser and which used an actual device.

Work in my existing project. First inspect its structure and the relevant page. Preserve its approved visual identity, working interactions and content. Ask for the page URL, screenshots or device information only when needed to reproduce the problem. Explain findings with evidence before changing code. Make focused changes, then report what changed, what you tested and what remains unverified.

Task: Audit keyboard and accessible interaction. Follow the main journey with Tab, Shift+Tab, Enter, Space and Escape. Check meaningful control names, visible focus, dialog focus containment and restoration, form labels, error messages and announced state changes. Ensure each action has one clear purpose and that touch users have an alternative to hover. Check reduced-motion behavior without removing essential feedback. Fix observed issues, document the steps to verify them and keep screen-reader testing distinct from inspecting ARIA attributes.

Work in my existing project. First inspect its structure and the relevant page. Preserve its approved visual identity, working interactions and content. Ask for the page URL, screenshots or device information only when needed to reproduce the problem. Explain findings with evidence before changing code. Make focused changes, then report what changed, what you tested and what remains unverified.

Task: Review release readiness. Compare the result with its reference at matching dimensions. Exercise real controls, empty/error states, direct URLs and browser Back. Check phone layout, missing media, console errors, public output and content delivery. Confirm the actual build command succeeds and report the relevant behavioral checks. Keep credentials and protected content out of public output. Identify external services that are not connected instead of presenting them as working. Prepare a focused release and recovery plan that preserves existing user data; publish only within the authorization already given.