fix: correct field type data mappings in documentation

Fix incorrect data storage columns and data types in SKILL.md and
field-types.md to match actual 2.x codebase definitions.

Author: ManukMinasyan

docs/content/2.essentials/3.field-types.md

@@ -13,10 +13,10 @@ Custom Fields includes 20+ pre-configured field types:
 
 | Field Type | Key | Data Type | Description |
 |------------|-----|-----------|-------------|
-| **Text Input** | `text` | String | Basic text input with validation |
+| **Text Input** | `text` | Text | Basic text input with validation |
 | **Email** | `email` | String | Email input with validation |
 | **Phone** | `phone` | String | Phone number input |
-| **Link** | `link` | String | URL validation and formatting |
+| **Link** | `link` | Text | URL validation and formatting |
 | **Textarea** | `textarea` | Text | Multi-line text input |
 | **Rich Editor** | `rich-editor` | Text | WYSIWYG editor with formatting |
 | **Markdown Editor** | `markdown-editor` | Text | Markdown syntax with preview |
@@ -31,8 +31,8 @@ Custom Fields includes 20+ pre-configured field types:
 | **Toggle** | `toggle` | Boolean | Switch-style toggle |
 | **Toggle Buttons** | `toggle-buttons` | Single-choice | Button group selection |
 | **Date** | `date` | Date | Date picker |
-| **Date Time** | `datetime` | DateTime | Date and time picker |
-| **Color Picker** | `color-picker` | String | Visual color selection |
+| **Date Time** | `date-time` | DateTime | Date and time picker |
+| **Color Picker** | `color-picker` | Text | Visual color selection |
 | **File Upload** | `file-upload` | String | File upload with validation |
 
 ## Creating Custom Field Types
@@ -77,7 +77,7 @@ class StarRatingFieldType extends BaseFieldType
     public function configure(): FieldSchema
     {
         return FieldSchema::numeric()
-            ->key('star-rating')
+            ->key('acme-star-rating')
             ->label('Star Rating')
             ->icon('heroicon-o-star')
             ->formComponent(function (CustomField $customField) {
@@ -291,11 +291,12 @@ enum FieldDataType: string
 ## Best Practices
 
 1. **Use Existing Filament Components**: Build on Filament's components like `Select`, `TextInput`, etc.
-2. **Follow Naming Conventions**: Use kebab-case for keys (e.g., `star-rating`, `country-select`)
-3. **Choose the Right Data Type**: Select the data type that matches how your field's values should be stored
-4. **Use Closures for Flexibility**: For complex components, use closure-based definitions
-5. **Test Your Components**: Ensure your field type works in forms, tables, and infolists
-6. **Consider Validation**: Only allow validation rules that make sense for your field type
+2. **Follow Naming Conventions**: Use kebab-case for keys (e.g., `acme-star-rating`, `myapp-country-select`)
+3. **Prefix Keys with Project/Org Name**: Always prefix custom field type keys with your project or organization name to avoid conflicts with built-in types (e.g., `acme-priority` instead of `priority`)
+4. **Choose the Right Data Type**: Select the data type that matches how your field's values should be stored
+5. **Use Closures for Flexibility**: For complex components, use closure-based definitions
+6. **Test Your Components**: Ensure your field type works in forms, tables, and infolists
+7. **Consider Validation**: Only allow validation rules that make sense for your field type
 
 ## Field Type Priority
 

resources/boost/skills/custom-fields-development/SKILL.md

@@ -138,27 +138,36 @@ public function getColumns(): array
 
 | Type | Key | Data Storage |
 |------|-----|--------------|
-| Text | `text` | string_value |
+| Text | `text` | text_value |
 | Email | `email` | string_value |
 | Phone | `phone` | string_value |
 | Textarea | `textarea` | text_value |
 | Rich Editor | `rich-editor` | text_value |
 | Markdown | `markdown-editor` | text_value |
-| Link | `link` | string_value |
+| Link | `link` | text_value |
 | Number | `number` | integer_value |
 | Currency | `currency` | float_value |
 | Date | `date` | date_value |
-| DateTime | `datetime` | datetime_value |
-| Select | `select` | string_value |
+| DateTime | `date-time` | datetime_value |
+| Select | `select` | integer_value |
 | Multi-Select | `multi-select` | json_value |
 | Checkbox | `checkbox` | boolean_value |
 | Checkbox List | `checkbox-list` | json_value |
-| Radio | `radio` | string_value |
+| Radio | `radio` | integer_value |
 | Toggle | `toggle` | boolean_value |
-| Toggle Buttons | `toggle-buttons` | string_value |
+| Toggle Buttons | `toggle-buttons` | integer_value |
 | Tags Input | `tags-input` | json_value |
-| Color Picker | `color-picker` | string_value |
-| File Upload | `file-upload` | json_value |
+| Color Picker | `color-picker` | text_value |
+| File Upload | `file-upload` | string_value |
+
+### Field Type Key Naming
+
+When creating custom field types, prefix keys with your project/organization name to avoid conflicts:
+
+- Use `acme-star-rating` instead of `star-rating`
+- Use `myapp-priority` instead of `priority`
+
+This prevents collisions if built-in field types are added later with similar names.
 
 ## Feature Flags