b2c-android-create-api

Generate Android B2C API layer components across multi-module architectures.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/herren-official/product-agents --skill b2c-android-create-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b2c-android-create-api
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2c-Android/create-api
Command: npx skills add https://github.com/herren-official/product-agents --skill b2c-android-create-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of the Android B2C API layer across modules (Service, Entity, Body, Repository interfaces/impl, Vo, UseCase, and DI wiring) according to project conventions.

Core Features & Use Cases

  • Auto-generates Service interfaces and Retrofit-based endpoints with proper DI registration.
  • Creates Entities mapped to Vo via SuccessResponseMapper and prepares Body objects for requests.
  • Generates Repository interfaces and RepositoryImpl stubs that follow Flow-based return types and error handling.
  • Supports optional UseCase assembly for multi-repository scenarios and clean architecture alignment.
  • Ensures consistency with multi-module architecture (core:data, core:data-api, core:ui-model, core:domain).

Quick Start

Provide the domain name, API endpoint path, HTTP method, request parameters, and response shape to generate the complete Android API layer.

Frequently Asked Questions about b2c-android-create-api

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

FAQPage Schema
How do I auto-generate an Android Retrofit API layer with repository and UseCase boilerplate?

To auto-generate an Android Retrofit API layer, provide the domain name, endpoint path, HTTP method, parameters, and response shape. The tool outputs Service interfaces, Entities, Bodies, Repository implementations, VOs, and UseCases with Flow-based return types and DI wiring.

What is the best way to structure a multi-module Android B2C API layer with Flow-based repositories?

Structuring a multi-module Android B2C API layer involves organizing code into core:data, core:data-api, core:ui-model, and core:domain modules. This approach generates Repository interfaces and implementations using Flow return types, SuccessResponseMapper for VO mapping, and proper error handling.

How do I map API responses to ViewModels and set up DI in a clean Android architecture?

Mapping API responses to ViewModels and setting up DI involves using SuccessResponseMapper to transform Entities to VOs and registering dependencies automatically. The generated code aligns with clean architecture by providing UseCase assembly for multi-repository scenarios.

Can I generate API request Body objects and Retrofit service interfaces for an Android B2C project?

Yes, you can generate API request Body objects and Retrofit service interfaces for an Android B2C project. The tool creates Retrofit-based endpoints with proper DI registration and prepares Body objects for requests based on your provided API endpoint path and parameters.

Does this Android code generator support clean architecture and multi-repository UseCase patterns?

The Android code generator supports clean architecture and multi-repository UseCase patterns by providing optional UseCase assembly. It targets multi-module architectures and ensures alignment with clean architecture principles through generated Repository interfaces and implementations.

What limitations exist when generating Android API layer components across multiple modules?

When generating Android API layer components across multiple modules, the tool targets specific project conventions including core:data, core:data-api, core:ui-model, and core:domain. It requires providing the domain name, API endpoint path, HTTP method, request parameters, and response shape to generate the complete API layer.