/* =========================================================
   more design — corporate site v2
   Base: Figma "SP" design (RDFYXIxTqaUjOL78sJk0DT, node 2:2)
   Mobile-first; desktop layout (>=900px) reflows the same
   content, since only a mobile mockup exists in the source.
   ========================================================= */

:root {
  --color-cyan: #2bc5c6;
  --color-yellow: #fbe9a5;

  /* One cyan for every accent: the comps' button colour. It replaces a second
     cyan at #00b2d0 that ran 4.1 ΔE away from it — close enough that the two
     read as the same colour, far enough to look like a mistake side by side.
     White on it is 2.6:1, short of AA. */
  --color-cyan-accent: #31adcb;
  /* 提供サービスのカードは1枚ずつアクセント色を持つ。いずれもカンプ実測。
     名刺は既存の --color-cyan-accent を流用しているのでここには無い。 */
  --color-service-blue: #485ffb;
  --color-service-orange: #f1ac44;
  --color-service-purple: #918bbd;
  --color-service-pink: #efc8d3;
  /* LINE のブランドグリーン。公式ロゴの #7EC36A をそのまま使う。 */
  --color-line-green: #7ec36a;

  /* Four greys, and nothing between them. Each step absorbed a near-identical
     value that had been written out somewhere else: 100 took #eef1f3 (3.0 ΔE),
     600 took #666 (4.4), 800 took #3a3a3a, #444 and the old text navy. */
  --color-gray-100: #e9e9e9;
  --color-gray-200: #d7d7d7;
  --color-gray-600: #727071;
  --color-gray-800: #333333;

  /* The one text colour: body default, headings and copy, on white and on
     every tinted ground. It was the brand navy #000e66, and the site also
     carried a separate near-black #1a1a1a for the body default; both now read
     as this single neutral dark, which is --color-gray-800 rather than a
     second almost-identical value beside it. Named for the job it does, since
     it is no longer a navy. */
  --color-text: var(--color-gray-800);

  /* 制作事例's category chip. Neutral grey rather than a brand tint, read
     off the comp: the cards below it already carry colour from the work
     itself, so the label stays quiet. 7.9:1, which clears AA. */
  --color-tag-bg: var(--color-gray-200);
  --color-tag-text: var(--color-gray-800);

  /* Footer sits on a light grey ground with deep-navy links, per the
     SP footer design. */
  --color-footer-bg: var(--color-gray-100);
  --color-footer-ink: #2b1e5c;

  /* 当店の強み sits on its own teal ground, domed at the top. Sampled from
     the section-head comp, where it is the flat fill behind the dome. */
  --color-point-bg: #69b1b4;

  /* The megaphone's own yellow, reused for the 4 in 当店の4つの強み so the
     numeral reads as part of the illustration. 1.6:1 on the teal — it only
     works as the oversized display numeral, never as body copy. */
  --color-strength-accent: #f3cf47;

  /* The light blue of the 現状を整理・分析して section, taken from the circle
     in its own decorative artwork. 2.0:1 on white — display use only. */
  --color-sky: #7ec1dd;
  --color-grid: #e2edf7;
  /* The warm cream ground, shared by the step cards and お客様の声. They were
     sampled separately, at #fdeed7 and #fdf0de — 2.8 ΔE apart, which is below
     what the eye picks up, so one value covers both. The step word is set a
     shade deeper on it, reading as a watermark rather than as copy. */
  --color-cream: #fdf0de;
  --color-step-mark: #faeac0;

  /* お悩み cases: the CASE tab, the headline and the balloon outline all use
     this amber, taken from the circle in the supplied avatar artwork so the
     two match exactly. Note it only reaches 2.0:1 on white. */
  --color-case: #f1ab44;

  /* お客様の声 sits on the shared cream ground (--color-cream), with the video
     thumbnails in a near-black warm brown and its own magenta button. Both
     read off the comp; white on the magenta is 5.3:1, which clears AA. */
  --color-voice-media: #2b2220;
  --color-voice-cta: #c8286e;

  /* 料金ページのプラン。Each plan is drawn in its own accent; these two are the
     ones with nothing close enough already on the site to reuse — the blue is
     21.9 ΔE from --color-cyan-accent, the badge yellow 17.8 from
     --color-strength-accent. (お試しプラン's teal is within 3.7 of
     --color-point-bg, so it borrows that instead of adding a third.) */
  --color-plan-blue: #00adf1;
  --color-plan-royal: #226cff;
  --color-plan-badge: #ffd300;

  /* 料金ページの問い合わせ帯。The band itself is the site cyan: the comp reads
     #50afcd, 4.6 ΔE from --color-cyan-accent, which is the same call already
     made for the service-row icons, so it reuses the token rather than adding
     a near-duplicate. The other two have nothing close — the ink is 20.5 ΔE
     from --color-footer-ink, the orange 19.5 from --color-case — so they are
     their own values. The ink clears AA on the band (5.0:1); white on the
     orange is 2.0:1, which does not, and is kept because the comp sets it. */
  --color-contact-ink: #222584;
  --color-contact-cta: #ffa600;

  /* TOPページの料金セクションの星バッジ。A lemon yellow with nothing near it —
     17.3 ΔE from --color-plan-badge, the 料金ページ's ribbon yellow, and 27.7
     from --color-strength-accent — so it is its own value. The section's
     magenta and navy are not: they are --color-voice-cta (6.9 ΔE from the
     comp) and --color-contact-ink (0.6). */
  --color-burst: #fcef00;

  /* プラン詳細ページ。The pale band behind the figures is 7.0 ΔE from
     --color-grid, the only other near-white tint on the site, and reads
     distinctly bluer beside it, so it is its own value. The highlight is the
     one warm colour in the plan's service list; nothing on the site is near
     it (38.5 ΔE from --color-case, the closest), and it is estimated from
     12px text in the comp rather than from a flat fill, so it is accurate to
     roughly a just-noticeable step. 3.9:1 on white — AA for large text only,
     which is what it is used for. */
  --color-plan-band: #daf8ff;

  /* 比較表の地。Greener and a shade deeper than --color-plan-band, which the
     cards above it use — 8.5 ΔE apart, far enough to read as two colours when
     they sit on the same page, which is how the comp draws them. It carries
     both the header band and the hairlines between rows. */
  --color-compare-band: #c3f6f5;

  /* The 当店の強み dome, fitted to the section-head comp: sampling the teal
     edge column by column and least-squaring an ellipse through it gives a
     curve that rises 7.05% of the page width from the screen edges to the
     centre (rmse 0.8px on an 801px-wide comp). The fit is all but flat in
     the ellipse's own width, so the widest well-behaved member of that
     family is used — exactly twice the page — which makes the screen edge
     land at half the semi-axis and fixes rise at 0.133975 × the height.
     Capped at 1440px so the arc stops growing on wide desktops. */
  --dome-width: 200%;
  --dome-height: min(52.6vw, 757px);
  --dome-rise: calc(var(--dome-height) * 0.133975);

  --font-jp: "Noto Sans JP", "Hiragino Sans", "Yu Gothic", sans-serif;
  --font-en: "Inter", var(--font-jp);

  /* Type scale, set from the standard SP sizes. Every text style below
     pulls from these rather than carrying its own one-off value, so the
     whole site can be retuned from this one block.
     --fs-h1 scales with the viewport because the hero sits in a fixed
     one-line band: it reaches the 32px target on wider screens and eases
     down just enough to stay on one line on small phones. */
  --fs-h1: clamp(15px, calc(6.5vw - 5px), 32px); /* 大見出し */
  --fs-section-en: 38px;             /* セクション名（英字・装飾） */
  --fs-h2: 24px;                     /* 中見出し */
  --fs-h3: 20px;                     /* 小見出し */
  --fs-body: 16px;                   /* 本文 */
  --fs-button: 16px;                 /* ボタン */
  --fs-nav: 16px;                    /* ナビ・メニュー */
  --fs-note: 14px;                   /* 補足・注釈 */
  --fs-note-sm: 13px;                /* 補足・注釈（小） */
  --fs-price-row: 17px;             /* 料金ページのサービス行 */
  --fs-caption: 12px;                /* かなり小さい補助情報 */

  /* PC content max-widths — narrower for text-heavy/reading sections,
     wider for visual/grid sections. See individual section comments. */
  --container: 1200px;       /* base / header */
  --container-fv: 1160px;    /* FV (hero) */
  --container-works: 1120px; /* 制作事例 (Works grid) */
  --container-problem: 960px;  /* お悩み (Problem) */
  --container-insight: 960px;  /* 分析ステップ (Steps) */
  --container-point: 1160px; /* 当店の強み (Point cards) */
  --container-price: 640px;  /* サービス料金の本文 */

  /* One drop shadow for every white card on the page, so 制作事例 and
     提供サービス lift off the ground the same way. Fitted to the comp: the
     shadow spreads the same distance above and below the card — the comp's
     profiles on the two sides match — and fades over a long, soft tail
     rather than hugging its edge. */
  --shadow-card: 0 0 36px rgba(0, 0, 0, 0.12);

  /* Section rhythm. Every section's own top and bottom padding comes from
     these two, so the gap between any pair is the sum of the neighbours and
     the whole page can be re-spaced from here. The desktop block below
     raises them. */
  --space-section: 56px;
  --space-section-end: 72px;

  /* The sticky header's own height, measured: 61px on a phone, where the row
     is its min-height, and 68px from the 900px breakpoint, where the CTA pill
     makes the row taller than that. Anchor jumps offset by it. */
  --header-h: 61px;

  /* The band of grid paper the comp leaves between the last step card and
     the teal hill — wider than an ordinary section gap, and on top of the
     room the dome itself needs. */
  --analysis-gap: clamp(90px, 23vw, 390px);
}

* { box-sizing: border-box; }

/* The header is sticky, so an anchor jump would otherwise park the target
   underneath it — the top of a plan card, and its heading with it, sat behind
   the bar on both breakpoints. Offsetting the scroll container once here
   covers every jump on the site: the nav, the footer links, the サービス料金
   list and the CTA. The header is 61px tall on a phone and 68px once the CTA
   pill is in the row, and the 24px on top keeps the card's own shadow and the
   accent bar at its top edge clear of the bar rather than flush against it. */
html { scroll-behavior: smooth; scroll-padding-top: calc(var(--header-h) + 24px); }

body {
  margin: 0;
  font-family: var(--font-jp);
  color: var(--color-text);
  background: #fff;
  -webkit-font-smoothing: antialiased;
}

img { max-width: 100%; display: block; }
ul { list-style: none; margin: 0; padding: 0; }
a { color: inherit; text-decoration: none; }
button { font: inherit; border: none; background: none; cursor: pointer; padding: 0; }
h1, h2, h3, p { margin: 0; }

/* ===================== Header ===================== */
.header {
  position: sticky;
  top: 0;
  z-index: 100;
  background: #fff;
  box-shadow: 0 1px 0 rgba(0, 0, 0, 0.06);
}

.header__inner {
  max-width: var(--container);
  margin: 0 auto;
  min-height: 61px;
  display: flex;
  align-items: center;
  justify-content: space-between;
  padding: 8px 16px;
}

/* flex-shrink off: without it the header row steals width from the logo
   rather than from the nav, silently shrinking the lockup. */
.header__brand { display: flex; align-items: center; flex: 0 0 auto; }
/* Mark and wordmark come as one lockup, so it is sized by height and the
   width follows from the artwork's own 552:74 ratio. */
.header__logo { width: auto; height: 30px; }

.header__menu-btn {
  display: flex; align-items: center; justify-content: center;
  width: 40px; height: 40px; color: var(--color-gray-800);
}
/* Hamburger and close icons are swapped off the button's own expanded
   state, so no extra class bookkeeping is needed in JS. */
.header__menu-icon { width: 26px; height: 26px; }
.header__menu-icon--close { display: none; }
.header__menu-btn[aria-expanded="true"] .header__menu-icon--open { display: none; }
.header__menu-btn[aria-expanded="true"] .header__menu-icon--close { display: block; }

/* On phones the menu is a panel that hangs from the bar at the same width
   as the page's own content, and it repeats the footer: the same links at
   the same rhythm, the same rule, FOLLOW US and the copyright. The rules it
   shares with the footer are grouped there rather than restated here. */
.header__nav {
  position: fixed;
  /* Hangs from the right, under the button that opens it. It keeps the
     content width — the screen less the 20px gutters the sections use — so
     the space it leaves falls on the left. */
  inset: 61px 0 auto auto;
  width: calc(100% - 40px);
  /* Hugs its content, but never taller than the screen below the bar. */
  max-height: calc(100vh - 81px);
  background: var(--color-footer-bg);
  /* Flush under the bar and against the right edge, so only the bottom
     corners are drawn. */
  border-radius: 0 0 24px 24px;
  box-shadow: 0 14px 32px rgba(0, 0, 0, 0.14);
  transform: translateX(100%);
  /* Slow enough to read as a panel sliding in rather than a jump cut. */
  transition: transform 0.55s cubic-bezier(0.32, 0.72, 0, 1);
  overflow-y: auto;
  padding: 64px 20px 40px;
  text-align: center;
}
.header__nav.is-open { transform: translateX(0); }
/* Caps the menu's content — and with it the rule — on a wide phone. */
.header__nav > * { max-width: 640px; margin-left: auto; margin-right: auto; }

/* Hung off one left edge rather than a centre line: the labels differ enough
   in length that centred they read as a stack of unrelated headings. The
   FOLLOW US block under it keeps the footer's own centred layout. */
.header__nav-list { display: flex; flex-direction: column; align-items: flex-start; gap: 36px; text-align: left; }
.header__nav-list a,
/* 提供サービス is the group's heading, not a destination of its own, so it is
   a label rather than a link — it still has to sit like one. */
.header__nav-parent {
  display: inline-block;
  padding: 4px 8px;
  font-size: var(--fs-nav);
  font-weight: 500;
  letter-spacing: 0.08em;
  color: var(--color-footer-ink);
  white-space: nowrap;
}
.header__nav-list a:hover { opacity: 0.7; }
/* Not the text caret: it reads as a menu item, so it should not invite a
   selection drag. Kept off the shared block above, which links share. */
.header__nav-parent { cursor: default; }

/* 提供サービス carries the seven service pages. In the drawer they hang under
   their parent as a nested list rather than behind a tap: the panel already
   scrolls, and an accordion would put these pages one tap further away than
   every other link in the menu. */
.header__nav-item--has-sub { display: flex; flex-direction: column; align-items: flex-start; gap: 18px; }

/* Well inside the 36px the menu's own items sit apart, so the seven read as
   one cluster belonging to 提供サービス — and so they cost the panel as
   little height as they can. The indent is what says they belong to it: 24px
   past the label's own left edge, which the 8px of padding each item carries
   is measured from.
   The rule runs down that same 8px, so it starts under the first character of
   提供サービス rather than out in the panel's margin. margin 8 + the rule +
   padding 15 keeps the items on the 24px they already sat at. */
.header__subnav {
  display: flex;
  flex-direction: column;
  align-items: flex-start;
  gap: 12px;
  margin-left: 8px;
  padding-left: 15px;
  border-left: 1px solid rgba(43, 30, 92, 0.22);
}
/* Declared after `.header__nav-list a`, which is the same specificity: it is
   source order that lets the smaller size through. */
.header__subnav a { padding: 2px 8px; font-size: 14px; opacity: 0.8; }
.header__subnav a:hover { opacity: 0.55; }

/* The comp's menu ends at お客様の声; the CTA pill is a desktop-bar item. */
.header__nav-cta-item { display: none; }
.header__nav-cta {
  display: inline-block; margin-top: 8px; padding: 12px 24px;
  background: var(--color-cyan-accent); color: #fff !important;
  border-radius: 37px; font-weight: 600; text-align: center;
}

/* ===================== FV (Hero) ===================== */
.fv { padding: 0 20px 28px; }

.fv__inner {
  max-width: var(--container-fv);
  margin: 0 auto;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 16px;
  text-align: center;
}

/* The artwork runs to the edges of the screen, so the media block cancels
   the section's own side padding. */
.fv__media { width: calc(100% + 40px); display: flex; justify-content: center; padding: 8px 0 16px; margin: 0 -20px; }
.fv__image { width: 100%; max-width: 560px; height: auto; }

.fv__heading { display: flex; flex-direction: column; align-items: center; gap: 10px; }

.fv__heading-line span {
  display: inline-block;
  background: var(--color-cyan);
  color: #fff;
  font-family: var(--font-en);
  font-weight: 700;
  font-size: var(--fs-h1);
  letter-spacing: 0.02em;
  padding: 6px 16px;
  white-space: nowrap;
}

.fv__lead {
  max-width: 480px;
  margin-top: 16px;
  text-align: left;
  font-weight: 600;
  font-size: var(--fs-body);
  line-height: 2;
  color: var(--color-text);
}

/* ===================== CTA ===================== */
.cta {
  padding: 10px 40px;
  display: flex;
  align-items: center;
  justify-content: center;
}

.cta__button {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  /* No min-width: the pill is sized by its own label, and the side padding
     is set so the shape lands on the comp's proportions (about twice the
     width of the lettering, and 3.5 times as wide as it is tall). The old
     0.19em tracking was far looser than the comp, which sets the label
     almost solid. */
  padding: 18px 50px;
  background: var(--color-cyan-accent);
  color: #fff;
  border-radius: 37px;
  font-weight: 600;
  font-size: var(--fs-button);
  letter-spacing: 0.06em;
  transition: opacity 0.2s ease, transform 0.2s ease;
}
.cta__button:hover { opacity: 0.85; transform: translateY(-1px); }

/* The two closing CTAs — one after 提供サービス, one at the foot of the page —
   carry their own breathing room rather than leaning on a neighbouring
   section's padding. The space is split evenly above and below so the
   button sits in the middle of its band; the amount is the average of the
   section rhythm's two figures, which leaves the page's overall length
   where it was. */
.cta--closing {
  padding-block: calc((var(--space-section) + var(--space-section-end)) / 2);
}

/* 提供サービス has no ground of its own, so its closing padding and the CTA's
   would stack into a gap above the button twice the one below it. Pulling the
   CTA up by exactly that padding leaves a single gap, matched top and bottom.
   The CTA at the foot of the page is left alone: お客様の声 does have a ground,
   and lifting the button would set it on the cream. */
.service + .cta--closing {
  margin-top: calc(-1 * var(--space-section-end));
}

/* ===================== Works (slider) ===================== */
/* Top padding is 40 rather than 50: .cta already contributes 10px below
   the button, and the design sets the illustration 50px under it. */
.works { padding: var(--space-section) 0 var(--space-section-end); }

.works__slider {
  position: relative;
  max-width: var(--container-works);
  margin: 0 auto;
  padding: 0 20px;
}

/* A horizontal scroller also clips vertically — overflow-y cannot stay
   visible once overflow-x is auto — so without room inside the box the
   cards' drop shadows would be cut off a few pixels below them. The padding
   opens that room and the matching negative margins take it back out of the
   layout, so the cards stay exactly where they were. Only vertically: side
   padding here would be scrolled away by the snap on load. */
