Skip to content

Basinfy/Basinfy-SaaS-Studio / .claude/skills/saas-frontend-taste

saas-frontend-taste

Verified

Design, refine, and verify SaaS screens with anti-slop copy and responsive layout checks.

FileKindSize
SKILL.mdskill md11.1 KB
assets/backgrounds/backgrounds.cssother41.5 KB
assets/backgrounds/backgrounds.jsscript8.9 KB
assets/backgrounds/check.htmlother4.8 KB
assets/backgrounds/check.mjsscript14.2 KB
assets/backgrounds/demo.htmlother43.3 KB
assets/backgrounds/index.jsonconfig19.6 KB
assets/backgrounds/pick.mjsscript14.0 KB
assets/diagrams/demo.htmlother11.4 KB
assets/diagrams/diagram.cssother25.5 KB
assets/diagrams/diagram.jsscript89.2 KB
assets/diagrams/lab.htmlother11.2 KB
assets/diagrams/mount.jsscript609 B
assets/diagrams/presets.jsonconfig27.9 KB
assets/layout/check.mjsscript15.8 KB
assets/layout/deal.mjsscript9.5 KB
assets/layout/demo.cssother5.7 KB
assets/layout/fonts.htmlother9.5 KB
assets/layout/hero-centred.htmlother16.4 KB
assets/layout/hero-collage.htmlother15.7 KB
assets/layout/hero-editorial.htmlother8.1 KB
assets/layout/hero-film.htmlother7.8 KB
assets/layout/hero-photo.htmlother7.8 KB
assets/layout/hero-place.htmlother6.7 KB
assets/layout/hero-product.htmlother7.7 KB
assets/layout/hero-split.htmlother7.8 KB
assets/layout/hero-statement.htmlother8.4 KB
assets/layout/hero-triptych.htmlother14.2 KB
assets/layout/hero-word.htmlother10.1 KB
assets/layout/heroes.jsonconfig36.7 KB
assets/layout/img/credits.jsonconfig8.2 KB
assets/layout/img/photo-1068.jpgbinary48.0 KB
assets/layout/img/photo-1081.jpgbinary40.5 KB
assets/layout/img/photo-465.jpgbinary19.6 KB
assets/layout/img/photo-559.jpgbinary86.2 KB
assets/layout/img/photo-855.jpgbinary25.8 KB
assets/layout/img/photo-887.jpgbinary66.8 KB
assets/layout/img/photo-949.jpgbinary37.1 KB
assets/layout/img/photo-954.jpgbinary17.4 KB
assets/layout/img/photo-beans-hand.jpgbinary17.1 KB
assets/layout/img/photo-c166.jpgbinary32.3 KB
assets/layout/img/photo-c400.jpgbinary98.8 KB
assets/layout/img/photo-c7.jpgbinary24.7 KB
assets/layout/img/photo-c70.jpgbinary32.4 KB
assets/layout/img/photo-c8.jpgbinary25.1 KB
assets/layout/img/photo-c823.jpgbinary34.7 KB
assets/layout/img/photo-c96.jpgbinary33.0 KB
assets/layout/img/photo-d534.jpgbinary121.7 KB
assets/layout/img/photo-d540.jpgbinary119.9 KB
assets/layout/img/photo-d88.jpgbinary38.8 KB
assets/layout/img/photo-m61660576.jpgbinary39.5 KB
assets/layout/img/photo-m61757972.jpgbinary43.6 KB
assets/layout/layout-check.jsscript21.1 KB
assets/layout/layout.cssother44.4 KB
assets/layout/layout.jsscript14.8 KB
assets/moments/_demo/credits.jsonconfig1.3 KB
assets/moments/_demo/demo.cssother6.8 KB
assets/moments/_demo/in-card.htmlother1.8 KB
assets/moments/_demo/in-page-service.htmlother10.3 KB
assets/moments/_demo/in-page.htmlother9.6 KB
assets/moments/_demo/photo-1049-tall.jpgbinary36.5 KB
assets/moments/_demo/photo-1049.jpgbinary27.9 KB
assets/moments/_demo/photo-1081.jpgbinary39.9 KB
assets/moments/_demo/photo-640.jpgbinary102.7 KB
assets/moments/_demo/photo-702-tall.jpgbinary100.0 KB
assets/moments/_demo/photo-702.jpgbinary80.0 KB
assets/moments/_demo/photo-855.jpgbinary25.4 KB
assets/moments/_demo/photo-887.jpgbinary62.7 KB
assets/moments/closing-lift/demo.htmlother4.3 KB
assets/moments/closing-lift/meta.jsonconfig1.3 KB
assets/moments/closing-lift/moment.cssother2.3 KB
assets/moments/closing-lift/moment.jsscript2.9 KB
assets/moments/counter-rolls/demo.htmlother5.3 KB
assets/moments/counter-rolls/meta.jsonconfig913 B
assets/moments/counter-rolls/moment.cssother718 B
assets/moments/counter-rolls/moment.jsscript3.3 KB
assets/moments/cursor-spotlight/demo.htmlother4.3 KB
assets/moments/cursor-spotlight/meta.jsonconfig1.2 KB
assets/moments/cursor-spotlight/moment.cssother1.2 KB
assets/moments/cursor-spotlight/moment.jsscript2.2 KB
assets/moments/gallery.htmlother8.2 KB
assets/moments/giant-type-pass/demo.htmlother3.6 KB
assets/moments/giant-type-pass/meta.jsonconfig1.0 KB
assets/moments/giant-type-pass/moment.cssother1.5 KB
assets/moments/giant-type-pass/moment.jsscript2.0 KB
assets/moments/headline-arrives/demo.htmlother3.9 KB
assets/moments/headline-arrives/meta.jsonconfig1.0 KB
assets/moments/headline-arrives/moment.cssother1.6 KB
assets/moments/headline-arrives/moment.jsscript2.6 KB
assets/moments/index.jsonconfig21.4 KB
assets/moments/iris-opens/demo.htmlother4.9 KB
assets/moments/iris-opens/meta.jsonconfig1.3 KB
assets/moments/iris-opens/moment.cssother2.0 KB
assets/moments/iris-opens/moment.jsscript4.6 KB
assets/moments/letters-assemble/demo.htmlother4.2 KB
assets/moments/letters-assemble/meta.jsonconfig1.0 KB
assets/moments/letters-assemble/moment.cssother1.1 KB
assets/moments/letters-assemble/moment.jsscript2.9 KB
assets/moments/lib.jsscript10.5 KB
assets/moments/line-carries-colour/demo.htmlother4.4 KB
assets/moments/line-carries-colour/meta.jsonconfig1.4 KB
assets/moments/line-carries-colour/moment.cssother1.6 KB
assets/moments/line-carries-colour/moment.jsscript4.0 KB
assets/moments/lines-rise/demo.htmlother5.1 KB
assets/moments/lines-rise/meta.jsonconfig984 B
assets/moments/lines-rise/moment.cssother1.3 KB
assets/moments/lines-rise/moment.jsscript3.0 KB
assets/moments/liquid-hover/demo.htmlother3.3 KB
assets/moments/liquid-hover/meta.jsonconfig1.4 KB
assets/moments/liquid-hover/moment.cssother457 B
assets/moments/liquid-hover/moment.jsscript13.1 KB
assets/moments/liquid-type/demo.htmlother3.0 KB
assets/moments/liquid-type/meta.jsonconfig1.0 KB
assets/moments/liquid-type/moment.cssother462 B
assets/moments/liquid-type/moment.jsscript4.1 KB
assets/moments/marquee-row/demo.htmlother4.3 KB
assets/moments/marquee-row/meta.jsonconfig867 B
assets/moments/marquee-row/moment.cssother2.0 KB
assets/moments/marquee-row/moment.jsscript2.4 KB
assets/moments/moments.jsscript6.0 KB
assets/moments/photo-chapters/demo.htmlother5.1 KB
assets/moments/photo-chapters/meta.jsonconfig1.8 KB
assets/moments/photo-chapters/moment.cssother6.2 KB
assets/moments/photo-chapters/moment.jsscript6.1 KB
assets/moments/picture-develops/demo-film.htmlother3.9 KB
assets/moments/picture-develops/demo.htmlother4.2 KB
assets/moments/picture-develops/meta.jsonconfig1.4 KB
assets/moments/picture-develops/moment.cssother1.9 KB
assets/moments/picture-develops/moment.jsscript9.2 KB
assets/moments/pinned-chapters/demo.htmlother5.4 KB
assets/moments/pinned-chapters/meta.jsonconfig1.3 KB
assets/moments/pinned-chapters/moment.cssother6.9 KB
assets/moments/pinned-chapters/moment.jsscript4.2 KB
assets/moments/window-parallax/demo.htmlother3.8 KB
assets/moments/window-parallax/meta.jsonconfig913 B
assets/moments/window-parallax/moment.cssother591 B
assets/moments/window-parallax/moment.jsscript1.2 KB
assets/moments/word-highlight/demo.htmlother4.5 KB
assets/moments/word-highlight/meta.jsonconfig1.0 KB
assets/moments/word-highlight/moment.cssother849 B
assets/moments/word-highlight/moment.jsscript2.0 KB
assets/moments/word-rotate/demo.htmlother4.5 KB
assets/moments/word-rotate/meta.jsonconfig948 B
assets/moments/word-rotate/moment.cssother906 B
assets/moments/word-rotate/moment.jsscript2.2 KB
assets/motion/_hover-test.htmlother1.4 KB
assets/motion/demo.htmlother34.1 KB
assets/motion/meta.jsonconfig2.7 KB
assets/motion/motion.cssother25.1 KB
assets/motion/motion.jsscript22.8 KB
assets/starter.htmlother34.2 KB
assets/system.cssother100.5 KB
assets/system.jsscript34.9 KB
assets/ui/_lab/build-index.mjsscript4.0 KB
assets/ui/_lab/loops.htmlother8.7 KB
assets/ui/_lab/object-card.htmlother4.7 KB
assets/ui/_lab/selftest.htmlother3.1 KB
assets/ui/apps/fragment.cssother3.0 KB
assets/ui/apps/fragment.htmlother2.3 KB
assets/ui/apps/fragment.jsscript2.0 KB
assets/ui/apps/meta.jsonconfig1.6 KB
assets/ui/base.cssother15.7 KB
assets/ui/calendar/fragment.cssother4.4 KB
assets/ui/calendar/fragment.htmlother3.4 KB
assets/ui/calendar/fragment.jsscript3.4 KB
assets/ui/calendar/meta.jsonconfig957 B
assets/ui/cards.cssother21.6 KB
assets/ui/cards.htmlother52.3 KB
assets/ui/chat/fragment.cssother3.9 KB
assets/ui/chat/fragment.htmlother5.0 KB
assets/ui/chat/fragment.jsscript2.9 KB
assets/ui/chat/meta.jsonconfig1.1 KB
assets/ui/checklist/fragment.cssother2.2 KB
assets/ui/checklist/fragment.htmlother1.3 KB
assets/ui/checklist/fragment.jsscript1.5 KB
assets/ui/checklist/meta.jsonconfig901 B
assets/ui/code/fragment.cssother2.6 KB
assets/ui/code/fragment.htmlother1.6 KB
assets/ui/code/fragment.jsscript1.7 KB
assets/ui/code/meta.jsonconfig857 B
assets/ui/cursor/fragment.cssother2.4 KB
assets/ui/cursor/fragment.htmlother1.7 KB
assets/ui/cursor/fragment.jsscript3.2 KB
assets/ui/cursor/meta.jsonconfig1.2 KB
assets/ui/diff-review/fragment.cssother13.9 KB
assets/ui/diff-review/fragment.htmlother4.9 KB
assets/ui/diff-review/fragment.jsscript2.4 KB
assets/ui/diff-review/meta.jsonconfig3.9 KB
assets/ui/doc/fragment.cssother2.4 KB
assets/ui/doc/fragment.htmlother1.2 KB
assets/ui/doc/fragment.jsscript3.2 KB
assets/ui/doc/meta.jsonconfig1.2 KB
assets/ui/files/fragment.cssother3.9 KB
assets/ui/files/fragment.htmlother3.3 KB
assets/ui/files/fragment.jsscript3.4 KB
assets/ui/files/meta.jsonconfig1.7 KB
assets/ui/icons/asana.svgother1004 B
assets/ui/icons/calendly.svgother1.8 KB
assets/ui/icons/confluence.svgother2.4 KB
assets/ui/icons/docker.svgother2.2 KB

