- Home
- Skills
- Prompt & Skill Engineering
- Senior Kotlin Fleet Management Engineer
Works with the AI Agents you already use
Senior Kotlin Fleet Management Engineer
- Connecting backend behavior to browser-based BackOffice features.
$10
Senior Kotlin Fleet Management Engineer
Example session with this skill installed
Add a maintenance scheduling workflow to this fleet-management project. Inspect the repository first. Connect the Ktor backend to the web BackOffice, follow the current architecture and API conventions, and add relevant tests. Don't assume the workflow rules or frontend stack from old planning documents.
- Read your context and instructions
- Compiled the senior kotlin fleet
Summary
I’ll implement maintenance scheduling as one backend-to-web vertical slice, following the repository’s existing patterns. I’ll first verify who can schedule work, which vehicle states are eligible, what fields the API requires, and whether scheduling changes vehicle availability.
Implementation outline
Backend
- Add the operation to the existing maintenance capability.
- Enforce authorization at the API boundary and validate the scheduling rules in the owning application/domain logic.
- Persist through the current repository and migration conventions; add a migration only if the verified schema requires one.
- Return the project's established response and error format.
Web BackOffice
- Add the workflow to the existing navigation and feature structure.
- Build a form for verified fields and show loading, validation, recoverable error, and confirmation states.
- Submit through the existing authenticated API client. UI permission checks support usability; the backend remains the security boundary.
Tests
- Cover allowed and rejected scheduling cases.
- Verify backend authorization and request/response behavior.
- Test web form state, validation feedback, and recovery from request failure.
- Add database or contract tests if the critical behavior depends on them and the project supports those test layers.
Verification
I’ll run the focused tests and relevant Gradle checks discovered in the repository’s build or CI configuration, then review the complete diff. I’ll report any checks that could not be run rather than treating them as passed.
This outline is illustrative. Actual types, routes, state rules, file paths, and commands must come from the target repository.
Connects securely to your tools. The creator never sees your data.
About this skill
Senior Kotlin Fleet Management Engineer
Build fleet-management features with a senior Kotlin engineer's workflow: understand the real project first, then deliver a focused, tested feature across the backend and web BackOffice.
What this skill helps with
- Extending Kotlin/Ktor fleet and vehicle-rental backends.
- Connecting backend behavior to browser-based BackOffice features.
- Creating focused feature skeletons that follow the target repository's architecture.
- Reviewing vehicle, rental, maintenance, driver, customer, accounting, reporting, and tracking workflows.
- Checking permissions, state transitions, persistence, retries, concurrency, API contracts, and tests.
How it works
The skill directs the coding agent to inspect repository instructions, Gradle configuration, relevant source code, API contracts, migrations, comparable features, tests, and CI checks before proposing changes.
It then guides the agent to:
- Verify the requested behavior, user permissions, and domain rules.
- Plan the smallest useful vertical slice across domain, persistence, API, web UI, and tests.
- Implement using the project's existing conventions.
- Run relevant project-supported checks, review the full diff, and report exactly what was and was not verified.
Built for real fleet projects
Fleet systems have product-specific rules for vehicle availability, rental lifecycles, maintenance scheduling, accounting, staff access, organization boundaries, and location data. This skill treats those as requirements to verify—not assumptions to copy from a template.
It distinguishes implemented behavior from roadmap notes and stale diagrams, and avoids imposing a fixed schema, endpoint list, currency, role model, library, or module layout.
Frontend scope
Web BackOffice UI only. The skill can guide Compose Multiplatform/Wasm work when the target repository actually uses it, but it requires checking the project's Gradle targets and source sets first. It does not generate native Android or iOS UI.
Included
- Repository-first senior engineering workflow
- Fleet domain discovery guide
- Kotlin/Ktor backend guidance
- Web BackOffice guidance
- Backend/client API integration guidance
- Testing and quality guidance
- Synthetic end-to-end maintenance feature example
This is a Markdown skill package, not an application, code generator, or deployment configuration. It does not replace project requirements, security review, or testing.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Prompt & Skill Engineering.
No support for Android or iOS UI. Does not support non-Kotlin backends. Requires existing Gradle configuration for reconnaissance.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 21 days ago
Permissions
File Scopes