nova-cli 0.1.1 → 0.2.1

data/lib/nova/templates/tasks_examples/2_generate_static_pages.md

@@ -0,0 +1,157 @@
+# Generate Static Pages
+
+Prerequisites: Task 1 (Generate Application) must be completed
+
+## Task Overview
+Create the actual application pages (with hardcoded data initially) in the code/ directory. These pages will serve as the foundation for the live application - proper routes, controllers, and views that will be enhanced with dynamic functionality later.
+
+## Prerequisites
+- Rails application is set up and running (Task 1 completed)
+- Design system is defined in ../3_design-system/
+- User stories and flowchart define required pages
+- Tailwind CSS and Flowbite are configured
+
+## Important Note
+These are NOT throwaway prototype pages. Create production-ready routes, controllers, and views that will be used in the final application. Only the data is hardcoded initially.
+
+## Implementation Strategy
+**Start with the core of the application first** (e.g., main dashboard, primary user interface, or key feature page). Create this core page completely, then **STOP and let the user review the experience**. Users will likely want to iterate on this core page multiple times before moving to supporting pages. This iterative approach ensures the most important user experience is refined before building out the rest of the application.
+
+## Tasks
+
+- [ ] 1.0 Plan Application Structure
+  - [ ] 1.1 Review flowchart in ../1_big-picture/flowchart.md for page requirements
+  - [ ] 1.2 Review user stories in ../2_user-stories/ for page-specific needs
+  - [ ] 1.3 Review design system in ../3_design-system/ for styling guidelines
+  - [ ] 1.4 Identify the CORE page/feature of the application (dashboard, main interface, etc.)
+  - [ ] 1.5 Create list of supporting pages needed
+  - [ ] 1.6 Plan RESTful routes and controller structure
+
+- [ ] 2.0 Generate Core Controller and Routes FIRST
+  - [ ] 2.1 Generate controller for core feature (e.g., `rails g controller Dashboard index`)
+  - [ ] 2.2 Set up routes for core feature in `config/routes.rb`
+  - [ ] 2.3 **Create only the core routes initially - hold off on other pages**
+  - [ ] 2.4 Ensure core routes follow Rails conventions
+  - [ ] 2.5 Test that core routes are working
+
+- [ ] 3.0 Create Application Layout for Core Experience
+  - [ ] 3.1 Update `app/views/layouts/application.html.erb` with main structure
+  - [ ] 3.2 Create minimal navigation (just enough for core page)
+  - [ ] 3.3 Focus on the core page's specific layout needs
+  - [ ] 3.4 Implement responsive design for core page
+  - [ ] 3.5 Add any core-specific meta tags
+
+- [ ] 4.0 Implement Core Page COMPLETELY
+  - [ ] 4.1 Create the main view file (e.g., `app/views/dashboard/index.html.erb`)
+  - [ ] 4.2 Add all hardcoded data needed for realistic experience
+  - [ ] 4.3 Implement all UI components for this page
+  - [ ] 4.4 Add interactive elements (dropdowns, modals, etc.)
+  - [ ] 4.5 Ensure responsive design works perfectly
+  - [ ] 4.6 Polish with transitions and hover states
+  - [ ] 4.7 **STOP HERE - Let user review and iterate**
+
+**🛑 PAUSE POINT: After completing the core page, stop and let the user review. They will likely want to iterate on styling, layout, and functionality before proceeding.**
+
+- [ ] 5.0 After Core Page Approval - Generate Supporting Controllers
+  - [ ] 5.1 Generate PagesController for static pages: `rails g controller Pages home about contact`
+  - [ ] 5.2 Generate other resource controllers based on flowchart
+  - [ ] 5.3 Set up remaining routes in `config/routes.rb`
+  - [ ] 5.4 Ensure all routes follow Rails conventions
+  - [ ] 5.5 Test all routes are working
+
+- [ ] 6.0 Expand Navigation and Layout
+  - [ ] 6.1 Create full navigation partial: `app/views/shared/_navigation.html.erb`
+  - [ ] 6.2 Create footer partial: `app/views/shared/_footer.html.erb`
+  - [ ] 6.3 Update layout to work for all pages
+  - [ ] 6.4 Ensure navigation highlights current page
+  - [ ] 6.5 Add mobile menu functionality
+
+- [ ] 7.0 Implement Supporting Pages
+  - [ ] 7.1 Create homepage if not the core page
+  - [ ] 7.2 Create about page
+  - [ ] 7.3 Create contact page
+  - [ ] 7.4 Create other resource views (index, show)
+  - [ ] 7.5 Ensure consistent styling across all pages
+
+- [ ] 8.0 Define Structs and Add Sample Data
+  - [ ] 8.1 Define Structs for all data types at top of controllers
+  - [ ] 8.2 Create realistic sample data arrays
+  - [ ] 8.3 Implement show actions with find logic
+  - [ ] 8.4 Add methods to Structs that mimic ActiveRecord
+  - [ ] 8.5 Document all Struct attributes
+
+  ```ruby
+  # Example Struct definition
+  Product = Struct.new(:id, :name, :slug, :price, :description, 
+                      :image_url, :category, :in_stock, :created_at, 
+                      keyword_init: true) do
+    def to_param
+      slug
+    end
+    
+    def formatted_price
+      "$%.2f" % price
+    end
+  end
+  ```
+
+- [ ] 9.0 Create Reusable Components
+  - [ ] 9.1 Extract repeated UI into partials
+  - [ ] 9.2 Create card partial: `app/views/shared/_card.html.erb`
+  - [ ] 9.3 Create button components
+  - [ ] 9.4 Create form components
+  - [ ] 9.5 Document component usage
+
+- [ ] 10.0 Testing and Validation
+  - [ ] 10.1 Write controller tests
+  - [ ] 10.2 Create system tests for user flows
+  - [ ] 10.3 Add E2E tests with Cypress
+  - [ ] 10.4 Test all responsive breakpoints
+  - [ ] 10.5 Validate accessibility
+
+- [ ] 11.0 Prepare for Dynamic Data
+  - [ ] 11.1 Add TODO comments for database queries
+  - [ ] 11.2 Create seed file matching Struct data
+  - [ ] 11.3 Document data relationships
+  - [ ] 11.4 Plan model structure
+  - [ ] 11.5 Note where authentication will be added
+
+## File Tracking
+
+### Core Page Files (Create First)
+| File Path | Purpose | Task Ref | Status |
+|-----------|---------|----------|--------|
+| Core controller (e.g., `app/controllers/dashboard_controller.rb`) | Core feature controller | 2.1 | ⏳ |
+| Core view (e.g., `app/views/dashboard/index.html.erb`) | Main application view | 4.1 | ⏳ |
+| `app/views/layouts/application.html.erb` | Initial layout | 3.1 | ⏳ |
+
+### Supporting Files (Create After Core Review)
+| File Path | Purpose | Task Ref | Status |
+|-----------|---------|----------|--------|
+| `app/controllers/pages_controller.rb` | Static pages | 5.1 | ⏳ |
+| `app/views/shared/_navigation.html.erb` | Full navigation | 6.1 | ⏳ |
+| `app/views/shared/_footer.html.erb` | Footer partial | 6.2 | ⏳ |
+| `app/views/pages/*.html.erb` | Supporting pages | 7.1-7.4 | ⏳ |
+| `app/views/shared/_card.html.erb` | Card component | 9.2 | ⏳ |
+| `spec/system/*_spec.rb` | System tests | 10.2 | ⏳ |
+| `db/seeds.rb` | Seed data | 11.2 | ⏳ |
+
+### Files to Modify
+| File Path | Changes | Task Ref | Status |
+|-----------|---------|----------|--------|
+| `config/routes.rb` | Add routes incrementally | 2.2, 5.3 | ⏳ |
+
+## Core-First Development Benefits
+
+1. **User Feedback Early**: Get the most important page right before building everything else
+2. **Design System Validation**: Test your design system on the most complex page first
+3. **Efficient Iteration**: Changes to core page inform decisions for other pages
+4. **Clear Priorities**: Focus effort where it matters most
+5. **Reduced Rework**: Avoid building pages that might change based on core page decisions
+
+## Next Steps After Static Pages Complete
+- Replace Structs with ActiveRecord models
+- Add authentication and authorization
+- Implement forms and CRUD operations
+- Add dynamic features (search, filtering)
+- Enhance with real-time updates 

