com um clique
ai-dev-skills
ai-dev-skills contém 13 skills coletadas de olivomarco, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.
Skills neste repositório
Capture the current session's state into a clean, copy-pasteable handoff block so work can continue in a fresh session. Use when the user wants to hand off, continue elsewhere, start a new session, or uses any 'handoff' / 'continue session' trigger phrases.
Ingest YouTube transcripts from a single video or an entire playlist and produce a detailed, structured summary of what was said. Use when the user shares a YouTube URL (video or playlist) and wants a transcript, notes, key takeaways, or a summary. Triggers include 'summarize this YouTube video', 'transcribe this playlist', 'what does this video say', or any youtube.com / youtu.be link.
Roast the user about their own repository — a witty, savage-but-affectionate code review of the codebase's questionable choices. ONLY highlight really questionable choices, do not roast just for the sake of roasting. ONLY run when the user explicitly asks to be roasted, e.g. "roast me", "roast this repo", "roast my code", "destroy me", "be brutally honest about my repo". Never trigger automatically or infer this from unrelated requests. Technology-agnostic.
Audit a codebase for duplication and inconsistency (DRY violations) and propose concrete consolidation into shared components, helpers, and utilities. Use when asked to "find duplication", "DRY this up", "check consistency", "deduplicate code", or "find repeated patterns". Technology-agnostic.
Review the existing functionality of an application for correctness, broken flows, missing states, and bugs. Use when asked to "do a functional review", "check the app works correctly", "find broken flows", "review functionality", or "audit user flows". Technology-agnostic.
Review an application as a product and recommend the most impactful next features and functional improvements to build. Use when asked "what should I build next", "suggest new features", "next feature opportunities", "product improvement ideas", or "what's missing". Technology-agnostic.
Analyze a codebase for refactoring opportunities that improve maintainability, readability, and reduce technical debt, then produce a prioritized plan. Use when asked to "find refactoring opportunities", "identify code smells", "reduce tech debt", or "suggest refactors". Technology-agnostic.
Audit a codebase for security vulnerabilities and produce a prioritized remediation plan. Use when asked to "run a security review", "audit for vulnerabilities", "check OWASP Top 10", "find security issues", or "do a security audit". Technology-agnostic.
Audit unit-test coverage gaps and generate new tests to improve confidence on critical paths. Use when asked to "improve test coverage", "find untested code", "write missing unit tests", "audit test coverage", or "increase coverage". Technology-agnostic.
Remove AI-generated traces from text. Suitable for editing or reviewing text, making it sound more natural and like human handwriting. A comprehensive guide to "AI writing characteristics" based on Wikipedia. Detects and corrects the following patterns: exaggerated symbolism, Propaganda language, superficial analysis ending in -ing, vague attributions, excessive use of dashes, the three-part rule, AI vocabulary, negative parallelism, and excessive connecting phrases.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Audit and update existing documentation so it matches the current codebase — in-place updates only, no new files. Use when asked to "align the docs", "update documentation", "fix stale docs", "sync docs with code", or "check docs accuracy". Technology-agnostic.
Detect stale, dead, deprecated, or obsolete code, dependencies, config, and assets that can be safely removed. Use when asked to "find dead code", "check for stale code", "find unused dependencies", "detect obsolete code", or "clean up the codebase". Technology-agnostic.