Technical Specification: JSON to Golang Struct Converter

1. Overview

A high-performance, client-side utility that transforms raw JSON input into valid, typed Golang struct definitions. The interface prioritizes speed, clarity, and developer productivity.

2. Core Features

• Live Conversion: Real-time parsing as the user types or pastes JSON.
• Customizable Tags: Toggle support for standard json, mapstructure, xml, or gorm struct tags.
• Type Inference: Automatically detects types (string, int, float, bool, slice, map, struct).
• Naming Conventions: Options to toggle between PascalCase and snake_case for field names.
• Copy to Clipboard: One-click functionality to copy the generated struct.
• Clear Action: A one-click reset button to clear the input area.

3. UI/UX Design (Light Mode Only)

• Palette: Use a clean, professional SaaS aesthetic:
  • Background: #f8fafc (Slate 50)
  • Containers: #ffffff (White) with soft drop shadows (shadow-sm)
  • Primary Buttons: #4f46e5 (Indigo 600)
  • Text Colors: #1e293b (Slate 800) for primary, #64748b (Slate 500) for secondary.
  • Borders: #e2e8f0 (Slate 200).
• Layout:
  • Desktop: Two-pane side-by-side layout (Input Left, Output Right).
  • Mobile: Stacked layout (Input Top, Output Bottom).
• Animations: Subtle fade-in animations when generating code. Smooth border transitions on focus.

4. Technical Constraints & Architecture

• Frameworks: Pure Vanilla JS, HTML5, CSS3. Tailwind CSS via CDN for styling.
• Syntax Highlighting: Use Prism.js (or similar lightweight library) to render the output struct for readability.
• In-Memory Only: Because this runs in a sandboxed iframe, DO NOT use localStorage, sessionStorage, or cookies. State management must be handled purely in memory (JavaScript variables).
• Security:
  • No usage of eval(), alert(), prompt(), or confirm(). All interactions (like "copied to clipboard" notifications) must be handled via custom, non-intrusive UI modals or toast messages within the DOM.
  • All external links must be target="_blank" and rel="noopener noreferrer".

5. Development Workflow

1. Validation: Implement a strict JSON validator on input. If the JSON is invalid, show a non-intrusive warning message within the UI instead of blocking the app.
2. Parsing Logic: Create a recursive function that iterates through the JSON object. For keys, generate a sanitized struct field name (e.g., removing special characters, applying correct casing). For values, map JSON types to Go primitive types (e.g., float64 for numbers, bool for booleans, interface{} for nulls).
3. Formatting: Ensure output indentation is configurable (2 spaces vs 4 spaces).
4. Performance: Ensure the conversion logic is debounced (e.g., wait 300ms after keystroke) to prevent UI lag on large JSON files.