System Requirements Document for nova-personal

1. Introduction

The nova-personal project is a personal Daily Learning & Skill Development Manager designed to help users strengthen their skills in aptitude & logical reasoning, programming & coding, data structures & algorithms, SQL & databases, n8n automation, AI tools and API integration, and full-stack development. The system provides a structured daily task plan, focusing on progressive learning and practical interview preparation.

2. System Overview

Nova-personal delivers a personalized learning experience through a daily task plan that includes aptitude questions, coding problems, SQL questions, n8n automation tasks, a mini project, revision, and progress tracking. The system is designed for a single user, the Learner, who interacts with the application to complete tasks and track progress. The application requires user authentication to maintain continuity of learning history and progress tracking.

2a. Product Interpretation and Delivery Boundary

The application is designed to be a personal learning manager, focusing on individual skill development without external recipients or additional workflow roles. It operates within a 3-hour daily schedule, providing a structured learning path with progressive difficulty. The system requires user authentication to ensure continuity of learning history and progress tracking. The application does not provide solutions or workflow JSON until the user attempts the task or explicitly requests it.

2b. Source Content Inventory

Not applicable as no content source directive was provided.

2c. Page Content and Component Coverage

Landing

• Purpose: Introduce the personal daily learning manager, its audience, and its daily planning and progress functions.
• Components:
  • Overview of learning goals and daily task structure.
  • Call-to-action to log in or start learning.

Login

• Purpose: Allow the Learner to authenticate and access their learning history.
• Components:
  • Username and password fields.
  • Authentication error handling.
  • Password recovery option.

Daily Plan

• Purpose: Display the ordered Day 1 and subsequent daily sections, schedules, and command-driven continuation.
• Components:
  • Daily task list including aptitude, coding, SQL, n8n, mini project, and revision.
  • Time allocation for each task.
  • Command interface for task navigation (e.g., "NEXT", "TODAY").

Curriculum

• Purpose: Provide a revisitable learning-path destination for rotating aptitude, coding, SQL, n8n, and progressively harder project topics.
• Components:
  • Topic rotation schedule.
  • Access to learning materials and resources.

Submissions

• Purpose: Record learner attempts before answer keys, solutions, or workflow JSON are released.
• Components:
  • Submission interface for each task.
  • Status indicators for attempted tasks.

Feedback

• Purpose: Provide feedback on attempts, explain mistakes, improve code, give complexity analysis, and supply follow-up practice.
• Components:
  • Detailed feedback on submitted answers.
  • Suggestions for improvement and practice questions.

Progress

• Purpose: Track completion, scores, weak and strong topics, mistakes, concepts, and weekly reviews.
• Components:
  • Progress table with Date, Aptitude, Coding, SQL, n8n, Project, and Score.
  • Weekly review summary and next week's focus.

3. Functional Requirements

• As a Learner, I should receive a daily task plan covering aptitude, coding, SQL, n8n automation, a combined coding/API/database/n8n mini project, and revision. (explicit)
• As a Learner, I should receive 5 aptitude questions daily with easy-to-hard progression and rotating listed topics; answers should be withheld until I attempt them. (explicit)
• As a Learner, I should receive 3 daily coding problems at easy, medium, and hard difficulty with rotating listed languages and topics; solutions should be withheld until attempted. (explicit)
• As a Learner, I should receive 2 daily SQL questions using realistic tables and rotating listed SQL topics; answers should be withheld until attempted. (explicit)
• As a Learner, I should receive 1 practical n8n automation task daily, progressing through the specified five-level learning path; complete workflow JSON should be withheld until attempted or requested. (explicit)
• As a Learner, I should receive one progressively more complex daily mini project combining coding, API, database, and n8n. (explicit)
• As a Learner, I should receive end-of-day revision consisting of 5 previous aptitude questions, 2 previous coding concepts, 2 SQL questions, and 1 n8n concept. (explicit)
• As a Learner, I should be able to maintain a progress table tracking completion, failed questions, weak and strong topics, coding mistakes, and n8n concepts learned. (explicit)
• As a Learner, I should receive a weekly review every 7 days covering specified totals, accuracy, completed workflows, strengths, weaknesses, and next week's focus. (explicit)
• As a Learner, I should be able to plan around approximately 3 hours daily using the specified recommended schedule and adjust when I report different available time. (explicit)
• As a Learner, I should be taught progressively and practically for interview preparation, using real-world problems and n8n projects, preferring JavaScript/Python for automation coding, and including APIs and PostgreSQL in advanced work. (explicit)
• As a Learner, I should have my mistakes retained within the conversation and support commands DONE, HINT, SOLUTION, SKIP, TODAY, NEXT, REVIEW, and WEEKLY REVIEW with specified behaviors. (explicit)
• As a Learner, I should start with Day 1 and generate today's complete tasks. (explicit)
• As a Learner, I must establish an application identity before durable progress, submissions, feedback, and revision history can persist. (required_inference)
• As a Learner, returning verification must restore my prior learning history before generating continuity-based revision or weekly reviews. (required_inference)