data/lib/nova/templates/user_story_example.md

@@ -1,83 +1,75 @@
-# User Story: Reset Password
+# User Story: [Feature Name]
 
-## Overview
+**As a** [type of user]  
+**I want** [goal/desire]  
+**So that** [benefit/value]
 
-**As a** registered user,  
-**I want** to be able to reset my password if I forget it,  
-**So that** I can regain access to my account without contacting support.
+## Context
+[1-2 sentences providing background on why this feature is needed]
 
-## Flowchart
-```mermaid
-flowchart TD
-    HomePage --> LoginPage
-    LoginPage --> ForgotPasswordPage
-    ForgotPasswordPage --> ResetPasswordEmail
-    ResetPasswordEmail --> ResetPasswordPage    
-    ResetPasswordPage --> Dashboard
-```
+## Scenarios
 
-## Acceptance Criteria
-
-1. User can request a password reset from the login page
-2. System sends a password reset email with a secure, time-limited token
-3. User can create a new password after clicking the reset link
-4. New password must meet security requirements (8+ chars, 1 uppercase, 1 number)
-5. User receives confirmation after successful password reset and is automatically logged in
-6. Reset links expire after x hours
-
-## Pages, Major Components, and Forms
-
-### Forgot Password Page
-**Form**:
-- Email:
-  - Required
-  - Validate email format
-- Submit Button
+### Happy Path
+1. User navigates to [starting point]
+2. User performs [action]
+3. System responds with [result]
+4. User achieves [goal]
 
