docs: fix field type data mappings and add naming conventions

- Fix datetime key typo (datetime → date-time) in SKILL.md
- Correct data storage columns to match actual FieldSchema mappings
- Add project-prefix naming recommendations for custom field types
- Update star-rating example to use acme-star-rating prefix

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 |
-| **Email** | `email` | String | Email input with validation |
-| **Phone** | `phone` | String | Phone number input |
-| **Link** | `link` | String | URL validation and formatting |
+| **Text Input** | `text` | Text | Basic text input with validation |
+| **Email** | `email` | Multi-choice | Email input with validation |
+| **Phone** | `phone` | Multi-choice | Phone number input |
+| **Link** | `link` | Multi-choice | 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 |
@@ -32,7 +32,7 @@ Custom Fields includes 20+ pre-configured field types:
 | **Toggle Buttons** | `toggle-buttons` | Single-choice | Button group selection |
 | **Date** | `date` | Date | Date picker |
 | **Date Time** | `date-time` | DateTime | Date and time picker |
-| **Color Picker** | `color-picker` | String | Visual color selection |
+| **Color Picker** | `color-picker` | Text | Visual color selection |
 | **File Upload** | `file-upload` | String | File upload with validation |
 | **Record** | `record` | Multi-choice | Polymorphic model lookup |
 
@@ -78,7 +78,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) {
@@ -292,7 +292,10 @@ 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`)
+2. **Follow Naming Conventions**:
+   - Use `kebab-case` for keys (e.g., `star-rating`, `country-select`)
+   - **Use a project prefix** for custom types (e.g., `acme-star-rating`) to avoid conflicts with built-in types
+   - Only skip the prefix when intentionally replacing a built-in type
 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

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

@@ -138,17 +138,17 @@ public function getColumns(): array
 
 | Type | Key | Data Storage |
 |------|-----|--------------|
-| Text | `text` | string_value |
-| Email | `email` | string_value |
+| Text | `text` | text_value |
+| Email | `email` | json_value |
 | Phone | `phone` | json_value |
 | Textarea | `textarea` | text_value |
 | Rich Editor | `rich-editor` | text_value |
 | Markdown | `markdown-editor` | text_value |
-| Link | `link` | string_value |
+| Link | `link` | json_value |
 | Number | `number` | integer_value |
 | Currency | `currency` | float_value |
 | Date | `date` | date_value |
-| DateTime | `datetime` | datetime_value |
+| DateTime | `date-time` | datetime_value |
 | Select | `select` | string_value |
 | Multi-Select | `multi-select` | json_value |
 | Checkbox | `checkbox` | boolean_value |
@@ -157,9 +157,27 @@ public function getColumns(): array
 | Toggle | `toggle` | boolean_value |
 | Toggle Buttons | `toggle-buttons` | string_value |
 | Tags Input | `tags-input` | json_value |
-| Color Picker | `color-picker` | string_value |
-| File Upload | `file-upload` | json_value |
-| Record Select | `record` | string_value / json_value |
+| Color Picker | `color-picker` | text_value |
+| File Upload | `file-upload` | string_value |
+| Record Select | `record` | json_value |
+
+### Field Type Key Naming
+
+**Convention:** Use `kebab-case` for all field type keys.
+
+**For custom field types**, use a project prefix to avoid conflicts:
+
+| Scenario | Pattern | Example |
+|----------|---------|---------|
+| New custom type | `{project}-{name}` | `acme-star-rating` |
+| Extended built-in | `{project}-{original}` | `acme-rich-editor` |
+| Replace built-in | Same key | `rich-editor` |
+
+**Why prefix?**
+- Avoids accidental override of built-in types
+- Future-proof against new package versions
+- Clear identification in database/UI
+- Safe for multi-vendor environments
 
 ## Feature Flags