seo-audit
VerifiedRun the SEOmator CLI on a site and score it against 398 rules across 20 categories (SEO, technical, content, security, JS rendering, AI readiness), with reports an LLM can act on. It can also diff two audits to show what a deploy changed. Reach for it to find out why a site underperforms in search, to review a site's health, or to check a release before and after.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 25.1 KB |
| references/rules.md | markdown | 4.4 KB |
| scripts/clean.mjs | script | 673 B |
| scripts/extract-hints.mjs | script | 6.9 KB |
| scripts/gen-icons.mjs | script | 3.7 KB |
| scripts/gen-tokens.mjs | script | 2.6 KB |
| scripts/generate-icon.mjs | script | 3.2 KB |
| scripts/hints-mapping.mjs | script | 31.7 KB |
| scripts/map-hints.mjs | script | 2.6 KB |
| scripts/resign-native.mjs | script | 2.1 KB |
| scripts/sync-docs.mjs | script | 11.9 KB |
| scripts/vite-plugin-inline-assets.mjs | script | 1.1 KB |
| scripts/vite-plugin-tokens.mjs | script | 1.0 KB |
scripts/vite-plugin-tokens.mjs
View on GitHub/**
* Regenerate `ui/styles/tokens.css` before any Vite build or dev server.
*
* Registered in both `vite.web.config.ts` and `electron/electron-vite.config.ts`
* rather than as an npm `prebuild` script, because four commands reach Vite
* directly — `web:build`, `web:dev`, `electron:build`, `electron:dev` — and a
* prebuild hook would cover only the one that runs through `npm run build`.
* The failure it prevents is quiet: a stale or missing token file leaves
* Tailwind's aliases resolving to nothing and the app renders unstyled, and CI
* never sees it because CI runs the one path that was covered.
*/
import { execFileSync } from 'node:child_process';
import { fileURLToPath } from 'node:url';
import { dirname, resolve } from 'node:path';
const here = dirname(fileURLToPath(import.meta.url));
export function designTokens() {
return {
name: 'seomator-design-tokens',
buildStart() {
execFileSync(process.execPath, [resolve(here, 'gen-tokens.mjs')], { stdio: 'inherit' });
},
};
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |