Frontend Repository CLI Generator

Problem

In frontend repositories, API calls, request types, enum constants, and auth settings are often spread across directories and custom HTTP wrappers. Manually building a CLI can miss optional fields, nested types, status-code meanings, or environment-specific base URLs.

How It Works

• Builds a repository profile first: detects monorepo structure and locates API, type, enum, and HTTP wrapper files.
• Samples before scanning: reads a few API files to infer baseURL, path prefixes, and calling patterns, then scans candidate endpoints.
• Parses types and enums: extracts fields, optional markers, enum values, and comments from TypeScript interface, type, and constant files.
• Detects auth strategy: supports Bearer Token, Cookie, API Key, and no-auth flows, with matching auth commands or configuration.
• Confirms before generation: outputs a technical plan first, then generates a Python Click or Node.js oclif project for local installation and debugging.

Boundaries

This is best suited for frontend repos with clear API layers, type definitions, and business enums. Dynamic URL construction, runtime configs, or unconventional auth may require manual review. Cookie capture also depends on a local browser debugging setup.