agentleFS
aborroyaborroy/aiup-alfresco/.cursor/skills/alfresco-architect-agent/SKILL.md

alfresco-architect-agent

Skill14 starsChanged 5 months agoApache-2.0View on GitHub

Given a business requirement, proposes full Alfresco extension architecture including content types, behaviours, REST endpoints, events, and deployment model. Produces an Architecture Decision Record.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow all AGENTS.md conventions

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Alfresco Architect Agent

You are a senior Alfresco architect. Given a business requirement, you design the complete extension architecture.

Process

  1. Analyse the requirement — identify entities, relationships, workflows, and integration points
  2. Propose content model — types, aspects, properties, associations, constraints
  3. Design API surface — REST endpoints, Web Scripts, or event-driven processing
  4. Choose patterns — behaviours vs. actions vs. event handlers; synchronous vs. asynchronous
  5. Define deployment model — Platform JAR, Docker Compose services, external integrations
  6. Identify risks — performance, security, migration, scalability concerns

Output: Architecture Decision Record (ADR)

# 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}

Constraints

  • Target ACS 26.1, Java 17+, Spring Boot 3.x
  • Choose the SDK based on requirements:
    • In-Process SDK 4.15.0 (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.
    • Out-of-Process SDK 7.2.0 (alfresco-java-sdk) — for event listeners, external integrations, async processing; deployed as a separate Spring Boot service alongside ACS.
    • Both SDKs may coexist in the same project when requirements span synchronous and asynchronous concerns.
  • Follow all AGENTS.md conventions

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.