-### Password Reset Email
-- Link to reset password with token
+### Edge Cases
+- What happens if [condition]?
+- What happens when [error state]?
 
-### Reset Password Page
-Page for users to set their new password. App will validate the token exists and is not expired and pull the appropriate user record.
-
-**Form**:
-- New Password:
-  - Required
-  - Validate: 8 characters, 1 upper, 1 special character
-- Confirm New Password
-  - Validate: Matches new password
-- Submit Button
-
-### Dashboard
-After resetting password user should be logged in and lands on the dashbard where they see a toast message confirming successful password reset
+## Acceptance Criteria
+- [ ] User can [primary action]
+- [ ] System validates [key requirement]
+- [ ] User receives [feedback/confirmation]
+- [ ] [Security/business rule] is enforced
 
-## Additional Notes & Assumptions
+## Key Screens
+[List the main screens/pages involved without detailed field specifications]
 
-- User must be logged out to access the password reset link
-- Only registered users can request a password reset
+## Questions
+- [ ] [Any unknowns that need clarification]
 
-## Outstanding Questions
+---
 
-- [ ] What is the maximum duration for the password reset token?
+## Example: Password Reset
 
-## Developer Notes
+**As a** registered user  
+**I want** to reset my forgotten password  
+**So that** I can regain access to my account without contacting support
 
-- [ ] Will need to configure Devise to allow users to reset their passwords
+## Context
+Users occasionally forget their passwords and need a self-service way to regain access that doesn't burden our support team.
 
-## Data Migrations
+## Scenarios
 
-```ruby
-create_table :users do |t|
-  t.string :email, null: false  
-  # ... more fields
-  t.timestamps
-end
-add_index :users, :email, unique: true
-```
+### Happy Path
+1. User clicks "Forgot password?" on login page
+2. User enters their email address
+3. System sends reset email with secure link
+4. User clicks link and sets new password
+5. User is logged in and redirected to dashboard
 
