Introduction

At Gothsec/promptd, we are building a robust platform designed to streamline AI interaction workflows. As our application grows, providing a seamless user experience for model selection and prompt submission has become a top priority. In our latest development cycle, we focused on implementing a structured UI approach for handling model selection via a submission modal.

Streamlining User Input

When dealing with generative AI, the transition from "selecting a model" to

Authentication is the gatekeeper of your user experience. If your login flow feels clunky or disconnected from the rest of your application's design language, you are already losing trust before the user has even logged in. In the Gothsec/promptd project, we recently focused on unifying our authentication interface by integrating Shadcn UI components directly into our existing modal workflows.

The Problem with Generic Modals

Many developers treat authentication modals as separate islands.

Introduction

In our ongoing work on the promptd project, we recently hit a point where our dependency management needed a more efficient strategy. As our stack grew, we focused on streamlining our package installation and disk usage, leading us to migrate our workflow to pnpm.

The Shift to Pnpm

Moving to a new package manager is often seen as a minor infrastructure update, but in a project utilizing React and modern UI components, it significantly impacts the local development

Most developers want to jump straight into the schema design or component library setup. We are working on the promptd project, an upcoming tool designed to streamline prompt management, and my first commit wasn't a database migration or a UI layout. It was a single Markdown file: SRS.md.

The Problem with Starting in the IDE

It is tempting to start spinning up a project with Supabase and scaffolding a UI with Shadcn UI before having a concrete plan.