taste-lint 0.0.1

package/data/rules/copywriting/copywriting-punctuation-tics.yaml

@@ -0,0 +1,35 @@
+# One of the 21 AI-writing checks Every ran with Jev (Mike Taylor, "Jev judged
+# everything I've written in 0.7 seconds", 15 Sep 2026). The question is the
+# published wording; the second sentence says what to ignore.
+# Candidate list from EveryInc/compound-writing skills/cw-ai-check/SKILL.md, lexicon rows on sentence patterns.
+id: copywriting-punctuation-tics
+title: Overuses dashes, colons or parenthetical asides in a patterned way
+categoryId: machine-prose
+source:
+  repo: every.to
+  path: https://typesafe-parallel-judgment-lab.every-4573.chatgpt.site/downloads/typesafe-lab-source.zip (scripts/run-ai-checker.mjs)
+  line: 1
+  ruleId: punctuation_tics
+unit: [paragraph]
+question:
+  context: [docType]
+  instructions: >-
+    Does the writing overuse em dashes, colons, or parenthetical asides in a patterned way? Ignore a single aside, and punctuation inside code or quoted material.
+  criteria:
+    true:
+      what: A dash, colon or parenthesis in nearly every sentence, each doing the same job.
+      examples:
+        - "The plan was simple (or so we thought): ship fast, learn faster (and cheaper), then scale: the usual story."
+        - "Design is a conversation: with the user, with the material (and with the budget), with the past."
+    false:
+      what: Punctuation that varies with the sentence.
+      examples:
+        - "We planned to ship fast and learn from the first hundred users. It took three months longer than that."
+        - "Design is a conversation with the user. The budget joins it later, usually uninvited."
+thresholds: { review: 0.4, act: 0.75 }
+severity: minor
+fix:
+  hint: >-
+    Rewrite two of the asides as sentences. Keep the one that earns its place.
+status: review-only
+handWritten: [question, fix, thresholds]

package/data/rules/copywriting/copywriting-reader-first.yaml

@@ -0,0 +1,59 @@
+# Sourced from mblode/taste-training headline-analyzer.tsx (WHAT signals) and the lesson
+# lead-with-the-readers-world.mdx (Why, How, What).
+id: copywriting-reader-first
+title: Headline that leads with what the product is
+categoryId: reader-first-framing
+source:
+  {
+    repo: mblode/taste-training,
+    path: apps/web/components/demos/copywriting/headline-analyzer.tsx,
+    line: 58,
+  }
+unit: [heading, jsx-text]
+mechanical:
+  phrases:
+    [
+      platform,
+      software,
+      solution,
+      suite,
+      all-in-one,
+      introducing,
+      meet,
+      is a,
+      is the,
+      is an,
+      we built,
+      we made,
+      the tool,
+      a tool,
+    ]
+question:
+  context: [docType, headingAbove]
+  instructions: >-
+    The TEXT is a headline or hero line on a page selling or introducing a product. Return true when it opens by naming what the product is (a platform, a tool, a solution, "Introducing X") before saying why that matters to the reader. Return false when it leads with the reader's problem or outcome, when the DOC TYPE is documentation, reference or a lesson where naming the thing first is correct, or when it is not a headline.
+  criteria:
+    true:
+      what: What-first headline.
+      examples:
+        - "Introducing Northwind, the all-in-one platform for modern teams"
+        - "A collaboration tool for growing companies"
+    false:
+      what: Why-first, or a context where What belongs first.
+      examples:
+        - "Roll any file back to how it was an hour ago"
+        - "Stop losing Friday afternoons to merge cleanup"
+        - "The systemOne endpoint accepts state and questions"
+thresholds: { review: 0.4, act: 0.75 }
+severity: minor
+fix:
+  hint: >-
+    Climb the ladder: why this matters to the reader, then how, then what. Let What lead only where the reader already holds the motivation.
+preconditions:
+  {
+    notInCode: true,
+    role: [heading],
+    docType: [marketing, ui, unknown, lesson],
+  }
+status: review-only
+handWritten: [mechanical, question, fix, thresholds, preconditions]

package/data/rules/copywriting/copywriting-register-shift.yaml

