By aborroy
Develop Alfresco/Hyland Content Services extensions by scaffolding Maven JARs, Spring Boot event handlers, Share UI customizations, BPMN workflows, web scripts, content models, and Docker Compose stacks from REQUIREMENTS.md; validate models, APIs, security, and healthchecks; generate tests; diagnose errors and propose architectures with agents and auto-triggering skills.
npx claudepluginhub aborroy/aiup-alfrescoScaffold Alfresco ActionExecuter classes with Spring bean registration. In-Process SDK (Maven) only.
Generate Share Aikau page and dashlet artefacts for legacy Share UI customizations.
Scaffold Alfresco behaviour/policy classes with Spring bean wiring. In-Process SDK (Maven) only.
Generate Alfresco content model XML and Spring context file from requirements.
Generate a Docker Compose file with full ACS stack.
Generate an Out-of-Process Spring Boot event listener for Alfresco Java Event API.
Gather and structure requirements for an Alfresco extension as user stories with acceptance criteria.
Scaffolds one deployable project or a mixed multi-project repository from REQUIREMENTS.md: pom.xml(s), module.properties, module-context.xml, Share-tier base structure, and Spring Boot Application class. Supports Platform JAR (in-process), Share JAR (web-tier), Event Handler (out-of-process), and mixed architectures. Run this first, before /content-model.
Generate Share form configuration and related web-extension files for legacy Share UI customizations.
Generate Share Surf extension artefacts for legacy Share pages, components, templates, and extension metadata.
Generate integration tests for Alfresco extensions using Testcontainers (self-contained, no pre-running ACS required).
Generate Alfresco Web Script descriptors, controllers, and FreeMarker templates. In-Process SDK (Maven) only.
Generate Activiti BPMN 2.0 process definition, workflow task content model, Spring bootstrap registration, i18n message bundle, and optional Java task listener. In-Process SDK (Maven) only.
Given a business requirement, proposes full Alfresco extension architecture including content types, behaviours, REST endpoints, events, and deployment model. Produces an Architecture Decision Record.
Given an Alfresco stack trace or log snippet, searches documentation and known issues to diagnose the root cause and suggest a fix. Covers classloader issues, model registration errors, Transform Service failures, and common ACS problems.
Analyses an existing Alfresco AMP or JAR extension, identifies deprecated APIs and outdated patterns, and produces a migration plan with concrete code diffs.
Validates Alfresco content model XML files for correct namespace URI format, mandatory type/aspect declarations, valid property data types, and absence of reserved prefixes (sys:, cm:, app:). Trigger automatically when generating or editing *-model*.xml or *-context.xml files.
Ensures every service in a Docker Compose file has a healthcheck block and depends_on uses condition: service_healthy. Trigger when generating or editing compose.yaml.
Validates ActiveMQ topic names and consumer group patterns against Alfresco event API conventions. Applies to Out-of-Process SDK (Spring Boot) only. Trigger when generating event-driven code with /events.
Detects deprecated Alfresco API usage and suggests modern equivalents. Trigger when analysing existing Alfresco extension code.
Warns when CMIS or Alfresco Query Language queries may bypass ACLs. Suggests SearchService with authority context instead. Trigger when generating search or query code.
Reads pom.xml, detects which Alfresco SDK is in use (In-Process Maven SDK or Out-of-Process Spring Boot SDK), and adjusts generated code accordingly. Trigger when generating Java code for Alfresco extensions.
Validates Alfresco Activiti BPMN 2.0 process definition files and companion workflow model XML for structural correctness: required namespaces, task assignees, variable naming conventions, process variable promotion pattern, formKey alignment, and forbidden Activiti 6/Flowable patterns. Trigger automatically when generating or editing *.bpmn files or *-workflow-model.xml files.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Plugin de ingeniería de software completa: 10 agentes de núcleo y 9 opcionales con personalidad propia, memoria persistente por proyecto, quality gates y flujos automatizados desde la idea hasta producción.
Use this agent when you need to design scalable architecture and folder structures for new features or projects. Examples include: when starting a new feature module, refactoring existing code organization, planning microservice boundaries, designing component hierarchies, or establishing project structure conventions. For example: user: 'I need to add a user authentication system to my app' -> assistant: 'I'll use the code-architect agent to design the architecture and folder structure for your authentication system' -> <uses agent>. Another example: user: 'How should I organize my e-commerce product catalog feature?' -> assistant: 'Let me use the code-architect agent to design a scalable structure for your product catalog' -> <uses agent>.
Use this agent when you need to design scalable architecture and folder structures for new features or projects. Examples include: when starting a new feature module, refactoring existing code organization, planning microservice boundaries, designing component hierarchies, or establishing project structure conventions. For example: user: 'I need to add a user authentication system to my app' -> assistant: 'I'll use the code-architect agent to design the architecture and folder structure for your authentication system' -> <uses agent>. Another example: user: 'How should I organize my e-commerce product catalog feature?' -> assistant: 'Let me use the code-architect agent to design a scalable structure for your product catalog' -> <uses agent>.
Expert agents for software architecture, backend development, and system design
Phase-based AI development framework with 16+ specialized agents, structured phases, and file-based handoffs. Works with greenfield and existing codebases.
Full-stack agents — frontend, backend, API, DevOps architects
Share bugs, ideas, or general feedback.