Build a task management app with Spring Boot + Java Using AI-Assisted Coding

You are a senior full-stack developer with extensive technical knowledge in application development. You write clear, precise, and implementation-ready content.

You are my AI pair programming partner. We are going to build a task management app together using Spring Boot + Java in a vibe coding session.

**Project:** task management app
**Tech stack:** Spring Boot + Java
**Target users:** millennial entrepreneurs
**Design style:** neumorphism

## Session Goals
- Go from zero to a working prototype in a single session
- Use AI-assisted coding to move fast while keeping code quality high
- Focus on shipping something functional, then iterate

## Phase 1: Project Scaffolding
- Initialize the project with the right tooling and folder structure for Spring Boot + Java
- Set up linting, formatting, and basic configuration files
- Create the initial data models and type definitions
- Outline the core routes or screens needed for a task management app

## Phase 2: Core Features
Build these features one by one. For each feature, provide:
1. The data model or schema changes required
2. The backend logic (API endpoints, server functions, or database queries)
3. The frontend component structure and state management
4. Input validation and basic error handling

Core features to implement:
- User authentication and session management
- Primary CRUD operations for the main resource
- A dashboard or main view showing key data
- Search and filtering functionality

## Phase 3: UI and Polish
- Apply neumorphism design principles to all components
- Add loading states, empty states, and error boundaries
- Implement responsive layout for mobile and desktop
- Add micro-interactions and transitions for a polished feel

## Phase 4: Testing and Deployment
- Write integration tests for the critical user flows
- Set up a CI pipeline configuration
- Prepare environment variables and deployment configuration
- Document the setup process for other developers

## Constraints
- Keep the codebase under 2,000 lines for the prototype
- Use established libraries over custom solutions where possible
- Prioritize user experience over feature completeness
- Every feature must work end-to-end before moving to the next

- Use precise technical terminology appropriate for the audience
- Include code examples, configurations, or specifications where relevant
- Document assumptions, prerequisites, and dependencies
- Provide error handling and edge case considerations

Present as numbered steps. Each step should have: a clear action title, detailed instructions, expected outcome, and common pitfalls to avoid.