Use this skill whenever the user mentions Microsoft Teams in a development context — whether they're building, integrating, configuring…
Draft anonymous one-page company teasers for sell-side M&A processes.
Research, validate, and set up technology profiles in content/technologies.
Generates structured 4-choice quizzes from technical articles, documentation, or tutorials to assess reader comprehension.
Identifies and resolves technical debt by auditing redundant code, unused imports, and debugging statements before session completion.
Identify, categorize, and prioritize technical debt.
End-of-session tech debt cleanup. Scans for TODOs, dead code, unused imports, type issues, and quick wins before you log off.
Optimize resumes for software engineering, PM, and technical roles
Create a new Rails project
Automatically identifies project languages, frameworks, and dependencies by analyzing configuration files to ensure development consistency.
Systematic debugging methodology for diagnosing failures and root cause analysis.
Write clear technical analysis, system architecture documents, decision records, and research synthesis.
Art-to-engine pipeline specialist - Masters shaders, VFX systems, LOD pipelines, performance budgeting, and cross-engine asset optimization
Use when writing a technical blog post from raw project data like research notes, session logs, Reddit/LinkedIn drafts, code, hex dumps…
Guidelines, research patterns, diagram standards, and publishing workflows for creating technical blog posts on yogendra.me (Hugo Clarity…
Technical briefing for developer sharing.
Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity
Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages.
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects.
Technical debt cleanup - inspects and cleans up duplicate code, console.log, unused imports, etc.
Identifies and remediates technical debt by cleaning up redundant code, unused imports, and debug statements to maintain high code quality.