Claude Skills by hamza-ali-shahjahan

Top-level routing brain. Given any user request, identifies the product + stage + intent, then routes to the right downstream agent.

Map the competitive landscape by tier (direct/indirect/acquirer/adjacent) and argue why each could win. Antidote to competitor neglect.

Plan customer discovery — define target profile, build prospect list, draft interview script, set up outreach + scheduling logistics.

Stress-test an idea or hypothesis. Build the strongest possible case AGAINST it, find disconfirming evidence, and surface the assumptions Hamza is implicitly making.

Generate startup ideas grounded in Hamza's existing patterns, current trends, and validated demand signals. Never just brainstorms — pulls from real signals.

Synthesize a batch of customer interviews into evidence-for + evidence-against the hypothesis, with pattern surfacing and bias flagging.

Build TAM/SAM/SOM, market trends, buyer landscape — anchored in citable public data, not vibes.

Turn vague problem observations into testable hypothesis statements with specific who/when/severity/current-workaround dimensions.

Build the brand foundation — positioning, story, voice, naming, visual primitives — so every other launch asset (landing, content, outreach) sings the same song.

First 100 customers by hand. Sourcing → personalized cold messages → follow-up cadence → tracking. Volume × signal, not spam.

Build a community around the product — Discord/Slack/forum, waitlist nurture, early-user comms. Choose the right venue, don't default to Discord.

Build content calendars and draft individual pieces — blog posts, social, LinkedIn, threads — anchored on keyword research and brand voice.

Pull real keyword data from GSC (own sites) + Ahrefs Webmaster Tools (own sites) + DataForSEO (competitor/general). Produce a clustered keyword brief.

Write landing page copy that converts. Hero + 3 value props + social proof + objections + CTA. Anchored on validated user language.

Plan and execute the launch — Product Hunt, Hacker News, X/Twitter, LinkedIn, newsletters, communities — sequenced for compounding signal.

Initial pricing for a product — packaging, tiers, anchor, monthly vs annual, free vs trial. Anchored on value-based pricing + van Westendorp where data exists.

Build the SEO strategy — content hubs, target keywords, internal linking, schema, technical baseline — for a product that needs organic growth.

Define a product's architecture BEFORE Claude Code writes a line. Produces CLAUDE.md, scope.md, and a 1-page architectural decisions doc.

Drive Claude Code build sessions inside a product folder. Enforces session discipline: read CLAUDE.md + scope.md first, log decisions after.

Define the measurement framework BEFORE launch. North star, activation criterion, retention targets, Sean Ellis target, and false-positive shape.

Block scope creep. Every feature ask gets pressure-tested against scope.md. Bar to amend: specific evidence from real users.

Pre-launch security review covering auth, data exposure, input validation, and dependency vulns. Produces a remediation list, not a "looks good" stamp.

Identify patterns across products — what's working that should propagate, what's failing in similar ways, what knowledge should become MEMORY.md entries.

Quarterly portfolio review. Hard call on what to kill, what to maintain, what to double down on. Forces decisions.

Decide where attention goes today across the 10-product portfolio. The "if you had 4 hours to work on the portfolio, do this" agent.

Pull metrics across all products into a single view. Powers the dashboard and the daily/weekly briefings.

Pre-enterprise compliance check — SOC2 / GDPR / HIPAA / CCPA gap analysis with prioritized remediation. Not a substitute for real audit.

Design growth loops (Reforge/Balfour framework). Identify acquisition, monetization, and engagement loops with quantified inputs and outputs.

Identify and deepen moats — workflow lock-in, data network effects, domain depth, integration depth. Audit current moats + propose investments.

Iterate pricing post-PMF based on real data — willingness to pay, expansion revenue, packaging tweaks, annual upsell, enterprise pricing.

Analyze retention curves, identify churn drivers, and propose interventions. Differentiates between leaky bucket (acquisition >> retention) and PMF problems.

Triage incoming support — categorize, prioritize, draft responses, identify product bug vs user-error vs feature-request. Routes to engineering when needed.

Generate startup ideas grounded in Hamza's portfolio patterns + current trends. Wraps the idea-generator agent.

Pull keyword data from GSC, Ahrefs Webmaster, and DataForSEO. Returns a clustered keyword brief.

Quarterly portfolio review with forced verdicts (DOUBLE-DOWN / MAINTAIN / MINIMAL / KILL) for every product.

Build a full launch playbook for a product — PH, HN, X, LinkedIn, email warm-up, cold outreach, pricing, brand assets. Sequenced for compounding signal.

Snapshot of ALL products — one table, one recommendation. The "where should I focus today" command.

Snapshot of one product — current metrics, stage, blockers, and the #1 recommended action today.

One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.

Run a full validation pass on an idea — sharpening, devil's advocate, market sizing, competitor mapping, customer discovery plan.

Map a product's competitive landscape — direct + adjacent competitors, their positioning, naming conventions, and white-space. Persists findings to a per-product competitors file so it compounds over time. Use before naming, positioning, pricing, or GTM — and as the collision baseline for name-clearance.

Clear a product/brand name BEFORE buying a domain or branding anything. Runs same-industry collision, trademark signal, domain availability, and distinctiveness checks. Returns RED/YELLOW/GREEN verdicts with evidence. Use whenever a new product is being named, a domain is about to be bought, or a user proposes a name.

End-to-end product naming pipeline — brief → competitor scan → theme-by-theme generation → clearance → selection → TLD/budget → lock. Embeds the operator's default iterative shortlist-by-theme selection method. Use to name a new product or rename an existing one. Composes competitor-research and name-clearance.

Ship the SEO + AEO foundation (Google/Bing/Yandex + ChatGPT/Claude/Perplexity) into a Hamzaish product. Adds llms.txt, AI-bot-friendly robots.txt, FAQPage/SoftwareApplication JSON-LD, sitemap, and the meta head block.

Top-level routing brain. Given any user request, identifies the product + stage + intent, then routes to the right downstream agent.

Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.

Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.

QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

Map the competitive landscape by tier (direct/indirect/acquirer/adjacent) and argue why each could win. Antidote to competitor neglect.

Plan customer discovery — define target profile, build prospect list, draft interview script, set up outreach + scheduling logistics.