skills.rest
OpenOLAT
OpenOLATOFFICIAL
Explore all skills by this author →
Website𝕏@openolatGitHub

openolat-dev

Guide OpenOlat LMS development with Java, Spring, and Hibernate architecture conventions.

434|167|Updated Mar 29, 2018
Search Tags:#development#architecture#patterns#velocity#controllers#openolat
One-click install
npx skills add https://github.com/OpenOLAT/OpenOLAT --skill openolat-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openolat-dev
Source: https://github.com/OpenOLAT/OpenOLAT/tree/main/.claude/skills/openolat-dev
Command: npx skills add https://github.com/OpenOLAT/OpenOLAT --skill openolat-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenOlat developers often wrestle with adhering to architecture guidelines, patterns, and conventions across controllers, services, forms, and templates. This skill provides structured, authoritative guidance to write correct, idiomatic OpenOlat code.

Core Features & Use Cases

  • Architecture knowledge and patterns for OpenOlat LMS development.
  • Conventions for controllers, services, forms, templates, and module structure.
  • Guidance to fix bugs, implement new features, and ensure consistent coding practices.

Quick Start

Describe the architecture pattern you are implementing and I will generate a focused code example.

Frequently Asked Questions about openolat-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement OpenOLAT controllers and services following the correct architecture patterns?▼

OpenOLAT architecture patterns guide developers in structuring controllers, services, forms, and templates to ensure correct, idiomatic Java/Spring/Hibernate code for the LMS.

What is the standard module structure for OpenOLAT LMS development?▼

The standard OpenOLAT module structure organizes controllers, services, forms, and templates according to specific architecture conventions that maintain consistency and velocity across Java/Spring/Hibernate-based projects.

How do I write idiomatic OpenOLAT code for new features and bug fixes?▼

Writing idiomatic OpenOLAT code involves applying structured architecture guidelines and pattern references to implement features and fix bugs consistently across controllers, services, forms, and templates.

Does OpenOLAT development require specific conventions for forms and templates?▼

OpenOLAT development requires specific conventions for forms and templates to maintain architectural consistency, providing structured guidance and practical examples for Java/Spring/Hibernate-based LMS projects.

Can I get practical code examples for OpenOLAT architecture patterns?▼

You can get practical code examples for OpenOLAT architecture patterns by describing the pattern you are implementing, which generates focused code examples for controllers, services, forms, and templates.

Why does my OpenOLAT code not follow the expected architecture conventions?▼

OpenOLAT code may not follow expected architecture conventions if controllers, services, forms, and templates are not structured according to the established patterns and guidelines for Java/Spring/Hibernate-based projects.

Related Skills

Explore More Software Engineering Skills→
phamtiendatbg92phamtiendatbg92

tech-stack-config

Configure Spring Boot 3.4.4 and Java 17 tech stack conventions for API projects.

Community
Advanced
ysyecustysyecust
40

springboot-tdd

Automate TDD guidance for Spring Boot services with JUnit 5, Mockito, MockMvc, and Testcontainers.

Community
Advanced
klu-devklu-dev
2

java-coding-standards

Analyze Java 17+ Spring Boot code for adherence to coding standards.

Community
Intermediate
andresdiegolandaandresdiegolanda
10

testing

Standardize Mockito service unit tests and @WebMvcTest controller tests for Java projects.

Community
Intermediate