Fullstack Project Creator

Create standardized Java Spring Boot + Vue3 full-stack project structure for users.

Author: @superchao9
Version: 1.0.0
License: MIT

Use Cases

Use this Skill when users need to create new projects or features, to generate standardized project structure and initial files.

Trigger Keywords (any one will activate)

This Skill activates when user expressions contain the following patterns:

Pattern	Example
Create/New/Generate + Project/System/Feature	"Create a lottery project", "Generate user management system"
Write/Build/Develop + Project/System/Feature

"Help me write a blog project", "Build an order system" |
| Give me/Need + Project/System | "Give me a lottery project", "Need an image management feature" |
| XX Project/System/Module | "Lottery project", "User management module" (implies creation intent) |
| Simple/Complete + Project | "Simple lottery project", "Complete e-commerce system" |

Non-triggering Cases

• - Asking about existing project issues: "This lottery project has an error, how to fix?"
• Modifying/optimizing existing code: "Help me change the lottery logic"
• Pure technical consultation: "How to implement lottery algorithm"

Project Creation Process

1. 1. Requirement Communication - Confirm project requirements with user
2. Generate Project Structure - Create standardized directories and files
3. Generate Code - Generate initial code based on requirements

Project Structure Specification

Created projects must follow this structure:

CODEBLOCK0

Tech Stack Specification

Backend (Java)

• - Framework: Spring Boot 3.2+
• JDK: 17+
• Database: MySQL 8.0
• ORM: MyBatis Plus
• Build Tool: Maven
• API Documentation: SpringDoc OpenAPI

Frontend (Vue3)

• - Framework: Vue 3.4+
• Build Tool: Vite 5+
• UI Library: Element Plus
• State Management: Pinia
• Routing: Vue Router 4
• HTTP Client: Axios

Code Specification

Java Backend

1. 1. Package Name: INLINECODE0
2. Class Name: PascalCase
3. Method Name: camelCase
4. Database Fields: snake_case
5. Must Include: Lombok, unified return format, global exception handling

Vue3 Frontend

1. 1. Component Name: PascalCase
2. Composition API: Use <script setup> syntax
3. Styles: Use scoped CSS
4. API Encapsulation: Unified encapsulation in api/ directory

Creation Steps

When recognizing user intent to create a project:

Step 1: Confirm Project Information

• - Project name (extracted from user description, e.g., "lottery" → lottery)
• Core features/modules
• Complexity (simple/standard/complete, default is standard)

Step 2: Ask for Generation Path

Must ask user: "Where should the project be generated? For example:"

• - INLINECODE4
• INLINECODE5
• INLINECODE6
• Or press Enter to use default working directory

Step 3: Handle Permission Issues

When trying to write to user-specified path:

If insufficient permissions (cannot write):
CODEBLOCK1

If option 1 (Grant permissions):
Provide permission setting guidance for corresponding system (see "Permission Setting Guide" below)

If option 2 (Working directory):

• - Ensure ~/.openclaw/workspace/generated-projects/ directory exists
• Create project folder in that directory
• Record actual generation path

Step 4: Generate Project Content

• - Create standardized directory structure
• Generate config files (pom.xml, package.json, application.yml, etc.)
• Generate business code (database tables with audit fields, backend code, frontend code)
• Generate documentation

Step 5: Output Project Information

After generation is complete, must output:

1. 1. Project Path: Complete absolute path
2. Project Structure: Directory tree display
3. Startup Steps: How to start the project
4. Main Files Description: Purpose of key files

Trigger Examples

The following user expressions should trigger this Skill:

User Input	Recognized Project Name	Complexity
"Help me create a lottery project"	lottery	Standard
"Generate a simple image management system"

image-manager | Simple |
| "Build a user management project" | user-management | Standard |
| "Give me an order system" | order-system | Standard |
| "Help me write a blog project" | blog | Standard |
| "Need a content publishing feature" | content-publisher | Simple |
| "Create a new e-commerce project" | ecommerce | Complete |

Complete Example Dialog

Scenario 1: User specifies path (normal case)

User: "Help me create a lottery project"

Assistant: "Okay! I'll help you create a lottery project.

Confirmation:

• - Project name: lottery
• Complexity: Standard (includes frontend, backend and database)

Where should the project be generated?
For example:

• - INLINECODE8
• INLINECODE9
• Or press Enter to use default working directory

Please enter path:"

User: "d:\my-projects\lottery"

Assistant: "✅ Project generation complete!

📁 Project Path: INLINECODE10

📂 Project Structure:
CODEBLOCK2

🚀 Startup Steps:

1. 1. Import database: INLINECODE11
2. Start backend: INLINECODE12
3. Open frontend: Browser access INLINECODE13

📋 Main Files:

• - backend/pom.xml - Maven Config
• INLINECODE15 - Lottery API
• INLINECODE16 - Lottery Page
• INLINECODE17 - Database Initialization"

---

Scenario 2: Insufficient permissions

User: "d:\projects\lottery"

Assistant: "⚠️ Cannot write to specified path d:\projects\lottery, insufficient permissions.

Please choose:

1. 1. [Grant folder permissions] - I will guide you on how to set permissions
2. [Generate in working directory] - Project will be generated in default working directory

Please enter 1 or 2:"

User: "2"

Assistant: "✅ Project has been generated in working directory:

📁 Project Path: INLINECODE19

[Subsequent output of project structure, startup steps...]"

Path Specification and Permission Handling

Path Inquiry Principle

Never use hardcoded paths. Must ask user for desired generation path before each project creation.

Example inquiry:

Where should the project be generated?

• - Enter absolute path, e.g.: INLINECODE20
• Or press Enter for default: INLINECODE21

Permission Setting Guide

When user chooses "Grant folder permissions", provide the following guidance:

Windows (PowerShell):
CODEBLOCK3

Windows (GUI):

1. 1. Right-click target folder → Properties
2. Security → Edit
3. Add → Enter your username → Check Names
4. Check "Full control" → OK

macOS/Linux:
CODEBLOCK4

Working Directory Fallback

If user chooses to generate in working directory:

• - Path: INLINECODE22
• Auto-create generated-projects directory (if not exists)
• Inform complete path after project generation

Path Examples

User Choice	Generation Path Example
Custom path	INLINECODE24
macOS/Linux

~/projects/lottery/ or /home/user/projects/lottery/ | | Default working directory | ~/.openclaw/workspace/generated-projects/lottery/ |

Database Audit Fields Specification

All database tables must include the following audit fields:

Field Name	Description	Data Type	Nullable	Default	Constraints
creator	Creator	varchar(64)	Yes	''	DEFAULT ''
createtime

Creation Time | datetime | No | CURRENTTIMESTAMP | NOT NULL |
| updater | Updater | varchar(64) | Yes | '' | DEFAULT '' |
| updatetime | Update Time | datetime | No | CURRENTTIMESTAMP | NOT NULL, ON UPDATE CURRENT_TIMESTAMP |
| deleted | Deleted Flag | bit | No | b'0' | DEFAULT b'0', NOT NULL |
| tenant_id | Tenant ID | bigint | No | 0 | DEFAULT 0, NOT NULL |

SQL Example

CODEBLOCK5

Java Entity Example

CODEBLOCK6

Notes

1. 1. Must ask for path first: Don't assume any fixed path, ask user every time
2. Handle permission issues: When encountering insufficient permissions, provide clear two-option choice
3. All generated code must include English comments
4. Must include basic CRUD examples
5. Code style should be unified and standardized
6. Provide clear README instructions
7. All tables must include creator, createtime, updater, updatetime, deleted, tenant_id six audit fields
8. On completion output: Project path, structure tree, startup steps, main files description