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

Introduction

In the Gothsec/promptd project—a tool designed for streamlined prompt management—we recently focused on improving the platform's visual identity. While functionality is the backbone of any application, professional branding and shareable previews are critical for user experience and discoverability.

The Power of Open Graph Images

When users share links from your application on social platforms, the "Open Graph" (OG) image is often the first thing a potential user sees.

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.

Getting Started with Promptd

Recently, I began working on promptd, a new project focused on building robust prompt management workflows. To ensure a fast development cycle and a scalable foundation, I opted for a modern stack that emphasizes type safety and seamless backend integration.

The Technical Stack

Choosing the right tools is like setting the foundation of a house. For promptd, I selected:

• Next.js: Providing server-side rendering and an intuitive routing system.

Improving Auth Infrastructure

Authentication logic often becomes the most fragile part of a growing codebase. In our promptd project, we recognized that maintaining custom session management was becoming a burden, especially when trying to ensure consistent user state across both server-side and client-side transitions.

The Challenge

Managing complex state between the browser and the server requires careful handling of cookies and session persistence. We faced issues with:

Foundation Matters

Starting a new project often feels like staring at a blank canvas. With the recent launch of the Gothsec/promptd project, we focused on establishing a robust, scalable foundation that balances rapid development with clean architectural patterns. By utilizing React and Next.js, we ensure the interface is both performant and highly interactive.

Establishing the Structure

When setting up the base architecture, the primary goal was to create a maintainable CSS

The Challenge

In our ongoing development of the Gothsec/promptd project, we recognized that our interface needed better visual hierarchy and clarity, especially concerning legal compliance and user transparency. Specifically, the text colors used for our Privacy and Terms of Service disclosures lacked sufficient contrast, making them difficult for some users to read against the standard background.

The Solution

To address this, we performed a targeted update to our React-based UI

Building a custom authentication system from scratch is a classic trap. You spend weeks perfecting password hashing and session management, only to realize your users just want to click 'Sign in with Google' and move on with their day. Recently, in the promptd project, we decided to offload this complexity by integrating managed identity providers.

The Authentication Overhead

When scaling an application, the burden of maintaining user credentials grows exponentially.