Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

New Application / Add Moduels-Features to Existing Application Prompts - md file

Design new applications or add modules/features to existing applications using DDD principles, and generate structured Markdown output.

When to Use

  • User describes a new business application they want to build

  • User wants to add new modules to an existing application

  • User wants to add new features to an existing module

  • User explains business flows or processes without existing code/BRD

How to Use

Tell your AI agent what you want to build. It will apply DDD principles and generate structured FlexBase-ready Markdown.

Example prompts you can give your AI agent:

Design a new scheduling app for healthcare with patient, provider, and appointment management
Add a new Payments module to my existing application
Add invoice generation and reporting features to the Orders module
Convert these user stories into FlexBase features
Analyze this business flow and provide a quick FlexBase design

Task Catalog

Task 1: Complete New Application Design

Goal: Design an entire new application with multiple modules User provides: Business application requirements Output: Organized Markdown with modules, features, validations, events/subscribers, domain services

Task 2: New Module Design (Add to Existing App)

Goal: Design a new module for an existing application User provides: Module requirements and existing application context Output: Module Markdown with features, validations, events/subscribers, cross-module integration

Task 3: New Feature Design (Add to Existing Module)

Goal: Design specific features for an existing module User provides: Feature requirements and target module name Output: Feature Markdown with validations, events/subscribers per feature

Task 4: Quick Flow Analysis

Goal: Quick analysis of a simple business flow User provides: Business flow description Output: Concise Markdown with module, features, entities, validations, events

Task 5: User Story to Feature Mapping

Goal: Convert user stories into FlexBase features User provides: User stories Output: Mapped features with operation types, validations, events

Task 6: API & Integration Design

Goal: Design external API integrations User provides: API descriptions or Swagger/OpenAPI specs Output: RestServiceModel domain services + integration features

Task 7: Scheduled Task / CronJob Design

Goal: Design automated/scheduled features User provides: Scheduled process requirements Output: CronJob features with triggers and subscribers

Task 8: Event-Driven Architecture Design

Goal: Design complex event chains with multi-level subscribers User provides: Event flow description Output: Event hierarchy with first-level and second-level subscribers

Task 9: Screen / UI Flow Design

Goal: Design UI layouts and screen flows from requirements User provides: Application requirements with UI descriptions Output: Screen flow metadata enriching features with layout information

Key Rules (Applied Automatically)

  • Module names PLURAL PascalCase (e.g., Orders, Customers, Payments)

  • Feature names operation-centric PascalCase (e.g., CreateOrder, GetCustomerById)

  • DDD principles — bounded contexts → modules, aggregate roots → domain entities

  • Valid operation types: CREATE, UPDATE, DELETE, SOFTDELETE, GETPAGEDLIST, GETLIST, GETBYID, GETSINGLE

  • featureType: WebAPI (user-initiated) or CronJob (scheduled)

  • Large files split automatically — per-module files

Related

Last updated