Add references/seo.md: head, semantics, and structured-data rules for full-page builds - #49
Open
MiguelMialdeaDev wants to merge 1 commit into
Open
Add references/seo.md: head, semantics, and structured-data rules for full-page builds#49MiguelMialdeaDev wants to merge 1 commit into
MiguelMialdeaDev wants to merge 1 commit into
Conversation
Hallmark already decides the <head>, heading levels and image attributes on every full-page build; this makes those decisions explicit. Conditional load — component-scope builds skip it.
|
@MiguelMialdeaDev is attempting to deploy a commit to the Together AI Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds one conditional-load reference —
references/seo.md— plus a single dispatch line inSKILL.md. No existing file is modified beyond that line.Hallmark already makes every decision in this file whenever it emits a full page: what goes in the
<head>, which element wraps a heading, whether an image declares its dimensions. Right now those decisions are made implicitly, and often wrong —<title>left unset, heading level chosen by type size rather than document structure, the hero image lazy-loaded,<img>shipped withoutwidth/height.None of it shows up in a screenshot, which is why it survives the current gates.
Why this fits the rules already here
Hallmark bans fabricated content — invented metrics, testimonials, logo counts (
anti-patterns.md§ Invented metrics, gate 46).Structured data is that same rule one layer down. An
aggregateRatingdescribing reviews nobody wrote is a fabricated metric that only machines read — and unlike a made-up conversion percentage, it's the one that earns a manual action. The file says so explicitly and points back at the existing rule instead of inventing a parallel one.Token discipline
<head>. Component-scope builds skip it entirely.layout-and-space.md(6.8) andresponsive.md(5.9).Scope
Deliberately narrow — only what is genuinely a page-construction decision:
h1, no skipped levels, landmarks, named sectionsalt, intrinsic dimensions, eager hero## BansLeft out on purpose: keyword research, link building, redirects, sitemaps, analytics. None of those are design decisions and none belong in this skill.
Possible follow-ups
Not in this PR, to keep it reviewable — happy to open either separately if they're wanted:
performance.md— Core Web Vitals budgets, font-loading strategy, image formatslocale.md— non-English typography and copy conventions (quotation marks, casing, punctuation)Notes
There's no
CONTRIBUTING.md, so I matched the house style ofcolor.mdandresponsive.md: British spelling, imperative voice, opening diagnosis, closing## Bans.Happy to rename (
seo.mdvsdiscoverability.md), move it, or cut scope — tell me what you'd prefer and I'll amend.