assets/starter.html

View on GitHub
<!doctype html>
<!-- data-type: the page's type, plan line 1 (SKILL.md section 1): software, product, place or service,
     the same value as <meta name="page-type">.
     data-radius: sharp, soft or round. data-ground: the lit ground behind UI (sand, sky, sage, or
     painting with painterly-landscape). data-buttons: the dealt button look (sections.md, section 2):
     solid, pill, tonal, arrow or block; the button markup stays the same. data-motion: the
     micro-interactions of assets/motion (references/motion.md); keep it.
     lang: the language the page is written in, from the brief (or its market when the brief does not say): "de" for
     a German page, "en" for an English one; screen readers read in it and system.css hyphenates headings by it. -->
<html lang="[en]" data-type="[software]" data-radius="soft" data-ground="sand" data-buttons="solid" data-motion>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
<title>[Name]: [what it is] for [who or where]</title>
<meta name="description" content="[One sentence: what it is, for whom or where, the main benefit.]">
<!-- the head of a shared link and the tab (references/system.md, Head): the title and description above, never the
     same words; the card picture is the hero's own tile from shoot.mjs (tiles/desktop-sec-01-a.jpg) copied beside
     the page as share.jpg; the icon is the client's logo, else the dealt mark as favicon.svg; theme-color is the
     page ground (--p-bg as start.mjs prints it). canonical only once the client's domain is known: until then the
     line stays a comment and the report lists it. -->