@@ -0,0 +1,58 @@
+# Sourced from mblode/taste-training sweep-runner.tsx (sweep 2, Voice).
+id: copywriting-register-shift
+title: Formal or slangy register breaking the product voice
+categoryId: machine-prose
+source:
+  {
+    repo: mblode/taste-training,
+    path: apps/web/components/demos/copywriting/sweep-runner.tsx,
+    line: 84,
+  }
+unit: [paragraph, heading, jsx-text]
+mechanical:
+  phrases:
+    [
+      we are pleased to,
+      we're stoked,
+      furthermore,
+      moreover,
+      gonna,
+      ain't,
+      henceforth,
+      thus,
+      utilize,
+      utilise,
+      herein,
+      aforementioned,
+      kindly,
+      per our,
+      whilst,
+    ]
+question:
+  context: []
+  instructions: >-
+    Read the TEXT as product or documentation copy. Return true when a word or phrase belongs to a clearly different register from plain spoken English: academic connectors (furthermore, moreover, thus), legal or corporate formality (henceforth, we are pleased to, kindly, utilize), or slang (gonna, stoked). Return false when the TEXT is consistently plain, when the formal word is a technical term with no plain equivalent, or when the TEXT quotes or teaches about register.
+  criteria:
+    true:
+      what: A register shift inside otherwise plain copy.
+      examples:
+        - "Furthermore, we are pleased to announce dark mode."
+        - "Utilize the dashboard to facilitate deployment."
+        - "We're stoked to have you. Henceforth your data syncs automatically."
+    false:
+      what: One plain register throughout, or discussion of the words.
+      examples:
+        - "Dark mode is here. Turn it on in Settings."
+        - "Use the dashboard to start your deployment."
+        - "Academic connectors like moreover signal a tone shift."
+severity: minor
+fix:
+  hint: Rewrite in the voice the rest of the page uses. Use "use" not "utilize", "so" not "thus", and drop the corporate opener.
+preconditions:
+  {
+    notInCode: true,
+    docType:
+      [tutorial, howto, reference, explanation, lesson, marketing, ui, unknown],
+  }
+status: review-only
+handWritten: [mechanical, question, fix]

package/data/rules/copywriting/copywriting-repetitive-transitions.yaml

@@ -0,0 +1,48 @@
+# One of the 21 AI-writing checks Every ran with Jev (Mike Taylor, "Jev judged
+# everything I've written in 0.7 seconds", 15 Sep 2026). The question is the
+# published wording; the second sentence says what to ignore.
+# Candidate list from EveryInc/compound-writing skills/cw-ai-check/SKILL.md, category 7 (formal transitions).
+id: copywriting-repetitive-transitions
+title: Repeatedly uses formal or formulaic transitions
+categoryId: machine-prose
+source:
+  repo: every.to
+  path: https://typesafe-parallel-judgment-lab.every-4573.chatgpt.site/downloads/typesafe-lab-source.zip (scripts/run-ai-checker.mjs)
+  line: 1
+  ruleId: repetitive_transitions
+unit: [paragraph]
+mechanical:
+  phrases:
+    - moreover
+    - furthermore
+    - additionally
+    - consequently
+    - thus
+    - hence
+    - in addition
+    - in conclusion
+    - to summarize
+    - ultimately
+  minMatches: 2
+question:
+  context: [docType]
+  instructions: >-
+    Does the writing repeatedly use formal or formulaic transitions? Ignore a single transition, and a passage whose sentences follow from each other without the connective.
+  criteria:
+    true:
+      what: Transitions doing the work the sentences should.
+      examples:
+        - "Moreover, the design is consistent. Furthermore, it is accessible. Additionally, it loads quickly. Consequently, users prefer it."
+        - "Thus the migration succeeded. Hence the team moved on. Moreover, morale improved."
+    false:
+      what: Sentences that connect by their content.
+      examples:
+        - "The design is consistent and loads quickly, which is why users kept choosing it over the old one in the test."
+        - "The migration finished a week early. The team spent that week on the flaky test suite instead."
+thresholds: { review: 0.4, act: 0.75 }
+severity: minor
+fix:
+  hint: >-
+    Cut the connective and let the order of the sentences carry the logic.
+status: review-only
+handWritten: [question, fix, thresholds, mechanical]

package/data/rules/copywriting/copywriting-requirements-language.yaml

@@ -0,0 +1,50 @@
+id: copywriting-requirements-language
+title: A requirement presented as a recommendation
+categoryId: reader-first-framing
+source:
+  repo: mblode/agent-skills
+  path: skills/docs-writing/rules/voice-requirements-language.md
+  line: 7
+  ruleId: voice-requirements-language
+unit:
+  - paragraph
+mechanical:
+  regex: \bshould\b
+  flags: giu
+question:
+  context:
+    - docType
+    - headingAbove
+  instructions: The TEXT is technical documentation. Return true only when it uses should for a requirement and the supplied text explicitly establishes that skipping it causes failure, rejection, data loss, or an irreversible unsafe operation. Do not infer undocumented requirements from technical knowledge. Return false for optional recommendations, expected behavior, quoted wording, style discussions, or insufficient evidence of necessity.
+  criteria:
+    "true":
+      what: Explicitly mandatory behavior weakened to should.
+      examples:
+        - You should supply an API key; requests without one are rejected.
+        - You should back up the database before upgrading; the upgrade permanently deletes the old tables.
+    "false":
+      what: A recommendation, expectation, direct requirement, or necessity not established locally.
+      examples:
+        - You should set a longer timeout on slow networks.
+        - The request should finish within a second.
+        - You must supply an API key; requests without one are rejected.
+severity: minor
+fix:
+  hint: Use must or a direct imperative when the text establishes a requirement. Keep should for recommendations and expectations.
+preconditions:
+  notInCode: true
+  docType:
+    - tutorial
+    - howto
+    - reference
+    - explanation
+    - agent-instructions
+status: review-only
+handWritten:
+  - title
+  - unit
+  - mechanical
+  - question
+  - fix
+  - preconditions
+  - severity

package/data/rules/copywriting/copywriting-searchable-headings.yaml

@@ -0,0 +1,52 @@
+id: copywriting-searchable-headings
+title: A documentation heading names no topic or action
+categoryId: page-structure
+source:
+  repo: mblode/agent-skills
+  path: skills/docs-writing/rules/nav-searchable-headings.md
+  line: 7
+  ruleId: nav-searchable-headings
+unit:
+  - heading
+mechanical:
+  regex: ^(?:common (?:issues|problems)|more (?:info(?:rmation)?|details)|overview|miscellaneous|other)\s*[.:?]?$
+  flags: giu
+question:
+  context:
+    - docType
+    - headingAbove
+  instructions: The TEXT is a documentation heading. Return true when it is generic and names neither the feature nor the task, such as Common issues or More information. Return false when the supplied heading context gives it a clear specific subject, when it names a concrete topic or action, or when it quotes a heading as an example. Do not assume unseen page context.
+  criteria:
+    "true":
+      what: A generic heading with no specific subject in the supplied context.
+      examples:
+        - Common issues
+        - More information
+    "false":
+      what: Specific topic or action, or a generic subheading with explicit subject context.
+      examples:
+        - Troubleshoot authentication errors
+        - Configure rate limits
+        - |-
+          TEXT: Overview
+          HEADING: Webhook retries
+severity: minor
+fix:
+  hint: Name the feature or reader task, for example Troubleshoot authentication errors. Keep a short subheading when its parent already supplies the subject.
+preconditions:
+  notInCode: true
+  docType:
+    - tutorial
+    - howto
+    - reference
+    - explanation
+    - agent-instructions
+status: review-only
+handWritten:
+  - title
+  - unit
+  - mechanical
+  - question
+  - fix
+  - preconditions
+  - severity

package/data/rules/copywriting/copywriting-semantic-links.yaml

@@ -0,0 +1,23 @@
+# Ported from mblode/agent-skills skills/ui-design/rules/nav-semantic-links.md by scripts/port-rules.ts.
+# Keys listed in handWritten are preserved on re-run; everything else is regenerated.
+id: copywriting-semantic-links
+title: Use Semantic Links for Navigation
+categoryId: page-structure
+source:
+  line: 9
+  path: skills/ui-design/rules/nav-semantic-links.md
+  repo: mblode/agent-skills
+  ruleId: nav-semantic-links
+scope:
+  include:
+    - "**/*.tsx"
+    - "**/*.jsx"
+unit:
+  - source
+mechanical:
+  flags: gus
+  regex: <(div|span|li)\b[^>]*\bonClick=\{[^}]*(router\.push|navigate\(|location\.href)
+severity: minor
+fix:
+  hint: Navigation should use `<a>` or framework `<Link>`, not click handlers on generic elements. A click handler on a div loses middle-click, open-in-new-tab, copy-link, and the browser's own back behaviour.
+status: review-only

package/data/rules/copywriting/copywriting-structural-symmetry.yaml

@@ -0,0 +1,35 @@
+# One of the 21 AI-writing checks Every ran with Jev (Mike Taylor, "Jev judged
+# everything I've written in 0.7 seconds", 15 Sep 2026). The question is the
+# published wording; the second sentence says what to ignore.
+# Candidate list from EveryInc/compound-writing skills/cw-ai-check/SKILL.md, category 9 (formulaic structure).
+id: copywriting-structural-symmetry
+title: Excessive structural symmetry or formulaic organisation
+categoryId: machine-prose
+source:
+  repo: every.to
+  path: https://typesafe-parallel-judgment-lab.every-4573.chatgpt.site/downloads/typesafe-lab-source.zip (scripts/run-ai-checker.mjs)
+  line: 1
+  ruleId: structural_symmetry
+unit: [paragraph]
+question:
+  context: [docType]
+  instructions: >-
+    Does the writing exhibit excessive structural symmetry or formulaic organization? Ignore a short list whose items are parallel by nature (steps, options) and any passage under three sentences.
+  criteria:
+    true:
+      what: Sentences or clauses built to the same template, in matched lengths, with a tidy three-part rhythm.
+      examples:
+        - "First, we gathered the data. Second, we cleaned the data. Third, we analysed the data. Each step mattered, each step took time, each step taught us something."
+        - "It is not about speed. It is about trust. It is not about features. It is about outcomes."
+    false:
+      what: Structure that follows the argument, uneven where the material is uneven.
+      examples:
+        - "We spent two days cleaning the export because half the dates were in US format; the analysis itself took an afternoon."
+        - "The rewrite shipped in March. Support tickets about the settings page fell from 40 a week to 6, and stayed there."
+thresholds: { review: 0.4, act: 0.75 }
+severity: minor
+fix:
+  hint: >-
+    Let the shape follow the material: one long sentence where the point needs it, one short one where it does not.
+status: review-only
+handWritten: [question, fix, thresholds]

package/data/rules/copywriting/copywriting-success-state-specific.yaml

@@ -0,0 +1,43 @@
+id: copywriting-success-state-specific
+title: Success message does not name the completed operation
+categoryId: actionable-microcopy
+source:
+  repo: installed/copywriting
+  path: skills/copywriting/references/ui-states.md
+  line: 1
+unit:
+  - paragraph
+  - jsx-text
+  - attr-string
+mechanical:
+  regex: "^(?:success[!.]?|operation completed(?: successfully)?[!.]?|done[!.]?)$"
+  flags: giu
+question:
+  context:
+    - docType
+    - headingAbove
+    - role
+    - element
+  instructions: The text is UI copy. Return true if it is a standalone success notification that says nothing about what completed. Return false for a control label, a named state, quoted examples, or when the supplied heading identifies the completed operation. Do not infer the notification role from a single ambiguous word.
+  criteria:
+    "true":
+      what: The stated failure is supported by the supplied text.
+      examples:
+        - Operation completed successfully!
+    "false":
+      what: The text is specific, justified, quoted, or outside this rule.
+      examples:
+        - Changes saved.
+severity: minor
+fix:
+  hint: Name what completed, proportional to the action.
+preconditions:
+  notInCode: true
+  docType:
+    - ui
+status: review-only
+handWritten:
+  - mechanical
+  - question
+  - preconditions
+  - fix

package/data/rules/copywriting/copywriting-temporal-words.yaml

@@ -0,0 +1,55 @@
+# Ported from mblode/agent-skills skills/docs-writing/rules/hygiene-no-temporal.md and
+# rules/hygiene-update-metadata.md.
+id: copywriting-temporal-words
+title: Wording anchored to the time of writing
+categoryId: reference-reading
+source:
+  {
+    repo: mblode/agent-skills,
+    path: skills/docs-writing/rules/hygiene-no-temporal.md,
+    line: 7,
+  }
+unit: [paragraph, heading]
+mechanical:
+  phrases:
+    [
+      currently,
+      recently,
+      at the moment,
+      coming soon,
+      in the near future,
+      as of today,
+      latest version,
+      the new,
+      brand new,
+      this year,
+      last year,
+      next release,
+      soon,
+    ]
+question:
+  context: [docType]
+  instructions: >-
+    The TEXT is from documentation. Return true when it will read as wrong or stale once time passes because it anchors to the moment of writing ("currently", "recently added", "coming soon", "the new dashboard", "as of today") without a version or date the reader can check. Return false when the TEXT carries a version marker or date, when the temporal word describes the reader's own action ("Now open the file"), or when the TEXT is not documentation.
+  criteria:
+    true:
+      what: Time-anchored wording with no version or date.
+      examples:
+        - "The dashboard currently supports three providers, with more coming soon."
+        - "We recently added dark mode to the new settings page."
+    false:
+      what: Versioned, dated, or an instruction step.
+      examples:
+        - "Since v3.2 the dashboard supports three providers."
+        - "Now run the migration."
+thresholds: { review: 0.4, act: 0.75 }
+severity: minor
+fix:
+  hint: Replace the time word with a version or date the reader can check, or delete it.
+preconditions:
+  {
+    notInCode: true,
+    docType: [tutorial, howto, reference, explanation, agent-instructions],
+  }
+status: review-only
+handWritten: [mechanical, question, fix, thresholds, preconditions]

package/data/rules/copywriting/copywriting-toast-successfully.yaml

@@ -0,0 +1,22 @@
+# Ported from mblode/agent-skills skills/ui-design/guidelines/copywriting.md (toasts) and
+# product-design rule/success-state-specific.
+id: copywriting-toast-successfully
+title: Success message padded with "successfully"
+categoryId: actionable-microcopy
+source:
+  {
+    repo: mblode/agent-skills,
+    path: skills/ui-design/guidelines/copywriting.md,
+    line: 15,
+  }
+unit: [jsx-text, attr-string]
+mechanical:
+  regex: "\\bsuccessfully\\b"
+  flags: giu
+severity: minor
+fix:
+  hint: >-
+    Name the thing that changed in past tense and stop: "Project deleted", not "Successfully deleted the project."
+preconditions: { notInCode: true, docType: [ui, unknown] }
+status: active
+handWritten: [mechanical, fix, preconditions]

package/data/rules/copywriting/copywriting-unexplained-action.yaml

@@ -0,0 +1,33 @@
+# Hand-authored from Every's writing checks (Mike Taylor and Dan Shipper,
+# "Jev judged everything I've written in 0.7 seconds", 15 Sep 2026): the
+# AI-tell questions and the four passage checks named in the article.
+id: copywriting-unexplained-action
+title: Names an action that cannot be pictured
+categoryId: reader-first-framing
+source:
+  repo: every.to
+  path: https://every.to/also-true-for-humans/mini-vibe-check-typesafe-s-jev-judged-everything-i-ve-written-in-0-7-seconds
+  line: 1
+unit: [paragraph]
+question:
+  context: [docType]
+  instructions: >-
+    Read the TEXT. Return true when it asks the reader to do, or describes someone doing, an action whose concrete steps cannot be pictured from the words (teach a calendar, activate the culture, leverage the learnings). Return false when the action names a thing a person could start doing now, or when the TEXT is a heading or label that a following paragraph will explain.
+  criteria:
+    true:
+      what: An action with no picturable steps.
+      examples:
+        - "A shared appointment calendar that parents and staff teach together."
+        - "Activate the community around the launch and operationalise the insights."
+    false:
+      what: An action a person could begin.
+      examples:
+        - "A shared appointment calendar that parents and staff both add bookings to."
+        - "Post the launch thread in the community channel on Monday and reply to every question that day."
+thresholds: { review: 0.4, act: 0.75 }
+severity: minor
+fix:
+  hint: >-
+    Replace the abstract verb with the first concrete step a person would take.
+status: review-only
+handWritten: [question, fix, thresholds]

package/data/rules/copywriting/copywriting-unnatural-polish.yaml

@@ -0,0 +1,48 @@
+# One of the 21 AI-writing checks Every ran with Jev (Mike Taylor, "Jev judged
+# everything I've written in 0.7 seconds", 15 Sep 2026). The question is the
+# published wording; the second sentence says what to ignore.
+# Candidate list from EveryInc/compound-writing skills/cw-ai-check/SKILL.md, category 0 (structural overcompletion, performed voice).
+id: copywriting-unnatural-polish
+title: Polished in a way that suppresses personal texture
+categoryId: machine-prose
+source:
+  repo: every.to
+  path: https://typesafe-parallel-judgment-lab.every-4573.chatgpt.site/downloads/typesafe-lab-source.zip (scripts/run-ai-checker.mjs)
+  line: 1
+  ruleId: unnatural_polish
+unit: [paragraph]
+# The question explicitly excludes reference and UI copy. Decide applicability
+# in code rather than paying Jev to rediscover this deterministic exclusion.
+preconditions:
+  docType:
+    [
+      tutorial,
+      howto,
+      explanation,
+      agent-instructions,
+      lesson,
+      marketing,
+      unknown,
+    ]
+question:
+  context: [docType]
+  instructions: >-
+    Does the writing feel polished in a way that suppresses personal texture or irregularity? Ignore reference documentation and UI copy, where a neutral register is the point.
+  criteria:
+    true:
+      what: Even, frictionless prose with no person behind it.
+      examples:
+        - "The initiative delivered meaningful improvements across several dimensions, and stakeholders responded positively to the enhanced experience."
+        - "Each component was carefully considered to ensure a cohesive, thoughtful result that balances form and function."
+    false:
+      what: Prose with a specific person, opinion or rough edge in it.
+      examples:
+        - "I hated the old settings page. It had 14 toggles and I could never remember which one hid the sidebar."
+        - "The first version was ugly and we shipped it anyway, because the two people who needed it were waiting."
+thresholds: { review: 0.4, act: 0.75 }
+severity: minor
+fix:
+  hint: >-
+    Put one specific, slightly uncomfortable sentence back in: what you thought, what went wrong, what you would not do again.
+status: review-only
+handWritten: [question, fix, thresholds]

package/data/rules/copywriting/copywriting-unraised-objection.yaml

@@ -0,0 +1,43 @@
+id: copywriting-unraised-objection
+title: Personal message defends against an unraised objection
+categoryId: actionable-microcopy
+source:
+  repo: mblode/ghostwriter
+  path: skills/ghostwriter/SKILL.md
+  line: 1
+unit:
+  - paragraph
+  - jsx-text
+  - attr-string
+mechanical:
+  regex: \b(?:(?:don.t|do not) get me wrong|I(?:.m| am) not saying|some might say)\b
+  flags: giu
+question:
+  context:
+    - docType
+    - headingAbove
+    - role
+    - element
+  instructions: Return true when a defensive preface introduces a hypothetical objection without evidence that anyone raised it and adds no constraint. Return false for a real correction, a quoted objection, an explicit boundary, or an important qualification.
+  criteria:
+    "true":
+      what: The stated failure is supported by the supplied text.
+      examples:
+        - Do not get me wrong, I am not saying collaboration is bad, but we can cancel this meeting.
+    "false":
+      what: The text is specific, justified, quoted, or outside this rule.
+      examples:
+        - You asked whether I oppose collaboration. I do not; I oppose this meeting schedule.
+severity: minor
+fix:
+  hint: State the concrete claim and preserve any real qualification.
+preconditions:
+  notInCode: true
+  docType:
+    - personal
+status: review-only
+handWritten:
+  - mechanical
+  - question
+  - preconditions
+  - fix

package/data/rules/copywriting/copywriting-unverifiable-proof.yaml

@@ -0,0 +1,23 @@
+# Ported from mblode/agent-skills skills/ui-design/rules/slop-unverifiable-proof.md by scripts/port-rules.ts.
+# Keys listed in handWritten are preserved on re-run; everything else is regenerated.
+id: copywriting-unverifiable-proof
+title: Unverifiable proof standing in for real evidence
+categoryId: evidence-over-claims
+source:
+  line: 10
+  path: skills/ui-design/rules/slop-unverifiable-proof.md
+  repo: mblode/agent-skills
+  ruleId: slop-unverifiable-proof
+scope:
+  include:
+    - "**/*.tsx"
+    - "**/*.jsx"
+unit:
+  - source
+mechanical:
+  flags: gui
+  regex: logoipsum|placehold\.|placeholder\.com|via\.placeholder|dummyimage|lorem ipsum
+severity: minor
+fix:
+  hint: '"99.9% uptime", "10,000+ teams", "3x faster", a testimonial from Jane Doe, CEO at Acme, and a strip of logos nobody has heard of. Every one of these is a claim about the world, and a visitor who cannot check any of them learns that this page''s numbers are decoration. The damage is not aesthetic: it '
+status: review-only