Project Analyzer plugins for comprehensive architectural analysis, component deep analysis, and dependency auditing
Run a full architectural analysis including dependencies, architecture, and component deep-dives. Generate comprehensive reports with MANIFEST index.
Run a dependency audit on the project and generate a full report with the findings and the documentation for each dependency.
Use this agent when you need a comprehensive architectural analysis of a codebase. Examples: <example>Context: User wants to understand the overall architecture of a new project they've inherited. user: 'I just inherited this codebase and need to understand its architecture' assistant: 'I'll use the architectural-analyzer agent to provide you with a comprehensive architectural analysis of the project' <commentary>The user needs architectural understanding, so use the architectural-analyzer agent to generate a detailed architectural report.</commentary></example> <example>Context: Team is preparing for a major refactoring and needs architectural insights. user: 'We're planning a major refactoring and need to understand our current architecture first' assistant: 'Let me use the architectural-analyzer agent to create a detailed architectural report that will help guide your refactoring decisions' <commentary>Since architectural understanding is needed for refactoring decisions, use the architectural-analyzer agent.</commentary></example> <example>Context: Code review reveals potential architectural issues. user: 'I've been reviewing code and I'm concerned about our architectural coupling' assistant: 'I'll use the architectural-analyzer agent to perform a deep architectural analysis and identify coupling issues' <commentary>Architectural concerns require the architectural-analyzer agent to provide comprehensive analysis.</commentary></example>
Use this agent when you need to perform deep technical analysis of software components, understand their implementation details, business rules, and architectural relationships. Examples: <example>Context: User wants to understand how a specific service works in their microservices architecture. user: 'Can you analyze the payment-service component and explain how it works?' assistant: 'I'll use the component-deep-analyzer agent to perform a comprehensive analysis of the payment-service component.' <commentary>The user is requesting detailed component analysis, so use the component-deep-analyzer agent to examine the payment-service implementation, dependencies, and business logic.</commentary></example> <example>Context: User has an architecture report and wants detailed analysis of key components mentioned in it. user: 'I have this architecture report that mentions several core components. Can you analyze each of the main components listed?' assistant: 'I'll use the component-deep-analyzer agent to examine each of the core components mentioned in your architecture report.' <commentary>The user wants component-level analysis based on an architecture report, which is exactly what the component-deep-analyzer agent is designed for.</commentary></example>
Use this agent when you need to analyze and audit the health, security, and status of dependencies in a software project. It identifies outdated, deprecated, or legacy libraries, checks for vulnerabilities, and provides structured, actionable insights without ever altering the codebase. Examples: <example>Context: User wants to understand the current state of their project's dependencies before a major release. user: 'Can you check if our dependencies are up to date and secure?' assistant: 'I'll use the dependency-auditor agent to analyze your project's dependencies and provide a comprehensive audit report.' <commentary>Since the user is asking for dependency analysis, use the dependency-auditor agent to review package health and security.</commentary></example> <example>Context: User is concerned about potential security vulnerabilities in their third-party libraries. user: 'I'm worried about security issues in our npm packages' assistant: 'Let me use the dependency-auditor agent to scan for security vulnerabilities and outdated packages in your project.' <commentary>The user has security concerns about dependencies, so use the dependency-auditor agent to perform a security-focused dependency audit.</commentary></example> <example>Context: User wants to modernize their codebase and remove legacy dependencies. user: 'We need to identify which libraries are outdated or deprecated in our project' assistant: 'I'll use the dependency-auditor agent to identify outdated, deprecated, and potentially risky dependencies that should be updated or replaced.' <commentary>Since the user wants to identify legacy dependencies, use the dependency-auditor agent to analyze dependency health and modernization opportunities.</commentary></example>
Uses power tools
Uses Bash, Write, or Edit tools
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uma coleção de plugins para o Claude Code voltados à arquitetura de software e à documentação de design. Os plugins automatizam tarefas como registrar decisões arquiteturais, gerar diagramas, analisar a arquitetura de projetos e produzir guias de desenvolvimento por linguagem.
Este marketplace oferece quatro plugins para documentação e análise arquitetural:
| Plugin | Descrição | Comandos |
|---|---|---|
| ADRs Management | Análise, geração e vinculação de Architecture Decision Records (ADRs) | /adrs-management:adr-map, :adr-identify, :adr-generate, :adr-link |
| Diagrams Generator | Geração de diagramas C4 (PlantUML) e Mermaid a partir de Feature Design Documents (FDDs) | /diagrams-generator:c4-generate, :mermaid-generate |
| Project Analyzer | Análise arquitetural completa, análise profunda de componentes e auditoria de dependências | /project-analizer:generate-architectural-report, :run-dependency-audit |
| Development Guidelines | Geração de guias de desenvolvimento abrangentes e específicos por linguagem | /development-guidelines:guidelines-generate |
Todos os comandos abaixo são executados dentro do Claude Code no terminal (rode
claude). Em outros ambientes (extensões/IDE) o comando/pluginpode não estar disponível.
/plugin marketplace add Lucassamuel97/claude-plugins
Esse comando registra o repositório do GitHub como uma fonte de plugins. Você verá: Successfully added marketplace: lucassamuel-plugins.
O identificador do marketplace (
lucassamuel-plugins) é o camponamedefinido em .claude-plugin/marketplace.json — não é o nome do repositório.
Instale apenas os que for usar (ou todos):
/plugin install adrs-management@lucassamuel-plugins
/plugin install diagrams-generator@lucassamuel-plugins
/plugin install project-analizer@lucassamuel-plugins
/plugin install development-guidelines@lucassamuel-plugins
Após instalar, os comandos não ficam ativos imediatamente. Recarregue:
/reload-plugins
Se os comandos ainda não aparecerem após o
/reload-plugins, feche e reabra o Claude Code (saia e rodeclaudenovamente).
Os comandos dos plugins são namespaced pelo nome do plugin, no formato /<plugin>:<comando>:
/diagrams-generator:mermaid-generate docs/features/FDD_Rate_Limiter.md
/adrs-management:adr-map
/project-analizer:generate-architectural-report
/development-guidelines:guidelines-generate Python
Dica: digite
/e comece a escrever o nome do comando (ex.:/merou/diagrams) para o autocomplete mostrar o nome/namespace exato com que cada comando foi registrado.
Para navegar pelos plugins instalados e seus comandos a qualquer momento:
/plugin
Os comandos usam o prefixo do plugin (
/<plugin>:<comando>). Se preferir, digite/e use o autocomplete para localizá-los.
Documente decisões arquiteturais de forma sistemática, seguindo um fluxo de 3 fases (mapear → identificar → gerar) com vinculação ao final:
/adrs-management:adr-map # Fase 1: mapeia a base de código em módulos lógicos
/adrs-management:adr-identify AUTH DATA # Fase 2: identifica ADRs em potencial nos módulos
/adrs-management:adr-generate BILLING # Fase 3: gera ADRs formais no formato MADR
/adrs-management:adr-link # Vincula os ADRs com relacionamentos bidirecionais
Os ADRs podem ser gerados em vários idiomas (en, pt-BR, es, fr, de). O plugin aplica filtragem rigorosa — apenas cerca de 5% das descobertas viram ADRs — e usa o histórico do git para enriquecer o contexto temporal.
Crie documentação visual a partir de Feature Design Documents (FDDs):
/diagrams-generator:c4-generate docs/features/FDD_Rate_Limiter.md # Diagramas C4 (C1–C4) em PlantUML
/diagrams-generator:mermaid-generate docs/features/FDD_Rate_Limiter.md # Diagramas Mermaid (sequência, fluxo, classe, ER)
O idioma dos diagramas é detectado automaticamente a partir do FDD, mantendo os termos técnicos em inglês (Service, Gateway, Redis etc.). Nenhum diagrama é inventado quando o FDD não tem informação suficiente.
Este repositório já inclui um FDD de exemplo em docs/features/FDD_Rate_Limiter.md (um SDK de rate limiting em Go) para você testar os comandos imediatamente.
Analise a arquitetura e as dependências do projeto (somente leitura — não modifica o código):
npx claudepluginhub lucassamuel97/claude-plugins --plugin project-analizerDevelopment Guidelines plugin for generating comprehensive language-specific development guideline documents
Diagrams Generator plugins for C4 and Mermaid diagram generation from Feature Design Documents
ADRs Management plugins for Architecture Decision Records analysis, generation, and linking
Ultra-compressed communication mode. Cuts 65% of output tokens (measured) while keeping full technical accuracy by speaking like a caveman.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Unified capability management center for Skills, Agents, and Commands.