fender-guitars
The guitar brand that defined rock and roll — Telecaster, Stratocaster, and Precision Bass — instruments played by Hendrix, Clapton, and every generation since.
What this skill does
# Fender Guitars ## Historical Timeline - 1946 — Leo Fender founds Fender Electric Instrument Manufacturing Company in Fullerton, California - 1950 — Telecaster (originally Broadcaster) becomes the first mass-produced solid-body electric guitar - 1951 — Precision Bass revolutionizes bass guitar; fretted design enables accurate intonation - 1954 — Stratocaster debuts with three pickups and contoured body — becomes the world's most copied guitar - 1965 — Leo Fender sells to CBS for $13M due to health issues - 1985 — CBS-era ends; employee-led buyout creates Fender Musical Instruments Corporation - 2012 — Fender acquires Gretsch (partnership), Squier line expands globally - 2021 — Fender files for IPO (valued at ~$3B), withdraws due to market conditions - 2024 — Fender Play digital learning platform reaches 1M+ subscribers ## Business Model Fender generates ~$1.5B annually across guitars (Stratocaster, Telecaster, American Professional and Ultra series), basses (Precision Bass, Jazz Bass), amplifiers, accessories, and digital services. The company operates a tiered brand strategy: American-made premium ($1,500–$3,000), Mexican-made mid-range ($800–$1,500), and Squier budget line ($200–$500) capturing all price segments. Fender Play (online learning, $10/month) creates recurring revenue. The used/vintage market for Fender instruments (1950s–60s models sell for $200K–$500K) reinforces brand prestige. ## Competitive Moat Fender's Stratocaster and Telecaster designs are the most imitated guitar shapes in history — but the original American-made instruments maintain a quality and heritage premium that copycats cannot match. Leo Fender's original designs (bolt-on neck, three single-coil pickups, tremolo system) remain the industry standard 70+ years later. The artist endorsement roster (Eric Clapton, Stevie Ray Vaughan, John Mayer, Yvette Young) creates cultural relevance. Fender's manufacturing expertise in Ensenada (Mexico) and Corona (California) provides quality control at scale. ## Key Data - **Annual revenue**: ~$1.5B (estimated, privately held) - **Guitars sold**: Millions of Stratocasters produced since 1954 - **Manufacturing**: Corona (California, USA), Ensenada (Mexico), Japan - **Digital**: Fender Play — 1M+ subscribers - **Vintage market**: 1950s Strats sell for $200K–$500K at auction ## Interesting Facts - Leo Fender never learned to play guitar — he was a radio repairman who designed instruments by listening to musicians describe what they needed. His inability to play may have been his greatest advantage, as he approached instrument design as an engineer rather than a player. - The Stratocaster has been to space: astronaut Chris Hadfield played David Bowie's 'Space Oddity' on a Stratocaster aboard the International Space Station in 2013.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".