.works__track {
  display: flex;
  gap: 10px;
  overflow-x: auto;
  overscroll-behavior-x: contain;
  scroll-snap-type: x mandatory;
  -webkit-overflow-scrolling: touch;
  scrollbar-width: none;
  /* The bottom is -32 rather than -36: the track kept 4px under the cards
     before this. */
  margin: -36px 0 -32px;
  padding: 36px 0 36px;
}
.works__track::-webkit-scrollbar { display: none; }

.works__nav {
  position: absolute;
  top: 40%;
  transform: translateY(-50%);
  z-index: 2;
  width: 36px;
  height: 36px;
  border-radius: 50%;
  background: #fff;
  color: var(--color-cyan-accent);
  display: flex;
  align-items: center;
  justify-content: center;
  box-shadow: 0 2px 10px rgba(0, 0, 0, 0.18);
  transition: opacity 0.2s ease, transform 0.2s ease;
}
.works__nav svg { width: 18px; height: 18px; }
.works__nav:hover { opacity: 0.85; }
.works__nav:disabled { opacity: 0.35; pointer-events: none; }
.works__nav--prev { left: 4px; }
.works__nav--next { right: 4px; }

/* Metrics follow the Figma card (170x305): a 158px image, a 10px gap,
   then the text block. The 305px is a minimum rather than a fixed height —
   real case copy runs longer than the placeholder it was drawn with, and
   the flex row already stretches every card to match the tallest. */
.work-card {
  flex: 0 0 auto;
  width: 170px;
  scroll-snap-align: start;
  display: flex;
  flex-direction: column;
  gap: 10px;
  min-height: 305px;
  background: #fff;
  border-radius: 20px;
  overflow: hidden;
  padding-bottom: 16px;
  box-shadow: var(--shadow-card);
}

.work-card__image { width: 100%; flex: none; aspect-ratio: 170 / 158; background: var(--color-gray-200); overflow: hidden; }
.work-card__image img { width: 100%; height: 100%; object-fit: cover; }

.work-card__body { padding: 0 15px; display: flex; flex-direction: column; gap: 5px; }

.work-card__tag {
  display: inline-flex;
  align-self: flex-start;
  align-items: center;
  height: 29px;
  background: var(--color-tag-bg);
  border-radius: 11px;
  padding: 0 12px;
  font-family: var(--font-en);
  font-size: var(--fs-caption);
  font-weight: 600;
  letter-spacing: 0.08em;
  color: var(--color-tag-text);
}

.work-card__title { font-family: var(--font-en); font-size: var(--fs-body); font-weight: 600; line-height: 1.5; letter-spacing: 0.04em; }
/* Tightened from the 0.19em the placeholder text was set at: that spacing
   reads as a design accent on a 3-character dummy, but as slack on a real
   sentence. */
.work-card__desc { font-family: var(--font-en); font-size: var(--fs-caption); font-weight: 600; line-height: 1.7; letter-spacing: 0.04em; color: var(--color-gray-600); }

/* ===================== Problem ===================== */
.problem {
  position: relative;
  /* Above the next section, which is positioned too: without this its
     background would paint over the tail hanging off the bottom. */
  z-index: 1;
  background: var(--color-yellow);
  padding: 0 0 var(--space-section-end);
  display: flex;
  flex-direction: column;
  align-items: center;
}

/* The comp runs the lead line straight into the illustration, so this head
   drops the shared 28px below it. */
.problem .section-head { margin-bottom: 3px; }

/* The section title lives inside the white illustration band so the two
   stay a single block — as separate children of .problem they would be
   split by that flex row's gap, showing a stripe of yellow between them. */
.problem__head {
  width: 100%;
  padding: 50px 0 0;
}

.problem__intro-band {
  position: relative;
  width: 100%;
  background: #fff;
  display: flex;
  flex-direction: column;
  align-items: center;
  /* The character hangs below the white band onto the yellow, so nothing is
     clipped here; the hill no longer overflows sideways either. */
  overflow: visible;
  /* The yellow between the hill and CASE01, as a share of the viewport. */
  margin-bottom: 34.6%;
}

/* Reproduces the original 390x352 artwork's proportions as a sizing
   reference, so the dome, character and label — each positioned by the
   percentages they occupied in that artwork — stay in lockstep at any
   viewport width. */
.problem__intro-canvas {
  position: relative;
  width: 100%;
  max-width: 640px;
  /* Far shallower than the artwork's own 390:352. The comp runs the lead
     line straight into the character and starts the hill just under it, so
     the white band is only a fifth as tall as it is wide; the character
     itself hangs out of the bottom onto the yellow. */
  aspect-ratio: 473 / 100;
}

/* The hill: a half-ellipse as wide as the band, so its ends land exactly
   on the band's bottom corners and the yellow below carries on without a
   seam. The comp draws it as a very shallow arc — it rises about 3% of the
   viewport from the edges to the middle — rather than the tall dome the
   artwork's own hill had. */
.problem__intro-ground {
  position: absolute;
  inset: auto 0 0 0;
  /* Spans the band, which is the full page width, so the arc's ends land on
     the band's bottom corners and nothing hangs off the page. The height is
     the rise itself — about 3% of the window, as the comp draws it. */
  height: 2.9vw;
  border-radius: 50% 50% 0 0 / 100% 100% 0 0;
  background: var(--color-yellow);
}

/* Thought bubbles either side of the character, above the hill. The two
   files are mirrors of each other: the trailing dots point inwards, so the
   left set has them running right and the right set running left. They sit
   below the character in the stack so any overlap tucks behind them. */
.problem__intro-bubbles {
  position: absolute;
  top: 11.2%;
  width: 30%;
  height: auto;
  z-index: 1;
}
.problem__intro-bubbles--left { left: 2%; }
.problem__intro-bubbles--right { right: 2%; }

/* The character illustration itself has no baked-in background — it's
   the source vector art, not the flattened composite — so it can sit
   directly on the CSS dome with no seam or clipping needed. */
.problem__intro-character {
  position: absolute;
  left: 50%;
  /* The artwork is cropped to the figure itself now that the "?" props are
     gone, so these two numbers are re-derived to land it in exactly the
     same place and at the same size as the old padded file did. */
  top: 34.2%;
  width: 30%;
  height: auto;
  transform: translateX(-50%);
  z-index: 2;
}

.problem__list {
  width: 100%;
  max-width: 640px;
  padding: 0 16px;
  display: flex;
  flex-direction: column;
  gap: 24px;
}

/* The whole yellow block reads as one speech bubble: a border triangle
   hangs off the bottom edge as its tail. */
.problem::after {
  content: "";
  position: absolute;
  top: 100%;
  left: 50%;
  transform: translateX(-50%);
  width: 0;
  height: 0;
  border-left: 76px solid transparent;
  border-right: 76px solid transparent;
  border-top: 62px solid var(--color-yellow);
}

.problem__item { display: flex; }

/* ---- Case card ---- */
/* The CASE label is a tab on top of the card, so the card's top-left corner
   is square and the label carries the rounding there instead. */
.case-card { container-type: inline-size; width: 100%; }

.case-card__label {
  display: inline-block;
  padding: 5px 32px;
  background: var(--color-case);
  color: #fff;
  border-radius: 12px 12px 0 0;
  font-family: var(--font-en);
  font-size: var(--fs-body);
  font-weight: 700;
  letter-spacing: 0.12em;
}

.case-card__body {
  background: #fff;
  border-radius: 0 20px 20px 20px;
  /* Narrow sides: the longest headline runs nearly the full width of the
     card in the comp. */
  padding: 36px 10px 24px;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 28px;
}

/* The headlines are written to two lines of about 11 characters, which fits
   at the full 20px on any normal phone. The card-based cap only bites on
   very narrow screens, where it shrinks rather than adding a third line. */
.case-card__title {
  text-align: center;
  font-size: min(var(--fs-h3), calc((100cqi - 20px) / 11.4));
  font-weight: 700;
  line-height: 1.5;
  color: var(--color-case);
}

.case-card__voice { display: flex; align-items: center; justify-content: center; gap: 12px; }

/* The artwork is already cropped to its own circle, so this only sizes it. */
.case-card__avatar { flex: 0 0 auto; width: 84px; height: 84px; }

.case-card__balloon {
  position: relative;
  padding: 12px 18px;
  border: 2px solid var(--color-case);
  border-radius: 10px;
  text-align: center;
  font-size: var(--fs-note-sm);
  line-height: 1.8;
  letter-spacing: 0.02em;
  color: var(--color-text);
}
/* Outline triangle first, then the white one inset by the border width, so
   the tail picks up the same 2px outline as the balloon. */
.case-card__balloon::before,
.case-card__balloon::after {
  content: "";
  position: absolute;
  top: 50%;
  right: 100%;
  width: 0;
  height: 0;
  border: 9px solid transparent;
  transform: translateY(-50%);
}
.case-card__balloon::before { border-right-color: var(--color-case); }
.case-card__balloon::after { border-right-color: #fff; margin-right: -3px; }

/* ===================== Analysis ===================== */
/* Graph paper drawn with two repeating gradients rather than an image, so it
   stays crisp and costs nothing to download. */
.analysis {
  position: relative;
  overflow: hidden;
  background:
    repeating-linear-gradient(to right, var(--color-grid) 0 1px, transparent 1px 19px),
    repeating-linear-gradient(to bottom, var(--color-grid) 0 1px, transparent 1px 19px),
    #fff;
  /* Top padding is measured from the comp: the eyebrow sits 11.7% of the page
     width below the tip of the お悩み tail. The stationery in the corners is
     allowed to sit alongside the heading, exactly as it does in the comp. */
  padding: 109px 20px calc(var(--analysis-gap) + var(--dome-rise));
}

/* Stationery scattered into the top corners, running off the edges as in
   the comp. Decorative only, so they sit behind the text. */
.analysis__deco {
  position: absolute;
  top: 16px;
  z-index: 0;
  width: 30%;
  max-width: 140px;
  height: auto;
}
.analysis__deco--left { left: -4%; }
.analysis__deco--right { right: -4%; }

.analysis__head {
  position: relative;
  z-index: 1;
  max-width: 640px;
  margin: 0 auto;
  text-align: center;
  color: var(--color-text);
}

.analysis__eyebrow {
  font-size: var(--fs-body);
  font-weight: 500;
  letter-spacing: 0.06em;
}

.analysis__title {
  margin-top: 11px;
  display: flex;
  flex-direction: column;
  gap: 14px;
  font-size: var(--fs-h2);
  font-weight: 700;
  line-height: 1.4;
  letter-spacing: 0.02em;
}

.analysis__accent { color: var(--color-sky); }

.analysis__lead {
  margin-top: 21px;
  font-size: var(--fs-body);
  font-weight: 500;
  line-height: 1.8;
  letter-spacing: 0.02em;
}
.analysis__lead em { font-style: normal; }

/* ---- Step cards ---- */
.steps {
  list-style: none;
  width: 100%;
  max-width: 640px;
  margin: 0 auto;
  padding: 44px 0 0;
  display: flex;
  flex-direction: column;
  gap: 24px;
}

.step-card {
  container-type: inline-size;
  position: relative;
  overflow: hidden;
  background: var(--color-cream);
  border-radius: 24px;
  padding: 36px 20px 32px;
}

/* The step word sits behind everything as a watermark and is allowed to run
   off the card's left edge, exactly as it is drawn in the comp. */
.step-card__mark {
  position: absolute;
  top: 4px;
  left: 14px;
  z-index: 0;
  font-family: var(--font-en);
  font-size: 17cqi;
  font-weight: 700;
  line-height: 1;
  letter-spacing: 0.06em;
  color: var(--color-step-mark);
}

/* Each card's artwork arrives as one SVG: the photo circle, the sticky
   notes and their layering are all baked in, so the only thing CSS has to
   know is where the circle's centre sits inside it — that is what
   --circle-center carries, and the transform below uses it to put the
   circle (not the whole drawing) in the middle of the card. */
.step-card__media {
  position: relative;
  z-index: 1;
  display: block;
  width: 68%;
  max-width: 336px;
  height: auto;
  margin: 0 auto;
  transform: translateX(calc(50% - var(--circle-center)));
}

.step-card--know   { --circle-center: 38.7%; }
.step-card--find   { --circle-center: 60.44%; }
.step-card--layout { --circle-center: 46.07%; }
.step-card--create { --circle-center: 58.2%; }

.step-card__title {
  position: relative;
  z-index: 1;
  margin-top: 24px;
  text-align: center;
  font-size: var(--fs-h2);
  font-weight: 700;
  letter-spacing: 0.04em;
  color: var(--color-text);
}

.step-card__body {
  position: relative;
  z-index: 1;
  margin-top: 20px;
  display: flex;
  flex-direction: column;
  gap: 4px;
  font-size: var(--fs-body);
  line-height: 1.7;
  letter-spacing: 0.02em;
  color: var(--color-text);
}

/* ===================== Point ===================== */
/* The teal ground rises in a wide, shallow dome. A border-radius with a
   50% horizontal and a small vertical radius draws that arc across the
   whole width without an extra element — and, unlike an oversized
   pseudo-element, it cannot overflow the page sideways. */
.point {
  --point-pad-top: var(--space-section);
  position: relative;
  background: var(--color-point-bg);
  padding: var(--point-pad-top) 20px var(--space-section-end);
}

/* The cap is only as tall as the dome's rise and clips the ellipse, so the
   oversized shape can never push the page sideways. Sinking the ellipse by
   (height - rise) puts its cut-off edges exactly on the section's own top
   line, leaving one continuous curve. */
.point__dome {
  position: absolute;
  left: 0;
  right: 0;
  /* Overlaps the section by 1px so the two teal areas cannot leave a
     hairline seam where they meet. */
  bottom: calc(100% - 1px);
  height: calc(var(--dome-rise) + 1px);
  overflow: hidden;
  pointer-events: none;
}

.point__dome::before {
  content: "";
  position: absolute;
  left: 50%;
  bottom: calc(var(--dome-rise) + 1px - var(--dome-height));
  transform: translateX(-50%);
  width: var(--dome-width);
  height: var(--dome-height);
  border-radius: 50% 50% 0 0 / 100% 100% 0 0;
  background: var(--color-point-bg);
}

/* Illustrated section title: a mark, the English name set large, and the
   Japanese reading beneath it. The <h2> wraps both words so the heading
   still reads as "Works 制作事例" to a screen reader. */
.section-head {
  display: flex;
  flex-direction: column;
  align-items: center;
  padding: 0 20px;
  margin-bottom: 28px;
  text-align: center;
}

/* The gap lives on the icon, not the title, so a head without an
   illustration (お悩み) starts flush at the English name. */
.section-head__icon { width: 70px; height: auto; margin-bottom: 15px; }

.section-head__title {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 8px;
  color: var(--color-text);
}

.section-head__en {
  font-family: var(--font-en);
  font-size: var(--fs-section-en);
  font-weight: 600;
  letter-spacing: 0.1em;
  line-height: 1.1;
}

.section-head__ja {
  font-size: var(--fs-note);
  font-weight: 500;
  letter-spacing: 0.12em;
}

/* Used where the Japanese line is the section's lead question rather than
   just the section name, so it is set at heading size. */
.section-head__ja--lead {
  font-size: var(--fs-h3);
  font-weight: 400;
  letter-spacing: 0.04em;
  line-height: 1.5;
}

.section-head__accent { font-style: normal; color: var(--color-cyan-accent); }

/* 当店の強み is the one head that sits on the teal ground, so its Japanese
   line is reversed out while the English name keeps the navy. */
.point .section-head { position: relative; z-index: 1; }
.point .section-head__title { color: #fff; }
.point .section-head__en { color: var(--color-text); }

/* The megaphone straddles the dome: two thirds of it stand on the grid
   paper above, one third rests on the teal. Its height follows the English
   name, but it is placed against the dome's apex — which sits one rise
   above the section's own top edge — so the illustration keeps touching
   the hill however the curve is sized. In the comp the bell's foot lands
   0.50em below the apex and the English name's ink starts 0.74em below it,
   which is the icon box sitting straight on the name with no gap at all. */
.point .section-head__icon {
  width: auto;
  height: calc(var(--fs-section-en) * 1.66);
  margin-bottom: 0;
}

/* The lift belongs to the head, not to the megaphone inside it: hung off
   the icon, the negative margin eats the flex container's own height,
   which bottoms out at zero once the head is taller than the lift — and
   then margin-bottom below measures from the padding edge instead of from
   the label. On the head itself the box stays honest at every width.
   The comp leaves 30.7px under the ink of 当店の4つの強み on a 390px page,
   a little under half the section rhythm; 3.3px of that is the label's own
   descent space, so the margin carries the rest. */
.point .section-head {
  margin-top: calc(-1 * (var(--point-pad-top) + var(--dome-rise) + var(--fs-section-en) * 1.11));
  margin-bottom: calc(var(--space-section) * 0.49);
}

/* The 4 in more design の4つの強み is display type, not a word: it overhangs
   the line rather than pushing the label apart. */
.section-head__count {
  position: relative;
  /* Dropped off the shared baseline: in the comp the numeral hangs below
     the Japanese it sits in, the way a price tag's figure does. */
  top: 0.1em;
  margin: 0 0.12em;
  font-family: var(--font-en);
  font-size: calc(var(--fs-section-en) * 1.49);
  font-weight: 600;
  line-height: 0;
  letter-spacing: 0;
  color: var(--color-strength-accent);
}

/* The numeral is tall enough to reach the English name above it, so this
   one head opens the two lines further than the shared 8px. */
.point .section-head__title { gap: calc(var(--fs-section-en) * 0.47); }

.point__list {
  max-width: var(--container-point);
  margin: 0 auto;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 80px;
}

/* The card is its own measuring stick: the comp sets the illustration, the
   numeral and the diagram as fractions of the card's width, not the
   viewport's, and the card is narrower on desktop than on a phone. */
.point__card {
  container-type: inline-size;
  width: 100%;
  max-width: 352px;
  background: #fff;
  /* Fitted to the comp's corner: 58 rows of the arc least-square to a 44px
     radius (the same fit returns 38.9px for our own 40px card, so the
     reading carries a −3% bias and 43.3px reads as 44). */
  border-radius: 44px;
  overflow: hidden;
}

/* The side padding is measured off the card 02 comp, where the body runs to
   within 1.4% of each edge — 4px on a 350px card. The bottom padding is not:
   the comp closes the card up almost immediately after the last line, and
   that was tried and turned down, so the original breathing room below the
   copy stays. */
.point__card-top {
  padding: 28px 4px 24px;
  display: flex;
  flex-direction: column;
  align-items: center;
  text-align: center;
}

/* The numeral hangs from the bottom of this box rather than floating in the
   middle of it: in the comp its foot lands 34.1% of the card below the top
   edge, clear of the illustration, and 5.7% above the first heading bar. */
.point__number-wrap {
  position: relative;
  display: flex;
  align-items: flex-end;
  justify-content: center;
  width: 100%;
  min-height: 31.1cqi;
}

/* The drawing runs into one of the card's top corners, so it cancels the
   card's own padding rather than sitting inside it. Which corner, and how
   wide the drawing is, are the only things that change between cards. */
.point__number-icon {
  position: absolute;
  left: -12px;
  top: -28px;
  width: var(--illus-w, 39.3cqi);
  max-width: none;
  height: auto;
  z-index: 0;
}

.point__card--illus-right { --illus-w: 43cqi; }
.point__card--illus-right .point__number-icon { left: auto; right: -12px; }

.point__number {
  position: relative;
  z-index: 1;
  font-family: var(--font-en);
  font-weight: 700;
  font-size: 18.3cqi;
  color: var(--color-point-bg);
  letter-spacing: 0.05em;
  line-height: 1.3;
}

/* A label, not a banner. The ground sits on the inline text rather than on
   the heading box, so a heading broken over two lines comes out as two
   separate bars, each only as wide as its own line — which is how the comp
   draws it. line-height then doubles as the gap between those bars. */
.point__card-heading {
  max-width: 100%;
  margin-top: 0;
  font-weight: 600;
  /* Each line is broken by hand, so it must not re-wrap. The divisor is how
     many ems the longest line across the four cards runs to, tracking
     included; dividing the space left over after the card's and the bar's
     padding by it gives the largest size that still fits once the cards
     narrow on desktop. A card whose heading runs longer than the rest can
     set --head-em to keep its own lines intact — at the cost of setting
     smaller than its neighbours.
     9.45 = 制作して終わらない, the longest of the four lines, at 9 characters
     on the 1.05em advance the 0.05em tracking gives them. */
  font-size: min(var(--fs-h3), calc((100cqi - 44px) / var(--head-em, 9.45)));
  letter-spacing: 0.05em;
  line-height: 1.84;
  text-align: center;
}

.point__card-heading span {
  background: var(--color-point-bg);
  color: #fff;
  padding: 0.5px 18px;
  -webkit-box-decoration-break: clone;
  box-decoration-break: clone;
}

.point__card-text {
  width: 100%;
  /* 8.3% of the card under the last bar, against the 20.2% we had. */
  margin-top: 3.6cqi;
  /* The card itself only insets its contents by 4px, which the centred
     heading bars hide but the left-aligned copy does not. 18px is the padding
     the bars carry inside themselves, so the two agree. */
  padding-inline: 18px;
  font-weight: 600;
  /* The measure is exactly 100cqi - 44px (the card's 4px a side plus this
     18px), so the divisor is the characters per line: 19 of them, which holds
     the longest of the four texts (90 characters) in five lines at any card
     width. At the 350px design width that comes to 16.1px, so --fs-body is
     what applies there and only a narrower card eases the size down. */
  font-size: min(var(--fs-body), calc((100cqi - 44px) / 19));
  line-height: 1.85;
  letter-spacing: 0.02em;
  color: #435489;
  text-align: left;
}

.point__card-bottom { width: 100%; height: 210px; background: var(--color-gray-600); overflow: hidden; }
.point__card-bottom img { width: 100%; height: 100%; object-fit: cover; }

/* A diagram rather than a photograph: it keeps the card's white ground and
   sits centred in it, so it is not cropped to a band. */
/* The diagram keeps its own white ground and sits inside the block rather
   than filling it. It takes the same fixed height as the photographs and the
   artwork is sized off that height, so the four cards stay level at every
   card width — a cqi-sized diagram grew past the photos on a desktop. */
.point__card-bottom--figure {
  background: #fff;
  padding: 12px;
  display: flex;
  align-items: center;
  justify-content: center;
}
.point__card-bottom--figure img {
  width: auto;
  height: 100%;
  max-width: 100%;
  object-fit: contain;
}

/* ===================== Service ===================== */
.service { padding: var(--space-section) 0 var(--space-section-end); }

/* The palette mark is a squarer, denser drawing than the Works bird, so it
   is set smaller to carry the same weight next to the English name. */
.service .section-head__icon { width: 54px; }

.service__list {
  max-width: var(--container-works);
  margin: 0 auto;
  padding: 0 20px;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 24px;
}

.service-card {
  /* カードごとのアクセント。タグとボタンが参照する。 */
  --card-accent: var(--color-service-blue);
  container-type: inline-size;
  width: 100%;
  max-width: 352px;
  background: #fff;
  border-radius: 20px;
  overflow: hidden;
  box-shadow: var(--shadow-card);
}

/* The image bows gently downward along its bottom edge — the same curve
   language as the section domes, at card scale. Raising only the two bottom
   corners leaves the centre as the lowest point; the rise is in cqi so the
   bow keeps its shape as the card narrows. */
/* The tag sits on the photograph, so it needs a box that is not the image's
   own: that one clips to the bowed bottom edge and would bite the pill. */
.service-card__media { position: relative; }

.service-card--logo { --card-accent: var(--color-service-orange); }
/* カンプの #50afcd。プランカードの帯などと同じ判断で既存のシアンを流用。 */
.service-card--namecard { --card-accent: var(--color-cyan-accent); }
.service-card--package { --card-accent: var(--color-cyan-accent); }
.service-card--illust { --card-accent: var(--color-service-pink); }
.service-card--movie { --card-accent: var(--color-service-purple); }

.service-card__image {
  width: 100%;
  aspect-ratio: 352 / 311;
  /* Every card now carries its own photograph; this only shows while one
     loads, so it is a light placeholder rather than the old dark block. */
  background: var(--color-gray-100);
  border-radius: 0 0 50% 50% / 0 0 5.4cqi 5.4cqi;
  overflow: hidden;
}
.service-card__image img { width: 100%; height: 100%; object-fit: cover; }

/* The heading runs closer to the card edges than the body copy does, so the
   inset is split: a narrow one here, and the rest added back on the text. */
.service-card__body {
  padding: 51px 10px 32px;
  display: flex;
  flex-direction: column;
  align-items: center;
}

/* Hung off the photograph's lower edge rather than sitting in the body, and
   set large enough to read as the card's label. The size follows the card so
   the longest tag (各種印刷物デザイン制作, 11 characters) still fits inside it;
   all five share one container width, so they all land on the same size. */
.service-card__tag {
  position: absolute;
  left: 50%;
  bottom: 22px;
  transform: translateX(-50%);
  padding: 7px 28px;
  border-radius: 999px;
  background: var(--card-accent);
  color: #fff;
  font-size: min(27px, calc((100cqi - 72px) / 11));
  font-weight: 700;
  line-height: 1.2;
  letter-spacing: 0.02em;
  white-space: nowrap;
}

/* Set to hold the design's two lines. Each half is a nowrap inline-block, so
   the break always falls between them rather than orphaning the trailing
   「へ」. 19px rather than the scale's 20px because the longer half runs
   almost the full card width at the 390px design size; below that the size
   follows the viewport so it still fits on one line. */
.service-card__title {
  text-align: center;
  font-size: min(21px, calc((100cqi - 20px) / 17.3));
  font-weight: 700;
  line-height: 1.72;
}
.service-card__title span { display: inline-block; white-space: nowrap; }

/* The seven descriptions are written to the same length so they set the same
   five lines. 48px is the card's own horizontal inset (10 + 14 a side), so
   the measure is exactly 100cqi - 48 and the divisor below is literally the
   characters per line. 18.06 is what lets the widest card the desktop grid
   makes (355px) still reach the full --fs-body of 17px, so the descriptions
   are written to fit five lines at that rate rather than the size being eased
   down to fit them. Only a card narrower than the design width actually eases
   the size. */
.service-card__desc {
  width: 100%;
  margin-top: 28px;
  padding: 0 14px;
  font-size: min(var(--fs-body), calc((100cqi - 48px) / 18.06));
  line-height: 1.84;
  /* No tracking here, unlike the rest of the body copy: the comps set these
     descriptions solid, and the 0.02em was costing a character per line —
     enough to push 各種印刷物デザイン制作 onto a seventh line. */
  letter-spacing: 0;
}

/* Sits close under the copy — much closer than the copy sits under the
   heading — so it reads as the end of that block rather than a third item. */
.service-card__button {
  margin-top: 8px;
  display: flex;
  align-items: center;
  justify-content: center;
  width: 247px;
  max-width: 100%;
  min-height: 70px;
  padding: 8px 16px;
  border-radius: 999px;
  background: var(--card-accent);
  color: #fff;
  font-size: 24px;
  font-weight: 700;
  letter-spacing: 0.04em;
  transition: opacity 0.2s ease, transform 0.2s ease;
}
.service-card__button:hover { opacity: 0.88; transform: translateY(-1px); }

/* ===================== Voice ===================== */
/* The comp hangs the watermark close to the section's top edge on phones,
   so this one section opens with less than the shared rhythm; desktop keeps
   it, where the comp puts the watermark a full --space-section down. */
.voice { background: var(--color-cream); padding: 20px 0 var(--space-section-end); }

/* The section name again, oversized and in the pale yellow, set into the
   top-left corner above the heading. It stays in the flow so it opens its
   own space rather than running under the speech-bubble mark. Decorative:
   hidden from screen readers, since the real heading follows straight
   after. The size is smaller on phones, where the section is narrow. */
/* The comp sets this head looser than the others: more air under the
   watermark and between the English name and its Japanese reading. */
.voice .section-head__title { gap: 23px; }

.voice__watermark {
  margin: 0 0 26px 5%;
  font-family: var(--font-en);
  font-size: 10vw;
  font-weight: 700;
  line-height: 1;
  letter-spacing: 0.06em;
  color: var(--color-yellow);
}

/* Two speech bubbles, a wider drawing than the Works bird, so it takes a
   little more width to read at the same weight. */
.voice .section-head__icon { width: 76px; margin-bottom: 10px; }

.voice .section-head { margin-bottom: 40px; }

/* Set at heading size like the お悩み lead. The two halves are nowrap
   inline-blocks so the break falls where the design puts it. */
.voice__lead {
  padding: 0 20px;
  text-align: center;
  font-size: var(--fs-h3);
  font-weight: 400;
  line-height: 1.7;
  letter-spacing: 0.04em;
  color: var(--color-text);
}
.voice__lead span { display: inline-block; white-space: nowrap; }

/* On phones the three voices scroll one at a time; from 900px up the desktop
   rules below turn the same track back into a wrapped row and hide the
   arrows. The JS driving both sliders is keyed off data attributes, so this
   shares 制作事例's behaviour without sharing its markup. */
.voice__slider {
  position: relative;
  max-width: var(--container-works);
  margin: 0 auto;
  padding: 40px 20px 0;
}

.voice__list {
  display: flex;
  gap: 20px;
  overflow-x: auto;
  overscroll-behavior-x: contain;
  scroll-snap-type: x mandatory;
  -webkit-overflow-scrolling: touch;
  scrollbar-width: none;
}
.voice__list::-webkit-scrollbar { display: none; }

.voice__nav {
  position: absolute;
  /* Centred on the thumbnail rather than the whole card, which runs on
     below it with the caption and the client name. */
  top: 36%;
  z-index: 2;
  width: 36px;
  height: 36px;
  border-radius: 50%;
  background: #fff;
  color: var(--color-cyan-accent);
  display: flex;
  align-items: center;
  justify-content: center;
  box-shadow: 0 2px 10px rgba(0, 0, 0, 0.18);
  transition: opacity 0.2s ease, transform 0.2s ease;
}
.voice__nav svg { width: 18px; height: 18px; }
.voice__nav:hover { opacity: 0.85; }
.voice__nav:disabled { opacity: 0.35; pointer-events: none; }
.voice__nav--prev { left: 4px; }
.voice__nav--next { right: 4px; }
/* With a single interview there is nothing to send, so the arrows go rather
   than sitting there greyed out — the same rule the quote slider uses. They
   come back on their own once a second card is added. */
.voice__slider.is-static .voice__nav { display: none; }

.voice-card {
  flex: 0 0 auto;
  width: 100%;
  max-width: 352px;
  scroll-snap-align: center;
}

/* The corner is elliptical, not circular. The two radii are set from the
   straight runs left between them in the comp: 28% across leaves the top and
   bottom edges flat for 44% of the width, and 41.5% down leaves the left and
   right edges flat for 17% of the height. A circular radius cannot hit both
   at once, which is why the vertical figure is the larger of the two. */
.voice-card__media {
  width: 100%;
  aspect-ratio: 4 / 3;
  background: var(--color-voice-media);
  border-radius: 28% / 41.5%;
  overflow: hidden;
  /* Reset for the card that is a <button> (the ones with a video attached);
     harmless on the plain <div> placeholders. */
  display: block;
  padding: 0;
  border: 0;
  appearance: none;
}
.voice-card__media img { width: 100%; height: 100%; object-fit: cover; }

/* The card that plays a video. The interviews are vertical (9:16) while the
   comp draws this window 4:3, so the card shows a still cropped to the comp's
   shape and the video itself opens in a dialog at its own proportions. The
   still is framed a little above centre: on the source frame that keeps both
   speakers and the logo in the window rather than the caption band below. */
.voice-card__media--video {
  position: relative;
  cursor: pointer;
}
.voice-card__media--video img {
  object-position: center 40%;
  transition: transform 0.3s ease;
}
.voice-card__media--video:hover img,
.voice-card__media--video:focus-visible img { transform: scale(1.04); }

/* Keyboard focus keeps a ring — it is the only thing telling that user where
   they are — but in the section's own magenta rather than the browser's blue,
   and held off the card so it reads as a ring and not as a border. */
.voice-card__media--video:focus-visible {
  outline: 3px solid var(--color-voice-cta);
  outline-offset: 4px;
}

.voice-card__play {
  position: absolute;
  top: 50%;
  left: 50%;
  transform: translate(-50%, -50%);
  width: 21%;
  max-width: 72px;
  aspect-ratio: 1;
  pointer-events: none;
  filter: drop-shadow(0 2px 10px rgba(0, 0, 0, 0.35));
  transition: transform 0.2s ease;
}
.voice-card__play svg { width: 100%; height: 100%; display: block; }
.voice-card__media--video:hover .voice-card__play,
.voice-card__media--video:focus-visible .voice-card__play {
  transform: translate(-50%, -50%) scale(1.08);
}

/* ---- インタビュー動画のダイアログ ---- */
.video-modal,
.photo-modal {
  position: fixed;
  inset: 0;
  z-index: 100;
  display: flex;
  align-items: center;
  justify-content: center;
  padding: 20px;
}
.video-modal[hidden],
.photo-modal[hidden] { display: none; }

.video-modal__backdrop,
.photo-modal__backdrop {
  position: absolute;
  inset: 0;
  background: rgba(0, 0, 0, 0.82);
}

/* The dialog is the video: 9:16, as tall as the viewport allows, and never
   wider than the screen on a phone held upright. */
.video-modal__dialog {
  position: relative;
  /* Sized from the width so the 9:16 box survives on a narrow phone, where a
     height-first box would be squeezed by max-width and stop being 9:16.
     The width is whichever is smaller: the screen, or what fits in 86vh. */
  width: min(100%, calc(86vh * 9 / 16));
  max-width: 506px;
  aspect-ratio: 9 / 16;
}

.video-modal__frame,
.video-modal__frame iframe {
  width: 100%;
  height: 100%;
  display: block;
  border: 0;
  border-radius: 16px;
}

.video-modal__close,
.photo-modal__close {
  position: absolute;
  right: 0;
  bottom: calc(100% + 10px);
  width: 40px;
  height: 40px;
  display: flex;
  align-items: center;
  justify-content: center;
  padding: 0;
  border: 0;
  border-radius: 999px;
  background: rgba(255, 255, 255, 0.14);
  color: #fff;
  cursor: pointer;
}
.video-modal__close svg,
.photo-modal__close svg { width: 22px; height: 22px; }
.video-modal__close:hover,
.photo-modal__close:hover { background: rgba(255, 255, 255, 0.28); }

/* 拡大したプロフィール写真。元画像は 884px 四方（表示 408px の 2.1 倍）で、
   表示サイズは 408px のまま据え置いている。丸く切り抜いたサムネイルと違い、
   ここでは写真の四隅まで見せたいので角丸の四角にしている。 */
.photo-modal__dialog {
  position: relative;
  /* 86vh から閉じるボタンのぶん（40px＋10px の間隔）を引いている。
     横向きの画面など縦が短いとき、ボタンがダイアログの上に出る作りなので、
     引いておかないと画面の外に追い出される。 */
  width: min(100%, calc(86vh - 50px), 408px);
  aspect-ratio: 1;
}
.photo-modal__dialog img {
  width: 100%;
  height: 100%;
  display: block;
  border-radius: 16px;
  object-fit: cover;
}

/* The caption rides up over the bottom of the thumbnail. A negative margin
   does that in normal flow, so nothing has to be positioned and the name
   below still sits under whatever height the caption ends up at. */
.voice-card__comment {
  /* Stacked above the window it overlaps: the video card is position:
     relative (it has to be, to place the play badge), and a positioned
     element paints over a static sibling whatever the source order says. */
  position: relative;
  z-index: 1;
  width: 78%;
  margin: -20px auto 0;
  /* 11% of the card width — 38px at the 390px design size, as in the comp,
     but it eases in on narrower phones so the quote stays on two lines
     instead of spilling onto a third. */
  padding: 10px 11%;
  background: #fff;
  border-radius: 999px;
  font-size: 18px;
  font-weight: 700;
  line-height: 1.5;
  letter-spacing: 0.02em;
  /* Break between phrases, not anywhere a character happens to land: without
     it 「愛犬を入れたロゴをお／願いしました」 leaves the お stranded at the end
     of the first line. Chromium only; elsewhere it falls back to the ordinary
     break, which is what the quote had before. */
  word-break: auto-phrase;
  color: var(--color-text);
}

.voice-card__name {
  margin-top: 26px;
  text-align: center;
  font-size: var(--fs-body);
  letter-spacing: 0.08em;
  color: var(--color-text);
}

/* Closing block: a handful of short written comments under the video
   testimonials. Every length here is read off the comp at its 402px design
   width and then expressed against the card, so the pair keeps its
   proportions as the row narrows. */
.voice__quotes {
  display: flex;
  flex-direction: column;
  align-items: center;
  padding: 0 20px;
  margin-top: 31px;
}

.voice__quotes-icon { width: 183px; height: auto; }

.voice__quotes-lead {
  margin-top: 15px;
  text-align: center;
  font-size: var(--fs-body);
  font-weight: 500;
  letter-spacing: 0;
  color: var(--color-cyan-accent);
}

/* Two abreast at every width — the comp shows them as a pair, and they are
   short enough to stay readable even on a 320px screen. */
/* A slider on both breakpoints, sharing the 制作事例 / お客様の声 behaviour
   through the same data attributes. The window shows the same cards it did as
   a static row — two here, three from 900px — and further quotes scroll in
   rather than opening another row. */
.voice__quotes-slider {
  position: relative;
  width: 100%;
  max-width: 520px;
  margin-top: 35px;
}

.voice__quotes-list {
  width: 100%;
  display: flex;
  gap: 31px;
  align-items: stretch;
  overflow-x: auto;
  overscroll-behavior-x: contain;
  scroll-snap-type: x mandatory;
  -webkit-overflow-scrolling: touch;
  scrollbar-width: none;
}
.voice__quotes-list::-webkit-scrollbar { display: none; }

.voice__quotes-nav {
  position: absolute;
  top: 50%;
  transform: translateY(-50%);
  z-index: 2;
  width: 36px;
  height: 36px;
  padding: 0;
  border: 0;
  border-radius: 50%;
  background: #fff;
  color: var(--color-cyan-accent);
  display: flex;
  align-items: center;
  justify-content: center;
  box-shadow: 0 2px 10px rgba(0, 0, 0, 0.18);
  cursor: pointer;
  transition: opacity 0.2s ease;
}
.voice__quotes-nav svg { width: 18px; height: 18px; }
.voice__quotes-nav:hover { opacity: 0.85; }
.voice__quotes-nav:disabled { opacity: 0.35; pointer-events: none; }
.voice__quotes-nav--prev { left: -6px; }
.voice__quotes-nav--next { right: -6px; }
/* Nothing to scroll — three quotes exactly fill the desktop window — so the
   arrows go rather than sitting there greyed out. They come back on their own
   once there are more cards than the row can hold. */
.voice__quotes-slider.is-static .voice__quotes-nav { display: none; }

.quote-card {
  /* Two in the window, the gap taken out of the share. Fixed rather than
     flexible: in a scroll track a shrinkable card would squeeze the whole set
     into view instead of letting it run off the edge. */
  flex: 0 0 calc((100% - 31px) / 2);
  scroll-snap-align: start;
  container-type: inline-size;
  display: flex;
  flex-direction: column;
  align-items: center;
  background: #fff;
  border-radius: 22px;
  padding: 11px 12px 7px;
  text-align: center;
}

.quote-card__avatar { width: auto; height: 80px; }

.quote-card__tag {
  margin-top: 10px;
  font-size: var(--fs-note);
  font-weight: 500;
  line-height: 1.35;
  letter-spacing: 0;
}
.quote-card__tag span {
  display: inline-block;
  padding: 1px 14px;
  border-radius: 999px;
  background: var(--color-cyan-accent);
  color: #fff;
}

/* The comp sets these nine characters to the line. The cap holds that
   rhythm as the card narrows, and the floor stops the type going below
   readable size on the smallest phones. */
.quote-card__text {
  margin-top: 24px;
  font-size: clamp(13px, calc(100cqi / 9), 15px);
  line-height: 1.63;
  letter-spacing: 0;
  color: var(--color-text);
}

.quote-card__name {
  margin-top: auto;
  padding-top: 25px;
  font-size: var(--fs-note);
  line-height: 1.5;
  letter-spacing: 0.04em;
  color: var(--color-text);
}

/* ============ サービス料金（TOPページの抜粋） ============
   Measured off the comp at 2.0359× — its 794px width against the 390px
   design. The scale is confirmed by the section head, whose English name
   comes out 30.5px of ink against the 29.4px the existing --fs-section-en
   already draws, and by the card: 642 comp px is 315px, which fits the 350px
   the page's own padding leaves. At 1.79× the card would be 359px and would
   not. */
.home-price {
  padding: var(--space-section) 20px var(--space-section-end);
}

/* The comp sets the English name in the deep navy rather than the body
   colour — the same ink the 料金ページ's contact band uses. The head keeps the
   site's own spacing below it rather than the comp's 33px, so this section
   opens like every other one. */
.home-price .section-head__title { color: var(--color-contact-ink); }

.home-price__plans {
  display: flex;
  flex-direction: column;
  gap: 32px;
}

.home-price__plan {
  position: relative;
  width: 100%;
  max-width: 315px;
  margin-inline: auto;
}

.home-price__label {
  margin: 0 0 12px;
  font-size: 18px;
  font-weight: 700;
  line-height: 1.4;
  letter-spacing: 0.02em;
  text-align: center;
  color: var(--color-voice-cta);
}

/* The card clips its own corners so the magenta band rounds with it; the
   star badge is a sibling rather than a child for exactly that reason, since
   it has to hang off the top-left corner. */
.home-price__card {
  overflow: hidden;
  border: 1px solid var(--color-voice-cta);
  border-radius: 44px;
  background: #fff;
}

.home-price__amount {
  margin: 0;
  height: 79px;
  /* Grid rather than flex: baseline-aligned flex items sit at the top of the
     box, so the price hung high in the band. A single auto column keeps the
     three parts on one baseline while align-content centres the whole group
     in the 79px. */
  display: grid;
  grid-auto-flow: column;
  justify-content: center;
  align-content: center;
  align-items: baseline;
  gap: 2px;
  /* Never wraps: the row is one price, and letting it break put 円(税込) on
     a second line inside the band. */
  flex-wrap: nowrap;
  white-space: nowrap;
  padding: 0 12px;
  background: var(--color-voice-cta);
  color: #fff;
  line-height: 1;
}
.home-price__amount-pre { font-size: 15px; font-weight: 500; letter-spacing: 0.08em; }
.home-price__amount-num { font-family: var(--font-en); font-size: 40px; font-weight: 600; letter-spacing: 0; }
.home-price__amount-unit { font-size: 16px; font-weight: 500; letter-spacing: 0; }

/* The starred card sets its price clear of the badge instead of centring it,
   which is what the comp does too: there the badge ends 60.9px in from the
   card edge and the first digit starts at 62.4px. */
.home-price__plan:has(.home-price__burst) .home-price__amount {
  justify-content: end;
  padding-left: 60px;
  padding-right: 6px;
}

.home-price__body { padding: 28px 10px 24px; }

.home-price__heading {
  margin: 0;
  font-size: 17px;
  font-weight: 700;
  line-height: 1.6;
  letter-spacing: 0;
  text-align: center;
  color: var(--color-voice-cta);
}

/* 12.3px in the comp — the section packs a paragraph into a 315px card, so
   this is the one place on the site that goes below --fs-caption. */
.home-price__text {
  margin: 14px 0 0;
  font-size: 12px;
  font-weight: 400;
  line-height: 2.34;
  letter-spacing: 0;
  color: var(--color-text);
}

.home-price__burst {
  position: absolute;
  top: 18px;
  left: -22px;
  width: 84px;
  height: 84px;
  margin: 0;
  display: flex;
  align-items: center;
  justify-content: center;
  transform: rotate(-12deg);
}
.home-price__burst svg { position: absolute; inset: 0; width: 100%; height: 100%; }
.home-price__burst-text {
  position: relative;
  /* Sized to the star rather than to taste: the burst has an inner radius of
     34.5px, and 「サポート付き」 at 6 characters makes the wider of the two
     lines. At 10.5px the two-line block is 63x27.3px, whose corner sits
     34.3px from the centre — just inside the inner circle, so no glyph rides
     out over a spike. */
  font-size: 10.5px;
  font-weight: 700;
  line-height: 1.3;
  letter-spacing: 0;
  text-align: center;
  color: var(--color-voice-cta);
}

/* ＼詳しくはこちら／ — the two strokes are drawn rather than typed, so they
   keep their angle and weight instead of depending on the full-width
   backslash a given font happens to ship. */
.home-price__more-lead {
  margin: 25px 0 0;
  display: flex;
  align-items: center;
  justify-content: center;
  gap: 14px;
  font-size: 15px;
  font-weight: 500;
  letter-spacing: 0.04em;
  color: var(--color-cyan-accent);
}
.home-price__more-lead::before,
.home-price__more-lead::after {
  content: "";
  width: 2px;
  height: 20px;
  background: currentColor;
  border-radius: 1px;
}
.home-price__more-lead::before { transform: rotate(-22deg); }
.home-price__more-lead::after { transform: rotate(22deg); }

.home-price__more {
  margin: 9px auto 0;
  display: flex;
  align-items: center;
  justify-content: center;
  width: 253px;
  max-width: 100%;
  min-height: 72px;
  padding: 8px 16px;
  border-radius: 999px;
  background: var(--color-cyan-accent);
  color: #fff;
  font-size: 17px;
  font-weight: 700;
  letter-spacing: 0.02em;
  transition: opacity 0.2s ease, transform 0.2s ease;
}
.home-price__more:hover { opacity: 0.85; transform: translateY(-1px); }

/* ==================== 制作の流れ ====================
   Measured off the comp at 4.167× — its 1625px width against the 390px
   design. Confirmed by the head: the comp's "Flow" is 90.5 × 29.8px of ink,
   and --fs-section-en at 38px already draws 29.4px of it.
   The section's two colours are both already on the site: the rules, dots and
   step numbers are #50afcd, which is --color-cyan-accent as everywhere else,
   and the ink is #232583, 0.6 ΔE from --color-contact-ink. */
.flow {
  padding: var(--space-section) 20px var(--space-section-end);
}

/* "Flow" is what sits on the page's centre line; the 5STEP mark hangs off its
   left rather than being part of the centred group. */
.flow__lockup {
  position: relative;
  display: inline-block;
}

.flow__mark {
  position: absolute;
  right: calc(100% + 18px);
  top: -11px;
  width: 90px;
  height: 61px;
  color: var(--color-contact-ink);
}

/* Traced from the comp: two strokes that converge to the right but stop
   short of meeting, pointing into the word. Drawn rather than imaged — swap
   in the original artwork if there is one. */
.flow__chevron {
  position: absolute;
  left: 26px;
  top: 0;
  width: 64px;
  height: 61px;
}

.flow__mark-text {
  position: absolute;
  left: 0;
  bottom: 13px;
  display: flex;
  align-items: baseline;
  font-family: var(--font-en);
  font-size: 23px;
  font-weight: 600;
  line-height: 1;
  letter-spacing: 0.12em;
}
.flow__mark-num { font-size: 37px; letter-spacing: 0.02em; }

.flow__list {
  position: relative;
  margin: 0;
  padding: 0;
  list-style: none;
}

.flow__step {
  /* Where this step's dot sits. The gap between steps is padding rather than
     margin so the spine, which is drawn inside the step, runs through it. */
  --dot-top: 36px;
  position: relative;
  display: grid;
  grid-template-columns: 104px 1fr;
  padding: 0 0 12px 55px;
}
.flow__step + .flow__step { --dot-top: 82px; padding-top: 46px; }

/* The spine, a segment per step so it can stop at the last dot the way the
   comp does — there it ends with the fifth dot and leaves the final rule
   standing on its own. */
.flow__step::before {
  content: "";
  position: absolute;
  left: 15.3px;
  top: 0;
  bottom: 0;
  width: 3px;
  background: var(--color-cyan-accent);
}
.flow__step:first-child::before { top: calc(var(--dot-top) + 19px); }
.flow__step:last-child::before { bottom: auto; height: calc(var(--dot-top) + 38px); }

/* The dot overhangs the list's left edge the way the comp has it — 17.8px in
   from the page edge against the text's 20px. */
.flow__step-dot {
  position: absolute;
  z-index: 1;
  left: -2.2px;
  top: var(--dot-top);
  width: 38px;
  height: 38px;
  border-radius: 50%;
  background: var(--color-cyan-accent);
}

/* The rule starts where the STEP column does, not at the spine. */
.flow__step::after {
  content: "";
  position: absolute;
  left: 55px;
  right: 0;
  bottom: 0;
  height: 3px;
  background: var(--color-cyan-accent);
}

.flow__step-label {
  margin: 0;
  display: flex;
  flex-direction: column;
  align-items: flex-start;
  line-height: 1;
  color: var(--color-cyan-accent);
  font-family: var(--font-en);
  font-weight: 700;
}
.flow__step-word { font-size: 23px; letter-spacing: 0.12em; }
.flow__step-num { margin-top: 15px; font-size: 40px; letter-spacing: 0.02em; }

.flow__step-title {
  margin: 0;
  font-size: var(--fs-h3);
  font-weight: 700;
  line-height: 1;
  letter-spacing: 0.02em;
  color: var(--color-contact-ink);
}

.flow__step-text {
  margin: 16px 0 0;
  font-size: 12px;
  font-weight: 500;
  line-height: 2;
  letter-spacing: 0;
  color: var(--color-contact-ink);
}

/* The last step is the one the section is arguing for, so the comp switches
   its label, its dot and the rule behind its title to yellow. That yellow is
   #f8cf00, 2.4 ΔE from --color-plan-badge — the 料金ページ ribbon's — so it
   reuses that rather than adding a fourth. The spine above the dot stays
   cyan, as in the comp. */
.flow__step--final .flow__step-label { color: var(--color-plan-badge); }
.flow__step--final .flow__step-dot { background: var(--color-plan-badge); }

/* Drawn as a band behind the lettering rather than a full highlight: in the
   comp it covers the lower half of the ink and stops just under the baseline,
   10.4px tall against the title's 19.3px of ink. */
.flow__step-marker {
  background: linear-gradient(
    transparent 50%,
    var(--color-plan-badge) 50%,
    var(--color-plan-badge) 86%,
    transparent 86%
  );
}

/* ============ more design について ============
   Measured off the comp at 3.428× — its 1337px against the 390px design,
   confirmed by the cyan rule it happens to include at the top: 1023 comp px
   for the 297.3px rule 制作の流れ already draws.
   The ground is --color-cream: the comp reads #fcefdd against the token's
   #fdf0de. The ink is --color-contact-ink, as in the two sections above. */
.about {
  position: relative;
  /* Room for the wave, which is painted above the box rather than inside it
     so the cream below can stay a plain background. */
  margin-top: 63px;
  padding: 4px 16px 0;
  background: var(--color-cream);
  text-align: center;
}

/* The cream's top edge: one long wave, high at 117px across and low at 303px.
   Traced from the comp column by column and fitted with three curves, which
   sit within about 2px of the sampled edge. preserveAspectRatio is off so it
   stretches with the window rather than cropping. */
.about__wave {
  position: absolute;
  left: 0;
  right: 0;
  bottom: 100%;
  height: 63px;
  line-height: 0;
  pointer-events: none;
}
.about__wave svg { display: block; width: 100%; height: 100%; }

.about__head { margin-bottom: 0; padding: 0; }

/* Drawn rather than imaged — there is no bird in the assets. Swap in the
   original artwork if there is one. */
.about__bird {
  display: block;
  width: 32px;
  height: 28px;
  margin: 0 auto 9px;
}

.about .section-head__title { color: var(--color-contact-ink); }
.about .section-head__title { gap: 12px; }

/* 押すと拡大するので、画像そのものではなくボタンに包んである。
   余白と幅はボタン側が持ち、画像はその中いっぱいに置く。 */
.about__photo-button {
  display: block;
  width: 136px;
  margin: 26px auto 0;
  padding: 0;
  border: 0;
  background: none;
  cursor: zoom-in;
}

.about__photo {
  width: 136px;
  height: 136px;
  border-radius: 50%;
  object-fit: cover;
}

.about__role {
  margin: 34px 0 0;
  font-family: var(--font-en);
  font-size: 15px;
  font-weight: 500;
  line-height: 1;
  letter-spacing: 0.02em;
  color: var(--color-contact-ink);
}

.about__name {
  margin: 21px 0 0;
  font-family: var(--font-en);
  font-size: 27px;
  font-weight: 700;
  line-height: 1;
  letter-spacing: 0.02em;
  color: var(--color-contact-ink);
}

/* Held to the same 310px the よくあるご質問 cards above it run to, rather
   than the 358px the comp draws: at 358 the copy reached past the 305px rule
   under it and nearly touched the screen's edges. Each sentence starts a
   line; the wrapping inside one is the browser's. */
.about__bio {
  max-width: 310px;
  margin: 24px auto 0;
  font-size: 11.8px;
  font-weight: 500;
  line-height: 2.71;
  letter-spacing: 0;
  text-align: left;
  color: var(--color-contact-ink);
}

.about__hobby-title {
  margin: 20px 0 0;
  font-size: 14px;
  font-weight: 700;
  line-height: 1;
  letter-spacing: 0.02em;
  color: var(--color-contact-ink);
}
/* The rule above the heading, carried by it so the two stay together. */
.about__hobby-title::before {
  content: "";
  display: block;
  width: 305px;
  max-width: 100%;
  height: 1px;
  margin: 0 auto 20px;
  background: var(--color-contact-ink);
}

.about__hobby {
  max-width: 310px;
  margin: 20px auto 0;
  font-size: 12px;
  font-weight: 500;
  line-height: 2.51;
  letter-spacing: 0.03em;
  color: var(--color-contact-ink);
}

/* The cream's bottom edge, the mirror of the wave at the top, with the bird
   perched on it. The bird keeps its own size but is placed as a share of the
   width so it stays on the same part of the curve when the wave stretches. */
.about__foot {
  position: relative;
  margin: 11px -16px 0;
  height: 70px;
  line-height: 0;
  /* White behind it, because this one sits inside the section: without it the
     section's own cream shows through everything the wave leaves empty and
     the edge comes out as a straight line. The wave at the top escapes that
     by being painted above the box rather than in it. */
  background: #fff;
}
.about__foot svg { display: block; width: 100%; height: 100%; }
.about__bird-big {
  position: absolute;
  z-index: 1;
  left: 72.2%;
  top: 0;
  width: 77px;
  height: 47px;
}

/* ==================== よくあるご質問 ====================
   Measured off the comp at 2.404× — the About bird it carries at the top is
   186px across there against the 77.4px it is drawn at, and 47.4px tall
   against 114px, which agree to 0.1%.
   Both colours are already on the site: the Q and + discs read #50afcd,
   --color-cyan-accent as everywhere else, and the cards are --color-cream. */
.faq {
  padding: 14px 20px var(--space-section-end);
  text-align: center;
}

.faq__eyebrow {
  margin: 0;
  font-family: var(--font-en);
  font-size: 12px;
  font-weight: 500;
  line-height: 1;
  letter-spacing: 0.1em;
  color: var(--color-cyan-accent);
}

.faq__title {
  margin: 27px 0 0;
  font-size: 32px;
  font-weight: 700;
  line-height: 1;
  letter-spacing: 0;
  color: var(--color-contact-ink);
}

.faq__list {
  margin: 32px auto 0;
  max-width: 310px;
  display: flex;
  flex-direction: column;
  gap: 28px;
}

.faq__item {
  border-radius: 22px;
  background: var(--color-cream);
}

/* The row is the summary itself, so the whole card is the hit area. */
.faq__q {
  display: flex;
  align-items: center;
  gap: 11px;
  min-height: 97px;
  padding: 12px 11px 12px 15px;
  cursor: pointer;
  list-style: none;
  text-align: left;
}
.faq__q::-webkit-details-marker { display: none; }

.faq__q-mark {
  flex: none;
  width: 33px;
  height: 33px;
  display: flex;
  align-items: center;
  justify-content: center;
  border-radius: 50%;
  background: var(--color-cyan-accent);
  color: #fff;
  font-family: var(--font-en);
  font-size: 17px;
  font-weight: 600;
  line-height: 1;
}

.faq__q-text {
  flex: 1 1 auto;
  font-size: 12px;
  font-weight: 700;
  line-height: 2;
  letter-spacing: 0;
  color: var(--color-contact-ink);
}

/* One bar turns with the disc, so + becomes − when the card opens. */
.faq__toggle {
  position: relative;
  flex: none;
  width: 23px;
  height: 23px;
  border-radius: 50%;
  background: var(--color-cyan-accent);
}
.faq__toggle::before,
.faq__toggle::after {
  content: "";
  position: absolute;
  top: 50%;
  left: 6px;
  right: 6px;
  height: 2px;
  border-radius: 1px;
  background: #fff;
  transform: translateY(-50%);
}
.faq__toggle::after {
  transform: translateY(-50%) rotate(90deg);
  transition: transform 0.2s ease;
}
.faq__item[open] .faq__toggle::after { transform: translateY(-50%) rotate(0deg); }

/* The answer repeats the question's layout with an A disc in its place. The
   comp's disc reads #717171, which is --color-gray-600 to within half a ΔE,
   so it reuses that rather than adding a grey. */
.faq__a {
  display: flex;
  align-items: flex-start;
  gap: 11px;
  padding: 0 15px 20px;
  text-align: left;
}

.faq__a-mark {
  flex: none;
  width: 33px;
  height: 33px;
  display: flex;
  align-items: center;
  justify-content: center;
  border-radius: 50%;
  background: var(--color-gray-600);
  color: #fff;
  font-family: var(--font-en);
  font-size: 17px;
  font-weight: 600;
  line-height: 1;
}

.faq__a-body { flex: 1 1 auto; }

/* Lead and body run as one block at the comp's 24px line pitch, so the bold
   opening line and the explanation below it stay on the same rhythm. */
.faq__a-lead,
.faq__a-text {
  margin: 0;
  font-size: 12px;
  line-height: 2;
  letter-spacing: 0;
  color: var(--color-contact-ink);
}
.faq__a-lead { font-weight: 700; }
.faq__a-text { font-weight: 500; }

/* ==================== お問い合わせ（TOPページ） ====================
   Measured off the comp at 2.826× — the よくあるご質問 card it carries at the
   top is 876px there against the 310px it is drawn at. The supplied bird
   confirms it: 63.0 × 37.9 in the comp against the artwork's 62.35 × 37.86.
   Unlike the 料金ページ's band this one sits on the page's own white, with
   the two blocks separated by rules rather than by ground. */
.contact-home {
  padding: var(--space-section) 20px var(--space-section-end);
  text-align: center;
  color: var(--color-contact-ink);
}

.contact-home__bird {
  display: block;
  width: 63px;
  height: 38px;
  margin: 0 auto;
}

.contact-home__title {
  margin: 4px 0 0;
  font-family: var(--font-en);
  font-size: 42px;
  font-weight: 600;
  line-height: 1;
  letter-spacing: 0.02em;
}

.contact-home__ja {
  margin: 5px 0 0;
  font-size: 12px;
  font-weight: 500;
  line-height: 1;
  letter-spacing: 0.06em;
}

.contact-home__lead {
  margin: 27px 0 0;
  font-size: 17px;
  font-weight: 500;
  line-height: 1.5;
  letter-spacing: 0.01em;
}

/* 問い合わせの2択。Two stadium buttons, each stating its channel in the
   large type and repeating the action on a white pill inside it, so the
   button says both what it is and what tapping it does. */
.contact-choice {
  display: flex;
  flex-direction: column;
  align-items: center;
  width: 322px;
  max-width: 100%;
  min-height: 149px;
  margin: 28px auto 0;
  padding: 14px 16px 15px;
  border-radius: 999px;
  color: #fff;
  text-align: center;
  transition: opacity 0.2s ease, transform 0.2s ease;
}
.contact-choice:hover { opacity: 0.88; transform: translateY(-1px); }

.contact-choice--line { background: var(--color-line-green); }
.contact-choice--mail { margin-top: 38px; background: var(--color-cyan-accent); }

.contact-choice__name {
  font-size: 40px;
  font-weight: 700;
  line-height: 1;
  letter-spacing: 0;
}
.contact-choice__sub {
  margin-top: 8px;
  font-size: 16px;
  font-weight: 500;
  line-height: 1;
  letter-spacing: 0.04em;
}

/* The pill's contents sit against a fixed left inset rather than centred:
   the two labels differ by a character, and centring each one would leave
   the two badges on different verticals down the pair. The badge sits only
   6px in — it is a circle, so it carries its own optical margin. */
.contact-choice__pill {
  margin-top: 11px;
  display: flex;
  align-items: center;
  gap: 11px;
  width: 255px;
  max-width: 100%;
  min-height: 45px;
  padding: 4px 10px 4px 6px;
  border-radius: 999px;
  background: #fff;
  font-size: 19px;
  font-weight: 700;
  line-height: 1.3;
  letter-spacing: 0.01em;
}
.contact-choice--line .contact-choice__pill { color: var(--color-line-green); }
/* One character longer than the LINE label, and the comp holds both text
   blocks to the same 172px measure rather than the same size, so this one is
   set a touch smaller. */
.contact-choice--mail .contact-choice__pill { color: var(--color-cyan-accent); font-size: 17.3px; }

.contact-choice__icon { flex: none; width: 35px; height: 35px; }

/* 電話。Icon beside the three-line block, centred on it, the same
   arrangement the 料金ページ band uses. */
.contact-home__tel {
  max-width: 313px;
  margin: 44px auto 0;
  /* Ruled top and bottom: the phone number is the one channel that is not a
     button, so the rules are what hold it together as its own block. */
  padding: 35px 0 31px;
  border-top: 1px solid var(--color-contact-ink);
  border-bottom: 1px solid var(--color-contact-ink);
  display: flex;
  align-items: center;
  justify-content: center;
  gap: 14px;
  text-align: left;
}

.contact-home__icon { flex: none; width: 47px; height: 47px; }

.contact-home__label {
  margin: 0;
  font-size: 20px;
  font-weight: 500;
  line-height: 1.4;
  letter-spacing: 0.01em;
}

.contact-home__number {
  margin: 2px 0 0;
  font-family: var(--font-en);
  font-size: 34px;
  font-weight: 400;
  line-height: 1.2;
  letter-spacing: -0.04em;
}
.contact-home__number a { color: inherit; text-decoration: none; }

.contact-home__hours {
  margin: 15px 0 0;
  font-size: 16.5px;
  font-weight: 400;
  line-height: 1.4;
  letter-spacing: 0.01em;
}

/* ===================== Footer ===================== */
/* Phones do not get a footer: the hamburger menu already carries the same
   sitemap, FOLLOW US block and copyright, so repeating it at the end of the
   page would be the same panel twice. It comes back from 900px up, where
   the menu is a single row of links in the bar. */
.footer {
  display: none;
  background: var(--color-footer-bg);
  padding: 64px 20px 40px;
  text-align: center;
}
/* Caps the footer content — and with it the rule above FOLLOW US — so the
   line does not stretch the full window on wide screens. */
.footer > * { max-width: 640px; margin-left: auto; margin-right: auto; }

.footer__nav-list {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 36px;
}
/* The seven service pages, listed under 提供サービス the way the header's
   submenu carries them. The footer only exists from 900px up, so the row it
   forms is described with the rest of the desktop footer. */
.footer__subnav-list { display: none; }

.footer__nav-list a,
.footer__subnav-list a {
  display: inline-block;
  padding: 4px 8px;
  font-size: var(--fs-nav);
  font-weight: 500;
  letter-spacing: 0.08em;
  color: var(--color-footer-ink);
}
.footer__nav-list a:hover,
.footer__subnav-list a:hover { opacity: 0.7; }

/* The rule above the FOLLOW US block, drawn as a border on the block
   itself so it always spans the same width as the content. */
.footer__social,
.header__nav-social {
  margin-top: 44px;
  padding-top: 44px;
  border-top: 1px solid var(--color-footer-ink);
}

.footer__social-title,
.header__nav-social-title {
  font-family: var(--font-en);
  font-size: var(--fs-h3);
  font-weight: 500;
  letter-spacing: 0.08em;
  color: var(--color-gray-800);
}

.footer__social-list,
.header__nav-social-list {
  margin-top: 24px;
  display: flex;
  justify-content: center;
  gap: 24px;
}
.footer__social-list img,
.header__nav-social-list img { width: 48px; height: 48px; }
.footer__social-list a,
.header__nav-social-list a { display: inline-block; transition: opacity 0.2s ease; }
.footer__social-list a:hover,
.header__nav-social-list a:hover { opacity: 0.75; }

.footer__copy,
.header__nav-copy {
  margin-top: 40px;
  font-family: var(--font-en);
  font-size: var(--fs-caption);
  color: #888;
  letter-spacing: 0.05em;
}

/* ===================== Price (下層ページ) ===================== */
/* The page opens on a navy band whose lower edge domes upward, with the two
   figures straddling that curve. The two came as separate layers of one
   390x390 artboard, but the comp does not stack them at their artboard
   positions — it sets the figures lower and slightly right, so they hang a
   quarter of the band's height past its edge onto the white. These three
   numbers are solved from the comp against the artwork itself: two anchors
   (the top of the skin, the foot of the drawing) give a scale of 3.87 against
   its own units, and that scale then predicts the right-hand edge to within
   a pixel. */
.price-hero { position: relative; }

.price-hero__band { width: 100%; height: auto; }

.price-hero__figure {
  position: absolute;
  left: 32.82%;   /* of the page */
  top: 65.45%;    /* of the band's height */
  width: 38.19%;  /* of the page */
  height: auto;
}

/* No bottom padding: what follows this section sets its own distance, and the
   closing CTA already carries an even band of its own. */
.price-intro {
  padding: var(--space-section) 20px 0;
}

/* The comp leaves 41px under the ink of サービス料金 rather than the 28px the
   shared head carries, and 3px of that is the label's own descent space. */
.price-intro .section-head { margin-bottom: 21px; }

/* The comp sets the three sentences as one block with no extra space between
   them — the line pitch is the same right through — so each keeps its own
   paragraph for reading order without opening a gap. */
.price-intro__body {
  max-width: var(--container-price);
  margin: 0 auto;
  text-align: left;
  font-size: var(--fs-body);
  font-weight: 500;
  line-height: 2;
  color: var(--color-text);
  /* The comp breaks these lines at phrase boundaries — 「お問い合わせにて」
     then 「ご確認…」, never mid-word — so the copy wraps the same way here. */
  word-break: auto-phrase;
}

.price-intro__body p { margin: 0; }

/* The service list. Every bar carries the same tag motif twice: rounded at two
   opposite corners and cut square at the other two, once on the bar itself and
   once on the white badge inside it. The comp's numbers, read off a 390px
   page: the bar is 62px tall, the badge a 48px square inset 7px from the left
   edge and centred in that height, and the label starts at a fixed 93px from
   the bar's left rather than centring on it — which is why 動画編集 sits well
   left of centre. */
.price-menu {
  max-width: var(--container-price);
  margin: 52px auto 0;
  display: flex;
  flex-direction: column;
  gap: 9px;
}

.price-row {
  display: flex;
  align-items: center;
  min-height: 62px;
  padding-right: 16px;
  /* The comp draws these bars in #50afcd, 4.6 ΔE from the cyan the rest of the
     site already uses — near enough to read as the same colour and too near to
     stand beside it as a second one, so the accent covers both. The icons in
     the badges were recoloured to match. */
  background: var(--color-cyan-accent);
  /* 28px at the top-left and 21px at the bottom-right, both measured off the
     comp's arcs; the other two corners are square. */
  border-radius: 28px 0 21px 0;
  color: #fff;
  transition: opacity 0.2s ease;
}

.price-row:hover { opacity: 0.85; }
.price-row:focus-visible { outline: 3px solid var(--color-text); outline-offset: 2px; }

.price-row__badge {
  flex: none;
  width: 48px;
  height: 48px;
  margin-left: 7px;
  display: flex;
  align-items: center;
  justify-content: center;
  background: #fff;
  /* The same shape as the bar, squared off at the corner nearest it. */
  border-radius: 24px 24px 24px 0;
}

.price-row__badge img { width: 25px; height: 25px; }

/* The 38px is the comp's gap from the badge to the label, and it is set here
   rather than as the row's `gap` so it does not also open between the label
   and the chevron — that second gap left the two longest labels too little
   room and broke them over two lines. */
.price-row__label {
  flex: 1 1 auto;
  margin-left: 38px;
  font-size: var(--fs-price-row);
  font-weight: 700;
  letter-spacing: 0.05em;
  line-height: 1.4;
}

.price-row__chevron {
  flex: none;
  width: 19px;
  height: 23px;
  color: #fff;
}

/* Each service's plans open with a short rule, the service name in cyan and a
   one-line lead. All three are centred, and all three measurements come off
   the comp at a 390px page: a 187x2 rule, 67px under the list, then 22px to
   the name's ink and 38px from there to the lead's. */
.price-plan {
  max-width: var(--container-price);
  margin: 67px auto 0;
  padding: 0 20px;
  text-align: center;
}

.price-plan::before {
  content: "";
  display: block;
  width: 187px;
  height: 2px;
  margin: 0 auto;
  background: var(--color-cyan-accent);
}

.price-plan__title {
  margin-top: 17px;
  font-size: var(--fs-h3);
  font-weight: 700;
  letter-spacing: 0.04em;
  line-height: 1.4;
  color: var(--color-cyan-accent);
}

/* The comp runs this line nearly to both edges — 20 characters across 355px,
   which is 17.8px each and leaves only 17px of page margin. Set solid at 17px
   it comes to 340px, so it still reads as a full-width line while keeping the
   20px side padding every other section uses. Anything larger wraps, and a
   second line of four characters is worse than 4% less width. */
/* サービス単位のカードだけを載せる節。見出しも罫線もカードが持つ。 */
.price-plan--bare { margin-top: 56px; }
.price-plan--bare::before { display: none; }
.price-plan--bare .plan-cards { margin-top: 0; }

.price-plan__lead {
  margin-top: 25px;
  font-size: 17px;
  font-weight: 500;
  letter-spacing: 0;
  line-height: 1.8;
  color: var(--color-text);
}

/* ---- プランカード ---- */
/* Every measurement below is read off the card comp and expressed against a
   350px card, which is the page's content width. */
.plan-cards {
  margin-top: 40px;
  display: flex;
  flex-direction: column;
  gap: 32px;
}

.plan-card {
  position: relative;
  /* Each plan carries its own accent; the cards differ only in this one value. */
  --plan-accent: var(--color-cyan-accent);
  display: flex;
  flex-direction: column;
  padding: 25px 8px 36px;
  background: #fff;
  border-radius: 42px;
  /* The same 36px blur as the cards on the top page, carrying about two and a
     half times the ink — fitted to the comp's falloff, rmse 0.007 alpha. */
  box-shadow: 0 0 36px rgba(0, 0, 0, 0.3);
  text-align: center;
}

/* お試しプラン is drawn in a teal that lands 3.7 ΔE from the ground the 当店の強み
   section already sits on — the same colour to the eye, so it reuses it rather
   than adding a near-duplicate. */
.plan-card--teal { --plan-accent: var(--color-point-bg); }
.plan-card--blue { --plan-accent: var(--color-plan-blue); }
.plan-card--royal { --plan-accent: var(--color-plan-royal); }

/* The creatures are drawn at three different sizes and the comp places each of
   them 1:1, hanging them from a common baseline 56px down the card rather than
   from a common top. So the block is as tall as the largest — the rooster at
   46px — and the shorter ones are pushed down to meet that line. The header
   below closes up to make room: the comp takes about 10px out of each of the
   two gaps under the icon, so the card grows only by the icon's own height. */
.plan-card__icon {
  display: block;
  width: auto;
  height: 46px;
  margin: 0 auto 7px;
}

.plan-card__icon--sm { height: 37px; margin-top: 9px; }

/* The おすすめ flag hangs off the card's top-left corner. Its artwork is a
   square with three corners rounded and the fourth left sharp, and the comp
   places it at its drawn size. */
.plan-card__ribbon {
  position: absolute;
  z-index: 1;
  top: -21px;
  left: -11px;
  width: 84px;
  height: 84px;
  display: flex;
  align-items: center;
  justify-content: center;
  background: url(../assets/img/icons/price-ribbon.svg) center / contain no-repeat;
  color: #fff;
  font-size: 18px;
  font-weight: 700;
  letter-spacing: 0.02em;
  line-height: 1;
}

.plan-card:has(.plan-card__icon) { padding-top: 10px; }
.plan-card:has(.plan-card__icon) .plan-card__title { margin-top: 11px; }
.plan-card:has(.plan-card__icon) .plan-card__title::after { margin-top: 7px; }

/* The cards that stand for a whole service rather than a plan within one carry
   no icon and no eyebrow — just the service's name. The comp sets that name
   smaller than a plan name (23px against 25px) and closes the gaps below it. */
.plan-card--simple { padding-top: 50px; }
.plan-card--simple .plan-card__title { margin-top: 0; font-size: 23px; }
.plan-card--simple .plan-card__desc { margin-top: 18px; text-align: center; }
.plan-card--simple .plan-card__price { padding-top: 20px; }
.plan-card--simple .plan-card__button { margin-top: 12px; }

/* A short bar sitting on the card's top edge, the same width as the rule
   under the plan name. */
.plan-card::before {
  content: "";
  position: absolute;
  top: 0;
  left: 50%;
  transform: translateX(-50%);
  width: 188px;
  height: 5px;
  border-radius: 0 0 3px 3px;
  background: var(--plan-accent);
}

.plan-card__eyebrow {
  font-size: 18px;
  font-weight: 500;
  line-height: 1.5;
  /* Solid: プレミアムプラン's eyebrow is 19 characters and any tracking at all
     tips it past the card's 334px measure onto a second line. */
  letter-spacing: 0;
  color: var(--plan-accent);
}

.plan-card__title {
  margin-top: 21px;
  font-size: 25px;
  font-weight: 700;
  line-height: 1.4;
  letter-spacing: 0.02em;
  color: var(--plan-accent);
}

.plan-card__title::after {
  content: "";
  display: block;
  width: 188px;
  height: 2px;
  margin: 20px auto 0;
  background: var(--plan-accent);
}

.plan-card__desc {
  margin-top: 40px;
  font-size: 14.5px;
  font-weight: 400;
  line-height: 1.66;
  letter-spacing: 0;
  color: var(--color-text);
  text-align: left;
}

/* Where something sits between the band and the summary — 制作期間 — the
   band's edge no longer divides them, so the summary takes a rule of its own
   and the comp closes it up underneath. */
.plan-detail__summary--ruled {
  margin-inline: -13px;
  padding: 15px 13px 8.5px;
  border-top: 1px solid var(--color-cyan-accent);
}

/* お試しプラン centres its copy where 開業支援プラン ranges it left. */
.plan-card__desc--center { text-align: center; }

.plan-card__price {
  /* auto so a card stretched to match its neighbours puts the slack here,
     the way the comp does; the padding keeps the minimum gap. */
  margin-top: auto;
  padding-top: 28px;
  display: flex;
  align-items: baseline;
  justify-content: center;
  color: var(--color-text);
}

/* 金額のすぐ下に付く補足。プレミアムプランの「2 ヶ月目以降は月額〜」で
   使っている。金額は margin-top:auto で下に寄るので、この行はその
   直後に続く。 */
.plan-card__price-note {
  margin-top: 6px;
  font-size: 12px;
  font-weight: 500;
  letter-spacing: 0;
  line-height: 1.5;
  text-align: center;
  opacity: 0.72;
}

/* 金額の前に置く「月額」。TOP の home-price__amount-pre と同じ組みで、
   単位（15px）に揃えて数字より一段小さくしている。字間の 0.08em が
   そのまま数字との間のアキになる。 */
.plan-card__pre {
  font-size: 15px;
  font-weight: 500;
  letter-spacing: 0.08em;
}

.plan-card__amount {
  font-family: var(--font-en);
  font-size: 44px;
  font-weight: 700;
  line-height: 1.2;
  letter-spacing: 0;
}

.plan-card__unit {
  font-size: 15px;
  font-weight: 500;
  letter-spacing: 0;
}

.plan-card__button {
  margin-top: 17px;
  display: flex;
  align-items: center;
  justify-content: center;
  width: 275px;
  max-width: 100%;
  min-height: 61px;
  margin-inline: auto;
  padding: 8px 16px;
  border-radius: 999px;
  background: var(--plan-accent);
  color: #fff;
  font-size: 18px;
  font-weight: 700;
  letter-spacing: 0.02em;
  transition: opacity 0.2s ease;
}

.plan-card__button:hover { opacity: 0.85; }

/* ---- プラン詳細ページ ---------------------------------------------------
   料金ページのプランカードから開く1プラン1ページの詳細。Measured off the
   comp at 1.523× — its 187px rule against ours and its 350px card against the
   page's content width agree to within 0.8%, and every size below is that
   comp divided by it. The page shares the 料金ページ's card chrome (42px
   radius, the same soft shadow, the accent bar on the top edge) but sets its
   own type: the service name runs larger than the 料金ページ's section head
   (22px against 20px) and the line under it smaller (14px against 17px),
   because here it is the page's own title rather than one heading in a list.
   The comp's cyan reads #50afcd — the same 4.6 ΔE call already made for the
   問い合わせ帯 and the service-row icons, so it reuses --color-cyan-accent. */
.plan-page {
  max-width: var(--container-price);
  margin: 67px auto 0;
  padding: 0 20px;
  text-align: center;
}

/* The closing space belongs to the last plan on the page, not to every one of
   them: between two plans the gap is the next block's own top margin, and
   without this the last card's shadow ran straight into the footer. */
.plan-page:last-child { padding-bottom: var(--space-section-end); }

.plan-page::before {
  content: "";
  display: block;
  width: 187px;
  height: 2px;
  margin: 0 auto;
  background: var(--color-cyan-accent);
}

.plan-page__title {
  margin-top: 22px;
  font-size: 22px;
  font-weight: 700;
  letter-spacing: 0.04em;
  line-height: 1.4;
  color: var(--color-cyan-accent);
}

/* A second plan on the same page opens with its heading alone — no rule, no
   line under it. The comp stacks that heading on two lines and leaves it more
   leading than the page's own title, which sets on one. */
.plan-page--plain { margin-top: 72px; }
.plan-page--plain::before { display: none; }
.plan-page--plain .plan-page__title { margin-top: 0; }
.plan-page__title--stack { line-height: 1.73; }
/* Plans stacked straight under the page's own heading, with no row wrapper
   between them — the same 48px the wrapped rows use. Scoped to direct
   children so it never reaches the cards inside a row, which take their
   spacing from that row's gap. The second rule is for a plan that follows a
   row rather than another card, which is how WEBサイト制作 sets LP 制作 apart
   from the three site plans. */
.plan-page > .plan-detail + .plan-detail,
.plan-detail-row + .plan-detail { margin-top: 48px; }

/* Plans that share a heading. On a phone they stack; the comp sets the two
   gaps it shows at 54 and 43px, so the pair takes the middle. */
.plan-detail-row {
  margin-top: 33px;
  display: flex;
  flex-direction: column;
  gap: 48px;
}

/* The card's own top margin is for the one that follows the page's lead; in
   the row the gap does that job, and a margin here would add to it. */
/* margin-inline: auto stops a flex item stretching across the cross axis, so
   while the row is a column each card would shrink to its own content width
   and the stack would come out ragged. Give them the row's width instead; the
   card keeps its own max-width, and at >=1160px flex-basis takes over. */
.plan-detail-row .plan-detail { margin-top: 0; width: 100%; }

/* The comp breaks this after できる rather than letting it run to the card's
   full width, so the break is set rather than left to the measure. */
.plan-page__lead {
  margin-top: 36px;
  font-size: 14px;
  font-weight: 500;
  letter-spacing: 0;
  line-height: 24.3px;
  color: var(--color-text);
}

/* 名刺デザイン's lead is a paragraph rather than a two-line strapline, and
   the comp ranges it left across the page's full measure. */
.plan-page__lead--left { text-align: left; }

.plan-detail {
  position: relative;
  margin-top: 35px;
  /* 13px rather than the comp's 11: the summary has to break after WordPress
     and again after スタートプ the way the comp does, and Noto Sans JP runs
     about 1.5% wider than the face the comp is set in, so at 11px the first
     line takes one character more than it should. */
  /* No bottom padding of its own: the last block inside carries it, so the
     rule above the service list runs to the card's edges the way the one
     above 契約期間 does. */
  padding: 24px 13px 0;
  background: #fff;
  border-radius: 42px;
  box-shadow: 0 0 36px rgba(0, 0, 0, 0.3);
  text-align: left;
}

/* The same short bar on the card's top edge as the 料金ページ's plan cards. */
.plan-detail::before {
  content: "";
  position: absolute;
  top: 0;
  left: 50%;
  transform: translateX(-50%);
  width: 186px;
  height: 6px;
  border-radius: 0 0 3px 3px;
  background: var(--color-cyan-accent);
}

/* Pulled 9px wider than the card's own measure on both sides. The longest
   eyebrow — 新商品・サービスを LP で集客したい方へ — sets 336px and the comp
   keeps it on one line; at the card's 324 it broke with a single character on
   the second. The block is centred, so the extra width changes nothing for
   the shorter ones, and 42px corners leave the line clear of the edge. */
.plan-detail__head {
  margin-inline: -9px;
  padding-bottom: 23px;
  text-align: center;
}

.plan-detail__eyebrow {
  font-size: 18px;
  font-weight: 500;
  letter-spacing: 0;
  line-height: 1.5;
  color: var(--color-cyan-accent);
}

/* A plan whose name is the service itself carries no line above it. The comp
   does not simply drop the lead and close up: it sets the name lower in the
   card and leaves more under it, so the head keeps the depth it has on the
   cards that do have one. */
.plan-detail__head--name-only { padding-bottom: 35px; }
.plan-detail__head--name-only .plan-detail__name { margin-top: 29.5px; }

/* 名刺デザイン sets its line above the name at 14.5px where every other card
   sets it at 18 — small enough that it reads as a qualifier on the name
   rather than as a line of its own. */
.plan-detail__eyebrow--sm { font-size: 14.5px; }

.plan-detail__name {
  margin-top: 20px;
  font-size: 25px;
  font-weight: 700;
  letter-spacing: 0.02em;
  line-height: 1.4;
  color: var(--color-cyan-accent);
}

/* ---- 料金ブロック ----
   A full-bleed pale band inside the card, so it runs to the rounded edge on
   both sides. The comp leaves almost nothing under the last line of the
   caution — 4.6px, which is the line box's own half-leading — so the band
   carries no bottom padding of its own. */
.plan-detail__price {
  margin: 0 -13px;
  padding: 22px 13px 0;
  background: var(--color-plan-band);
  text-align: center;
}

/* A plan with a single figure carries no badges, so the band's own top
   padding stands in for the row that would have been there. The comps hold
   the band at the same depth whether its caution runs to one line or two —
   with one line the space falls under it — so the floor is set here rather
   than left to the copy. */
.plan-detail__price--single { padding-top: 26.5px; min-height: 138px; }
.plan-detail__price--single .plan-detail__total { margin-top: 0; }

.plan-detail__badges {
  display: flex;
  justify-content: center;
  align-items: stretch;
  gap: 22px;
}

.plan-detail__badge {
  flex: 0 0 136px;
  min-height: 101px;
  padding: 10px 6px 8px;
  border-radius: 28px;
  background: var(--color-cyan-accent);
  color: #fff;
  text-align: center;
}

.plan-detail__badge-label {
  font-size: 13px;
  font-weight: 500;
  letter-spacing: 0;
  line-height: 1.5;
}

/* Set in the page font rather than --font-en: the comp's figures measure as
   Noto Sans JP's own — Inter's are 8% narrower here — and the large total
   below reads the same way. */
.plan-detail__badge-amount {
  margin-top: 9px;
  font-size: 26px;
  font-weight: 700;
  letter-spacing: 0;
  line-height: 1.2;
}

.plan-detail__badge-note {
  margin-top: 4px;
  font-size: 13px;
  font-weight: 500;
  letter-spacing: 0;
  line-height: 1.5;
}

.plan-detail__total {
  margin-top: 23px;
  display: flex;
  align-items: baseline;
  justify-content: center;
  color: var(--color-cyan-accent);
}

/* .plan-card__pre と同じ役割。詳細ページ側の金額に付く「月額」。 */
.plan-detail__total-pre {
  font-size: 15px;
  font-weight: 500;
  letter-spacing: 0.08em;
}

.plan-detail__total-num {
  font-size: 44px;
  font-weight: 700;
  letter-spacing: 0;
  line-height: 1.2;
}

.plan-detail__total-unit {
  font-size: 15px;
  font-weight: 500;
  letter-spacing: 0;
}

/* The one line that does not follow the rest of the card up a full step: at
   13px its two lines run to 324px, which is the card's whole measure, and it
   would sit on the band's edges. */
/* Pulled 5px wider than the band's measure on both sides. ロゴデザイン's
   caution breaks after 26 characters, which comes to 325px — one past the
   324 the band's own padding leaves — and the last character dropped onto a
   line of its own. The line is centred, so the extra width shows nowhere
   else. */
.plan-detail__caution {
  margin: 16px -5px 0;
  font-size: 12.5px;
  font-weight: 400;
  letter-spacing: 0;
  line-height: 21px;
  color: var(--color-cyan-accent);
}

/* Ranged left where the others centre, which means its longest line has to
   fit rather than just sit inside a centred column. It goes back to the 12px
   the comps actually set — the half point the centred ones carry is there to
   keep them off the band's edges — and takes 10px out of the band's padding,
   which puts the ※ where the comp puts it and leaves 7px of slack. */
.plan-detail__caution--left {
  margin-inline: -10px;
  padding-left: 15px;
  font-size: 12px;
  text-align: left;
}

/* ---- 制作期間 ----
   Only the WEBサイト制作 plans carry this: a calendar, the words, and the
   span of time, all in the accent. Measured off that page's comp at 1.7410×
   (679px wide against a 390px page). */
.plan-detail__period {
  padding: 25px 0 26px;
  text-align: center;
  color: var(--color-cyan-accent);
}

.plan-detail__period-icon {
  display: block;
  width: 59px;
  height: 65px;
  margin: 0 auto;
}

.plan-detail__period-label {
  margin: 22px 0 0;
  font-size: 21px;
  font-weight: 700;
  letter-spacing: 0;
  line-height: 1.4;
}

.plan-detail__period-value {
  margin: 6px 0 0;
  font-size: 26px;
  font-weight: 700;
  letter-spacing: 0;
  line-height: 1.4;
}

/* ---- 説明文と仕様 ---- */
.plan-detail__summary {
  padding: 13.5px 0 17px;
  font-size: 14.5px;
  font-weight: 400;
  letter-spacing: 0;
  line-height: 27.6px;
  color: var(--color-text);
}

/* Each block below the summary is separated by a hairline that runs the
   card's full width, so the rules read as the card's own divisions rather
   than as underlines under the copy. */
.plan-detail__term,
.plan-detail__services {
  margin: 0 -13px;
  padding: 10.5px 13px 18px;
  border-top: 1px solid var(--color-cyan-accent);
}

.plan-detail__term-title,
.plan-detail__services-title {
  font-size: 15px;
  font-weight: 500;
  letter-spacing: 0;
  line-height: 1.5;
  color: var(--color-cyan-accent);
}

.plan-detail__term-body {
  margin: 10px 0 0;
  font-size: 15px;
  font-weight: 500;
  letter-spacing: 0;
  line-height: 1.5;
  color: var(--color-text);
}

.plan-detail__services { padding-top: 11px; padding-bottom: 16px; }

/* Straight after the band there is no rule to draw: the band's own edge
   already divides them. ロゴデザイン's card is built this way — no summary,
   no 制作期間, the list following the figures directly. */
.plan-detail__price + .plan-detail__services { border-top: 0; }

/* The comp sets this list a step smaller than the card's copy — it is the
   longest block on the page — but still within reach of it, so it follows the
   rest of the card up and the notes wrap where they no longer fit. */
.plan-detail__service-list {
  margin-top: 11px;
  font-size: 13px;
  font-weight: 400;
  letter-spacing: 0;
  line-height: 29px;
  color: var(--color-text);
}

.plan-detail__service-list > li {
  position: relative;
  padding-left: 13px;
}

/* A hairline ring rather than the ○ character: the comp's mark is lighter
   than a solid 1px rule of the accent would be, so the stroke carries the
   accent at the weight the comp draws it. It stays this colour on the
   highlighted item, which is where the comp keeps it too. */
.plan-detail__service-list > li::before {
  content: "";
  position: absolute;
  left: 0;
  top: 9.5px;
  width: 11.5px;
  height: 11.5px;
  border: 1px solid rgba(49, 173, 203, 0.45);
  border-radius: 50%;
}

/* A closing line under the list. The comp keeps it on the list's own rhythm
   and ranges it with the rings rather than with the item text, so it reads as
   a remark on the whole list. */
.plan-detail__services-outro {
  margin: 0;
  font-size: 13px;
  font-weight: 400;
  letter-spacing: 0;
  line-height: 29px;
  color: var(--color-text);
}

/* The note under an item aligns with the item's own text, not with the ring,
   so a service and its detail read as one block. */
.plan-detail__service-note {
  display: block;
  color: var(--color-text);
}

/* ---- 料金プラン比較表 -------------------------------------------------
   The same card as the plans above it — 42px corners, the same shadow — with
   the table running edge to edge inside it, which is why the card clips its
   own overflow. Measured off the comp at 3.4282× (its 1193px card against our
   350px one). Every size in it is small because 350px has to hold four
   columns. The comp sets the whole table at 11.5px; 12 is as far as it will
   go, and only with a fiftieth of an em out of the tracking — at that size
   the longest label, SEO・コンテンツ改善, takes 116 of the label column's 122
   and スタンダード takes 71 of its column's 75. */
.compare {
  margin-top: 33px;
  padding-bottom: 19px;
  background: #fff;
  border-radius: 42px;
  box-shadow: 0 0 36px rgba(0, 0, 0, 0.3);
  /* So the header band's own corners come from the card's. */
  overflow: hidden;
}

.compare__table {
  width: 100%;
  table-layout: fixed;
  border-collapse: collapse;
  font-size: 12px;
  font-weight: 500;
  letter-spacing: -0.02em;
  line-height: 1.4;
  color: var(--color-text);
}

.compare__table th,
.compare__table td {
  padding: 0 2px;
  text-align: center;
  vertical-align: middle;
  font-weight: 500;
}

/* The label column takes the width its longest row needs; the three plans
   split what is left, so their marks sit on a regular rhythm. The comp spaces
   them unevenly — it lets the long labels run under the お試し column, which
   is empty on exactly those rows — and a fourth of a phone is too little to
   risk that on. */
.compare__table th:first-child {
  width: 36%;
  padding-left: 6px;
  text-align: left;
}

.compare__table thead th {
  height: 63px;
  background: var(--color-compare-band);
}

.compare__table thead th.is-featured {
  background: var(--color-cyan-accent);
  color: #fff;
}

.compare__table tbody th,
.compare__table tbody td {
  height: 41px;
  border-top: 1px solid var(--color-compare-band);
}

/* The band above already separates the first row, and the comp gives that row
   more room than the rest — it is the one carrying the figures. */
.compare__table tbody tr:first-child th,
.compare__table tbody tr:first-child td {
  height: 48px;
  border-top: 0;
}

/* 金額の上に乗せる「月額」。「月額 ￥110,000〜」は 12px で 93px あり、
   1/4 幅の列（幅 390px のとき 75px）には 1 行で入らない。金額だけなら
   67px で収まるので、「月額」を小さく上の行に逃がしている。 */
.compare__pre {
  display: block;
  margin-bottom: 1px;
  font-size: 10px;
  font-weight: 500;
  letter-spacing: -0.04em;
  line-height: 1.3;
  opacity: 0.68;
}

/* 料金・支払い形態の行の補足（「初回 ￥190,000」「＋初期費用」）。本体 12px に
   対して 10px まで落としている。1/4 幅の列に「初回 ￥190,000」が折り返さずに
   収まる上限がこの大きさ。 */
.compare__note {
  display: block;
  margin-top: 1px;
  font-size: 10px;
  font-weight: 500;
  letter-spacing: -0.04em;
  line-height: 1.3;
  opacity: 0.68;
}

/* 表の外、カードの下に置く一文。表と同じ 12px だが、カードの影の外なので
   左右は節の余白に合わせている。 */
.compare__footnote {
  margin: 14px 0 0;
  padding: 0 6px;
  font-size: 12px;
  font-weight: 500;
  line-height: 1.7;
  text-align: center;
  color: var(--color-text);
}
.compare__footnote a {
  color: var(--color-cyan-accent);
  text-decoration: underline;
  text-underline-offset: 3px;
}

.compare__yes {
  display: inline-block;
  width: 12px;
  height: 12px;
  border: 1px solid currentColor;
  border-radius: 50%;
  vertical-align: middle;
}

/* Read out, never drawn: the marks are the only thing in those cells, and a
   ring says nothing to a screen reader. */
.u-visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
  border: 0;
}

/* ---- 制作の流れ（プランページ） ---------------------------------------
   A spine down the left with a numbered disc per step, each step closed by a
   rule. Measured off the comp at 2.1231× (828px wide against a 390px page).
   The TOP page has a flow of its own but draws it differently — the number
   sits beside the disc there, inside it here — so this is its own component.
   The comp places the discs by hand: each one sits between 26 and 46px below
   its step's top, so they take the middle of that. */
.plan-flow {
  margin-top: 42px;
  /* The site's reset only covers ul; an ol still carries its 40px marker
     column, which would push the spine off the page's left margin. */
  margin-bottom: 0;
  padding: 0;
  list-style: none;
  text-align: left;
}

.plan-flow__step {
  --dot-top: 50px;
  position: relative;
  padding: 37px 0 13px 55px;
}

.plan-flow__step:first-child {
  --dot-top: 13px;
  padding-top: 0;
}

/* The spine, drawn per step so it runs unbroken through the gaps between them
   and still stops at the first and last disc rather than at the list's edge. */
.plan-flow__step::before {
  content: "";
  position: absolute;
  left: 18px;
  top: 0;
  bottom: 0;
  width: 2px;
  background: var(--color-cyan-accent);
}

.plan-flow__step:first-child::before { top: var(--dot-top); }

.plan-flow__step:last-child::before {
  bottom: auto;
  height: calc(var(--dot-top) + 38px);
}

/* The rule under a step starts where its copy does, not at the page edge. */
.plan-flow__step::after {
  content: "";
  position: absolute;
  left: 55px;
  right: 0;
  bottom: 0;
  height: 3px;
  background: var(--color-cyan-accent);
}

.plan-flow__dot {
  position: absolute;
  left: -1px;
  top: var(--dot-top);
  z-index: 1;
  width: 38px;
  height: 38px;
  display: flex;
  align-items: center;
  justify-content: center;
  border-radius: 50%;
  background: var(--color-cyan-accent);
  color: #fff;
  font-size: 26px;
  font-weight: 700;
  letter-spacing: 0;
  line-height: 1;
}

/* The copy is set in a step of its own from the rule, which is why these two
   carry a left padding the rule does not. */
.plan-flow__title {
  padding-left: 13px;
  font-size: 17px;
  font-weight: 700;
  letter-spacing: 0;
  line-height: 1.4;
  color: var(--color-contact-ink);
}

.plan-flow__text {
  margin-top: 6px;
  padding-left: 13px;
  font-size: 13px;
  font-weight: 400;
  letter-spacing: 0;
  line-height: 24px;
  color: var(--color-contact-ink);
}

/* ロゴデザイン's comp ranges the copy with the rules instead of stepping it
   in, which also gives the longest step the width it needs to stay on three
   lines rather than dropping two characters onto a fourth. */
.plan-flow--flush .plan-flow__title,
.plan-flow--flush .plan-flow__text { padding-left: 0; }

/* Ranged with the rules rather than with the copy: it is a note on the whole
   list, not on the last step. */
.plan-flow__note {
  margin-top: 12px;
  padding-left: 55px;
  font-size: 13px;
  font-weight: 400;
  letter-spacing: 0;
  line-height: 24px;
  text-align: left;
  color: var(--color-contact-ink);
}

/* ---- ご依頼前にご確認ください ------------------------------------------
   The page's closing notes, on a pale panel with no shadow. Measured off the
   comp at 3.9077× (its 1524px width against a 390px page): the panel is 358px
   across, which is a 16px page margin rather than the 20px the sections above
   it use.
   Its ground reads #ebf8fd — 5.8 ΔE from --color-plan-band, which is the pale
   panel this page already has in every plan card. The two never sit next to
   each other, so the page keeps two pale blues rather than three. */
.notice {
  max-width: var(--container-price);
  margin: 29px auto 0;
  padding: 0 16px var(--space-section-end);
}

/* The comp runs these notes the panel's full width, with the ※ sitting on its
   left edge and set at 11.5px. The panel here keeps 8px of padding so the
   text is not on the edge, and takes the size up with the rest of the page;
   between the two the notes run three lines longer than the comp's thirteen,
   which is what the larger size costs on a 358px panel. */
.notice__card {
  padding: 18px 8px 40px;
  background: var(--color-plan-band);
  border-radius: 36px;
}

.notice__title {
  font-size: 18px;
  font-weight: 700;
  letter-spacing: 0;
  line-height: 1.4;
  text-align: center;
  color: var(--color-text);
}

.notice__list {
  margin-top: 30px;
  font-size: 12.5px;
  font-weight: 400;
  letter-spacing: 0;
  line-height: 24px;
  color: var(--color-text);
}

/* Hanging indent: a note that runs on lines up under its own first character
   rather than under the ※. */
.notice__list > li {
  padding-left: 1em;
  text-indent: -1em;
}

.notice__list > li::before { content: "\203b"; }

/* =========================================================
   Desktop / tablet-landscape (>=900px)
   No dedicated PC design exists in the source file, so the
   same content is reflowed into a wider, multi-column layout.
   ========================================================= */
@media (min-width: 900px) {
  /* PC type scale. Only the sizes that step up on desktop are redefined —
     button / nav / note / caption stay at their SP values, which already
     match the PC guidance.
     --fs-h1 stays viewport-relative because the hero copy sits in a fixed
     one-line band inside the right-hand column: it grows toward the top of
     the 40-56px band as that column widens, and eases back at ~900px where
     the column is at its narrowest. */
  :root {
    --fs-h1: clamp(32px, 3.4vw, 42px); /* 大見出し */
    --fs-section-en: 48px;             /* セクション名（英字・装飾） */

    /* Desktop section rhythm. Every section's own top and bottom padding
       comes from these two, so the gap between any pair is the sum of the
       neighbours and the whole page can be re-spaced from here.
       The pair adds up to the standard 200px gap, keeping roughly the 4:5
       split the previous 104/130 had. */
    --space-section: 90px;
    --space-section-end: 110px;

    /* The CTA pill makes the header row taller than its 61px min-height from
       this breakpoint up, so anchor jumps have to clear more. */
    --header-h: 68px;

    /* On a phone this gap is a share of the window (23vw), which on a desktop
       keeps opening up with the monitor — 317px at 1377px wide, 390px once
       past 1696px — leaving a bare field of grid paper above the teal hill.
       Here it is set so the megaphone opens 提供サービス's own distance below
       the last step card: the palette sits --space-section under the teal
       edge, so the megaphone sits --space-section under the analysis cards.
       The gap is measured to the hill, which the megaphone hangs 1.11em of
       the English name above, so that much is added back. */
    --analysis-gap: calc(var(--space-section) + var(--fs-section-en) * 1.11);
    --fs-h2: 32px;                     /* 中見出し */
    --fs-h3: 22px;                     /* 小見出し */
    --fs-body: 17px;                   /* 本文 */
  }

  .voice { padding: var(--space-section) 0 var(--space-section-end); }
  .voice__watermark { font-size: min(13vw, 240px); }
  .voice__watermark { margin-bottom: 2.8vw; }
  .voice .section-head__icon { width: 96px; }
  .voice .section-head { margin-bottom: 56px; }
  /* Same row behaviour as 提供サービス, so further voices drop in alongside. */
  /* Back to a wrapped row: no scrolling, so the arrows go away too. */
  .voice__slider { padding: 56px 40px 0; }
  .voice__nav { display: none; }
  .voice__list { flex-wrap: wrap; justify-content: center; align-items: flex-start; gap: 40px 28px; overflow-x: visible; scroll-snap-type: none; }
  .voice-card { flex: 1 1 320px; max-width: 380px; }
  /* The two plans sit side by side and stretch to each other. That also
     settles the height difference the comp papers over by hand: its second
     card carries a two-line heading yet ends level with the first, because
     every gap inside it is squeezed (21.6px under the band against 33.8,
     18.7px under the last line against 33.9). Here the spacing stays the same
     in both cards and the row levels them instead. */
  .home-price__plans { flex-direction: row; justify-content: center; align-items: stretch; gap: 32px; }
  /* margin-inline cleared, not just the direction changed: the auto margin
     that centres the single column on a phone would otherwise eat the row's
     free space here and open the two cards to 321px apart. */
  .home-price__plan { display: flex; flex-direction: column; margin-inline: 0; }
  .home-price__card { flex: 1; display: flex; flex-direction: column; }
  .home-price__body { flex: 1; }

  /* No desktop comp for 制作の流れ. The timeline keeps the proportions it was
     drawn at and is held to reading width rather than stretching the step
     copy across the whole screen; only the body text steps up, to the size
     the rest of the page uses here. */
  .flow__list { max-width: var(--container-price); margin-inline: auto; }
  .flow__step-text { font-size: var(--fs-note); }

  /* Same for more design について: the ground and both waves stay full width,
     but the prose is held to reading width instead of running the whole
     screen, and steps up to the size the rest of the page uses here. */
  .about__bio,
  .about__hobby-title,
  .about__hobby { max-width: var(--container-price); margin-inline: auto; }
  /* 11.8px は 358px のカンプ幅に合わせた寸法。PC では読み幅が
     --container-price の 640px まで開くので、この幅の本文サイズ
     （--fs-body、17px）まで上げる。趣味の行は一段小さいまま。 */
  .about__bio { font-size: var(--fs-body); line-height: 2.3; }
  .about__hobby-title { font-size: var(--fs-body); }
  .about__hobby { font-size: 15px; }

  /* よくあるご質問 と お問い合わせ も、制作の流れ・more design について と
     同じ読み幅まで開く。310px のままだと、そこだけ本文が細い帯になって
     前後のセクションから浮く。カード・罫線・ボタンの中身はそのままで、
     枠だけ広がる。 */
  .faq__list { max-width: var(--container-price); }
  /* 12px was sized to the 310px card; on a 640px one it reads as a caption.
     16px is the body scale the rest of this width uses. */
  .faq__q-text,
  .faq__a-lead,
  .faq__a-text { font-size: 16px; }

  .contact-home__tel { max-width: var(--container-price); }

  /* The two channels sit side by side on a desktop. They keep the width the
     comp gives them rather than growing into the row: at 322px the pill still
     fills the button, and a 400px-wide stadium would read as a banner. The
     gap matches the 36px the pair stands apart. */
  .contact-home__choices {
    margin-top: 28px;
    display: flex;
    justify-content: center;
    align-items: stretch;
    gap: 36px;
  }
  .contact-home__choices .contact-choice { margin: 0; }

  /* more design について は下端が波なので padding-bottom を持たない。その
     ぶんこの境目だけ14pxまで詰まっていたので、よくあるご質問の上を他の
     セクションと同じ --space-section にする。SP はカンプどおりの14pxの
     まま（あちらは波の下に21px程度しか取っていない）。 */
  .faq { padding-top: var(--space-section); }

  .voice-card__comment { font-size: 20px; }
  /* Three quotes in the window here, at the same 244.5px the two-up layout
     gave them, so the cards themselves are unchanged and only the window
     grows. */
  .voice__quotes-slider { max-width: 796px; }
  .quote-card { flex-basis: calc((100% - 62px) / 3); }

  .service { padding: var(--space-section) 0 var(--space-section-end); }
  .service .section-head__icon { width: 68px; }
  /* Same row behaviour as the 当店の強み cards, so further services drop in
     alongside this one without another layout pass. */
  /* Three across on wide screens (5 services read as 3 + 2), two across
     below. The basis is the card width the longest heading needs to stay on
     its two lines, so a third card only joins the row once there is room. */
  .service__list { max-width: 1200px; flex-direction: row; flex-wrap: wrap; justify-content: center; align-items: stretch; gap: 28px; padding: 0 40px; }
  .service-card { flex: 1 1 344px; max-width: 380px; display: flex; flex-direction: column; }
  .service-card__body { flex: 1 1 auto; }

  .section-head { margin-bottom: 40px; }
  .section-head__icon { width: 88px; margin-bottom: 18px; }
  .section-head__ja { font-size: var(--fs-body); }
  .section-head__ja--lead { font-size: var(--fs-h3); }

  .header__inner { padding: 12px clamp(16px, calc(6.7vw - 44.3px), 40px); }
  .header__logo { height: clamp(30px, calc(4vw - 6px), 36px); }
  .header__menu-btn { display: none; }

  .header__nav { position: static; inset: auto; width: auto; max-height: none; background: none; border-radius: 0; box-shadow: none; transform: none; overflow: visible; padding: 0; text-align: left; }
  .header__nav > * { max-width: none; margin-left: 0; margin-right: 0; }
  /* The bar is a row of links again, so the menu's footer half goes away
     and the CTA pill comes back. */
  .header__nav-social, .header__nav-copy { display: none; }
  /* Flex, not block: as an inline-block the pill sits on a text baseline and
     the line box adds a descender's worth of space under it, which pushed the
     whole bar 5px taller than the rest of the row needs. */
  .header__nav-cta-item { display: flex; align-items: center; }
  /* The row's side padding, the gap, the label size and the pill's padding all
     ease with the viewport, because eight labels plus the CTA pill did not fit
     one header row at the 900px breakpoint. Five labels do, with room to
     spare, so the gap now opens rather than closes: 20px at 900 and 36px at
     1280, where the labels, the pill and the logo come to 723px of the 851.5px
     the row has.
     The easing still finishes at 1280px, not beyond: .header__inner stops
     growing at --container (1200px) plus its padding, so the row has no more
     room after that and a gap that kept opening simply pushed the pill out.
     The label size is left as it was, easing down to 13.5px: raising it back
     to 16px would take the row to within 20px of the logo at exactly 900.
     The logo is deliberately left out of the easing: taking it below its 30px
     would make it smaller on a laptop than it is on a phone. */
  .header__nav-list { flex-direction: row; align-items: center; padding: 0; gap: clamp(20px, calc(4.21vw - 17.9px), 36px); }
  .header__nav-list a,
  .header__nav-parent { padding: 0; font-size: clamp(13.5px, calc(0.66vw + 7.56px), var(--fs-nav)); letter-spacing: 0.05em; color: inherit; }
  /* Selected through the list so it outweighs the `.header__nav-list a`
     reset above, which is one tag more specific and was flattening the pill
     to padding: 0 — the text then sat in a box the size of its own line, with
     the rounded ends biting into the first and last characters. */
  .header__nav-list .header__nav-cta { margin-top: 0; padding: 10px clamp(12px, 1.5vw, 22px); }

  /* In the bar the same seven links become a panel under 提供サービス. */
  /* A plain block, exactly like the items either side of it: a flex item here
     centres its label on the row's height while its neighbours sit on their
     own baselines, and the label ends up 1-2px high. */
  .header__nav-item--has-sub { position: relative; display: block; }
  /* Covers the gap between the label and the panel so a pointer travelling
     down to the panel never drops the hover. */
  .header__nav-item--has-sub::after { content: ""; position: absolute; top: 100%; left: 0; right: 0; height: 8px; }

  .header__subnav {
    position: absolute;
    /* Straight under the label, not under the bar: the 8px is just enough to
       read as a separate surface. The panel therefore overlaps the lower half
       of the bar, which it can — it is inside the header and paints over it. */
    top: calc(100% + 8px);
    /* Hung off the label's own left edge. Centred, the panel reached further
       left than 提供サービス starts and read as belonging to the item before
       it. The item carries no padding in the bar, so 0 is that edge. */
    left: 0;
    align-items: stretch;
    gap: 0;
    min-width: 210px;
    /* The drawer's indent and its rule both go: the panel is its own surface
       here, so the grouping no longer needs marking inside it. */
    margin-left: 0;
    padding: 8px 0;
    border-left: 0;
    background: #fff;
    border-radius: 12px;
    box-shadow: 0 10px 28px rgba(0, 0, 0, 0.14);
    /* Faded out and made untouchable rather than hidden: 提供サービス is a
       label now, so these links are the only focusable thing in the group and
       visibility: hidden would take them out of the tab order with no way back
       in. Tabbing to one puts :focus-within on the item and opens the panel
       around it. */
    opacity: 0;
    pointer-events: none;
    transition: opacity 0.18s ease;
  }
  /* focus-within as well as hover, so the panel opens for the keyboard. */
  .header__nav-item--has-sub:hover .header__subnav,
  .header__nav-item--has-sub:focus-within .header__subnav { opacity: 1; pointer-events: auto; }

  .header__subnav a {
    display: block;
    padding: 9px 20px;
    font-size: 13.5px;
    letter-spacing: 0.05em;
    color: var(--color-gray-800);
    opacity: 1;
  }
  .header__subnav a:hover { opacity: 1; background: var(--color-plan-band); }

  .footer { display: block; }

  /* Desktop footer, measured off its own comp at 2× — the comp is 2000px for
     a 1000px page, which the FOLLOW US lettering confirms: 16.5px of cap
     against the 22px --fs-h3 already set here.
     The 640px cap is lifted so the two blocks can size themselves: the
     sitemap runs wide enough to break 5 / 4 / 1 the way the comp does, while
     the rule above FOLLOW US is a short centred line rather than a full-width
     one. */
  .footer > * { max-width: none; }

  .footer__nav-list {
    flex-direction: row;
    flex-wrap: wrap;
    justify-content: center;
    /* Held over from the ten-item sitemap, where it put the comp's 5 / 4 / 1
       breaks in place. The five the header carries come to 763px, so nothing
       wraps now and this only guards against a sixth label later. */
    max-width: 880px;
    margin-inline: auto;
    row-gap: 70px;
    column-gap: 38px;
  }
  /* 52–55px between one label's ink and the next in the comp; the links carry
     8px of their own padding either side, so the gap above is 38px. */
  .footer__nav-list a { font-size: 22px; }

  /* A second row under the five, not a column beside 提供サービス: the footer
     reads as one centred band and a hanging column would break it. The size
     and the softer ink are what mark them as the group's members. */
  .footer__subnav-list {
    display: flex;
    flex-wrap: wrap;
    justify-content: center;
    /* Seven on one line want 1141px, wider than the 780px the five above take
       up, so they break instead. 720 puts the break at 4 / 3: the first four
       come to 665px and a fifth would take 893. Both rows then sit inside the
       row above them, which is what keeps them reading as its members. */
    max-width: 720px;
    margin: 30px auto 0;
    row-gap: 16px;
    column-gap: 22px;
  }
  .footer__subnav-list a { font-size: 16px; opacity: 0.75; }
  .footer__subnav-list a:hover { opacity: 0.5; }

  .footer__social {
    max-width: 270px;
    margin: 46px auto 0;
    padding-top: 42px;
  }
  .footer__social-list { margin-top: 26px; gap: 40px; }
  .footer__social-list img { width: 47px; height: 47px; }

  .fv { padding: 64px 40px 72px; }
  .fv__inner { flex-direction: row; align-items: center; text-align: left; gap: 48px; }
  .fv__media { flex: 1 1 36%; width: auto; justify-content: flex-start; padding: 0; margin: 0; }
  .fv__image { max-width: 480px; }
  .fv__content { flex: 1 1 64%; display: flex; flex-direction: column; align-items: flex-start; gap: 20px; }
  .fv__heading { align-items: flex-start; }
  /* The copy set five lines at 480px, the last of them a lone 「い。」. It
     runs to 1901px of ink at 17px, so four lines need a little over 475px
     each and three would need 650: anything from 490 to 640 sets four, and
     560 sits in the middle of that band with room either side. The column
     itself is 712px here, so this is still well inside it. */
  .fv__lead {
    max-width: 560px;
    /* Japanese wraps between any two characters by default, which left one
       line ending on the lone kana of 「まずは」 and another splitting
       デザイン in half. auto-phrase breaks at phrase boundaries instead, so a
       word or a particle cluster stays whole. Kept to desktop: at the phone's
       350px measure the phrases are long enough relative to the line that
       holding them together leaves a badly ragged edge. Browsers without
       auto-phrase fall back to the plain character wrap — the same breaks as
       before, never worse. */
    word-break: auto-phrase;
  }

  /* No desktop comp for the plan cards, so each keeps the 350px it was drawn
     at and further plans line up beside it rather than stretching. The block
     widens to take a row of them while the heading stays at reading width. */
  .price-plan { max-width: var(--container-point); }
  .price-plan__title,
  .price-plan__lead { max-width: var(--container-price); margin-inline: auto; }
  .plan-cards { flex-direction: row; flex-wrap: wrap; justify-content: center; align-items: stretch; }
  .plan-card { flex: 0 1 350px; }

  /* The six single-plan sections each hold one card, so on their own they
     would run down the page one to a row while the WEB マーケティング group
     beside them sits three across. The wrapper lays the sections out on the
     same grid — same 350px column, same 32px gutter — so the whole page reads
     as one three-column table. The sections stay in the markup because the
     service list anchors to their ids; here they are only the cells.
     Stretching them and letting the card fill its cell keeps each row of
     three level, the same way .plan-cards already does inside a group. */
  .price-plan-grid {
    max-width: var(--container-point);
    margin: 56px auto 0;
    /* Same box as a .price-plan, so the grid drops from three columns to two
       at the same width the WEB マーケティング group does. */
    padding: 0 20px;
    display: flex;
    flex-wrap: wrap;
    justify-content: center;
    align-items: stretch;
    gap: 32px;
  }
  .price-plan-grid > .price-plan {
    flex: 0 1 350px;
    max-width: 350px;
    /* Cleared rather than just zeroed at the top: .price-plan carries
       margin-inline: auto, and an auto margin on a flex item eats the row's
       free space, which would spread the three columns instead of gutting
       them at the 32px the cards inside a group already use. */
    margin: 0;
    padding: 0;
    display: flex;
    flex-direction: column;
  }
  .price-plan-grid > .price-plan .plan-cards { flex: 1; }

  .cta { padding: 32px 40px; }
  /* Restated after the shorthand above, which would otherwise reset the
     closing CTAs' own block padding. */
  .cta--closing { padding-block: calc((var(--space-section) + var(--space-section-end)) / 2); }

  .works { padding: var(--space-section) 0 var(--space-section-end); }
  .works__slider { padding: 0 40px; }
  .works__track { gap: 22px; }
  .work-card { width: 240px; }
  .works__nav { width: 44px; height: 44px; }
  .works__nav svg { width: 22px; height: 22px; }
  /* Kept inside the slider box: at viewports near the 900px breakpoint the
     slider spans the full width, so a negative offset pushed the button past
     the viewport edge and produced a few px of horizontal scroll. */
  .works__nav--prev { left: 0; }
  .works__nav--next { right: 0; }

  .problem { padding-bottom: var(--space-section-end); gap: 40px; }
  /* The comp leaves a wide band of grid paper between the last step card
     and the teal hill — about 23% of the window, on top of the room the
     dome itself needs. Clamped so it stays generous at 1400px+ without
     swallowing the screen at the 900px breakpoint. */
  .analysis { padding-top: 220px; padding-left: 40px; padding-right: 40px; }
  .analysis__deco { top: 40px; width: 18%; max-width: 190px; }
  .analysis__deco--left { left: 3%; }
  .analysis__deco--right { right: 3%; }
  .problem__intro-canvas { max-width: var(--container-problem); }
  /* The character is sized off the canvas, which stops growing at
     --container-problem, but the yellow under it was a plain percentage of
     the window and kept opening up — 131px of it at 1000px against 407px at
     1800px. Capping the margin at the same 34.6% of the width the canvas
     settles on freezes the gap exactly where the illustration does, so the
     two stay locked together on any monitor. The cap equals the percentage
     at that width, so nothing jumps as it takes over. */
  .problem__intro-band { margin-bottom: min(34.6%, calc(var(--container-problem) * 0.346)); }
  /* The canvas is far wider here, so the bubbles stop scaling with it and
     move outboard of the (much larger) character instead. */
  .problem__intro-bubbles { width: 180px; top: 12%; }
  .problem__intro-bubbles--left { left: -6%; }
  .problem__intro-bubbles--right { right: -6%; }

  /* Cards auto-fill the row within the shared content width
     (--container-problem) instead of a fixed px size, so they always fit
     alongside the sections below. */
  .problem__list { max-width: var(--container-problem); flex-direction: row; justify-content: center; align-items: stretch; gap: 24px; padding: 0 40px; }
  .problem__item { justify-content: center; flex: 1 1 0; }
  .case-card { display: flex; flex-direction: column; }
  /* Same narrow sides as on a phone: the headlines are written to two lines
     and the cards are at their tightest here. */
  .case-card__body { flex: 1 1 auto; padding: clamp(28px, 3vw, 40px) 10px clamp(24px, 2.4vw, 28px); }
  .case-card__title { font-size: var(--fs-h3); }
  /* Side by side the cards are narrower than one phone-width card, so the
     voice row stacks rather than squeezing the balloon. */
  .case-card__voice { flex-direction: column; gap: 14px; }
  .case-card__balloon::before,
  .case-card__balloon::after { top: 0; right: auto; left: 50%; transform: translate(-50%, -100%); border-right-color: transparent; }
  .case-card__balloon::before { border-bottom-color: var(--color-case); }
  .case-card__balloon::after { border-bottom-color: #fff; margin-right: 0; margin-top: 3px; }

  .steps { max-width: var(--container-insight); padding: 64px 0 0; }
  .step-card { border-radius: 32px; padding: 32px 40px 48px; }
  .step-card__media { max-width: 420px; }

  .point { --point-pad-top: var(--space-section); padding: var(--point-pad-top) 40px var(--space-section-end); }
  /* Two across, two down. The basis is half the row rather than a fixed
     width, so a third card can never squeeze onto a line; the cap is what
     keeps the card near the size it was drawn at, since its numeral, its
     illustration and the PDCA diagram are all set as fractions of the card's
     own width and grow with it. The row gap is opened past the column gap so
     the two rows read as rows. */
  .point__list { flex-direction: row; flex-wrap: wrap; justify-content: center; align-items: stretch; gap: 40px 28px; }
  .point__card { flex: 0 1 calc(50% - 14px); max-width: 420px; display: flex; flex-direction: column; }
  .point__card-top { flex: 1 1 auto; }
  .point__card-bottom { flex: none; height: 210px; }
  .point__card-bottom--figure { flex: none; }

  /* プラン詳細ページ。No PC comp exists for this page, so the card keeps every
     size it has on a phone and only gains room: it widens to 480px, which is
     where the summary settles on two lines instead of three, and the side
     padding opens from the comp's 11px to 28px so the copy is not sitting on
     the rounded edge. */
  .plan-page { margin-top: var(--space-section); }
  .plan-page__title { font-size: 26px; }
  .plan-page__lead { font-size: 16px; line-height: 28px; }

  .plan-detail {
    max-width: 480px;
    margin-inline: auto;
    padding-inline: 28px;
  }

  .plan-detail__price { margin-inline: -28px; padding-inline: 28px; }
  .plan-detail__term,
  .plan-detail__services { margin-inline: -28px; padding-inline: 28px; }
  .plan-detail__summary--ruled { margin-inline: -28px; padding-inline: 28px; }

  /* Both of these have more than 600px to work with here, so they come up to
     the size of the copy around them. */
  .plan-flow__title { font-size: 21px; }
  .plan-flow__text,
  .plan-flow__note { font-size: 16px; line-height: 28px; }

  /* The band keeps its drawn proportions and only opens up: the copy comes up
     a step and the whole thing takes the page's desktop rhythm above and
     below. */

  .notice { margin-top: var(--space-section); }
  .notice__card { padding: 28px 32px 48px; }
  .notice__title { font-size: 23px; }
  .notice__list { margin-top: 36px; font-size: 16px; line-height: 30px; }

  .compare { padding-bottom: 24px; }
  .compare__table { font-size: 16px; letter-spacing: 0; }
  .compare__table th:first-child { padding-left: 20px; }
  .compare__table thead th { height: 76px; }
  .compare__table tbody th,
  .compare__table tbody td { height: 52px; }
  .compare__table tbody tr:first-child th,
  .compare__table tbody tr:first-child td { height: 60px; }
  .compare__yes { width: 15px; height: 15px; }

}

/* =========================================================
   Wide desktop (>=1160px)
   ========================================================= */
/* The three plans under すでに WEB サイトをお持ちの方へ read as one set, so
   they sit in a row once there is room for it. The row is capped at
   --container-point, which leaves each card 352px — near the 350 it was drawn
   at — so inside the row every card keeps the phone's side padding rather
   than the wider desktop one, and the copy breaks the way it was measured.
   Below this width three cards would each be under 344px, which is where the
   longest plan's lead stops fitting on one line, so they stay stacked.
   Equal heights: the slack falls under the shortest list, which is the card's
   own white space. */
@media (min-width: 1160px) {
  .plan-page--wide { max-width: var(--container-point); }

  /* Side by side the cards have to line up band for band, not just end at the
     same height. Flex can only stretch the cards themselves — it has no way to
     give three sibling cards a common height for their price bands — so the
     row becomes a grid and each card a subgrid of it. Every card in a given
     row carries the same blocks in the same order (head / price / … / services),
     so each block lands in the same track as its opposite numbers and the
     tallest one sets the track.

     Five tracks covers the longest card on the site (WEBマーケティング and
     WEBサイト制作); the shorter cards — パッケージ, 動画, イラスト, all three
     blocks — simply leave the last two tracks empty, and an empty track with
     nothing in it anywhere in the row measures 0. */
  .plan-detail-row {
    display: grid;
    grid-auto-flow: column;
    grid-auto-columns: minmax(0, 1fr);
    grid-template-rows: repeat(5, auto);
    /* Row gap 0: the subgrid takes its gutters from here, and inside a card
       the blocks are meant to touch — the band's own edge and the rules
       between sections are what separate them. 32px is only between cards. */
    gap: 0 32px;
  }

  .plan-detail-row .plan-detail {
    display: grid;
    grid-template-rows: subgrid;
    grid-row: 1 / -1;
    max-width: none;
    /* Not auto: auto inline margins would swallow the row's free space and
       the gap would collapse to nothing. */
    margin-inline: 0;
    padding-inline: 13px;
  }

  /* The band is now as tall as the tallest in the row — プレミアム's, which
     carries badges above the figure. Centring keeps the figure off the top
     edge in the cards that have no badges. */
  .plan-detail-row .plan-detail__price {
    display: flex;
    flex-direction: column;
    justify-content: center;
  }

  .plan-detail-row .plan-detail__price,
  .plan-detail-row .plan-detail__term { margin-inline: -13px; padding-inline: 13px; }
  .plan-detail-row .plan-detail__services { margin-inline: -13px; padding: 11px 5px 16px 11px; }

  /* Two to a row, the free space would push each card to 544px and the pair
     would read wider than every other card on the site. Hold them at the
     480px the stacked cards use and centre what is left over. */
  .plan-detail-row--pair {
    grid-auto-columns: minmax(0, 480px);
    justify-content: center;
  }
}

/* ===== WordPress Works: detail/archive ===== */
.works-single {
  padding: 48px 20px 80px;
}

.works-detail {
  width: 100%;
  max-width: 960px;
  margin: 0 auto;
}


/* -----------------------------------------
   Header
   ----------------------------------------- */

.works-detail__header {
  margin-bottom: 56px;
}

.works-detail__categories {
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  margin-bottom: 20px;
}

.works-detail__category {
  display: inline-flex;
  align-items: center;
  padding: 6px 16px;

  background: var(--color-tag-bg);
  color: var(--color-tag-text);

  border-radius: 999px;

  font-size: var(--fs-note);
  font-weight: 600;
  line-height: 1.4;
}

.works-detail__title {
  margin: 0;

  font-size: 32px;
  font-weight: 700;
  line-height: 1.4;
  letter-spacing: 0.04em;
}

.works-detail__client {
  margin-top: 12px;

  color: var(--color-gray-600);

  font-size: var(--fs-body);
  line-height: 1.7;
}


/* -----------------------------------------
   Sections
   ----------------------------------------- */

.works-detail__section {
  margin-top: 56px;
}

.works-detail__section h2 {
  margin: 0 0 20px;
  padding-bottom: 12px;

  border-bottom: 1px solid var(--color-gray-200);

  font-size: var(--fs-h2);
  font-weight: 700;
  line-height: 1.5;
}

.works-detail__section p {
  margin: 0;

  font-size: var(--fs-body);
  line-height: 2;
}

.works-detail__content {
  font-size: var(--fs-body);
  line-height: 2;
}

.works-detail__content p {
  margin: 0 0 16px;
}

.works-detail__content p:last-child {
  margin-bottom: 0;
}


/* -----------------------------------------
   Gallery
   ----------------------------------------- */

.works-detail__gallery {
  display: grid;
  gap: 24px;
}

.works-detail__image {
  margin: 0;
}

.works-detail__image img {
  display: block;
  width: 100%;
  height: auto;

  border-radius: 16px;
}


/* -----------------------------------------
   Related service
   ----------------------------------------- */

.works-detail__related {
  margin-top: 72px;
  padding: 32px;

  background: var(--color-gray-100);

  border-radius: 16px;
}

.works-detail__related h2 {
  margin-bottom: 24px;
}

.works-detail__service-link {
  display: inline-flex;
  align-items: center;
  justify-content: center;

  min-height: 52px;
  padding: 14px 28px;

  background: var(--color-cyan-accent);
  color: #fff;

  border-radius: 999px;

  font-size: var(--fs-button);
  font-weight: 600;
  line-height: 1.5;
  text-decoration: none;

  transition:
    opacity 0.2s ease,
    transform 0.2s ease;
}

.works-detail__service-link:hover {
  opacity: 0.85;
  transform: translateY(-1px);
}


/* -----------------------------------------
   PC
   ----------------------------------------- */

@media (min-width: 900px) {

  .works-single {
    padding-top: 80px;
    padding-bottom: 120px;
  }

  .works-detail__header {
    margin-bottom: 72px;
  }

  .works-detail__title {
    font-size: 40px;
  }

  .works-detail__section {
    margin-top: 72px;
  }

  .works-detail__gallery {
    gap: 32px;
  }

  .works-detail__related {
    padding: 40px;
  }
}

/* Works詳細：ページタイトル調整 */
.works-detail__page-head {
  margin-bottom: 40px;
}

.works-detail__page-head .section-head {
  margin-bottom: 0;
}

@media (min-width: 900px) {
  .works-detail__page-head {
    margin-bottom: 48px;
  }
}

/* =========================================================
   Works Archive
   制作事例一覧ページ
   ========================================================= */

.works-archive {
  padding: 48px 20px 80px;
}

.works-archive__page-head {
  margin-bottom: 48px;
}

.works-archive__page-head .section-head {
  margin-bottom: 0;
}

.works-archive__inner {
  width: 100%;
  max-width: var(--container-works);
  margin: 0 auto;
}


/* -----------------------------------------
   Category Filter
   ----------------------------------------- */

.works-archive__categories {
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  gap: 10px;

  margin-bottom: 48px;
}

.works-archive__filter {
  display: inline-flex;
  align-items: center;
  justify-content: center;

  min-height: 36px;
  padding: 7px 16px;

  background: var(--color-gray-100);
  color: var(--color-gray-800);

  border-radius: 999px;

  font-size: var(--fs-note);
  font-weight: 500;
}

.works-archive__filter.is-active {
  background: var(--color-cyan-accent);
  color: #fff;
}


/* -----------------------------------------
   Works Grid
   ----------------------------------------- */

.works-archive__grid {
  display: grid;
  grid-template-columns: 1fr;
  gap: 32px;
}

.works-archive__card {
  overflow: hidden;

  background: #fff;

  border-radius: 20px;
  box-shadow: var(--shadow-card);
}

.works-archive__card-link {
  display: block;
  height: 100%;
}

.works-archive__image {
  width: 100%;
  aspect-ratio: 16 / 10;

  overflow: hidden;
  background: var(--color-gray-100);
}

.works-archive__image img {
  width: 100%;
  height: 100%;

  object-fit: cover;

  transition: transform 0.3s ease;
}

.works-archive__card-link:hover .works-archive__image img {
  transform: scale(1.03);
}

.works-archive__image-placeholder {
  width: 100%;
  height: 100%;

  background: var(--color-gray-100);
}


/* -----------------------------------------
   Card Content
   ----------------------------------------- */

.works-archive__body {
  padding: 20px;
}

.works-archive__card-categories {
  display: flex;
  flex-wrap: wrap;
  gap: 8px;

  margin-bottom: 12px;
}

.works-archive__card-category {
  display: inline-flex;
  align-items: center;

  padding: 5px 12px;

  background: var(--color-tag-bg);
  color: var(--color-tag-text);

  border-radius: 999px;

  font-size: var(--fs-caption);
  font-weight: 600;
}

.works-archive__title {
  font-size: var(--fs-h3);
  font-weight: 700;
  line-height: 1.5;
}


/* -----------------------------------------
   Pagination
   ----------------------------------------- */

.works-archive__pagination {
  margin-top: 56px;
}

.works-archive__pagination .nav-links {
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  align-items: center;
  gap: 8px;
}

.works-archive__pagination .page-numbers {
  display: inline-flex;
  align-items: center;
  justify-content: center;

  min-width: 40px;
  height: 40px;
  padding: 0 10px;

  border-radius: 50%;

  font-size: var(--fs-note);
}

.works-archive__pagination .current {
  background: var(--color-cyan-accent);
  color: #fff;
}


/* -----------------------------------------
   Empty
   ----------------------------------------- */

.works-archive__empty {
  text-align: center;

  font-size: var(--fs-body);
}


/* -----------------------------------------
   PC
   ----------------------------------------- */

@media (min-width: 900px) {

  .works-archive {
    padding-top: 80px;
    padding-bottom: 120px;
  }

  .works-archive__page-head {
    margin-bottom: 56px;
  }

  .works-archive__categories {
    margin-bottom: 56px;
  }

  .works-archive__grid {
    grid-template-columns: repeat(3, 1fr);
    gap: 32px;
  }

  .works-archive__body {
    padding: 24px;
  }
}

/* Works 制作事例一覧ボタン */
.works__more {
  width: 100%;
  display: flex;
  justify-content: center;
  margin-top: 32px;
}

.works__more-link {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-width: 220px;
  min-height: 48px;
  padding: 10px 24px;
  border-radius: 999px;
  background: var(--color-cyan-accent);
  color: #fff;
  font-weight: 700;
  text-decoration: none;
}

/* 制作事例が1件だけの場合は中央配置 */
.works__track--single {
  justify-content: center;
}

/* -----------------------------------------
   Works detail: back to archive
   ----------------------------------------- */

.works-detail__back {
  margin-top: 40px;
  text-align: center;
}

.works-detail__back-link {
  display: inline-flex;
  align-items: center;
  justify-content: center;

  min-height: 52px;
  padding: 14px 28px;

  background: var(--color-cyan-accent);
  color: #fff;

  border-radius: 999px;

  font-size: var(--fs-button);
  font-weight: 600;
  line-height: 1.5;
  text-decoration: none;

  transition:
    opacity 0.2s ease,
    transform 0.2s ease;
}

.works-detail__back-link:hover {
  opacity: 0.85;
  transform: translateY(-1px);
}

/* Works pages: shared site header/footer */
body.post-type-archive-works .works-archive,
body.tax-works_category .works-archive,
body.single-works .works-single {
  padding-top: 96px;
}

@media (max-width: 767px) {
  body.post-type-archive-works .works-archive,
  body.tax-works_category .works-archive,
  body.single-works .works-single {
    padding-top: 76px;
  }
}

