Analyzing cue word engineering from a developer's perspective: a new programming paradigm in the age of big models

1. Introduction

With the rapid development of artificial intelligence, the terms Large Language Model (LLM), Agent, Retrieval Augmented Generation (RAG), and Prompt Engineering appear frequently in our technical discussions. Today, let's talk about Prompt Engineering and see how it has become a new "programming language" in the hands of developers.

2. Review of the traditional software development process

When it comes to software development, the process we're all familiar with generally goes something like this:

Requirements Analysis and Understanding
requirements disassembly
System Architecture Design
code implementation

As an example, if we want to develop an e-commerce system, we usually consider the following core functions:

Merchandise add-ons
Order Settlement
Payment processing
Returns Management

3. Traditional object-oriented programming implementation

Below is a simplified code example that implements these features using TypeScript:

class ShoppingCart {
  private cartItems: CartItem[] = [];

  addProductToCart(product: Product, quantity: number): void {
    // Add-On Logic Implementation
  }

  checkout(): Order {
    // Settlement Logic Implementation
  }
}

class PaymentService {
  payOrder(order: Order): void {
    // Payment Logic Implementation
  }
}

class ReturnService {
  processReturn(order: Order): void {
    // Returns Logic Implementation
  }
}

// RESTful API routing implementation
('/cart/add', () => {
  // Purchase Logic
});

('/cart/checkout', () => {
  // settlement logic
});

('/payment/process', () => {
  // payment logic
});

('/return/request', () => {
  // Returns Logic
});

4. Cue word engineering: a programming paradigm for large language models

Now, imagine what it would be like to implement these features with a cue word project. Let's take a look at an example:

## Role: e-commerce intelligent assistant

## Profile
- description: You are an AI assistant who is well versed in e-commerce business and can accurately handle all kinds of e-commerce related queries and operations.

## Goals
- Accurately understand user needs and ensure smooth execution of e-commerce processes.

## Rules
- Respond to questions that are out of scope with "I'm sorry, this is out of my scope".

## Skills
- Deep understanding of e-commerce business requirements, accurately inferring relevant scenarios and user intent.

### Workflow
1. Analyze user input and identify core requirements
2. According to the type of requirement, select the appropriate processing flow:
   - If the demand is for purchase or settlement, execute <Workflow-checkout>.
   - If it is a payment requirement, execute <Workflow-pay>; and if it is a return requirement, execute <Workflow-checkout>.
   - If it is a return request, execute <Workflow-return> 3.
3. Provide professional and accurate response

### Workflow-checkout
1. Validate cart status
2. Call the add-order module to perform the product add operation.

### Workflow-pay
1. Call the payment module to process the order payment process.

### Workflow-return
1. Manage user's emotions and understand the reason for return.
2. If the return is confirmed, provide professional guidance and call the return module to execute the return process.

### Initialization
As a <Role>, strictly follow <Rules>, perform tasks according to <Workflow> to ensure that the problem is solved effectively.

5. Cue deconstruction: deeper understanding of cue structure

5.1 Definitions and initialization

Cue word:

## Role: e-commerce intelligent assistant

## Profile
- description: You are an AI assistant who is well versed in e-commerce business and can accurately handle all kinds of e-commerce related queries and operations.

## Goals
- Accurately understand user needs and ensure smooth execution of e-commerce processes.

Versus traditional programming:

class ECommerceAssistant {
  constructor() {
     = "AI assistant proficient in e-commerce business, capable of accurately handling all kinds of e-commerce-related queries and operations";
     = ["Accurately understands user needs", "Ensures smooth execution of e-commerce processes"];
  }
  // Other methods of the class...
}

5.2 Main workflows

Cue word:

### Workflow
1. Analyze user input and identify core requirements
2. According to the type of requirement, select the appropriate processing flow:
   - If the demand is for purchase or checkout, perform <Workflow-checkout>; and if the demand is for payment, perform <Workflow-pay>.
   - If it is a payment requirement, execute <Workflow-pay>; and if it is a return requirement, execute <Workflow-checkout>.
   - If it is a return request, execute <Workflow-return> 3.
3. Provide professional and accurate response

Versus traditional programming:

function handleRequest(userInput: string) {
  const intent = parseUserIntent(userInput);

  switch(intent) {
    case 'checkout':
      return handleCheckout();
    case 'payment':
      return handlePayment();
    case 'return':
      return handleReturn();
    default:
      return "Unrecognizable requests";
  }
}

5.3 Specific function realization

Cue word:

### Workflow-checkout
1. Verify the shopping cart status
2. Call the add-order module to perform the product add operation

Versus traditional programming:

function handleCheckout() {
  if (validateCart()) {
    addProductToCart(); return "Product has been successfully added to the cart"; }
    return "Product has been successfully added to cart.
  } else {
    return "Cart status is abnormal, please try again later"; } else { "The product was added to the cart successfully.
  }
}