<meta property="og:type" content="website">
<meta property="og:title" content="[Name]: [what it is] for [who or where]">
<meta property="og:description" content="[The description above, or a shorter line of it]">
<meta property="og:image" content="[share.jpg]">
<meta name="twitter:card" content="summary_large_image">
<link rel="icon" href="[favicon.svg]" type="image/svg+xml">
<meta name="theme-color" content="[--p-bg]">
<!-- <link rel="canonical" href="https://[the client's domain]/"> -->
<!-- the kind decides every effect and motion allowance (SKILL.md section 1: data-type and page-type
     carry the page type, site-kind the kind). software: an app, SaaS, AI, developer tool or fintech
     (type software, site-kind software); a app (type software, site-kind devtools); hardware or a
     tech device (type product, site-kind tech). Every other product or brand (type product), a
     service firm or studio (type service) and a place (type place) are site-kind other:
     photographs, type and flat colour; their motion is the hero's entrance, the hover layer and one dealt photo- or type-led moment. A place adds
     <meta name="page-kind" content="place">. -->
<meta name="site-kind" content="[software]">
<meta name="page-type" content="[software]">
<!-- Replace the next line and the :root block with the block from: node <skill>/scripts/start.mjs css ...
     (Google Fonts links, system.css and the :root palette). Keep the order: system.css, ui/cards.css,
     motion/motion.css, backgrounds/backgrounds.css, layout/layout.css, icons/icon.css (the .ic-tile
     and .ic-ink rules: a black mark such as GitHub or Apple needs them on a dark ground). -->
<link rel="stylesheet" href="assets/system.css">
<link rel="stylesheet" href="assets/ui/cards.css">
<link rel="stylesheet" href="assets/motion/motion.css">
<link rel="stylesheet" href="assets/backgrounds/backgrounds.css">
<link rel="stylesheet" href="assets/layout/layout.css">
<link rel="stylesheet" href="assets/icons/icon.css">
<style>:root { /* --p-* palette, --font-* and --display-* exactly as start.mjs prints them (it alone deals the type) */ }</style>
<!-- the UI fragments' own CSS, linked here so a fragment is drawn with scripts off or before they run (ui.js only
     adds what is missing: it skips a stylesheet that is already linked). One line per fragment the page uses
     (assets/ui/<name>/fragment.css); delete the line when the page uses none. -->
<link rel="stylesheet" href="assets/ui/base.css">
<link rel="stylesheet" href="assets/ui/[name]/fragment.css">
<!-- a diagram card (assets/diagrams, references/diagrams.md): its stylesheet here and mount.js after the
     other scripts; delete both lines when the page has no diagram -->
<link rel="stylesheet" href="assets/diagrams/diagram.css">
<!-- the hero's entrance (references/motion.md): set before the first paint, after the stylesheets, so the hero's
     words wait for motion.js instead of flashing (its picture never waits); the 700ms mark fades them in if the
     script is late. Keep it on every page. -->
<script>document.documentElement.classList.add('m-enter');setTimeout(()=>document.documentElement.classList.add('m-enter-done'),700)</script>
<!-- the grounds' page tokens before the first paint (assets/backgrounds; plain, not deferred) -->
<script src="assets/backgrounds/backgrounds.js"></script>
<!-- moments (every kind is dealt one, two on a long page: moments.mjs pick --page <kind>): the guard, then one
     preload for the core, its lib and each dealt moment (assets/moments/<id>/moment.js). system.js mounts them.
<script>document.documentElement.classList.add('mo-js');setTimeout(()=>document.documentElement.classList.add('mo-safe'),2500)</script>
<link rel="modulepreload" href="assets/moments/moments.js">
<link rel="modulepreload" href="assets/moments/lib.js">
<link rel="modulepreload" href="assets/moments/[dealt id]/moment.js">
-->
<!-- page CSS: only what sits inside a visual and the kit lacks, and one --p-h per card group -->
<style>
  #features .panel { --p-h: 300px; }
  /* a phone stacks the four tiles into the section's two screens; the chat drops its day line and fades over
     40px, so its question and the answer's first line stand clear of the fade */
  @media (max-width: 639px) { #features .panel { --p-h: 180px; } #features .ui-chat__day { display: none; } #features .stage { --fade-h: 40px; } }
</style>
</head>
<!-- grounds (tech only; assets/backgrounds/pick.mjs deals 0 to 2 section grounds, never a page ground):
     a section ground is one class on its <section>; bg-topglow goes on a wrapper round the nav and the
     hero only when the deal lists it. On kind other (product, service, place: cafes, shops, studios) no
     ground class at all, and no data-ground on <html>: flat colour and photographs. -->
<body>
<!-- type: [software | product | place | service]
     deal: hero [..], nav [..], close [..], footer [..], rhythm [..], buttons [..], mark [..], grounds [..]
     moments: [dealt ids and their sections]
     The page is a stack of screens (layout-v4.md): the hero alone on the first, every other section
     and the footer exactly one or two (style="--h: 2" or class="g2"), its h2 first. Plan the content
     of each before building: one screen holds 708px of content at 1440x900.
     Every [bracket] in this file is replaced before the page ships: system.js outlines any left in red.
     One page: every link goes to an #id on it (a section's id, #contact, #top for the logo); Privacy,
     Terms and Imprint go to small pages you write (privacy.html ...) or are deleted (sections.md). -->

<!-- NAV (references/sections-library.md): one fixed, opaque bar on the page's .wrap. The dealt type is
     a class: nav-mega and nav-cards "nav", nav-centre "nav nav--centre", nav-split "nav nav--split";
     add nav--tone for the bar on the page's inverse ground. At least one word opens a full-width
     panel on hover and goes to its section on click; on a phone system.js turns the bar into a sheet.
     aria-current="page" marks the word of the page you are on, on an inner page only (pricing.html);
     a one-page site leaves it off every word.
     The logo: the client's own SVG; without one, the dealt mark and the name in the display face:
     arc, ring, stack, dots: <span class="mark" data-mark="arc" aria-hidden="true"></span>
     initial: <span class="mark mark--initial" aria-hidden="true">K</span> (the name's first letter)
     wordmark: no mark, the name alone. The footer repeats it.
     The skip link is the bar's first child and the page's first stop for the Tab key: hidden until focused, then
     shown over the logo (system.css .skip-link); its words in the page's language ("Zum Inhalt" on a German page). -->
<header class="nav">
  <div class="wrap nav__bar">
    <a class="skip-link" href="#top">Skip to content</a>
    <a class="nav__logo" href="#top"><span class="mark" data-mark="[dealt mark]" aria-hidden="true"></span>[Name]</a>
    <nav class="nav__links" aria-label="Main">
      <div class="nav__item">
        <a class="nav__link" href="#[section id]">[Word] <svg class="chev" viewBox="0 0 12 12" aria-hidden="true"><path d="M3 4.5l3 3 3-3" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/></svg></a>
        <div class="nav__menu">
          <div class="wrap grid">
            <!-- nav-mega: two or three link columns and one menu card. nav-cards and nav-split: three or
                 four a.menu-card.span-4 (or .span-3), each a .panel holding the client's photograph
                 (<img class="frame__img">) or one fragment at its corner, over a title and one line. -->
            <div class="menu-col span-3">
              <p class="t-label">[Group]</p>
              <a href="#[section id]">[Item]<span>[What it does, five words]</span></a>
              <a href="#[section id]">[Item]<span>[What it does, five words]</span></a>
              <a href="#[section id]">[Item]<span>[What it does, five words]</span></a>
            </div>
            <div class="menu-col span-3">
              <p class="t-label">[Group]</p>
              <a href="#[section id]">[Item]<span>[What it does, five words]</span></a>
              <a href="#[section id]">[Item]<span>[What it does, five words]</span></a>
            </div>
            <a class="menu-card span-3 start-10" href="#[section id]">
              <div class="panel"><img class="frame__img" src="[photo or screen]" alt="[what it shows]"></div>
              <span class="t-card">[What is new]</span>
              <span class="t-small muted">[One line]</span>
            </a>
          </div>
        </div>
      </div>
      <div class="nav__item"><a class="nav__link" href="#[section id]">[Word]</a></div>
      <div class="nav__item"><a class="nav__link" href="#[section id]">[Word]</a></div>
      <div class="nav__item"><a class="nav__link" href="#[section id]">[Word]</a></div>
    </nav>
    <!-- the main action is the one button; a plain word before it only for something the client really
         has (Sign in for an app with accounts, Gift cards it sells), else delete it -->
    <div class="nav__actions">
      <a class="nav__link" href="#[section id]">[Second action the client has]</a>
      <a class="btn btn--primary" href="#[section id]">[Main action]</a>
    </div>
    <button class="nav__toggle" type="button" aria-expanded="false" aria-label="Menu">
      <svg width="18" height="18" viewBox="0 0 18 18" aria-hidden="true"><path d="M2 5h14M2 13h14" stroke="currentColor" stroke-width="1.6" stroke-linecap="round"/></svg>
    </button>
  </div>
</header>

<main id="top">
  <!-- HERO: exactly the first screen; the fixed header lies over its top. Paste the dealt hero from
       assets/layout/hero-<id>.html (layout/deal.mjs deals it; heroes.json has its numbers) in place of
       this one, keeping its shape: section.hero > .wrap > .hero-text (+ one docked strip at most), and give it
       data-enter (its one entrance on load, motion.md; the head line above makes it run).
       A place's hero is never dealt: it is always assets/layout/hero-place.html (Recipe 3, the
       photograph under the header with nothing on it, the words under it on the ground).
       This default is the split: the words on span-6, the client's photograph on span-6 start-7 (the
       page's split pair, the same on every split: 6/6, 5/7 or 7/5), as tall as the hero's content box. The primary button carries the drawn arrow (svg.m-arrow). -->
  <section class="hero hero--split" data-enter aria-labelledby="hero-h">
    <div class="wrap">
      <div class="hero-text grid hero-split">
        <div class="hero-copy span-6">
          <!-- optional notice line: one line with a number (changed hours, a delivery cut-off) -->
          <p class="hero-notice">[One line with a number]</p>
          <h1 id="hero-h">[What it is] [for whom or where]</h1>
          <p class="t-lead">[How it works and the main benefit, with one hard fact.]</p>
          <div class="btn-row">
            <a class="btn btn--primary" href="#[section id]">[Main action]<svg class="m-arrow" viewBox="0 0 12 12" aria-hidden="true"><path class="m-arrow__stem" d="M1 6h8"/><path class="m-arrow__head" d="M4.5 2.5 8 6l-3.5 3.5"/></svg></a>
            <a class="btn btn--secondary" href="#[section id]">[Second action]</a>
          </div>
          <!-- three short facts at the foot of the column, on the picture's bottom line (desktop only); on a
               tech page one of them may count up once on load: <dd data-m-count>[1,240]</dd> -->
          <dl class="hero-facts">
            <div><dt>[Label]</dt><dd>[Fact]</dd></div>
            <div><dt>[Label]</dt><dd>[Fact]</dd></div>
            <div><dt>[Label]</dt><dd>[Fact]</dd></div>
          </dl>
        </div>
        <!-- a photograph of the client's work, place or product (its own frame: no caption under it);
             or a window, a phone or an object as the dealt hero says -->
        <div class="hero-visual frame frame--photo span-6 start-7">
          <img class="frame__img" src="[photo]" alt="[what it shows]" fetchpriority="high" data-source="[client | library | shoot]" data-subject="[what it is of]">
        </div>
      </div>
    </div>
  </section>

  <!-- SECTIONS: the type's plan (references/sections.md), each built to its recipe and planned to its
       screens. One example: the 2x2 of feature tiles, two boxes deep (.card--open: the words on the
       page ground, the panel under them), as two screens (.g2): row 1 the h2 and the first two tiles,
       row 2 the next two, starting --padt under the second screen's top. On a phone a section keeps
       its desktop count unless it says otherwise: style="--hm: 2" or class="g2m" when its stacked
       content needs two phone screens (check at 390x844: nothing may run into the next section).
       Each fragment is pasted from
       assets/ui/<name>/fragment.html and rewritten, at its recipe's place; one loop in the group
       (data-ui-loop); the others hold their finished picture and play while the pointer is on them. -->
  <section class="section g2" id="features" aria-labelledby="features-h">
    <div class="wrap">
      <div class="group">
        <div class="section-head">
          <h2 id="features-h">[What it does.] <span class="muted">[One sentence that sums up the four.]</span></h2>
        </div>
        <div class="grid">
          <article class="card card--row card--open span-6">
            <h3>[Verb + object]</h3>
            <p>[One or two short sentences with one concrete detail.]</p>
            <div class="panel" data-fx="[card effect: a tech page only]" data-fx-seed="21">
              <div class="stage stage--fade-b"><div class="at-rise fit" style="--fit-max:400px;--ax:max(24px, 50% - 200px);--ay:48px;--ay-sm:16px" data-ui-loop>
                <div class="ui ui-panel ui-chat" data-ui="chat">
                  <div class="ui-head"><span class="ui-agent" aria-hidden="true"></span><div class="ui-title">[Name]</div><span class="ui-chat__online">Online</span><span class="ui-spacer"></span></div>
                  <div class="ui-chat__body">
                    <div class="ui-chat__day">[Today, 9:41]</div>
                    <div class="ui-msg ui-msg--me" data-chat-q><span class="ui-msg__text">[A real customer question]</span></div>
                    <div class="ui-msg ui-msg--bot" data-chat-a>
                      <span class="ui-agent ui-msg__av" aria-hidden="true"></span>
                      <span class="ui-msg__col">
                        <span class="ui-chat__typing" aria-hidden="true"><i></i><i></i><i></i></span>
                        <span class="ui-chat__answer">[The answer in two lines, with <b>one real detail</b>.]</span>
                        <span class="ui-chat__srcs"><span class="ui-chat__src"><svg class="ui-icon" viewBox="0 0 16 16"><path d="M4 2.5h5l3 3v8H4z"/><path d="M9 2.5v3h3"/></svg>[Its source]</span></span>
                      </span>
                    </div>
                  </div>
                  <div class="ui-chat__input"><span class="ui-chat__ph">Write a message</span><span class="ui-chat__send" aria-hidden="true"><svg viewBox="0 0 16 16" width="14" height="14"><path d="M8 13V3.5M3.8 7.5 8 3.3l4.2 4.2" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round"/></svg></span></div>
                </div>
              </div></div>
            </div>
          </article>
          <!-- the second tile of row 1: a different fragment (notify, files with real icons, a diagram
               from assets/diagrams) or the client's photograph in the panel (<img class="frame__img">) -->
          <article class="card card--row card--open span-6">
            <h3>[Verb + object]</h3>
            <p>[One or two short sentences with one concrete detail.]</p>
            <div class="panel"><img class="frame__img" src="[photo or screen]" alt="[what it shows]" loading="lazy"></div>
          </article>
        </div>
      </div>
      <div class="grid">
        <!-- the third and fourth tiles, built like the first two, the same --p-h, so both rows match; a section
             with only two tiles drops this row and the g2 class (one screen) -->
          <article class="card card--row card--open span-6">
            <h3>[Verb + object]</h3>
            <p>[One or two short sentences with one concrete detail.]</p>
            <div class="panel"><img class="frame__img" src="[photo or screen]" alt="[what it shows]" loading="lazy"></div>
          </article>
          <article class="card card--row card--open span-6">
            <h3>[Verb + object]</h3>
            <p>[One or two short sentences with one concrete detail.]</p>
            <div class="panel"><img class="frame__img" src="[photo or screen]" alt="[what it shows]" loading="lazy"></div>
          </article>
      </div>
    </div>
  </section>

  <!-- FAQ: every answer open, always (no accordion): <div class="faq"><div class="faq__item"><h3>[Question]</h3>
       <p>[Answer in one or two sentences.]</p></div> ...</div>, the questions people really ask.
       QUOTE-STAT: a quote with the speaker's face beside one big number, still. One screen; merge it into
       the section above when alone it holds under 495px. A number that counts up (data-m-count,
       motion.js) is a tech page's one count, in its hero only (a fact in .hero-facts), never in a card,
       a panel or a section further down; a count, never a year or a price. -->
  <template data-part="quote-stat">
    <section class="section" id="[section id]" aria-labelledby="[quote id]">
      <div class="wrap">
        <div class="section-head"><h2 id="[quote id]">[Who uses it, plainly]</h2></div>
        <div class="grid fill">
          <figure class="quote span-8">
            <blockquote>[What the customer said, in their words, at most 40 words.]</blockquote>
            <div class="person"><img src="[portrait]" alt="[Full name]" width="40" height="40"><span><span class="person__name">[Full name]</span><span class="person__role">[Role], [Company]</span></span></div>
          </figure>
          <div class="stat-aside span-3 start-10">
            <p class="t-stat">[64%]</p>
            <p class="t-small muted">[What the number counts, over what time]</p>
          </div>
        </div>
      </div>
    </section>
  </template>

  <!-- PEEK-LIST (a place's or a service's moment): rows beside one photograph that changes at once to
       the row under the pointer, the focus or a tap (system.js). Text left, the photograph on the split
       line; every row's words on the left line (the row on show is marked by a dot after its name).
       A price, date or place the brief does not give carries data-assumed on its own element
       (<span class="rows__value" data-assumed>3.60 €</span>): the checker lists each one for the report. -->
  <template data-part="peek-list">
    <section class="section" id="[section id]">
      <div class="wrap">
        <div class="section-head"><h2>[What the rows are: rooms, the house, services]</h2><p>[One line.]</p></div>
        <div class="grid grid--top fill" data-peek>
          <ul class="rows span-6">
            <li data-peek-to="[key 1]" tabindex="0"><span class="rows__name">[Name]</span><p>[One line with one concrete detail.]</p><span class="rows__value">[Price, hours or size]</span></li>
            <li data-peek-to="[key 2]" tabindex="0"><span class="rows__name">[Name]</span><p>[One line with one concrete detail.]</p><span class="rows__value">[Price, hours or size]</span></li>
          </ul>
          <div class="frame frame--photo frame--fill span-6 start-7">
            <img class="frame__img" data-peek-for="[key 1]" src="[photo of row 1]" alt="[what it shows]">
            <img class="frame__img" data-peek-for="[key 2]" src="[photo of row 2]" alt="[what it shows]" hidden>
          </div>
        </div>
      </div>
    </section>
  </template>

  <!-- VISIT (a place, screen 2, directly after the hero; sections.md): system.css's .visit, on the container's lines.
       Open type by default (no box). The full page puts it in a split column beside the client's photograph
       (.visit.visit--card on span-6, the photograph on span-6 start-7: the panel on --g-alt, 1024px and up only).
       The short page adds .visit--cols (address, hours and access as three columns, no rows) and puts the menu
       as .rows under it in the same section. Street and district only; a phone only when the brief gives one;
       at most two rows under the columns.
       The way there: "Get directions" only with a street from the brief; with a district and no street the link
       says "See the area" (?query=district+town); with only a town, no map link at all (a search for a whole
       city shows nobody the door).
       Hours the brief does not give are assumed: data-assumed on the dl (the report lists them), and then no
       open-now line (delete the <p data-open-now>): system.js never says "Open now" from assumed hours. -->
  <template data-part="visit">
    <section class="section" id="visit" data-place="visit" aria-label="Visit">
      <div class="wrap">
        <div class="visit">
          <div class="visit__head"><p class="t-label muted">Visit</p><p class="t-small" data-open-now></p></div>
          <div class="visit__cols">
            <div class="visit__col stack-4">
              <address class="visit__address">[Street]<br>[District]</address>
              <a class="link" href="https://www.openstreetmap.org/search?query=[street%20district%20city]">Get directions</a>
            </div>
            <div class="visit__col">
              <!-- data-tz: the venue's time zone; system.js marks today's row there. Assumed hours:
                   <dl class="hours" data-tz=".." data-assumed> -->
              <dl class="hours" data-tz="[Europe/Berlin]"><dt>[Mon to Fri]</dt><dd>[8 to 18]</dd><dt>[Sat]</dt><dd>[9 to 16]</dd><dt>Sun</dt><dd>Closed</dd></dl>
            </div>
          </div>
          <ul class="visit__rows">
            <li><span>[Access]</span><span>[Step-free at the front door]</span></li>
          </ul>
        </div>
      </div>
    </section>
  </template>

  <!-- DRAWING: only a dimension figure beside a product's specs (sections-library.md): the real side
       view with its measured spans, one SVG unit a millimetre, the viewBox the product plus 6% all
       round, --ar its width over height; every real part a g.part (lines .ln, a filled part .fill,
       one part .acc in the accent); two or three dimension lines (.dim) whose figures are the
       spans, placed in percent of the figure. Never the picture of a product that has no photograph
       (that is a shot ladder or a short page, sections.md, never a drawing), never hardware drawn as
       an SVG, clip-art or an icon. -->
  <template data-part="drawing">
    <figure class="drawing" style="--ar: [viewBox width / height]" role="img" aria-label="[The product, from the side, its main sizes]">
      <svg viewBox="0 0 [width] [height]" aria-hidden="true">
        <g class="part"><path class="fill" d="[a body or a top]"/></g>
        <g class="part"><path class="ln" d="[a frame, a leg, a strap]"/></g>
        <g class="part"><path class="acc" d="[the one part in the accent]"/></g>
        <g class="dim"><path d="[M x1 y H x2: the line]"/><path d="[the two end ticks]"/></g>
      </svg>
      <span class="drawing__dim" style="left: [x]%; top: [y]%">[1,400 mm]</span>
    </figure>
  </template>
</main>

<!-- FOOTER.CLOSING: the close and the footer in one last screen (system.css). Its .wrap holds exactly
     two children: the dealt close (row 1) and the links (row 2). The ground is dealt too: the page's
     ground (this one), "footer closing footer--dark ground-inverse", or "footer closing
     footer--statement" (the lit ground, full bleed). A place swaps row 2 for links-visit below.
     The close repeats the main action word for word; its h2 is eight words or fewer.
     Links go to the page's sections (#ids) and #contact; Privacy, Terms (and Imprint only when the
     brief gives the details) go to pages you write, never left dead. The legal row ends with the
     credits line when the page shows photographs that are not the client's: one short line naming the
     sources actually used, which opens the list. No address the brief does not give: street and
     district only, never a house number, a postcode, a phone in a real format or a register number. -->
