bar-assistant-application-service
Skill1.1k starsChanged 6 months agoMITView on GitHub
Use when implementing or refactoring Bar Assistant write-side workflows that go from Laravel controllers to application services and Eloquent-backed infrastructure repositories. Covers controller orchestration, DTO mapping, repository ports/adapters, dependency injection, and create/update/delete service conventions used in this codebase.
Trending
Quiet since August.about the whole repository
Who's talking about karlomikus/bar-assistant
- karlomikus/vue-salt-rim“bar-assistant version”GitHub · Aug 9, 2026 · 1 reactions
- karlomikus/vue-salt-rim“Add runtime cache busting”GitHub · Feb 3, 2026 · 1 reactions
- elfhosted/enhancements“Bar Assistant — self-hosted home cocktail bar manager”GitHub · Apr 28, 2026
- karlomikus/vue-salt-rim“Optionally hide "My Shelf" and associated features.”GitHub · Apr 24, 2026
- YunoHost/apps“Add Bar Assistant to wishlist”GitHub · Feb 18, 2026
The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 18
Talked about on GitHub (18 times).
On GitHub · 18
- Aug 9, 2026bar-assistant version — karlomikus/vue-salt-rim1 reaction
- Feb 3, 2026Add runtime cache busting — karlomikus/vue-salt-rim1 reaction
- Apr 28, 2026Bar Assistant — self-hosted home cocktail bar manager — elfhosted/enhancements0 reactions
- Apr 24, 2026Optionally hide "My Shelf" and associated features. — karlomikus/vue-salt-rim0 reactions
- Feb 18, 2026Add Bar Assistant to wishlist — YunoHost/apps0 reactions
13 more on GitHub
- Jul 17, 2025Bar assistant — community-scripts/ProxmoxVE0 reactions · 1 comment
- Jul 10, 2025Unable to start the services on different ports — bar-assistant/docker0 reactions · 7 comments
- Feb 20, 2025Update support for taxonomies — bar-assistant/data0 reactions
- Jan 16, 2025feat: implement oauth login — bar-assistant/docker0 reactions
- Jan 14, 2025feature: oauth login — karlomikus/vue-salt-rim0 reactions
- Nov 10, 2024basic example for oidc — karlomikus/vue-salt-rim0 reactions
- May 5, 2024Configuration for Meilisearch when API Key is required appears to be missing from documentation — karlomikus/vue-salt-rim0 reactions · 2 comments
- Oct 20, 2023[feat] Show cocktail and ingredient updated at/by information — karlomikus/vue-salt-rim0 reactions
- Sep 19, 2023Add Healthcks and Depends_on Healthy Condition — bar-assistant/docker0 reactions · 1 comment
- Jul 13, 2023Home Resource Planning — claha/smart-home0 reactions · 1 comment
- Apr 20, 2023[Add]: Bar Assistant — trueforge-org/truecharts0 reactions · 2 comments
- Jan 2, 2023New dashboard — karlomikus/vue-salt-rim0 reactions
- Jun 17, 2021Software to check out — claha/dotfiles0 reactions · 1 comment
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- clean-ddd-hexagonalSkill
- ubiquitous-languageSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when you are:
- Distinctive: line 30
Use the Ingredient flow as the main reference:
- Very specific: line 42
Add request/result DTOs in src/Application/.../DTO
- Distinctive: line 46
Update the Laravel controller to authorize, map request data, and call the service
- Distinctive: line 47
Add or update unit tests for the application service
- Distinctive: line 48
Add or update feature tests for the controller behavior when needed
- Very specific: line 60
Call abort(403) for failed policy checks
- Distinctive: line 73
Use repository methods for persistence instead of touching Eloquent directly
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Bar Assistant Application Service Workflow
Project-specific guidance for implementing write-side behavior in Bar Assistant without bypassing the application layer.
When to Use
Use this skill when you are:
- Adding a new controller action that should call a service in
src/Application - Implementing a new create, update, or delete use case
- Introducing a new domain repository port and Eloquent repository adapter
- Refactoring legacy controller logic into application services
- Wiring a new repository binding in
InfrastructureServiceProvider
Core Rule
For write operations, controllers should authorize and validate the request, build an application DTO, call an application service, and return the HTTP response. They should not contain persistence logic or call infrastructure repositories directly.
Controller -> Application Service -> Domain Repository port -> Eloquent adapterBest Example in This Repo
Use the Ingredient flow as the main reference:
- Controller:
app/Http/Controllers/IngredientController.php - Application service:
src/Application/Ingredient/IngredientService.php - Repository port:
src/Domain/Ingredient/IngredientRepository.php - Repository adapter:
app/Infrastructure/EloquentIngredientRepository.php - DI bindings:
app/Providers/InfrastructureServiceProvider.php - Unit tests:
tests/Unit/Application/Ingredient/IngredientServiceTest.php
Recommended Implementation Order
- Define or update the domain repository port in
src/Domain/... - Add request/result DTOs in
src/Application/.../DTO - Implement the application service method in
src/Application/...Service.php - Implement or extend the Eloquent repository adapter in
app/Infrastructure - Wire the repository interface to the adapter in
InfrastructureServiceProvider - Update the Laravel controller to authorize, map request data, and call the service
- Add or update unit tests for the application service
- Add or update feature tests for the controller behavior when needed
Controller Responsibilities
- Resolve the application service from the container
- Perform policy checks with the authenticated user
- Validate request payloads with
FormRequestand additional validators if needed - Translate HTTP request data into application DTOs
- Return the correct HTTP status and headers
Controllers in this repo commonly:
- Call
abort(403)for failed policy checks - Build DTOs explicitly instead of passing Laravel requests into the application layer
- Return
201with aLocationheader for create - Return
204for update and delete
Application Service Responsibilities
Application services in this repo:
- Orchestrate use cases using domain entities and repository ports
- Convert primitive request data into domain value objects and IDs
- Throw typed application exceptions such as
EntityNotFoundException - Return result DTOs for create/update operations when the caller needs persisted identifiers or metadata
- Use repository methods for persistence instead of touching Eloquent directly
Repository Conventions
- Repository interfaces live in
src/Domain/... - Eloquent adapters live in
app/Infrastructure - Adapter names follow
Eloquent{Name}Repository - Persisted IDs are database-generated and assigned back to transient domain objects with
setId() - Multi-step persistence is wrapped in DB transactions inside the adapter
- Mapping between Eloquent models and domain entities stays in the adapter
Create / Update / Delete Expectations
Create
- Controller validates input and authorizes
create - Controller builds a create DTO and calls the service
- Service builds a domain entity via a factory like
Entity::create(...) - Service resolves related entities through repository ports as needed
- Repository adapter persists the entity, assigns the generated ID, and returns the updated aggregate
- Controller returns
201andLocation
Update
- Controller loads the legacy model when needed for authorization context
- Controller authorizes
edit - Controller builds an update DTO and calls the service
- Service loads the aggregate through the repository port
- Service throws
EntityNotFoundExceptionif the aggregate does not exist - Service updates the aggregate through domain methods and persists it
- Controller returns
204unless a response body is required
Delete
- Controller loads the legacy model when needed for authorization context
- Controller authorizes
delete - Controller calls the delete service method with the route ID
- Service loads the aggregate or throws
EntityNotFoundException - Service performs any domain cleanup before deletion
- Repository adapter deletes the aggregate by domain ID
- Controller returns
204
Bar Assistant-Specific Details
- Domain code in
src/uses strict typing and value objects heavily - Legacy Laravel models still appear in controllers for policy checks and route-context lookups
- Services should stay framework-agnostic even if controllers are not
- Unit tests prefer in-memory repositories from
tests/Infrastructureinstead of mocks - Complex write flows often need both a primary repository and supporting repositories, as shown by
IngredientService
Reference Documentation
- references/IMPLEMENTATION-WORKFLOW.md — step-by-step controller/service/repository workflow for create, update, and delete
Source Files to Study First
app/Http/Controllers/IngredientController.phpsrc/Application/Ingredient/IngredientService.phpsrc/Domain/Ingredient/IngredientRepository.phpapp/Infrastructure/EloquentIngredientRepository.phpapp/Providers/InfrastructureServiceProvider.phptests/Unit/Application/Ingredient/IngredientServiceTest.php
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
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.

