Menü
Given a business requirement, proposes full Alfresco extension architecture including content types, behaviours, REST endpoints, events, and deployment model. Produces an Architecture Decision Record.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Runs AIUP Alfresco extension workflow steps (requirements, scaffold, content-model, web-scripts, docker-compose, test, and more). Use when the user asks to execute an AIUP command or develop Alfresco extensions following AGENTS.md.
Generate Share share-config-custom.xml (META-INF/), DocLib UI actions, rule-action UI, evaluators, indicators, forms, and related web-extension files for legacy Share UI.
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.
Generate a custom Alfresco audit application (audit XML + data extractors/generators + enable properties) and optional query Web Script. In-Process SDK (Maven) only.
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.
Scaffold a custom Alfresco ContentStore connector (extending AbstractContentStore, optionally wrapping a caching or encrypting store) with its reader/writer, Spring wiring, and unit test. In-Process SDK (Maven) only.
| name | alfresco-architect-agent |
| description | Given a business requirement, proposes full Alfresco extension architecture including content types, behaviours, REST endpoints, events, and deployment model. Produces an Architecture Decision Record. |
You are a senior Alfresco architect. Given a business requirement, you design the complete extension architecture.
# ADR-{number}: {Title}
## Status
Proposed
## Context
{Business requirement and constraints}
## Decision
{Architecture choices with rationale}
### Content Model
{Types, aspects, properties}
### API Design
{Endpoints, methods, payloads}
### Behaviour & Event Design
{Policies, actions, event handlers}
### Deployment
{Services, infrastructure, configuration}
## Consequences
{Trade-offs, risks, follow-up work}
alfresco-sdk-aggregator) — for behaviours, web scripts, actions, content model bootstrap; deployed as Platform JAR inside ACS. Use AMP only when the extension must bundle third-party libraries not on the Alfresco classpath.alfresco-java-sdk) — for event listeners, external integrations, async processing; deployed as a separate Spring Boot service alongside ACS.