<footer class="footer closing" id="contact" aria-labelledby="close-h">
  <div class="wrap">
    <!-- close--type (this one): the h2 and a line, the big button across the .wrap. Others below. -->
    <div class="closing__cta close--type">
      <div class="section-head">
        <h2 id="close-h">[The main action, plainly]</h2>
        <p>[One line: the trial, the price or the reply time.]</p>
      </div>
      <a class="btn btn--primary btn--xl btn--wide" href="#[section id]">[Main action]<svg class="m-arrow" viewBox="0 0 12 12" aria-hidden="true"><path class="m-arrow__stem" d="M1 6h8"/><path class="m-arrow__head" d="M4.5 2.5 8 6l-3.5 3.5"/></svg></a>
    </div>
    <div class="closing__links">
      <div class="grid">
        <div class="span-4 stack-4">
          <a class="nav__logo" href="#top"><span class="mark" data-mark="[dealt mark]" aria-hidden="true"></span>[Name]</a>
          <p class="footer__lede">[What the company does, in one plain line.]</p>
        </div>
        <div class="span-2 footer__col"><h3>[Nav word]</h3><ul><li><a href="#[section id]">[Link]</a></li><li><a href="#[section id]">[Link]</a></li></ul></div>
        <div class="span-2 footer__col"><h3>[Nav word]</h3><ul><li><a href="#[section id]">[Link]</a></li><li><a href="#[section id]">[Link]</a></li></ul></div>
        <div class="span-2 footer__col"><h3>[Nav word]</h3><ul><li><a href="#[section id]">[Link]</a></li><li><a href="#[section id]">[Link]</a></li></ul></div>
        <div class="span-2 footer__col"><h3>[Nav word]</h3><ul><li><a href="#[section id]">[Link]</a></li><li><a href="#contact">Contact</a></li></ul></div>
      </div>
      <div class="footer__legal">
        <span>&copy; 2026 [Company] &nbsp; <a href="privacy.html">Privacy</a> &nbsp; <a href="terms.html">Terms</a></span>
        <div class="socials"><!-- empty unless the brief gives the client's accounts: node <skill>/scripts/icons.mjs
             get si:x si:instagram --mono --out assets/icons prints one <span class="icon-mono"> per mark;
             put each in <a href=".." aria-label="..">..</a> --></div>
        <a class="credits" href="credits.html">Photographs via [sources used]</a>
      </div>
    </div>
  </div>
</footer>

<template data-part="close-photo">
  <!-- row 1 as close--photo: the head row, then the client's photograph down to the links -->
  <div class="closing__cta close--photo">
    <div class="section-head--split">
      <div><h2 id="close-h">[The main action, plainly]</h2><p class="t-lead">[One line with the price or the hours.]</p></div>
      <a class="btn btn--primary" href="#[section id]">[Main action]<svg class="m-arrow" viewBox="0 0 12 12" aria-hidden="true"><path class="m-arrow__stem" d="M1 6h8"/><path class="m-arrow__head" d="M4.5 2.5 8 6l-3.5 3.5"/></svg></a>
    </div>
    <div class="close__media"><img src="[a second photograph, never the hero's]" alt="[what it shows]" loading="lazy" data-source="[client | library | shoot]" data-subject="[what it is of]"></div>
  </div>
</template>

<template data-part="close-word">
  <!-- row 1 as close--word: the h2 and the button, then the name across the .wrap -->
  <div class="closing__cta close--word">
    <div class="section-head--split">
      <div><h2 id="close-h">[The main action, plainly]</h2><p class="t-lead">[One line: the trial or the reply time.]</p></div>
      <a class="btn btn--primary" href="#[section id]">[Main action]<svg class="m-arrow" viewBox="0 0 12 12" aria-hidden="true"><path class="m-arrow__stem" d="M1 6h8"/><path class="m-arrow__head" d="M4.5 2.5 8 6l-3.5 3.5"/></svg></a>
    </div>
    <p class="close__word" aria-hidden="true">[Name]</p>
  </div>
</template>

<template data-part="links-visit">
  <!-- row 2 on a place (footer closing footer--visit): where it is, set large, with the way there;
       the hours from the split line; one row of the nav's words. Street and district only. The link's words
       follow the visit block's: Get directions with a street, See the area with a district only, none with a town. -->
  <div class="closing__links">
    <div class="grid">
      <div class="span-6 stack-4">
        <address class="footer__address">[Street], [district]</address>
        <p><a class="link" href="https://www.openstreetmap.org/search?query=[street%20district%20city]">Get directions</a></p>
      </div>
      <div class="span-6 start-7 stack-4">
        <h3>Opening hours</h3>
        <!-- data-tz: the venue's time zone; system.js marks today's row there. Never .is-today by hand. -->
        <dl class="hours" data-tz="[Europe/Berlin]"><dt>[Mon to Fri]</dt><dd>[8 to 18]</dd><dt>[Sat]</dt><dd>[9 to 16]</dd><dt>Sun</dt><dd>Closed</dd></dl>
      </div>
    </div>
    <div class="footer__legal">
      <span>&copy; 2026 [Company] &nbsp; <a href="privacy.html">Privacy</a></span>
      <a class="credits" href="credits.html">Photographs via [sources used]</a>
    </div>
  </div>
</template>

<template data-part="booking-form">
  <!-- BOOKING FORM (references/system.md, Forms; sections-library.md booking-form): every field with a label you can
       see, the type, autocomplete and inputmode that fit it, its error line kept hidden until a submit fails
       (system.js shows it, sets aria-invalid and moves the focus to the first field to fix). data-endpoint: the
       address the client's form service gives, the only thing that may show data-sent; without one, action is a
       mailto: on .example (a stand-in the report lists) and no success line is shown. data-sent names what was sent
       in the button's own words ("Request a table" -> "Your table request is in. We reply within a day."). Six fields
       at most; never a modal. -->
  <form class="form" action="mailto:[hello@brand.example]" method="post" enctype="text/plain" data-endpoint="" data-sent="[Your table request is in. We reply within a day.]" novalidate>
    <div class="field"><label for="f-name">[Name]</label>
      <input id="f-name" name="name" type="text" autocomplete="name" required aria-describedby="f-name-err">
      <p class="field__error" id="f-name-err" hidden>[Write the name the booking is under.]</p></div>
    <div class="field"><label for="f-email">[Email]</label>
      <input id="f-email" name="email" type="email" autocomplete="email" inputmode="email" required aria-describedby="f-email-err">
      <p class="field__error" id="f-email-err" hidden>[Write an email address with an @, like name@example.com.]</p></div>
    <div class="field"><label for="f-date">[Date]</label>
      <input id="f-date" name="date" type="text" autocomplete="off" required aria-describedby="f-date-err">
      <p class="field__error" id="f-date-err" hidden>[Write the day you want to come.]</p></div>
    <div class="field"><label for="f-guests">[Guests]</label>
      <input id="f-guests" name="guests" type="text" inputmode="numeric" autocomplete="off" required aria-describedby="f-guests-err">
      <p class="field__error" id="f-guests-err" hidden>[Write how many people, as a number.]</p></div>
    <div class="btn-row"><button class="btn btn--primary" type="submit">[Request a table]</button></div>
    <p class="form__status" role="status" data-form-status></p>
    <p class="t-small muted">[We reply within a day.]</p>
  </form>
