artifact-theme-applier

name	artifact-theme-applier
description	Use when the user wants to restyle an existing deck, document, report, HTML page, landing page, or demo while preserving content and structure, with format-native visual verification. Do not use for brand strategy, blank-slate creation, UI review, or landing-page messaging, CTA, or SEO changes.

Artifact Theme Applier

Apply one coherent visual theme to an existing artifact without changing the artifact's core content or structure. Treat the artifact as the source of truth and adjust styling, layout polish, and presentation details to make it feel intentional.

Use this skill when the user wants to restyle or unify an existing deliverable, especially when the request mentions:

• slides or pitch decks
• docs, reports, or one-pagers
• existing HTML pages or existing landing pages
• demos, artifacts, or shareable previews

Do Not Use For

• reviewing code or UX quality as a critic
• creating a full artifact from a blank slate
• brand systems, marketing strategy, or identity design
• deep redesigns that change the artifact's purpose or content
• screenshot capture planning or single-image polish for launch assets
• styling work that should be handled by a site-wide design system instead of a one-off theme
• landing-page work that needs new section strategy, copy hierarchy, CTA redesign, or SEO decisions

Workflow

1. Identify the artifact and the goal.

   • Determine the file type, audience, and where the artifact will be viewed.
   • Decide whether the user wants a theme applied, a theme adjusted, or a custom theme created from constraints.
   • Preserve the artifact's meaning, structure, and content unless the user explicitly asks for deeper changes.
   • If the artifact is a landing page and the request changes section order, messaging, CTA flow, or indexability, stop and use landing-page-builder instead.

2. Extract theme constraints.

   • Note any existing brand colors, fonts, spacing rules, tone, or visual references.
   • If no theme assets exist, infer a theme from the artifact's content, audience, and mood.
   • Keep the scope to a manageable theme system rather than inventing unrelated visual directions.

3. Choose or derive the theme.

   • Prefer an existing theme if one is already available and fits the artifact.
   • If no ready-made theme fits, define a custom theme with a small set of consistent tokens such as colors, typography, spacing, surfaces, and accent usage.
   • Make sure the theme supports readability and consistent contrast across the whole artifact.

4. Apply the theme consistently.

   • Update the artifact so headers, body text, backgrounds, accents, and highlights follow the same visual logic.
   • Keep component or slide structure intact unless a layout adjustment is needed to support readability.
   • Avoid mixing multiple visual styles unless the artifact intentionally has separate sections.

5. Check for fit and friction.

   • Look for low-contrast text, crowded spacing, mismatched fonts, and overused accent colors.
   • Verify through the artifact's format-native path, not only by inspecting source markup or object properties:
     • for slides, render or open the deck and inspect representative opening, middle, and closing slides; verify exported PDF when export is a deliverable
     • for documents and reports, render or open in the intended document viewer and inspect page breaks, tables, headings, headers, and footers; verify PDF export when required
     • for HTML and existing landing pages, run the page in a browser and inspect at least one normal desktop and one relevant mobile viewport
     • for demos, open the intended runtime and inspect each representative themed state
   • Check clipping, contrast, broken layout, missing assets, and unchanged content structure in the rendered result.
   • Report every native viewer, runtime, or export path that could not be verified; a source-only check is not sufficient evidence of visual correctness.
   • If the theme clashes with the artifact's content or format, simplify the design rather than layering on more effects.
   • Stop if the requested change would require a full redesign instead of theme application.

Output Expectations

Return a concise summary that includes:

• the theme used or derived
• the main styling decisions applied
• any assumptions made because theme files or brand assets were missing
• the files or artifact areas changed
• each format-native viewer, runtime, render, or export path verified, plus any path that remains unverified

If no files were changed yet, explain what theme would be applied and what input is still needed.

Guardrails

• Keep the work instruction-first and artifact-focused.
• Do not turn this into a general design critique.
• Do not overwrite the artifact's content unless the user asks for content edits.
• Do not expand the theme into unrelated product branding work.
• Do not absorb landing-page strategy, copy restructuring, CTA redesign, or SEO posture work.
• Do not add scripts or reference files unless a deterministic asset pipeline is actually needed.