Update Cursor rule example (#885)

* update cursor rule

* update cursor rule

* formatting

* formatting

* update intro to rule example

* fix casing

Author: ethanpalm

.cursor/rules/writing-standards.mdc

@@ -428,7 +428,7 @@ description: "Concise description explaining page purpose and value"
 - Verify all code examples are syntactically correct and executable
 - Test all links to ensure they are functional and lead to relevant content
 - Validate Mintlify component syntax with all required properties
-- Confirm proper heading hierarchy with H2 for main sections, H3 for subsections
+- Confirm proper heading hierarchy with H2 for main sections, H3 for subsections. Do not use H1 (reserved for page title)
 - Ensure content flows logically from basic concepts to advanced topics
 - Check for consistency in terminology, formatting, and component usage
 - Include appropriate warnings for destructive or security-sensitive actions
@@ -483,4 +483,30 @@ description: "Concise description explaining page purpose and value"
 - Regularly review and update outdated information
 - Remove deprecated features and references
 - Update screenshots when UI changes occur
-- Maintain consistency across related documentation pages
+- Maintain consistency across related documentation pages
+
+## Request handling examples
+
+### When asked to "create a new page":
+1. First, determine the appropriate location in the file structure
+2. Create the file with proper frontmatter
+3. Structure content using appropriate Mintlify components
+4. Include relevant images and code examples
+
+### When asked to "improve existing content":
+1. Review current structure and identify gaps
+2. Suggest specific component improvements
+3. Add missing callouts or examples
+4. Ensure proper heading hierarchy
+
+## Component selection decision trees
+
+### For procedures:
+- Use <Steps> when: Sequential numbered instructions
+- Use <Tabs> when: Platform-specific alternatives
+- Use <AccordionGroup> when: Optional supplementary info
+
+### For code examples:
+- Use single ``` when: One language, simple example
+- Use <CodeGroup> when: Same concept in multiple languages
+- Use <RequestExample>/<ResponseExample> when: API documentation