4. User Personas

• Learner: The user completing daily aptitude, coding, SQL, n8n, revision, and mini-project work and receiving evaluations and progress tracking.

5. Core User Flows

Learner Daily Task Flow

1. Access Landing Page: Learner visits the Landing page to understand the system's purpose and structure.
2. Login: Learner logs in to access their personalized learning plan.
3. View Daily Plan: Learner views the daily task plan, including aptitude, coding, SQL, n8n, mini project, and revision.
4. Complete Tasks: Learner attempts each task in the Daily Plan, submitting answers and code as required.
5. Receive Feedback: Learner receives feedback on submissions through the Feedback page.
6. Track Progress: Learner reviews their progress and performance on the Progress page.
7. Weekly Review: Every 7 days, Learner receives a comprehensive review of their performance and focus areas for the next week.

6. Visuals Colors and Theme

• Muse: Haraldur Thorleifsson
• Palette (light mode):
  • Background: #F5F5F5
  • Surface: #FFFFFF
  • Text: #333333
  • Primary: #FF6B6B
  • Accent: #FFD93D
  • Muted: #CCCCCC
• Typography:
  • Headings: Sora — Bold, large, uppercase
  • Body: Outfit
  • Scale: 1.25 modular, 64/48/32/24/16
• Shape Language: Chunky rounded cards and sections with soft radii.
• Layout: Single-column layout with generous padding.
• Motion: Lively entrance animations and hover pops.
• Imagery: Custom character and spot illustrations.

7. Signature Design Concept

A bold, oversized headline across a color-blocked illustration in the hero section, featuring a vibrant illustration of a character learning in a digital environment. Interactive elements with expressive hover animations and progress trackers using vibrant accent colors.

8. Interaction Model & Motion Direction

• Interaction Model: Animated
• Motion Tempo: Expressive
• Hero Dimensionality: Layered_2d
• Landing Hero Motion Brief: A large vibrant illustration of a character learning, with bold type overlay and primary accents. Entrance animations and hover pops create a sense of interactivity and engagement. Reduced-motion state available for accessibility.

9. Non-Functional Requirements

• The application must support approximately 3 hours of daily learning activities with the ability to adjust based on user input. (explicit)
• The system must retain user mistakes and learning history for feedback and progress tracking. (explicit)
• The application must provide a secure login mechanism to protect user data and learning history. (required_inference)

10. Tech Stack

• Frontend: React
• Backend: Python/FastAPI
• Database: PostgreSQL
• Automation: n8n
• Containerization: Docker/docker-compose
• Deployment: Kubernetes (only if required for deployment)

11. Assumptions and Constraints

• The Learner has approximately 3 hours per day for learning activities.
• The application will not provide solutions or workflow JSON until the Learner attempts the task or explicitly requests it.
• The system focuses on personal learning management without external recipients or additional workflow roles.

12. Glossary

• Learner: The user engaging with the nova-personal application for daily learning and skill development.
• n8n: An automation tool used within the learning tasks.
• PostgreSQL: A relational database management system used for storing user progress and task data.