</template>

<!-- ACTION BAR (a place: required; other types may use it): fixed at the phone's foot, the main
     action, or Get directions and Book, as the brief allows. Delete it on other pages. Keep it a child of body,
     after the footer: system.js shows it once the hero's button has scrolled away and hides it while the screen shows one of
     its actions (the nav's button sits in the sheet), so add no script for it; never a third copy of an action in
     a notice or a card.
<nav class="actionbar" aria-label="Quick actions">
  <a class="btn btn--primary" href="#[section id]">[Main action]</a>
</nav>
-->

<!-- nav, tabs, highlights, effects, fragments, moments, pause buttons and the guards: system.js;
     hovers, presses, the nav's current word, tabs, focus, counts and card loops: motion.js;
     the heroes' small moments: layout.js. Add no script for these. -->
<script type="module" src="assets/system.js"></script>
<script type="module" src="assets/motion/motion.js"></script>
<script type="module" src="assets/layout/layout.js"></script>
<script type="module" src="assets/diagrams/mount.js"></script>
<!-- a print object (data-print) loads its script after these (assets/objects/_print-core/README.md):
<script type="module" src="assets/objects/_print-core/auto.js"></script>
     a big scene (data-big-scene) loads assets/scenes/scenes.js instead (references/scenes.md) -->
</body>
</html>
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall