Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Install or check the Claude Code usage status bar (rate limits 5h/7d, session context, reset countdown). Also use to change the display language.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Enforce opinionated, production-grade coding standards across JavaScript, TypeScript, Python (FastAPI/Django/Flask/scripts), Java (Spring Boot), C++, and PostgreSQL. Applies to new code AND reviews/refactors existing code. Covers modular file sizes, folder structure, design principles (SOLID, DRY, KISS), naming conventions, and Next.js App Router best practices. ALWAYS trigger this skill when: - User is starting a new project, module, service, or feature - User asks to review, audit, refactor, or clean up code - User asks to "follow best practices", "apply coding standards", or "make this production-ready" - Any new .ts, .tsx, .js, .py, .java, .cpp, .sql file is being created - User mentions Next.js, FastAPI, Spring Boot, or PostgreSQL schema design - User says "structure this properly", "make this modular", or "how should I organize this"
Tailor Yash's LaTeX resume to a pasted job description. Classifies into a category (ai/fullstack/frontend/backend/web3), rewrites bullets to maximize ATS fit while preserving the 1-page Jake Gutierrez template, scores against a 6-dimension ATS rubric, runs a recruiter devil's-advocate critique, and auto-iterates up to v3. Use when user types /tailor-resume followed by a job description.
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".
Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)