All authors
Claude Skills by karero
github.com/karero57 skills1 installs139 views
- Website ReviewThe Double-Knuth review for a site — a two-pass correctness + cross-file consistency audit run at the END of a build (pre-launch) and after ADDING or substantially editing a page. Pass 1 = bugs/correctness (delegates the diff to /code-review); Pass 2 = completeness + route/URL/SEO/config/email/docs consistency against the site contract. Read-only: returns a ranked BUG/RISK/NIT list with file:line + fixes. Prerequisite: website-qa green. Also owns the "review depth" decision for website work —...Votes: 0GitHub stars: 6
- Website ScorecardOPTIONAL public scorecard: publish what a site's own test gate checked, as a dated section on one page. `npm run scorecard` runs the whole suite and writes scorecard.json (checks passed per area, pages, date, tested version); a component renders it and tells the reader when the site was edited after the run. The owner can add the four Lighthouse scores of a PageSpeed run, with a re-run link. A red run writes nothing, so a card never shows a failed run as passed. Never runs unasked: publishing...Votes: 0GitHub stars: 6
- Website Seo GeoThe on-page SEO + GEO contract for a new site: exact metadata limits (title 50–60 chars, meta description 140–160 with a 120 floor), og:title/og:description == title/desc, twitter inherits OG, clean canonical == og:url, required JSON-LD schema, and llms.txt for AI answer engines. Use when building or reviewing a page's <head> / metadata (step 5 of the new-website pipeline), or when a title/description is too long or tags are out of sync. Enforced by the seo.spec.ts check in the new-website te...Votes: 0GitHub stars: 6
- Website StoryOPTIONAL story layer: narrate the home page as the customer's story — the visitor as hero, their problem as the villain, the brand as the guide with a three-step plan — captured in STORY.md and mapped onto a seven-section home page. Inspired by Donald Miller's StoryBrand framework, in this suite's own words. POSITIONING.md still decides WHAT is claimed; STORY.md decides only how the home page tells it and loses every conflict. Never runs unasked: offered once after website-positioning, or run...Votes: 0GitHub stars: 6
- Website TaglineOPTIONAL: find the one short line that sits under the logo (the tagline; a German-speaking owner calls it the "Claim"). Leads with purpose: starts from what the business is there to do for its customer, taken from POSITIONING.md, not from clever wording. Shows the owner six to eight candidate lines in three or four different directions, asks which direction sounds like them, then refines on the owner's feedback, for at most three rounds, until they pick ONE or stop. Records it in TAGLINE.md a...Votes: 0GitHub stars: 6
- Website Team SetupTurn a one-owner new-website repo into one several people and AI assistants (Codex, Claude Code) can work on at once without overwriting each other: invite collaborators, set the repo settings, prove the CI workflow starts on its own (the fix for a silent one is bundled), block direct pushes to `main`, connect Cloudflare Pages to GitHub without the known traps, write rights, merge rule and who publishes live into `AGENTS.md`, hand the team a one-page guide. Run once, when a second person join...Votes: 0GitHub stars: 6
- Wordpress InspectorCount what a live WordPress site holds before anyone promises to move it. Read-only, from the outside: no login, no backup. scripts/wp_inventory.py asks the site's public addresses (REST API, sitemap) and reports each content type the API lists (WordPress's internal ones left out) with its number of records, where the sitemap disagrees, signs of a page builder and forms, and when the count is incomplete: the basis for an estimate. After the move, scripts/check_move.py asks the new site for ea...Votes: 0GitHub stars: 6