By aborroy
Develop Alfresco/Hyland ECM extensions with AI-assisted scaffolding, validation, and diagnostics. Generate Java/Spring Boot code for content models, REST APIs, workflows, and UI components; validate XML configs, Docker Compose, and BPMN; analyze deprecated APIs and produce migration plans.
Scaffold a full ACA/ADW UI extension: plugin.json descriptor, provideExtension() providers function, NgRx actions and effects, Angular standalone components for the requested extension points (page, sidebar, context menu, toolbar), HTTP service, and integration patch instructions for extensions.module.ts, project.json, and app.config.json.
Scaffold Alfresco ActionExecuter classes with Spring bean registration. In-Process SDK (Maven) only.
Generate Share Aikau page and dashlet artefacts for legacy Share UI customizations.
Generate a custom Alfresco audit application (audit XML + data extractors/generators + enable properties) and optional query Web Script. In-Process SDK (Maven) only.
Scaffold Alfresco behaviour/policy classes with Spring bean wiring. 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 custom Alfresco audit application XML for well-formedness, correct audit model namespace, application key matching the enable property, and every RecordValue dataExtractor/dataGenerator referencing a declared and registered bean. Trigger automatically after generating or editing a *-audit.xml or an audit *DataExtractor.java / *DataGenerator.java file.
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.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses power tools
Uses power tools
Uses Bash, Write, or Edit tools
Uses Bash, Write, or Edit tools
A Claude Code plugin and portable prompt pack for Alfresco extension development. It packages the workflow as command specs, skills, and agents so the same repository guidance can be reused from Claude, Codex, OpenClaw, or another coding agent.
AIUP (AI Unified Process) is a spec-driven approach to AI-assisted development. This project applies AIUP principles to Alfresco extensions.
If this project keeps expanding in scope and quality, it may eventually supersede the guidance currently collected in alfresco-developer-series.
claude plugin install aborroy/aiup-alfresco
Or for local development:
claude --plugin-dir /path/to/aiup-alfresco
If you are using Codex, OpenClaw, or another agent, installation is optional; you can use the portable renderer below directly from the repository checkout.
The slash-command UX is Claude-specific, but the command logic is portable because it lives in commands/*.md and AGENTS.md.
List the available commands:
./scripts/aiup-command.sh list
Render a Codex-compatible prompt for /requirements:
./scripts/aiup-command.sh render --agent codex requirements \
"We need to manage technical documents with categories and review dates"
Render an OpenClaw-compatible prompt for /scaffold:
./scripts/aiup-command.sh render --agent openclaw scaffold
The renderer emits a plain prompt that tells the target agent to:
AGENTS.mdcommands/<name>.mdskills/ or agents/ files manuallySee PORTABILITY.md for the non-Claude workflow.
Run the workflow inside Claude Code:
In-Process extensions (behaviours, web scripts, actions, workflows — deployed as JAR/AMP inside ACS):
/requirements # Gather requirements + decide project architecture
/scaffold # Generate pom.xml, module.properties, module-context.xml
/content-model # Generate content model XML
/workflow # Generate Activiti BPMN process + workflow task model (optional)
/web-scripts # Generate Web Script descriptors & controllers
/behaviours # Scaffold behaviours/policies
/actions # Scaffold action executors
/scheduled-jobs # Generate cluster-safe Quartz scheduled job + unit test
/docker-compose # Generate full ACS stack compose.yaml
/test # Generate integration tests
Out-of-Process extensions (event listeners — deployed as a separate Spring Boot app):
/requirements # Gather requirements + decide project architecture
/scaffold # Generate pom.xml, Application.java, application.properties
/events # Generate Spring Boot event listener
/docker-compose # Generate full ACS stack + listener service compose.yaml
/test # Generate integration tests
Mixed extensions (both in-process and out-of-process components):
/requirements # Gather requirements + decide project architecture
/scaffold # Generate aggregator POM + both sub-module skeletons
/content-model # Generate content model XML (platform sub-module)
/behaviours # Scaffold behaviours/policies (platform sub-module)
/events # Generate Spring Boot event listener (events sub-module)
/docker-compose # Generate full ACS stack compose.yaml
/test # Generate integration tests for both modules
Legacy Share/UI extensions (Share-tier addons such as share-config-custom.xml, Surf, Aikau):
/requirements # Gather requirements + decide whether Share is really the UI target
/scaffold # Generate a Share-only project or a mixed repo+share/events layout
/share-config # Generate Share forms and share-config-custom.xml
/surf # Generate Surf pages, components, and extension metadata
/aikau # Generate Aikau pages, widget models, and dashlet-style UI
Share-tier architecture is now modeled explicitly at the planning and scaffolding level.
/share-config, /surf, and /aikau are available now.
npx claudepluginhub aborroy/aiup-alfrescoUse 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>.
Universal templating and Harness expert plugin for Claude Code - enables fully autonomous project generation, pipeline creation, and deployment automation through a unified template interface. Supports Handlebars, Cookiecutter, Copier, Maven archetypes, and Harness pipelines. 5 commands, 6 agents, 3 skills.
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>.
Full-stack agents — frontend, backend, API, DevOps architects
Expert agents for software architecture, backend development, and system design