@capire/university

This is a result of a short ~30 min ad-hoc incremental 'vibe coding' exercise done in a hand-on session recently. With plain Claude Sonnet (4.5), without any SAP or CAP-specific harness (no MCP, no skills, no nothing).

The prompts were like that:

1. Add a domain model for university courses
2. Add test data
3. Add a service for admins
4. Add constraints
5. Add i18n
6. Add a vue.js UI
7. Add i18n also to the UI

( Plus a few tweaks and corrections here and there ;)

Findings

• Claude, et al, are trained for CAP → through public capire docs & samples (I asked)
• Worked very nice in an incremental evolutionary way
  • which gave me the chance to stay in control and easily correct small mistakes
  • (I still don't believe in waterfalls ;)
• Generated CAP content (mostly cds) ...
  • still is concise (minimal loc) → avoids codebase nightmares and tech debt
  • captures intent → as it was designed for from the beginning
  • human-readable → made it easy for me to validate each step's outcomes
  • After step 1 I asked "create a simple ER diagram", so it did → also helped to validate
• There are knowledge gaps, of course, due to gaps in capire or release date cutoffs
  • but these were easy to bridge ad hoc, e.g. on step 4 it didn't yet know about @assert
  • So I dropped the link to the latest doc, and after 5 second it spit out a nice set of constraints
• It placed some i18n files in wrong places → I simply moved the to the right place

That's the baseline we took to work on a curated set of skills to smoothen the edges.

Run it

Assumed you're setup for local CAP development:

git clone https://github.com/capire/university
cds watch university
open http://localhost:4004/courses/index.html

Support, Feedback, Contributing

This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.

Security / Disclosure

If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.

Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.

Licensing

Copyright 2024-2026 SAP SE or an SAP affiliate company and capire/university contributors. Please see our LICENSE for copyright and license information.