Assess a codebase's architecture with hard evidence — module map, dependency direction, layering breaks, coupling and cohesion hotspots weighted by git churn — then rank 3-5 improvement moves by risk-adjusted value and actually execute the lowest-risk move end to end with tests green before and after, finishing with a dated architecture doc containing before/after mermaid diagrams. Use when someone says "improve the architecture", "this codebase is a mess", "reduce coupling", "untangle dependencies", "refactor safely", "layering is broken", "circular imports", "tech debt assessment", "where should we refactor first", or "clean up module boundaries" and wants executed change, not just a slideware review.
Extracts a complete design system from a screenshot, live URL, or existing app codebase: palette, type scale, spacing rhythm, radii, shadows, and a component inventory, then normalizes everything into deduplicated tokens, emits them in the target stack's format (CSS custom properties, Tailwind config, Flutter ThemeData, or SCSS variables), and generates a living styleguide page rendering every token and component state. Use when: 'extract the design system', 'pull the colors from this screenshot', 'copy this site's design', 'turn this UI into tokens', 'reverse-engineer this design', 'build a design system from our app', 'make a styleguide', 'tokenize our styles', 'what fonts and colors does this site use'.
Run multi-source web research with adversarial verification and produce a cited report: decomposes the question into 3-6 distinct queries (broad, specific, comparative, recency-anchored), searches and ranks sources by authority, recency, and specificity, fetches the top 5-10 and extracts facts with per-fact source IDs, then runs an adversarial pass that actively searches for evidence CONTRADICTING each key claim, and synthesizes a themed report with a TL;DR, inline [n] citations, an explicit conflicts section, and coverage caveats, saved to ~/research-reports/ and printed inline. Use when the user says: research this topic, deep dive on X, what's the current state of X, compare X vs Y with sources, find evidence for/against, fact-checked report, is it true that X, literature scan, market scan, due diligence on X, cited summary of X.
Build a complete indie launch package for an app, tool, or library — product audit, positioning (one-liner, value props, objection answers), finished launch assets written to a launch/ directory (landing copy, App Store or Play Store or npm/directory listing text, Product Hunt draft, Show HN draft, a 2-week social calendar with 14 fully written posts), an SEO baseline audit with fixes applied when the repo is present, and an hour-by-hour launch-day runbook. Use when someone says "help me launch", "launch plan", "Product Hunt draft", "Show HN post", "write my landing copy", "app store listing", "marketing for my app", "go to market", "launch checklist", "how do I announce this", or when a product is built and needs distribution artifacts, not more code.
One-command PR gate that runs four passes over exactly the changed surface — code review (correctness then simplification), security (injection, authz, secrets, dependency diff), tests (run the suite and flag untested changed lines), and accessibility when UI files changed — and emits a single machine-parseable verdict: MERGE, MERGE-WITH-NITS, or BLOCK with numbered findings, each carrying file:line and a concrete fix. Use when someone says "is this PR ready to merge", "pre-merge check", "gate this branch", "review before I merge", "run the full check on my diff", "can I ship this", "final check", "PR gate", or in CI-like flows where one verdict must summarize review, security, tests, and a11y in a single run.
Conduct a complete feature workflow in one skill — brainstorm, plan, TDD implementation, self-review, delivery summary — with hard gates between stages: no stage starts until the prior stage's artifact exists on disk (brainstorm note, plan doc, green tests per step). Use when someone says "build this feature properly", "take this from idea to done", "brainstorm then implement", "run the full workflow", "plan and build X", "do this the right way", "TDD this feature", "structured feature development", or when a feature request arrives raw and needs the whole arc — options weighed, plan written, red-green-refactor execution, and a reviewed diff — without plugin sprawl or human babysitting between stages.
Convert any pile of documents (PDF, Word, HTML pages, wiki exports, PowerPoint slides) into clean, LLM-ready markdown context: inventories the sources, picks the right extractor per file type (pdftotext or PyMuPDF for PDF, pandoc or mammoth for docx, readability extraction for HTML, python-pptx for slides), preserves structure (headings, real markdown tables, code blocks), strips boilerplate and navigation, chunks by heading hierarchy into 2-4k token files under context/<source>/ with an INDEX.md, and spot-checks three random chunks against the originals for fidelity. Use when the user says: convert these docs to markdown, prep these PDFs for Claude, turn this documentation into context, markitdown these files, extract text from these documents, make this wiki LLM-readable, ingest these docs, build a context folder.
Build an investor or product pitch deck as a real PPTX file from a written brief: extracts the fundamentals (problem, solution, market, traction, business model, ask) and flags anything missing as explicit TODO placeholders instead of inventing numbers, chooses a narrative arc (problem-first for investors, demo-first for product, before/after for sales), drafts 10-12 slides each with speaker notes, renders with python-pptx using a clean typographic template (one idea per slide, big numbers, no clip art), then re-opens the file to assert slide count and non-empty notes. Use when the user says: make a pitch deck, investor deck, seed deck, fundraising slides, product pitch presentation, sales deck, turn this brief into slides, deck for the demo day, YC application deck, build me a PPTX pitch.