README.md

Practitioner: AI-Powered Interview Creation

Practitioner empowers you to streamline the interview creation process with the assistance of artificial intelligence (AI). Leverage the power of Gemini AI to craft effective and insightful interview questions, saving you valuable time and effort.

Key Features

• AI-Driven Question Generation: Generate interview questions tailored to specific job roles, skills, and company needs using Gemini AI's capabilities.
• Next.js Framework: Benefit from the performance and flexibility offered by Next.js, a popular React framework for building modern web applications.
• TypeScript Support: Ensure code maintainability and catch errors early with TypeScript's static typing features.
• Tailwind CSS Styling: Craft a visually appealing and responsive user interface with Tailwind CSS's utility-first approach.
• Drizzle ORM Integration: Manage project data effectively using Drizzle ORM, a lightweight and performant ORM library.

Getting Started

To set up Practitioner and begin creating AI-powered interviews, follow these steps:

1. Prerequisites:

   • Node.js and npm (or yarn) installed on your system. You can verify this by running node -v and npm -v (or yarn -v) in your terminal.

2. Clone the Repository:

3. Replace .env.exmaple with your variables

4. Run Drizzle query to push migrations to database

bun run db:push

Start the Development Server:

bun run dev  # or yarn dev

This will start a local development server, typically accessible at http://localhost:3000.

Tech Stack

• Frontend: Next.js (https://cdn.ampproject.org/c/s/nextjs.org/?amp=1)
• Programming Language: TypeScript (https://www.typescriptlang.org/)
• CSS Framework: Tailwind CSS (https://tailwindcss.com/docs/installation)
• ORM: Drizzle ORM (https://github.com/drizzle-team/drizzle-orm)
• AI Engine: Gemini AI (details about accessing and integrating Gemini AI are likely specific to their platform/documentation)

Contributing

We welcome contributions to Practitioner! If you'd like to get involved, please refer to the CONTRIBUTING.md file (if it exists) for guidelines on code style, testing, and pull request submission.