Transformar trabalho recente em rascunhos de conteudo pra publicar, com pesquisa de estrategia de viralizacao na web antes de drafting. Use quando o usuario quiser virar um achado tecnico, resolucao de bug, release ou case study em post de LinkedIn, thread de Twitter, caption de Instagram, ou outline de artigo. Default eh perguntar quais plataformas, mas aceita argumento (ex: /content linkedin, /content all). Salva os rascunhos em /content/drafts/YYYY-MM-DD-<slug>/ no repo atual pra revisao manual antes de postar. Tambem deve atuar PROATIVAMENTE: ao detectar trabalho content-worthy em qualquer sessao, sugerir ao usuario sem esperar invocacao explicita.
Creates Jira tasks from meeting notes, specs, or feature descriptions. Supports both iOS (Swift/SwiftUI) and Backend (Node.js/TypeScript) platforms. Use this skill whenever a user pastes meeting notes, a spec, a feature request, or any description of work to be planned. Triggers on: "create tasks", "break this into tickets", "plan this feature", "create Jira tickets", "turn this into tasks", or when a user pastes meeting notes or a feature spec and asks what to do with it. Always use this skill for task planning — even if the user doesn't say "Jira" or "tickets" explicitly.
Indexa, busca e sugere docs .md espalhados por ~/Desktop/knowledge/, pelo repo do projeto atual, e pelo dir de memory do Claude. Use quando o usuario perguntar "o que eu tinha doc sobre X?", "tem alguma ideia stale?", ou quando voce (Claude) terminar uma sessao tecnica e quiser sugerir docs relacionados pra atualizar/conectar. Tambem usado pra criar novos docs com frontmatter padronizado nos lugares certos. Aceita subcomandos: stale, drafts, related, suggest, new, index.
Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build plugin overhead, duplicate module builds from configuration drift, circular dependencies between modules, oversized modules needing splitting, or modularization best practices.
Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped `.build-benchmark/` artifacts. Use when a developer wants a baseline, wants to compare before and after changes, asks to measure build performance, mentions build times, build duration, how long builds take, or wants to know if builds got faster or slower.
Implement approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement. Use when the developer has reviewed an optimization plan and approved specific changes, or when there is a clear list of build-setting or source-level fixes to apply and verify.
Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to xcode-build-fixer, and re-benchmarking after changes. Use when a developer wants an end-to-end build optimization workflow, asks to speed up Xcode builds, wants a full build audit, or needs a recommend-first optimization pass covering compilation, project settings, and packages.
Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking.