Explore skills
Showing 48091–48120 of 77081 skills
Cria visualizações de dados interativas e profissionais usando Highcharts.js, gerando HTML standalone com gráficos animados, responsivos e acessíveis. Use este skill sempre que o usuário pedir para criar gráficos, charts, dashboards, visualizações de dados, ou qualquer representação visual de dados numéricos/categóricos. Deve ser usado quando o usuário mencionar termos como "gráfico", "chart", "dashboard", "highcharts", "visualização de dados", "gráfico de linhas", "barras", "pizza", "scatter", "heatmap", "treemap", "gauge", "stock chart", "mapa", "gantt", "sankey", "funnel", ou quando fornecer dados (CSV, JSON, tabela, planilha) pedindo representação visual. Também deve ser ativado quando o usuário pedir gráficos bonitos, interativos, animados, com tooltip, drill-down, ou exportáveis. Funciona com dados inline, CSV, JSON, e arquivos de dados. Sempre gera HTML standalone completo e funcional.
stribus/pygerengastos
Stars: 1Claude CodeCodexQuinto agente do Time de Migração. Define como provar que o sistema novo é comportamentalmente equivalente ao legado, com critérios adaptados ao paradigma escolhido. Produz parity_specs.md e parity_tests/*.feature em Gherkin. Ativação: /reversa-inspector (geralmente invocado por /reversa-migrate).
stribus/pygerengastos
Stars: 1Claude CodeCodexPrimeiro agente do Time de Migração. Detecta o paradigma do sistema legado a partir das specs, infere o paradigma natural da stack alvo, alerta sobre gaps e força uma decisão consciente do usuário. Produz paradigm_decision.md, leitura obrigatória de todos os agentes posteriores. Ativação: /reversa-paradigm-advisor (geralmente invocado por /reversa-migrate).
stribus/pygerengastos
Stars: 1Claude CodeCodexEsboça a abordagem técnica como delta sobre o legado, gerando roadmap, investigation, data-delta, onboarding e interfaces da feature ativa. Use quando o usuário digitar "/reversa-plan", "reversa-plan", "esboçar plano técnico" ou pedir para virar requirements em desenho de solução. Terceiro skill do ciclo forward, depois de `/reversa-requirements` e (opcionalmente) `/reversa-clarify`.
stribus/pygerengastos
Stars: 1Claude CodeCodexCria ou atualiza os princípios duradouros do projeto e propaga sugestões de ajuste nos templates dependentes. Princípios são raros, mudam pouco e influenciam todos os artefatos. Use quando o usuário digitar "/reversa-principles", "reversa-principles", "definir princípios" ou pedir para criar/alterar/aposentar um princípio do projeto. Pode rodar antes mesmo da primeira feature.
stribus/pygerengastos
Stars: 1Claude CodeCodexAuditoria de clareza textual do requirements. Verifica se a prosa é boa o bastante para gerar plano sem ambiguidade. NÃO mistura com auditoria de testes de implementação. Use quando o usuário digitar "/reversa-quality", "reversa-quality" ou pedir para revisar a qualidade do requirements antes de planejar. Etapa opcional do ciclo forward.
stribus/pygerengastos
Stars: 1Claude CodeCodexMapeia a superfície do projeto legado — estrutura de pastas, linguagens, frameworks, dependências e entry points. Use no início de uma análise de engenharia reversa para criar o inventário inicial do projeto.
stribus/pygerengastos
Stars: 1Claude CodeCodexQuinto agente do Time de Migração. Traduz as telas do sistema legado em especificações executáveis, fechando a lacuna entre o catálogo do design-system e o código pronto. Opera em duas fases. Fase 1: detecta plataforma origem/alvo, apresenta os modos (literal, modernizado, híbrido) e exige decisão humana, produzindo screen_modernization_decision.md. Fase 2: gera target_screens.md, screen_deviation_log.md e, quando o oráculo legado roda, golden files com manifest.yaml para o Inspector consumir. Ativação: /reversa-screen-translator (geralmente invocado por /reversa-migrate, entre Designer e Inspector).
stribus/pygerengastos
Stars: 1Claude CodeCodexTerceiro agente do Time de Migração. Propõe estratégias de migração com trade-offs explícitos, considerando brief, paradigma e apetite. Recomenda uma estratégia mas deixa a escolha como decisão humana. Produz migration_strategy.md, risk_register.md e cutover_plan.md. Ativação: /reversa-strategist (geralmente invocado por /reversa-migrate).
stribus/pygerengastos
Stars: 1Claude CodeCodexDecompõe o roadmap em ações atômicas com IDs sequenciais, dependências e marcador de paralelismo. Use quando o usuário digitar "/reversa-to-do", "reversa-to-do", "decompor em tarefas" ou pedir para virar o roadmap em uma lista executável. Quarto skill do ciclo forward, depois de `/reversa-plan`.
stribus/pygerengastos
Stars: 1Claude CodeCodexDocumenta a interface do sistema legado a partir de screenshots — extrai componentes, layouts, fluxos de navegação e estados de tela. Use quando screenshots do sistema estiverem disponíveis, sem necessidade de o sistema estar em execução.
stribus/pygerengastos
Stars: 1Claude CodeCodexInitialize or repair the local OYYO LinkedIn workspace and explain installation. Use when the user asks to install, configure, onboard, create local state, or check whether the pack is ready.
vpicciuolo/Linkedin-SuperAgent-MultiSkills
Stars: 1Claude CodeCodexAbre la rama de una rebanada con el nombre correcto. Usala al empezar una rebanada, antes de que cualquier especialista toque el árbol.
luciano-stefano-meloclaps/platform-argentum
Stars: 0Claude CodeCodexSafely add, change, pin, update, or remove flake inputs and external packages in the nixcf NixOS repository. Use for flake.nix or flake.lock changes; nixpkgs channel changes; input follows relationships; packages consumed from an input; module package options; or wiring an external package or module into a host, Home Manager profile, NixOS module, or Home Manager module.
lifeich1/nixcf
Stars: 0Claude CodeCodexImplement and review scoped NixOS or Home Manager module changes in the nixcf repository. Use when adding a reusable module, changing a `fool.*` option, wiring imports, enabling a feature for a host or Home profile, moving shared logic out of host/profile files, or updating the corresponding module documentation.
lifeich1/nixcf
Stars: 0Claude CodeCodexSafely audit or change Agenix-managed credentials and their runtime wiring in the nixcf repository. Use for secrets/default.nix declarations, secrets/secrets.nix recipient mappings, encrypted .age payload metadata, Xray settings, user password secrets, or the cross-layer Attic client/server/netrc credential path, including recipient changes, rotation planning, plaintext-to-Agenix migration, and credential leak remediation.
lifeich1/nixcf
Stars: 0Claude CodeCodexAdd, review, or refactor network-facing NixOS and Home Manager services in the nixcf repository while preserving service state and assigning each firewall rule to one owner. Use for firewall policy, listen addresses, ports, service users, systemd hardening, OCI containers, and service options involving Gitea, Attic, Hobob, Syncthing, vlmcsd, Bilibili Live Recorder, VirtualBox or desktop networking, Xray, OpenSSH, and KDE Connect.
lifeich1/nixcf
Stars: 0Claude CodeCodexModel product UI actions from user intent questions after a meaningful outcome, completion, created resource, imported data, uploaded file, synced integration, report, deployment, automation, review state, handoff, or workflow milestone. Use when deciding which actions to show, hide, group, name, prioritize, defer, or place across outcome, item, selection, continuation, navigation, recovery, and assistance scopes.
JohnWayneeee/ai-agent-skills
Stars: 1Claude CodeCodexConvert Pencil `.pen` design files and named Pencil node IDs into production frontend code. Use when asked to implement, migrate, reproduce, or refine a Pencil/Figma-like visual design in code, especially for responsive artboards, glassmorphism, typography matching, background image layers, design tokens, or visual fidelity debugging against Pencil node IDs.
JohnWayneeee/ai-agent-skills
Stars: 1Claude CodeCodexBest practices for writing, reviewing, and refactoring React Flow / @xyflow/react v12 canvases. Use when work touches React Flow components, custom nodes, custom edges, handles, node data typing, viewport controls, MiniMap/Background/Panel usage, NodeToolbar, NodeResizer, or workflow-builder review tasks.
JohnWayneeee/ai-agent-skills
Stars: 1Claude CodeCodexAnti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
afawzy886619888866-cloud/Sierra-Estates
Stars: 0Claude CodeCodexSystem-design thinking before any doc or code: goals/non-goals, back-of-envelope numbers, components and contracts, failure modes, operability, security, trade-offs. Use for "design this system", "architecture for X", "trade-offs for X", "how should we architect", "API design", "data model for", "service boundaries", or before an ADR. Hands off to /ship:write-docs to record the decision. Not implementation planning (/ship:design — that turns a decided design into stories).
heliohq/ship
Stars: 94Claude CodeCodexPlan implementation before coding: investigate the repo, write spec and plan, and validate with a peer. Use for "plan", "design approach", "scope", or any coding task needing a plan. Not system-design thinking (/ship:arch-design) or full /ship:auto.
heliohq/ship
Stars: 94Claude CodeCodexImplement from a spec or plan: extract stories, build in safe waves, test, commit, and get peer review per story. Use for "implement", "build/code this plan", or targeted fix findings. If no plan exists, use /ship:design first.
heliohq/ship
Stars: 94Claude CodeCodexAdd durable end-to-end tests for user/API-visible behavior. Detect or scaffold the E2E framework, write tests, run the app, and store evidence. Use for E2E, Playwright/Cypress, regression tests, or quality gates. Not exploratory QA.
heliohq/ship
Stars: 94Claude CodeCodexShip completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery.
heliohq/ship
Stars: 94Claude CodeCodexRuntime QA of a change: start the app, test acceptance criteria and edge cases, and report evidence. Use for "test this", "QA", "does it work", exploratory checks, or post-review runtime verification. Not static code review.
heliohq/ship
Stars: 94Claude CodeCodexImprove existing code without changing behavior: scan smells, simplify, dedupe, reuse utilities, and verify after edits. Use for refactor, cleanup, simplify, reduce duplication, extract method, dead code, or code smells. No PR.
heliohq/ship
Stars: 94Claude CodeCodexStatic code review of the active diff: trace changed paths and report concrete P1/P2/P3 correctness, security, or spec bugs with file:line evidence. Use for code review or bug checks. Not runtime QA.
heliohq/ship
Stars: 94Claude CodeCodexCreate or update structured docs under docs/ with frontmatter, numbering, lifecycle status, and index regeneration — guides, references, troubleshooting, design docs and ADRs. Use for "write a doc", "document this", "create a guide", "write an ADR", "update the docs". For the system-design thinking itself (architecture, trade-offs, failure modes) use /ship:arch-design first — it hands back here to record the decision.
heliohq/ship
Stars: 94Claude CodeCodex