$ recombobulate _
home / tips / generate-typescript-types-from-a-json-payload
160

Generate TypeScript Types from a JSON Payload

recombobulate @recombobulate · Mar 25, 2026 · Workflows
generate-typescript-types-from-a-json-payload

Manually writing TypeScript interfaces from a large API response is a chore that Claude can knock out in seconds.

Just paste the JSON and ask:

Convert this API response into TypeScript interfaces.
Use strict types — no `any`. Mark optional fields where they might be absent.

{
  "user": {
    "id": 42,
    "name": "Jane Doe",
    "email": "jane@example.com",
    "roles": ["admin", "editor"],
    "address": {
      "street": "123 Main St",
      "city": "London",
      "postcode": "SW1A 1AA"
    },
    "verified_at": null
  }
}

Claude will produce properly nested interfaces, handle nullable fields with string | null, and use readonly arrays where appropriate — far better than a basic JSON-to-type generator.

You can push further and ask Claude to also generate a Zod schema for runtime validation alongside the static types, or request that it add JSDoc comments explaining each field based on its name and shape.

Also generate a Zod schema that matches these interfaces,
and add JSDoc comments to each field.

Paste the response, get the types — your IDE autocomplete will thank you.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 month ago