feat: add field management commands

[angeloashmore]

Resolves: #21, #22

Description

Adds a prismic field command group for managing fields on local slice, page type, and custom type models. This enables full content modeling from the CLI without needing to use the Prismic editor.

Commands:

• prismic field add <type> <id> --to <model> — Add a field to a model.
• prismic field list --from <model> — List all fields on a model.
• prismic field remove <id> --from <model> — Remove a field from a model.

Supported field types for field add:

• boolean
• color
• date
• embed
• geopoint
• number
• text
• timestamp
• rich-text
• select
• table
• image
• link
• link-to-media
• content-relationship
• integration
• group
• uid (page types and custom types only)

Each field type has its own subcommand with type-specific flags (e.g. --default-value, --placeholder, --allow).

The --to flag accepts a relative path to a model.json (slice) or index.json (page/custom type). For slices, --variation selects the variation (defaults to "default"). For types, --tab selects the tab (defaults to "Main").

Field IDs support dot-notation paths (e.g. my_group.my_field) to target fields nested inside groups.

Checklist

• A comprehensive Linear ticket, providing sufficient context and details to facilitate the review of the PR, is linked to the PR.
• If my changes require tests, I added them.
• If my changes affect backward compatibility, it has been discussed.
• If my changes require an update to the CONTRIBUTING.md guide, I updated it.

Preview

# Add a text field to a slice
prismic field add text title --to slices/Hero/model.json --label "Title"

# Add a rich text field with specific block types
prismic field add rich-text description --to slices/Hero/model.json \
  --allow heading1,paragraph,strong,em --single

# Add a select field with options
prismic field add select color --to customtypes/page/index.json \
  --option red --option green --option blue --default-value red

# Add a link field to a specific custom type tab
prismic field add link cta_link --to customtypes/page/index.json \
  --tab "CTA" --allow-target-blank

# Add a field inside a group using dot-notation
prismic field add text cards.name --to slices/Hero/model.json

# Add a boolean field with labels
prismic field add boolean is_featured --to customtypes/blog_post/index.json \
  --true-label "Featured" --false-label "Not featured"

# Target a specific slice variation
prismic field add image background --to slices/Hero/model.json \
  --variation "withBackground"

# List all fields on a slice
prismic field list --from slices/Hero/model.json

# Remove a field
prismic field remove old_field --from slices/Hero/model.json

How to QA ¹

---

Note

Medium Risk
Adds new CLI surface area that mutates local slice/custom type JSON models (including nested group targeting), so mistakes could overwrite models or generate incorrect types despite having good e2e coverage.

Overview
Introduces a new prismic field command group with add, list, and remove subcommands to manage fields on local slice and custom type models, and wires it into the main CLI router.

field add supports multiple field-type subcommands (e.g. boolean, rich-text, link, uid, etc.), applies type-specific flags, prevents overwriting existing fields, and regenerates types after saving. Model targeting is centralized in new resolveModel/resolveFieldTarget helpers to support --to/--from, slice --variation, type --tab, and dot-notation for nested group fields; extensive new tests cover add/list/remove flows and error cases.

^{Written by Cursor Bugbot for commit 44cc21e. This will update automatically on new commits. Configure here.}

Footnotes

1. Please use these labels when submitting a review:
   ❓ #ask: Ask a question.
   💡 #idea: Suggest an idea.
   ⚠️ #issue: Strongly suggest a change.
   🎉 #nice: Share a compliment. ↩

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

parseNumber silently accepts empty strings and Infinity

Low Severity

parseNumber uses Number(value) followed by a Number.isNaN() check, but Number("") returns 0 (not NaN) and Number("Infinity") returns Infinity. This means --min "" is silently accepted as 0, and --min Infinity is accepted as Infinity, both bypassing the validation intended to reject non-numeric input.