Rapid landing-page iteration loop
Source workflow
Start with the message and copy
Ask what the page should convey to users and settle the copy before building. Dhravya ran the work in one Claude Opus 4.6 1M session and reported completing the page in four hours; preserve those as his case-study setup and result, not universal requirements or promises.
Prepare targeted design skills
Identify the design capabilities the plan needs. In the source, Dhravya wanted strong SVG animation, transcribed the best lessons from SVG-animation courses, and had a subagent prepare a small targeted skill. He prepared the other basic skills he wanted a designer to know in the same way.
Build special-effects tooling separately
For animated ASCII art and pixelization, send two subagents to research performant web implementations. Build the effects as a separate package so those details do not confuse the main design work. The source's package included the implementation and recorded GIF demonstrations.
Supply real business context
Give the main Claude Code session the business requirements, team priorities, user requests, prior coding-session context, customer recordings, and team meetings available through the Supermemory Claude Code plugin. Use that combined context to form the design language and strategy.
Complete and inspect the whole page
Build the complete page in the main session and have Claude look at and think about the result throughout the work. Analyze the entire page for performance and SEO after implementation.
Prefer iteration velocity over waiting for a supposedly perfect page. The source reports a 40% conversion increase for this page and four hours of work; treat both as observations from Dhravya's page, not guaranteed outcomes.
Continue through the team
Connect the workflow to an authorized background agent so another teammate can continue landing-page work through additional iteration cycles. The source describes a non-technical teammate using that setup autonomously.
XSkills operational adaptations
Preflight repository access, Claude Code or an equivalent coding harness, subagent support, the required design skills, business-context retrieval, rendering, and performance/SEO analysis. If an exact source capability is unavailable, state the substitution and return the missing implementation or verification step instead of claiming the full source loop ran.
XSkills safety adaptations
Use course material, packages, recordings, meetings, customer data, and brand assets only with the required access and rights. Minimize private context sent to any model. Require explicit authorization before publishing or deploying the rebuilt page. Do not invent customer evidence or present the reported timing or conversion lift as a forecast.
Return
Return the copy decision, prepared skills, separate effects tooling, context actually used, completed page, performance and SEO analysis, observed limitations, and any unexecuted background-agent handoff.
Source attribution
Independently compiled by XSkills from Dhravya Shah's X Article about rebuilding a landing page in four hours with Claude. Shah did not author or review this skill. Capability fallback, rights and privacy limits, truthful-result framing, and publish/deploy authorization are XSkills adaptations. Attribution does not imply endorsement.