Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Statamic Field Settings
statamic-addon/visual-editor
cursor
statamic-defaults
fieldtypes
control-panel
addon-builds
config-fields
vue-components
fieldsets

NEVER change Statamic default fields — only build on top unless the user explicitly asks

Install
php artisan boost:add-skill statamic-addon/visual-editor

Save this content to: .cursor/rules/statamic-field-settings.mdc

# Statamic default and fields are untouchable

This outranks every other rule in this addon. Same rule as `~/.cursor/rules/00-statamic-default-urorligt.mdc`.

Do not change, replace, wrap, or hijack Statamic's normal field behaviour in the Control Panel. Display name, handle, instructions, defaults, integers, text, replicator, grid, bard — they keep working as Statamic ships them.

Only **build on top**. Changing Statamic default is allowed only when the user explicitly asks for that change **in this message**.

## Forbidden

- Subclass + `::register()` on an existing handle (`iconify`, `replicator`, `text`, …)
- Wrap/replace a field's Vue component
- `npm run cp:build` here or on the site when it rebuilds `addon.js` — that breaks field settings
- Overwrite `public/vendor/app/` or `public/vendor/statamic-addon/`
- Change `DefaultSetsFieldtype.js` (bundled in `addon-DmXwhlR7.js`)
- CSS that hits native inputs
- `appendConfigFields` on `Fieldtype::class` so every field's settings break

## Allowed (on top of Statamic)

- `appendConfigFields` on **one** fieldtype, adding a setting, class untouched
- A **separate** small script, never a new `addon.js`
- YAML `default:` in fieldsets

Statamic default and fields are untouchable

This outranks every other rule in this addon. Same rule as ~/.cursor/rules/00-statamic-default-urorligt.mdc.

Do not change, replace, wrap, or hijack Statamic's normal field behaviour in the Control Panel. Display name, handle, instructions, defaults, integers, text, replicator, grid, bard — they keep working as Statamic ships them.

Only build on top. Changing Statamic default is allowed only when the user explicitly asks for that change in this message.

Forbidden

  • Subclass + ::register() on an existing handle (iconify, replicator, text, …)
  • Wrap/replace a field's Vue component
  • npm run cp:build here or on the site when it rebuilds addon.js — that breaks field settings
  • Overwrite public/vendor/app/ or public/vendor/statamic-addon/
  • Change DefaultSetsFieldtype.js (bundled in addon-DmXwhlR7.js)
  • CSS that hits native inputs
  • appendConfigFields on Fieldtype::class so every field's settings break

Allowed (on top of Statamic)

  • appendConfigFields on one fieldtype, adding a setting, class untouched
  • A separate small script, never a new addon.js
  • YAML default: in fieldsets
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
3mdikram/worldmoneywords
snowsoft/config
itmosoft/laravel-subscriptions
larva/laravel-ai-qwen
diephp/sequences
users-au/socialite-provider
twidpay/twid-logger
mrnewport/laravel-plaid
mrnewport/laravel-repo
mrnewport/laravel-docsign
mrnewport/laravel-stow
mrnewport/laravel-flow
mrnewport/laravel-priceable
mrnewport/laravel-nestedterms
fredmeng/laravel-apidoc-generator
itstructure/laravel-multilingual-tools
pdustdar/elasticsearch
markupai/php-sdk
rlacerda83/lumem-microservice-shipment
uni-method/symfony-lib