Hypertune content skill

Hypertune content audit

Hypertune is a Windows PC game-performance optimizer made by COMPREADY Inc. Austin owns it and signs off every claim. This skill makes every audit by Som, Vinny and Hoa run the same way. It does not write pages; it finds what must change before Austin sees them.

Update this file every time new feedback arrives (see Changelog). A rule is added only when it traces to real feedback, with the date and the source.

When to use

• A new draft is ready for the hand check (step 6 of the V8 drafting process), before it goes to Vinny and then Austin.
• An existing live page is being revised (also run "Revising existing pages" below).
• Feedback from Austin or the client comes in: audit the revised page against it, then add the lesson here.
• Another model is asked to check an audit (see the handoff note).

Inputs needed

Ask for anything missing before starting. Don't audit from memory.

Paths are relative to ERN/ern-cro-plugin/evidence/hypertune/2026-10-03/.

If a fact appears in no approved source, it is a finding. Do not look it up on the open web and add it.

When sources disagree, the higher one wins: (1) Austin's latest written feedback, including wording he wrote himself; (2) V13; (3) V8 section 2; (4) V5 and the live site. Never flag Austin's own wording as a style or claims finding. Log every disagreement you find under Questions for Austin, even if the page follows the winning source. Known open ones (15 Oct): Mac support, "partnered with AMD", naming Thomas Schappy, yearly price ($59.99 vs $69.99 from 16 Oct), refund and data email (info@hypertune.gg vs support@compready.net).

The audit pass

Read the whole page once without stopping, then run these checks in order. Quote the exact words for every finding.

1. Facts. Every statement about Hypertune (price, refund, trial, platforms, hardware, company, founders, safety, revert) matches V13 in meaning. Lines V13 or V8 mark [Austin to confirm] keep that tag on the page or come out. Prices carry the date they apply from.

2. Feature names. Features use Hypertune's own names, in the product's order: CPU Overclocking, GPU Overclocking, Windows Debloating, Network Optimizations, Memory Optimizations, Game Hub. No invented groupings (Processor, Graphics, Memory, Windows, Network, Games) and no renamed variants ("memory optimisation", "Windows features", "game profiles" as a name). Paid add-ons (Expert Tuning) are introduced as optional, with who they are for, and never read as part of the subscription.

3. Steps. Every step uses the exact labels from the app, the site or the video, for example "Restore tab > most recent restore point > Restore". A generic step ("open Hypertune and revert your changes") fails. If the real path isn't known, the fix is [UI path needed], never a guessed path.

4. No guessing. At every point where a reader would ask "where?" or "then what?", the page gives the link, the exact menu or the next step. That covers cancel links, policy links, support channels, download location and what happens next. Platform and hardware are stated once, clearly. Every link opens and lands on the right page. When the copy lists features or steps, each one has a visual or none do; a missing one is [Screenshot needed: what it shows]. Screenshots taken from other sites need permission or replacing, and no screenshot may show personal data (emails, names, licence keys).

5. Repetition. Each fact appears once, in the section where a reader would look for it. One short preview in the hero or summary strip is allowed; the detail lives in one section only. List every fact or setting that appears more than once (hero, strips, feature table, icon lists, FAQ, captions) and quote each place. FAQ answers don't restate the page unless the question asks for it. Where a setting repeats on purpose (game pages), every mention gives the same advice.

6. Claims. Nothing that isn't in the approved facts. Specifically:

7. Already cut by Austin, never reintroduce: crypto mining, cracked copies ("Hypertune crack"), Delaware law, Mac support, AMD in the Intel section, the XTU sentence in the FAQ, the GamesBeat review. (The Intel section's "built on Intel's Extreme Tuning Utility" partner line stays.)
8. Reassure, don't defend: say what Hypertune does, not what it isn't. Name a fear (mining, cracks, bans) only if the page answers that exact question, in one calm line.
9. A partner's section mentions only that partner. Press and review lists go to Austin before publishing.
10. V8 NEVER WRITE list: no "endorsed", "certified", "ban-proof", "undetectable"; no new "trusted by", "verified by" or "100% safe"; NVIDIA is "supports" only; no FPS figure above "up to 60%" without Hypertune's own data and a source; no pros, creators or testimonials unless on Austin's list.
11. Anti-cheat: only the approved line in V8 section 2. No "no anti-cheat issues" or named anti-cheat safety unless Austin confirmed that system.
12. Legal and policy detail goes behind a link: one line, then the Terms or Privacy Policy.

13. Separate what Hypertune stores from what a third party processes (Stripe and PayPal take payments; Hypertune never sees card details).

14. SEO keyword placement. Against the brief and the keyword split:

15. The primary keyword is not another page's primary, and no heading uses another page's primary.
16. Title 50 to 60 characters, primary near the start, "| Hypertune" at the end. Meta 140 to 155 characters with the primary word for word. Give the counts.
17. One H1 containing the primary or a close variant. Primary in the first 100 words. The answer to the search is in the first two sentences.
18. Every secondary is mapped to an H2, the first paragraph under one, or an FAQ question; list any that aren't placed.
19. Table captions carry a keyword; alt text describes what the image shows.

20. The full 15-point check stays in SEO-audit-checklist-private.md; this step only catches placement.

21. Style.

22. No em dashes anywhere, including headings, tables, alt text, captions and the meta description.
23. Human tone: second person, lead with what the reader gets, short sentences. The page has one line on why the company exists.
24. No spec-sheet lines copied from the fact register ("A feature left off is not applied"). Rewrite them for the reader ("You choose what changes").
25. No AI filler: "in today's world", "ultimate", "game-changer", "unlock", "elevate", "seamless", rhetorical questions, closing summaries.
26. US spelling, matching the product's names ("Optimizations").
27. Read the first screen aloud. If it sounds like an ad or an AI summary, it fails.

Revising existing pages

When the page is already live, every piece of copy in the revision is marked:

If a Changed or New piece has no keyword, its note must say so and give the reason (a fact fix, a claim cut, or Austin's request). A Changed or New piece with no note is a finding. Existing copy still gets the full audit pass; being live doesn't make it approved (V5 lists live lines that break the claims rules).

Output format

Start with one line: the page, the date, the auditor, and the verdict:

• Fix first: any Blocker or Fix finding the auditor can resolve.
• Blocked on Austin: only Questions for Austin remain.
• Ready for Austin: no Blockers or Fixes; Polish items may remain.

Then:

• Severity: Blocker (wrong fact, cut claim, NEVER WRITE breach, personal data in a screenshot), Fix (any other rule broken), Polish (reads better but nothing is wrong). Sort by severity.
• Rule broken is the step number and name above, so findings can be grouped.
• Fix gives the replacement text, or the tag to insert ([Austin to confirm], [UI path needed], [Screenshot needed]).
• After the table, list the Questions for Austin (anything only he can settle) and, for revisions, the Existing / Changed / New map.
• No praise, and don't summarize the page.

When another model checks this

Hand the checker this note with the audit:

You are checking a Hypertune copy audit. Do not rely on the auditor's reading. Before you start, ask for these files: (1) this SKILL.md, (2) the draft and, for a revision, the live page text, (3) week-1/V13-fact-sheet-and-listing-copy.md, (4) V8 section 2 (facts block and NEVER WRITE), (5) week-1/lessons-ai-content.md, (6) the page brief with its keywords and UI paths, (7) week-1/SEO-audit-checklist-private.md. Run the audit pass yourself, then compare your findings with the auditor's table. Report only (a) findings the auditor missed, (b) findings you think are wrong, with the source line, and (c) any fix that adds a fact not in V13. Don't rewrite the page.

If the checker can't get V13 or the brief, its review covers style and repetition only, and it must say so.

Updating this skill

When new feedback arrives: add the rule to the right step (or a new step), add any newly cut claim to step 6, update lessons-ai-content.md and V8 if the rule belongs in drafting too, and add a changelog line. Keep this file under about 200 lines; move detail into the source files and point to them.

Changelog

• v1.1, 15 October 2026. Added source precedence and the open conflicts list, severity and verdict rules, link and screenshot checks (third-party permission, personal data), the hero preview allowance for repetition. Corrected XTU: only the FAQ sentence was cut; the Intel partner line stays.

• v1, 15 October 2026. First version, from Austin's trust page feedback (14 Oct), Vinny's notes from the 12 Oct call and the CS2 hand check. Distilled from lessons-ai-content.md, SEO-audit-checklist-private.md, V8, V13, V5, and the before/after of the trust page (C2-trust-page-draft.md vs trust-page-mockup.html).