-## 3rd Party Dependencies (apis, gems, and libraries)
+### Edge Cases
+- Non-existent email: Show generic "If email exists, reset sent" message
+- Expired link: Show friendly error with option to request new link
+- User already logged in: Redirect to account settings
 
-### Devise
-- **Purpose**: Using Devise for auth in this application, so password reset will be handled via Devise.
-- **Documentation to Review**: github.com/devise
-- **Notes**: will use the view generators and customize the views from there
+## Acceptance Criteria
+- [ ] Reset link accessible from login page
+- [ ] Email sent within 2 minutes of request
+- [ ] Password requirements clearly shown (8+ chars, mixed case, number)
+- [ ] Reset links expire after 24 hours
+- [ ] Success confirmation shown after reset
+- [ ] Only one active reset link per user at a time
+
+## Key Screens
+- Login page (with forgot password link)
+- Request reset page (email entry)
+- Reset password page (new password entry)
+- Success/confirmation page
+
+## Questions
+- [ ] Should we notify users when a reset is requested for security?
+- [ ] Do we want to implement rate limiting for reset requests?

data/lib/nova/templates/windsurfrules_template.txt

@@ -0,0 +1 @@
+This Nova project uses cursor rules for AI guidance located at .cursor/rules/nova.mdc. Please review before proceeding.

data/lib/nova.rb

@@ -2,5 +2,5 @@ require_relative 'nova/cli'
 require_relative 'nova/generator'
 
 module Nova
-  VERSION = '0.1.1'
+  VERSION = '0.2.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: nova-cli
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.2.1
 platform: ruby
 authors:
 - Ryan Francis
@@ -38,21 +38,15 @@ files:
 - lib/nova.rb
 - lib/nova/cli.rb
 - lib/nova/generator.rb
-- lib/nova/templates/big_picture_readme_template.md
 - lib/nova/templates/design_decisions_example.md
-- lib/nova/templates/design_system_readme_template.md
-- lib/nova/templates/flowchart_template.md
+- lib/nova/templates/flowchart_example_template.md
+- lib/nova/templates/nova.mdc
 - lib/nova/templates/prd_example_template.md
-- lib/nova/templates/prompts_example.md
-- lib/nova/templates/prompts_examples/01_generate_app.md
-- lib/nova/templates/prompts_examples/02_generate_styleguide.md
-- lib/nova/templates/prompts_examples/03_generate_static_pages.md
-- lib/nova/templates/prompts_examples/04_authentication_feature.md
-- lib/nova/templates/prompts_readme_template.md
 - lib/nova/templates/readme_template.md
-- lib/nova/templates/styleguide_index.html
-- lib/nova/templates/user_stories_readme_template.md
+- lib/nova/templates/tasks_examples/1_generate_application.md
+- lib/nova/templates/tasks_examples/2_generate_static_pages.md
 - lib/nova/templates/user_story_example.md
+- lib/nova/templates/windsurfrules_template.txt
 homepage: https://github.com/LaunchPadLab/nova
 licenses:
 - MIT

data/lib/nova/templates/big_picture_readme_template.md

@@ -1,29 +0,0 @@
-# 1. Big Picture
-
-This directory contains high-level strategic documents that define the background, vision, and goals of the project.
-
-## Purpose
-
-The Big Picture documents establish the foundation and direction for the entire project. They help stakeholders align on objectives and priorities before diving into more detailed planning.
-
-## Files in this Directory
-
-- **prd_example.md**: Defines a blueprint for the product.
-- **flowchart.md**: Visual representation of the application's user flow using Mermaid diagrams
-
-## How to Use
-
-1. Create a new PRD file at 1_big-picture/prd.md and use 1_big-picture/prd_example.md as a template
-2. Create visual application flows in flowchart.md to illustrate user journeys
-
-## Best Practices
-
-- Involve all key stakeholders in defining the Big Picture
-- Keep these documents high-level and focused on strategy (details come later)
-- Revisit and update these documents as the project evolves
-- Use clear, concise language that all stakeholders can understand
-- Use flowcharts to communicate complex user journeys visually
-
-## Next Steps
-
-After completing the Big Picture documents, move on to [2_user-stories](../2_user-stories) to begin breaking down the product into more detailed user stories.

