claude

imersao

Skills de IA curadas da Imersão IA da ParisGroup — auditoria, testes, arquitetura, devops, mobile, docs e mais. Funciona em qualquer projeto.

1 on GitHubby ParisGroupv1.0.0MITupdated 1 month ago
/

Plugin imersao from marketplace imersao-ia in parisgroup-ai/imersao-ia-setup. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (74)

  • agents-maintenance

    Use when working in monorepos with multiple apps/packages, when CLAUDE.md or AGENTS.md files need validation, when detecting broken links, redundant or conflicting instructions, vague instructions, incomplete coverage, or inconsistent formatting - validates structure, links, and instruction quality

  • api-design

    Design and implement professional REST APIs with consistent patterns, proper error handling, versioning, pagination, and OpenAPI documentation. Use when building any API endpoint, service, or backend interface. Triggers on: REST API, GraphQL, endpoint design, API routes, backend services, webhooks.

  • brainstorming

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

  • ci-fix

    Diagnose and fix a failing CI / GitHub Actions run. Use when a pipeline or build breaks. Triggers on: ci quebrou, ci falhou, conserta o ci, arruma o ci, build quebrou, o actions ta vermelho, pipeline failing, workflow failed, fix ci.

  • clean-architecture

    Enforce clean architecture principles, SOLID patterns, and scalable code organization. Use when building backends, APIs, microservices, or any application requiring maintainable, testable structure.

  • code-consolidation

    This skill should be used when the user asks to "find duplicated code", "map responsibilities", "consolidate code", "find code sprawl", "analyze duplication", "create consolidation plan", or mentions "código duplicado", "responsabilidades espalhadas", "consolidar". Analyzes codebases to identify sca

  • code-quality

    Análise proativa e sob demanda de qualidade de código. Detecta código morto, duplicações, oportunidades de consolidação, complexidade excessiva e code smells. Sugere melhorias e executa correções com aprovação. Triggers on: código morto, dead code, duplicação, duplicated, cleanup, refactor, complexi

  • context-maintenance

    Use when starting a session on a project with memory files or AGENTS.md after a gap, after changing backend services or API configurations, after adding features or packages, or when the user says "check maintenance", "atualizar contexto", "context fresh", "memory audit". Also trigger proactively wh

  • coverage-check

    Validate coverage thresholds and PR gates, flagging critical low-coverage files. Use when enforcing a minimum coverage bar. Triggers on: checar cobertura, threshold de cobertura, gate de cobertura, minimo de cobertura, arquivos sem teste, coverage gate, coverage check.

  • coverage-report

    Analyze coverage history, trends and comparisons between snapshots or branches. Use when you want to see how coverage evolved. Triggers on: relatorio de cobertura, tendencia de cobertura, comparar cobertura, evolucao da cobertura, coverage report, coverage trend.

  • coverage-run

    Run test coverage across local stacks (Vitest, Playwright, pytest). Use when you want to measure how much of the code the tests cover. Triggers on: rodar cobertura, cobertura de testes, gerar coverage, quanto de cobertura, run coverage, test coverage.

  • database-design

    Design efficient database schemas with proper indexing, relationships, normalization, and migration strategies. Use when creating or modifying database structures. Triggers on: database schema, tables, migrations, indexes, SQL, queries, data modeling.

  • design-auditoria

    Use ao auditar produto digital (landing pública, painel logado, dashboard, fluxo multi-step, app) e entregar documento formal A4 print-ready (HTML + PDF) pronto pra stakeholder externo. Roda método em 6 camadas (captura, diagnóstico estrutural, heurísticas Nielsen+Laws of UX+Baymard, WCAG, fricção/d

  • design-critic

    Designer senior extremamente critico. Analisa aplicacao web em 5 pilares (Visual Consistency, Information Hierarchy, Interaction Quality, Spatial Design, Polish & Craft), captura screenshots via Playwright, gera relatorio com score, e aplica auto-fix em todos os findings. Triggers on: design audit,

  • design-usabilidade

    Use when analyzing user journeys, auditing UX quality, prototyping flows, or designing new pages/features from a product perspective. Triggers on: jornada do usuario, fluxo de agendamento, prototipo, prototipar, experiencia do usuario, UX audit, usabilidade, melhorar conversao, nova pagina, nova fea

  • docker-devops

    Create optimized Docker configurations, docker-compose setups, Kubernetes manifests, and CI/CD pipelines. Use when containerizing applications, setting up deployment infrastructure, or automating builds. Triggers on: Docker, Dockerfile, container, docker-compose, Kubernetes, k8s, CI/CD, GitHub Actio

  • drizzle-migrations

    Use when creating, applying, troubleshooting, or recovering Drizzle ORM migrations. Triggers on: schema change, new table, add column, alter table, migration error, type already exists, relation already exists, desync, mega-migration, db:generate, db:migrate, db:push, Railway deploy failure.

  • e2e-analyze

    Analyze E2E test failures with timeline reconstruction, code correlation, and history lookup. Use after running tests: 'analyze e2e', 'e2e failures', 'diagnose tests'.

  • e2e-architect

    Plan, audit or debug end-to-end (E2E) test coverage, flows and fixtures (Playwright). Use when designing or improving an E2E test suite. Triggers on: planejar testes e2e, arquitetura de testes e2e, cobertura e2e, estrategia de e2e, fixtures e2e, e2e architect, end-to-end test plan.

  • e2e-chrome-devtools

    Visual smoke test using Chrome DevTools MCP against a running web app (local or production). Navigates key pages, captures screenshots, inspects console errors, network failures, runs Lighthouse audits, tests mobile/dark-mode emulation, and traces performance. Use this skill whenever the user says "

  • e2e-fix-cycle

    Automated E2E test-fix cycle. Runs tests, analyzes failures, applies fixes in batches, re-runs until pass. Use for full automation: 'fix e2e', 'e2e cycle', 'auto-fix tests'.

  • e2e-run

    Smart E2E test runner with auto-detection of Playwright project and wait strategies. Use when running E2E tests: 'run e2e', 'e2e admin', 'test admin-tests', 'run creator tests'.

  • executing-plans

    Use when you have a written implementation plan to execute in a separate session with review checkpoints

  • find-skills

    Use when the user asks how to do something and may need a local or installable skill.

  • finishing-a-development-branch

    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

  • github-design

    Use when setting up GitHub repositories, workflows, issue templates, or project organization - enforces best practices for .github folder structure, reusable workflows, branch protection, CODEOWNERS, labels, and GitHub Projects. Triggers on: GitHub, repository setup, workflow, Actions, issue templat

  • i18n-audit

    Audita código fonte para encontrar textos hardcoded em português que precisam usar o sistema de tradução (i18n). Detecta strings em TSX/TS que deveriam usar t() ou useTranslations. Triggers on: texto hardcoded, hardcoded text, auditoria i18n, i18n audit, tradução faltando, missing translation in cod

  • i18n-maintenance

    Use when working with internationalization files, translation keys, or multi-language support - validates translation coverage, detects missing keys, finds unused translations, validates code↔JSON sync, and ensures consistency across all locales. Triggers on i18n, translation, locale, intl, multi-la

  • imersao-primeiros-passos

    Guia o aluno da Imersão IA da ParisGroup logo depois de instalar o ambiente. Use quando a pessoa disser 'instalei e agora', 'por onde começo', 'primeiros passos', 'como começo', 'estou perdido', 'o que faço agora', 'terminei o setup', 'comecei a imersão', 'me ajuda a começar', 'first steps', 'where

  • impeccable

    Provides premium design vocabulary, supporting Google Stitch spec-based DESIGN.md / PRODUCT.md and anti-pattern slop removal.

  • launch-audit

    Run a comprehensive pre-launch quality audit on any web application. Explores the codebase first, then generates project-specific audit prompts that reference the actual files, routes, hooks, and functions found. Covers 7 areas: security, functionality, domain data coherence, visual consistency, per

  • log-audit

    Use when analyzing error logs, production failures, or recurring log patterns from Railway, files, or console output.

  • logger-design

    Design e implementação de logging estruturado com distributed tracing. Enforça schema rígido, correlation IDs, sanitização de PII e boas práticas de observabilidade. Multi-stack (Node.js, Python, Go, Frontend). Triggers on: log, logging, logger, trace, tracing, observability, correlation, span, stru

  • maestro-analyze

    Investigate why a Maestro mobile test on the iOS Simulator failed. Use after a mobile/simulator test fails and you need the cause. Triggers on: teste mobile falhou, porque o teste do app quebrou, analisar falha mobile, maestro falhou, mobile test failed, ios simulator error.

  • maestro-capture

    Capture iOS Simulator screens via Maestro to compare the app against design references. Use when you want screenshots of the mobile app. Triggers on: screenshot do app, capturar telas do simulador, comparar com o design mobile, telas do app mobile, maestro capture, ios simulator screenshot.

  • maestro-fix-cycle

    Auto-repair loop for failing Maestro mobile tests on the iOS Simulator, one flow at a time. Use when you want mobile/simulator tests fixed automatically. Triggers on: conserta os testes mobile, arruma o teste do simulador, loop de correcao mobile, fix mobile tests, auto fix ios tests.

  • maestro-run

    Run the app's mobile UI tests on the iOS Simulator with Maestro. Use when you want to run mobile tests on a simulator. Triggers on: teste mobile, testar no simulador, rodar app no simulador iOS, teste de app mobile, maestro, mobile test, ios simulator test.

  • memory-bank

    Maintain and update project memory-bank files for persistent context across Claude Code sessions. Use when starting a new session, completing features, making architectural changes, or when context needs to be preserved. Triggers on: memory bank, project context, session start, context update, CLAUD

  • mobile-native-bestpractices

    Build or review React Native / Expo code for architecture, UX, performance and native best practices. Use when writing or reviewing a React Native / Expo app. Triggers on: react native, expo, app nativo, boas praticas mobile nativo, arquitetura react native, performance no app nativo, react native r

  • mobile-pwa-usability

    Use when building or modifying React/Next.js components, pages, layouts, PWA configurations, or CSS/Tailwind files - enforces mobile usability standards with mandatory checks for critical issues (touch targets, viewport, safe areas, accessibility) and recommendations for PWA optimization (manifest,

  • obsidian-docs

    Create comprehensive technical documentation following Obsidian conventions with bidirectional linking, proper folder structure, templates, and developer-focused content. Use when creating documentation, READMEs, wikis, knowledge bases, ADRs, runbooks, or any technical writing. Triggers on: document

  • pr-lifecycle

    Full PR lifecycle management: list, analyze, validate, and merge pull requests. Auto-detects validation gates per package and integrates a code-review pass for code analysis. Use when: managing PRs, checking PR status, reviewing open PRs, merging PRs, triaging PRs, cleaning up stale PRs, validating

  • project-release

    Use when releasing or deploying a project, creating versions or tags, or preparing a production publish flow.

  • project-stats

    Generate a comprehensive project statistics report with language breakdown, git activity, test coverage, dependencies, and infrastructure detection. Automatically compares with the previous report to show growth trends and deltas. Use this skill whenever the user asks for project statistics, project

  • prompt-maintenance

    Maintain prompt templates with dependency tracking, documentation, and validation. Use when auditing prompts, generating catalog, or checking template structure.

  • prototype-first

    Use ANTES de implementar qualquer feature de UI — prototipe e valide o design primeiro em vez de construir duas vezes. Roteia frontend web para o Design OS público (clone + npm run dev) e UI pequena para frontend-design; auto-pula em trabalho de backend, CLI ou biblioteca. Triggers — "nova tela", "n

  • pwa-audit

    Scan components for PWA mobile-first compliance violations. Use when: auditing touch targets, input sizing, touch-manipulation, safe areas across a codebase or module.

  • qa-mobile

    Check responsive layout and mobile-viewport regressions in the browser (web page, not a device). Use when a web page looks broken on small/mobile screen sizes. Triggers on: responsivo, layout no celular, quebrou no mobile, tela pequena, layout responsivo no navegador, responsive, mobile viewport.

  • railway-debug

    Analyze Railway production logs and debug deploy/runtime errors. Full workflow from log collection through root cause analysis, migration recovery, and post-deploy verification.

  • railway-logs

    Fetch and diagnose Railway deployment logs for production issues. Use when an app or deploy on Railway is erroring. Triggers on: logs do railway, ver os logs, erro em producao, app caiu, deploy quebrou no railway, railway logs, production error.

  • readme-maintenance

    This skill should be used when the user asks to "audit READMEs", "update documentation", "check README consistency", "find missing READMEs", "generate README", "validate docs", or mentions README/documentation maintenance for packages and apps.

  • redis-design

    Use when designing Redis data structures, caching strategies, or key schemas - enforces key naming conventions, hash tags for clustering, memory optimization, proper cache patterns, error handling with circuit breakers, and rate limiting algorithms. Triggers on: Redis, cache, key design, TTL, rate l

  • repo-cleanup

    Use when cleaning legacy junk accumulated in a repository — orphan docs, stale test artifacts, abandoned scripts, unused assets, backup files, deprecated migrations. Works generically across any stack (JS/TS, Python, Rust, Go, PHP, mixed monorepos). Uses grep/ripgrep to verify zero references before

  • reviewer

    Validate proposals before implementation and generate ADR/PR documentation. Forces structured review of plans, architecture decisions, and code changes before executing. Use when making significant changes, starting new features, refactoring, or when uncertainty exists. Triggers on: review this, val

  • saas-bootstrap

    Use when starting a new SaaS project from scratch, bootstrapping a production-ready monorepo with Stripe billing, authentication, and AI services. Triggers on: novo saas, bootstrap saas, criar projeto saas, new saas project, scaffold saas, production-ready saas, saas from scratch, monorepo saas, sta

  • saas-migration-audit

    Use when analyzing an existing project for migration feasibility to the canonical SaaS stack (Turborepo, Next.js, tRPC, Drizzle, Auth.js, Stripe, PageShell). Triggers on: migrar projeto, migration audit, avaliar migração, stack audit, comparar stack, viabilidade de migração, analisar projeto existen

  • security-practices

    Implement security best practices including authentication, authorization, input validation, encryption, and OWASP Top 10 protection. Use when handling user data, auth, or sensitive operations. Triggers on: security, authentication, authorization, JWT, OAuth, password, encryption, validation, XSS, S

  • session-close

    End-of-session cleanup that persists learnings, reviews work, closes tasks, and updates project memory. Use this skill at the end of any work session — when the user says "done", "terminei", "encerrar sessão", "session close", "wrap up", "finalizar", "fechar sessão", "vou parar", "that's it for toda

  • spell-check-pt-en

    Use when writing or editing user-facing text (PT-BR or EN) that will be persisted to files — UI copy, i18n strings, error messages, CLI help text, README/docs, commit messages, doc comments. Do NOT use for chat replies to the user, internal logs, or temporary scratch text.

  • sprint-report

    Use when generating a weekly sprint summary from TaskNotes or preparing a standup-style progress report.

  • subagent-driven-development

    Use when executing implementation plans with independent tasks in the current session

  • systematic-debugging

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

  • tag-audit

    Audit git tags vs npm versions vs package.json for misalignment. Use when: pre-release (both /release-maintenance and /project-release), after failed releases, investigating E409 conflicts, deploy version drift, or periodic health checks.

  • tasknotes

    This skill should be used when the user asks to 'create a task', 'add a TODO', 'plan a sprint', 'organize tasks', 'track time', 'setup Kanban', 'create task from code', 'sync tasks with sprint', 'pomodoro session', 'start pomodoro', 'time estimate', or mentions TaskNotes, task management, or project

  • team-execute

    Execute an implementation plan through the multi-agent team pipeline. Use when you have a plan and want agents to build it. Triggers on: executar o plano, rodar o plano com agentes, implementar o plano, build com agentes, team execute, execute plan.

  • team-plan

    Turn a feature request into an implementation plan using parallel research agents. Use when you want a multi-agent plan before building a feature. Triggers on: planejar feature, plano de implementacao, planejar com agentes, montar um plano, team plan, implementation plan, plano multi-agente.

  • team-reviewer

    Review a PR or local diff with a parallel team of specialized review agents. Use when you want a thorough multi-agent code review. Triggers on: revisar PR, review do diff, revisao com agentes, revisar minhas mudancas, revisao de codigo, team review, code review multi-agente.

  • test-driven-development

    Use when implementing any feature or bugfix, before writing implementation code

  • test-rigor-audit

    Use when auditing tests that may not verify real behavior: tautological assertions, missing assertions, skipped tests without a tracker, mock-everything tests, swallowed exceptions, snapshot churn, and framework traps in vitest/jest, pytest, Playwright, and bats. Trigger on requests such as "audit t

  • testing-strategy

    Write comprehensive test suites with proper structure, mocking strategies, fixtures, and coverage goals. Use when implementing unit tests, integration tests, or e2e tests. Triggers on: tests, testing, unit test, integration test, e2e, jest, vitest, pytest, mocking, TDD.

  • usecase-design

    Implement features in modular Clean Architecture with use cases and thin tRPC routers. Use when structuring backend feature logic into use-case modules. Triggers on: caso de uso, use case, clean architecture, criar use-case, organizar backend em modulos, camada de aplicacao, tRPC router.

  • verification-before-completion

    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

  • weekly-metrics

    Generate a weekly productivity metrics report for solo AI-assisted development. Analyzes git commits, TaskNotes, and collaboration patterns from the last 7 days, then proposes workflow optimizations. Use this skill whenever the user asks for a weekly report, productivity metrics, sprint retrospectiv

  • writing-plans

Slash commands (7)

  • /imersao:pg-imersao-goal

    Dia 3 · REFINAR — só o plano curto depois da validação. Não constrói o MVP. Não redesenha o produto.

  • /imersao:pg-imersao-implementar

    Dia 2 · CONSTRUIR — onda 1 (MVP) com writing-plans + executing-plans. O resto do produto fica no plano, na mesma pasta.

  • /imersao:pg-imersao-playbook

    Dia 1 · PLAYBOOK — tira o processo da cabeça e grava playbook.md. Use quando o aluno disser playbook, processo, rotina, curso ToStudy, tirar da cabeça.

  • /imersao:pg-imersao-prd

    Dia 1 · CONTEXTO — playbook + três caminhos + plano do produto com mapa de ondas (visão, onda 1, depois).

  • /imersao:pg-imersao-prototipo

    Dia 2 · DESENHAR — protótipo no Design OS, telas com selo onda 1 ou depois.

  • /imersao:pg-imersao-publicar

    Dia 3 · PUBLICAR — GitHub + Railway. Prova, uso e manutenção (onda 2 sem reinstalar).

  • /imersao:pg-imersao-start

    👈 COMECE AQUI — a bússola da imersão. Mostra os 3 dias da sala e o próximo passo (não executa nada).

View source on GitHub

Maintain imersao?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted