Responsive recomposition
Every dense desktop composition receives an explicit tablet and mobile fallback.
Need more than a one-off page? Landy gives you reusable sections, visual systems, responsive rules, QA policies, and TypeScript output — so you can launch faster without rebuilding the same design logic every time.
landy.dev/SKILL.mdStart from a short brief and choose a direction.
Use a ready-made conversion component without leaving a dead placeholder.
Clerk makes product UI itself the proof. This Landy adaptation does the same: the page shows real section primitives, project settings, workspace controls, and reusable conversion blocks instead of abstract marketing icons.
Explore all components →Manage the information Landy uses to compose and refine the page.
The current Clerk homepage expands authentication into concrete security and session-management capabilities. The equivalent Landy chapter expands “generate a page” into the production requirements that make the result usable.
Every dense desktop composition receives an explicit tablet and mobile fallback.
Detect clipped text, broken diagrams, accidental dead zones, and over-dense components.
Generate semantic UI, diagrams, typography, and CSS geometry instead of empty placeholders.
Do not fabricate logos, testimonials, performance metrics, security claims, or customer counts.
Keep typography, spacing, motion, diagram behavior, and proof rules consistent across generations.
Export a renderer and manifest instead of trapping the page inside a closed editor.
Clerk uses Organizations to demonstrate B2B multi-tenancy. This adaptation turns the same design grammar into Landy workspaces: brands, campaigns, shared templates, roles, and design policies.
Move between brands or campaigns without losing each workspace’s design system.
Separate brand governance from everyday page editing.
Clerk uses Billing as a major product pillar and visualizes the pricing component directly. For Landy, this section demonstrates how pricing, plans, and gated capabilities can be represented as reusable page primitives without copying Clerk’s billing functionality.
Generate a pricing narrative that is consistent with the rest of the page, then connect it to the user’s real billing system.
Illustrative plan data. Replace with verified pricing before production.
Clerk’s framework and integration sections signal that its components belong inside a developer’s existing stack. Landy’s template system should do the same: keep the page renderer portable and let the product decide the final integration.
Map generated sections to the project’s tokens and primitives instead of shipping a disconnected style island.
Expose meaningful CTA and section events without silently installing tracking libraries.
Populate real product copy, proof, screenshots, and metadata when the user provides them.
The Clerk homepage uses substantial verified social proof. This template ships with clearly labeled placeholders so Landy does not accidentally fabricate customer endorsement.
“Replace this with a verified quote that explains why the product was easier, faster, or safer to adopt.”
“If no testimonial exists, show the product behavior itself instead of inventing social proof.”
“Strong proof lives close to a high-friction decision, not in an arbitrary carousel.”
Start from the brief, let Landy select the visual system and page structure, then keep the final TypeScript output as part of your own stack.