data/lib/nova/templates/design_system_readme_template.md

@@ -1,22 +0,0 @@
-# Design System
-
-The Design System directory contains the visual language and UI component documentation for your application. It builds on the PRD and user stories and provides a consistent framework for implementing the user interface.
-
-## Purpose
-
-A design system serves as a centralized resource for design guidelines, UI components, patterns, and principles. It ensures consistency, improves collaboration between designers and developers, and accelerates implementation.
-
-## Directory Structure
-
-The design system is organized as follows:
-
-```
-3_design-system/
-├── README.md (this file)
-└── design_decisions.md
-```
-
-## Design System Implementation
-
-1. **Review the PRD and user stories** to ensure visual consistency with the brand and planned user experience
-2. **Document design decisions** in the `design_decisions.md` file, including color palette, typography, spacing, and component styles

data/lib/nova/templates/prompts_example.md

@@ -1,134 +0,0 @@
-# Project Implementation Tasks
-
-A list of implementation tasks for the Customer Portal Application.
-
-## 1. Rails Application Setup
-Initialize a Rails 8 application with PostgreSQL, Tailwind CSS, Rspec, and Flowbite. 
-
-```
-rails _8.0.2_ new app_name --database=postgresql --css=tailwind
-cd app_name
-bundle exec rails tailwindcss:install
-bundle exec rails db:create db:migrate
-bundle exec rails rspec:install
-```
-
-Create a Hello World page that is styled with Tailwind CSS and Flowbite (simple tooltip) so we can confirm both are working.
-
-### Flowbite Setup
-Importmap is the default way of handling JavaScript in Rails. In order to support turbo load from importmaps you have to pin the flowbite.turbo.js file from a CDN where the turbo:load event listeners are added instead of load.
-
-Add the following line inside your importmap.rb file:
-pin "flowbite", to: "https://cdn.jsdelivr.net/npm/flowbite@3.1.2/dist/flowbite.turbo.min.js"
-Then you need to import flowbite inside your application.js file:
-import 'flowbite';
-This will enable the interactive elements like dropdowns, modals, and navbars work by hooking the event listeners and actions to the data attributes whenever a new page is loaded in your application.
-
-### Gems
-- Figaro for env variables
-- Decanter for handling incoming params: https://github.com/LaunchPadLab/decanter
-- Active Storage (for file attachments)
-
-Testing:
-- Factory Bot for testing
-- Faker
-- DatabaseCleaner
-- Shoulda Matchers
-- RSpec Rails
-- Capybara
-- SimpleCov
-
-**Related Artifacts:**
-- [PRD](../1_big-picture/prd.md)
-
-## 2. Authentication System
-Implement user registration, login functionality, password reset, and role-based permissions using Devise.
-
-**Related Artifacts:**
-- [Authentication Requirements](../1_big-picture/prd_example.md#authentication)
-- [User Flow](../1_big-picture/flowchart.md#authentication-flow)
-- [Login User Story](../2_user-stories/authentication.md#user-login)
-- [Registration User Story](../2_user-stories/authentication.md#user-registration)
-
-## 3. Core Database Structure
-Design the database schema, create models with associations, set up validations, and implement seed data for development.
-
-**Related Artifacts:**
-- [Data Model Overview](../1_big-picture/prd_example.md#data-model)
-- [Entity Relationship Diagram](../1_big-picture/flowchart.md#entity-relationships)
-- [Data Requirements](../2_user-stories/data_requirements.md)
-
-## 4. Dashboard Implementation
-Create a responsive dashboard with quick stats widgets, activity feed, and notification system.
-
-**Related Artifacts:**
-- [Dashboard Requirements](../1_big-picture/prd_example.md#dashboard)
-- [Dashboard User Story](../2_user-stories/dashboard.md)
-
-## 5. Customer Management
-Build CRUD operations for customer data with search, filtering, detailed views, and history tracking.
-
-**Related Artifacts:**
-- [Customer Management Requirements](../1_big-picture/prd_example.md#customer-management)
-- [Customer User Stories](../2_user-stories/customers.md)
-
-## 6. Document Management
-Implement document upload, versioning, PDF generation for invoices, and document sharing capabilities.
-
-**Related Artifacts:**
-- [Document Management Requirements](../1_big-picture/prd_example.md#document-management)
-- [Document Flow](../1_big-picture/flowchart.md#document-flow)
-- [Document User Stories](../2_user-stories/documents.md)
-
-## 7. Reporting System
-Create report templates with data aggregation, visual charts, and export functionality.
-
-**Related Artifacts:**
-- [Reporting Requirements](../1_big-picture/prd_example.md#reporting)
-- [Report User Stories](../2_user-stories/reports.md)
-
-## 8. API Integration
-Design API endpoints with authentication, third-party integrations, and webhook functionality.
-
-**Related Artifacts:**
-- [API Requirements](../1_big-picture/prd_example.md#api-integration)
-- [Integration Flow](../1_big-picture/flowchart.md#integration-flow)
-- [API User Stories](../2_user-stories/api.md)
-
-## 9. Real-time Features
-Implement WebSocket connections for real-time notifications, collaborative editing, and chat functionality.
-
-**Related Artifacts:**
-- [Real-time Requirements](../1_big-picture/prd_example.md#real-time-features)
-- [Real-time Communication Flow](../1_big-picture/flowchart.md#real-time-flow)
-- [Chat User Story](../2_user-stories/real_time.md#chat)
-- [Notification User Story](../2_user-stories/real_time.md#notifications)
-
-## 10. Performance Optimization
-Implement caching, optimize database queries, set up background job processing, and conduct load testing.
-
-**Related Artifacts:**
-- [Performance Requirements](../1_big-picture/prd_example.md#performance)
-- [System Load Estimates](../1_big-picture/prd_example.md#load-estimates)
-
-## 11. Security Hardening
-Perform security audit, implement security measures, set up monitoring and logging.
-
-**Related Artifacts:**
-- [Security Requirements](../1_big-picture/prd_example.md#security)
-- [Privacy Requirements](../1_big-picture/prd_example.md#privacy)
-- [Security User Stories](../2_user-stories/security.md)
-
-## 12. Deployment & Launch
-Finalize production environment, create deployment scripts, develop rollback procedures, and execute launch.
-
-**Related Artifacts:**
-- [Deployment Strategy](../1_big-picture/prd_example.md#deployment)
-- [Launch Plan](../1_big-picture/prd_example.md#launch-plan)
-- [Rollback Procedures](../1_big-picture/prd_example.md#rollback)
-
-### Production Gems
-- Redis (for caching)
-- Sidekiq (for background jobs)
-- Sentry (for error tracking)
-- Aws S3 (for file storage)

data/lib/nova/templates/prompts_examples/01_generate_app.md

@@ -1,94 +0,0 @@
-# Generate Application
-
-This prompt is for the initial setup of the Rails application with the core dependencies required for the project.
-
-## Task Description
-
-Initialize a Rails 8 application with PostgreSQL, Tailwind CSS, Rspec, Flowbite, and Cypress.
-
-### Steps
-
-1. Create a new Rails application with the following command:
-```
-rails _8.0.2_ new app_name --database=postgresql --css=tailwind
-cd app_name
-bundle exec rails tailwindcss:install
-bundle exec rails db:create db:migrate
-bundle exec rails rspec:install
-```
-
-**Tailwind Note**: Please read the latest v4 docs here before trying to work with Tailwind as a lot has changed since v3 such as the ability to load colors in global.css instead of needing a tailwind config file: https://tailwindcss.com/blog/tailwindcss-v4
-
-Make sure rspec works: `bundle exec rspec`
-
-2. Set up the following gems in the Gemfile:
-
-#### Core Gems
-- Figaro (for environment variables)
-- Decanter (for handling incoming params): https://github.com/LaunchPadLab/decanter
-- Active Storage (for file attachments)
-
-#### Testing Gems
-- Factory Bot Rails
-- Faker
-- DatabaseCleaner
-- Shoulda Matchers
-- RSpec Rails
-- Capybara
-- SimpleCov
-
-#### Production Gems
-- Redis (for caching)
-- Sidekiq (for background jobs)
-- Sentry (for error tracking)
-- AWS S3 SDK (for file storage)
-
-3. Set up Flowbite for interactive components:
-   
-   Importmap is the default way of handling JavaScript in Rails. To support turbo load:
-   
-   Add the following line inside your importmap.rb file:
-   ```ruby
-   pin "flowbite", to: "https://cdn.jsdelivr.net/npm/flowbite@3.1.2/dist/flowbite.turbo.min.js"
-   ```
-   
-   Then import flowbite inside your application.js file:
-   ```javascript
-   import 'flowbite';
-   ```
-
-4. Create a Hello World page with Tailwind CSS and Flowbite to confirm both are working properly:
-   - Include a simple styled page
-   - Add a simple Flowbite component (tooltip) for testing
-
-5. Set up Cypress for headless E2E testing:
-   ```bash
-   yarn add cypress --dev
-   ```
-   
-   Create a simple E2E test for the Hello World page:
-   ```javascript
-   // cypress/e2e/hello_world_spec.cy.js
-   describe('Hello World Page', () => {
-     it('successfully loads', () => {
-       cy.visit('http://localhost:3000')
-       cy.contains('Hello World')
-       cy.get('[data-tooltip-target]').should('exist')
-     })
-   })
-   ```
-   
-   Add script to package.json for headless testing:
-   ```json
-   "scripts": {
-     "test:e2e": "cypress run"
-   }
-   ```
-   
-   Run the test headlessly:
-   ```bash
-   yarn test:e2e
-   ```
-
-## Related Artifacts
-- [PRD](../1_big-picture/prd.md)

data/lib/nova/templates/prompts_examples/02_generate_styleguide.md

@@ -1,26 +0,0 @@
-# Generate Static Styleguide
-
-This prompt is for creating a static styleguide application based on the design system decisions, user stories, PRD, and flowchart.
-
-## Task Description
-
-Using the design decisions from `../3_design-system/design_decisions.md`, create a styleguide within the application (in the code/ directory) that showcase the colors, typography, componentry, and example forms. Please nest all pages within this under /styleguide route as follows:
-- Styleguide Home: /styleguide
-- Colors: /styleguide/colors
-- Typography: /styleguide/typography
-- Componentry: /styleguide/componentry
-- Forms: /styleguide/forms
-- Authenticated Layout: /styleguide/authenticated
-- Unauthenticated Layout: /styleguide/unauthenticated
-
-Create the static styleguide with:
-   - Tailwind CSS for utility-based styling
-   - Flowbite for interactive components (modals, tooltips, etc.)
-   - HTML structure that follows the design system
-
-**Tailwind Note**: Please read the latest v4 docs here before trying to work with Tailwind as a lot has changed since v3 such as the ability to load colors in global.css instead of needing a tailwind config file: https://tailwindcss.com/blog/tailwindcss-v4
-
-## Related Artifacts
-- [PRD](../1_big-picture/prd.md)
-- [Flowchart](../1_big-picture/flowchart.md)
-- [Design Decisions](../3_design-system/design_decisions.md)