aesthetic-instrument
great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks,…
Local-business SEO and structured-data framework for content-platform Product-Builder products that need to be found (storefronts, restaurant online-ordering, real-estate listings, service-business sites). Codifies schema.org structured data
$ npx -y skills add avelikiy/great_cto --skill local-seo --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/local-seoContext preview
The summary Claude sees to decide when to auto-load this skill.
Local-business SEO and structured-data framework for content-platform Product-Builder products that need to be found (storefronts, restaurant online-ordering, real-estate listings, service-business sites). Codifies schema.org structured data
name: local-seo description: Local-business SEO and structured-data framework for content-platform Product-Builder products that need to be found (storefronts, restaurant online-ordering, real-estate listings, service-business sites). Codifies schema.org structured data (LocalBusiness/Product/Menu/RealEstateListing), Core Web Vitals as a ranking input, local on-page signals (NAP consistency, Google Business Profile alignment), sitemap/robots/canonical hygiene, and listing syndication. Applied by senior-dev when building public pages and checked by cms-reviewer. cms-reviewer reviews SEO; this skill is how you BUILD it right the first time. when_to_use: | Apply when building public, indexable pages for a local or commerce product: - storefront / online-ordering / listings / service-business landing pages - any page meant to rank in local or product search Do NOT apply to authenticated app surfaces or internal dashboards (noindex those). effort: low allowed-tools: Read, Write, Grep, Glob, WebFetch paths: - "docs/architecture/**" - "docs/design/**" - "app/**" - "src/**"
For a storefront, a restaurant, or a listing site, being discoverable IS the product. SEO designed in is cheap; SEO retrofitted is a rebuild. Build these signals from the first page.
Emit JSON-LD matching the entity, validated against Google's Rich Results requirements:
RealEstateAgent) — name, address (PostalAddress), geo, telephone, openingHours, priceRange, url, sameAs (social). This is the single highest-impact local SEO signal.
Validate every type with the Rich Results test before shipping; invalid JSON-LD earns nothing.
Name / Address / Phone must be **byte-identical** across the site, the LocalBusiness JSON-LD, and the Google Business Profile. Inconsistent NAP fractures local ranking. State the canonical NAP once and reuse it.
LCP / INP / CLS feed search ranking for these pages. Coordinate with performance-engineer, but the SEO-driven minimums: optimized responsive images (AVIF/WebP + srcset — see `media-pipeline-engineer`), no layout shift on load (sized media), fast TTFB. A slow local page loses to a fast competitor regardless of content.
from filters/pagination/UTM.
entity, not duplicated site-wide).
For listings/storefronts that syndicate (MLS/IDX, Google Shopping, marketplaces), the canonical lives on **our** page; syndicated copies point back. Define the feed format + update cadence (coordinate the source-of-truth with integrations-engineer).
When applied, contribute an **SEO** section to the architecture/design doc and a checklist the senior-dev build satisfies:
## SEO - schema.org types: <LocalBusiness subtype + Product/Menu/Listing> · JSON-LD validated - canonical NAP: <name/address/phone> (identical in JSON-LD + GBP) - CWV minimums: LCP/INP/CLS targets (with performance-engineer) - crawl: sitemap.xml (lastmod) · robots.txt · canonical on all · noindex app/admin - on-page: 1×h1, per-page title/meta, alt text, clean URLs - syndication (if any): canonical = our page; feed = <format/cadence>
You already have the agent. This is everything around it. great_cto runs Claude Code as a pipeline of 70 specialist agents — an independent model checks each stage before the next builds on it, spending caps refuse rather than warn, and three decisions stay yours: what gets built, how, and whether it ships.
Repo: avelikiy/great_cto
great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks,…
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect…
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes.…
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md),…
Structured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models…
Run the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact release.