writing-like-me
Write content in Dhruv Baldawa's authentic voice and style. Use when creating blog posts, LinkedIn posts, emails, documentation, technical writing, opinion pieces, or any written content that should sound like Dhruv. Triggers on requests like "write this as me", "draft in my voice", "write a blog post", "create a LinkedIn post", "help me write", or any content creation where the user wants their personal voice applied.
What this skill does
# Writing Like Dhruv
This skill captures Dhruv's distinctive writing voice for consistent, authentic content creation.
## Voice Profile Summary
**Core identity**: Pragmatic engineer who writes from lived experience, not theory.
**Tone**: Optimistic realism — honest about struggles, confident about what matters.
**Style**: Lean, direct, conversational. No corporate-speak or unnecessary jargon.
## Quick Reference
### DO
- Write in first person, grounded in experience
- State positions early, then build on them
- Keep paragraphs short (2-4 sentences)
- Use casual asides and occasional emoticons when fitting
- Back technical claims with tangible outputs/projects
- Respect reader's time — include TL;DR for longer pieces
- Question conventional wisdom without being preachy
- Pivot from setbacks to agency and growth
### DON'T
- Hide behind jargon or abstract theory
- Name-drop for credibility
- Over-explain or pad content
- Use toxic positivity — optimism must be earned
- Write prescriptively ("you should...") — prefer observation ("I noticed...")
- Be preachy or moralistic about opinions
## Content Types
### Blog Posts
Structure: Hook → Position → Evidence from experience → Reflection
Open with a direct statement or admission. Example openers:
- "I failed IIT JEE."
- "Recently coming out of my education, I have the following points to add..."
End with earned insight, not generic advice.
### LinkedIn Posts
Keep punchy. Lead with the insight or story hook. Use line breaks for rhythm. Avoid hashtag spam — 2-3 max if any.
### Technical Writing
Get to the point fast. State what the project does in the first sentence. Show don't tell — reference actual repos, scripts, outputs.
### Opinion Pieces
Ground arguments in personal observation. Use phrases like:
- "According to me..."
- "These are the most general things I have found..."
- "The problem with the system is..."
## Signature Phrases & Patterns
See [references/style-guide.md](references/style-guide.md) for detailed examples, phrase bank, and before/after rewrites.
## Process
1. Identify content type (blog, LinkedIn, email, technical, opinion)
2. Establish the core experience or observation driving the piece
3. Write the opening hook — direct, personal, no preamble
4. Build with specific evidence from experience
5. Close with earned perspective, not generic takeaway
6. Review: Is this lean? Would Dhruv actually say this?
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.