Reorganize Developer MCP best practices documentation

- Update SUMMARY.md to reflect new best practices structure
- Move best-practice.md content into organized subdirectory
- Improve documentation navigation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: Phil Whittaker

16/umbraco-cms/SUMMARY.md

@@ -367,11 +367,12 @@
     * [Claude Code](reference/developer-mcp/host-setup/claude-code.md)
     * [Cursor](reference/developer-mcp/host-setup/cursor.md)
     * [GitHub Copilot](reference/developer-mcp/host-setup/github-copilot.md)
+  * [Best Practice](reference/developer-mcp/best-practice/README.md)
+    * [Example Instruction File](reference/developer-mcp/best-practice/example-instructions.md)    
   * [Configuration](reference/developer-mcp/configuration.md)
   * [Available Tools](reference/developer-mcp/available-tools.md)
   * [Excluded Tools](reference/developer-mcp/excluded-tools.md)
   * [Use Cases and Scenarios](reference/developer-mcp/scenarios.md)
-  * [Best Practice](reference/developer-mcp/best-practice.md)
 * [API versioning and OpenAPI](reference/api-versioning-and-openapi.md)
 * [Searching](reference/searching/README.md)
   * [Examine](reference/searching/examine/README.md)

16/umbraco-cms/reference/developer-mcp/best-practice.md renamed to 16/umbraco-cms/reference/developer-mcp/best-practice/README.md

@@ -89,6 +89,8 @@ In some cases, it’s helpful to include a rules or instruction file that explai
 
 This helps the LLM reason more effectively about how to use the Developer MCP Server — especially when multiple tools are involved.
 
+View an example [instruction file](./example-instructions.md).
+
 ## Crafting Good Prompts
 
 While the Developer MCP Server provides structured access to tools, your results still depend heavily on **how well you prompt the model**. A good prompt sets clear intent, scope, and expectations — and helps the LLM make the most of the tools available to it.

16/umbraco-cms/reference/developer-mcp/best-practice/example-instructions.md

@@ -0,0 +1,51 @@
+---
+description: Get the most out of the Umbraco CMS developer MCP server
+---
+
+# Example instructions file
+
+Created by [Tom Madden](https://github.com/TwoMoreThings)
+
+# Umbraco Development Guidelines (v16.2.0)
+
+## Tool Usage
+
+- Use Context7 to retrieve Umbraco v16.2.0 documentation
+- Use the Umbraco MCP tool for ALL Umbraco interactions - make multiple calls as needed, never try to optimize with bulk operations
+- Use create-media MCP tool for media items, referencing files in wwwroot/media/my-folder
+
+## Content Structure
+
+- Always use Block List over Block Grid for composable pages
+- All navigable content pages must be nested under the Home page
+- All Content Type properties must belong to either a tab or a group
+
+## Block List Configuration
+
+- Items require a contentKey in UUID/GUID format
+    - Define labels using the Umbraco Flavored Markdown format, e.g. {umbValue: propertyAlias} (NOT {{$propertyAlias}})
+
+## Templates & Content Types
+
+- For web page content types (non-element types):
+    - Create corresponding template via Management API first
+    - Assign template to content type
+    - Set as default template
+
+## Data Types
+
+- Save new Data Types in 'Custom Data Types' folder
+- Use 'Rich Text Editor [Tiptap]' for formatted text content
+- Use Link Picker instead of multiple TextString properties for links
+
+## File Handling
+
+- Never modify file metadata/dates (preserves Git change tracking)
+- Add static assets to wwwroot subdirectories
+- When downloading images, exclude favicon.png and apple-icon.png
+- Look for CSS/inline style images, not just src attributes
+
+## Models & Publishing
+
+- STOP and prompt user to generate models and restart site (never generate manually)
+- Verify the node Layout is set correctly when saving/publishing pages