skills

Use when the user mentions "analyzing a project", "analyzing a repository", "analyzing GitHub", "project analysis", "source code analysis", "architecture analysis", "code analysis", "studying this project", "studying this framework", "seeing how this library is implemented", "comparing two projects", "project evaluation", "framework evaluation"

Design and implement distinctive, production-ready frontend interfaces with strong aesthetic direction. Use when asked to create or restyle web pages, components, or applications (HTML/CSS/JS, React, Vue, etc.).

Interview the user relentlessly about a plan, design, or domain model until reaching shared understanding. Use when user wants to stress-test a plan, get grilled, or mentions "grill me".

Trigger native web search. Use when you need quick internet research with concise summaries and full source URLs.

Fetch a URL or convert a local file (PDF/DOCX/HTML/etc.) into Markdown using `uvx markitdown`, optionally it can summarize

Use `uv` instead of pip/python/venv. Run scripts with `uv run script.py`, add deps with `uv add`, use inline script metadata for standalone scripts.

Use when creating, editing, auditing, or validating Agent Skills. Covers TDD-based creation and specification compliance auditing.

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.

Compact the current conversation into a handoff document for another agent to pick up.

Use when reviewing code, conducting code reviews, analyzing pull requests, or when the user mentions "code review", "PR review", "code quality", or "static analysis".

Use when creating git commits, writing commit messages, or when the user mentions conventional commits, semantic versioning, or automated changelog generation.

Use when generating comprehensive documentation for a codebase, creating wiki pages, documenting architecture, or when the user mentions "deep wiki", "codebase documentation", or "generate docs".

Use when analyzing security vulnerabilities, conducting security reviews, checking for common vulnerabilities, or when the user mentions "security", "vulnerability", "CVE", "OWASP", or "penetration test".

Use when analyzing system performance, debugging performance issues, investigating bottlenecks, or when the user mentions "performance analysis", "USE method", "flame graphs", "Brendan Gregg", or "system performance".