different CLAUDE.md approach

Author: ethanpalm

.claude/CLAUDE.md

@@ -1,41 +1,46 @@
 # Mintlify documentation
 
+## Working relationship
+- You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
+- ALWAYS ask for clarification rather than making assumptions
+- NEVER lie, guess, or make up information
+
 ## Project context
-- Official documentation site for Mintlify platform
 - Format: MDX files with YAML frontmatter
 - Config: docs.json for navigation, theme, settings
-- Images: /images/ directory with light/dark variants
+- Components: Mintlify components
 
 ## Content strategy
-- Use MCP search before writing new content
+- Document just enough for user success - not too much, not too little
+- Prioritize accuracy and usability of information
+- Make content evergreen when possible
+- Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason
 - Check existing patterns for consistency
-- Cross-link to related information when it helps users accomplish tasks
-- Maintain examples that work for all Mintlify users
+- Start by making the smallest reasonable changes
 
-## Frontmatter requirements
+## Frontmatter requirements for pages
 - title: Clear, descriptive page title
 - description: Concise summary for SEO/navigation
-- icon: Appropriate icon matching content type
 
 ## Writing standards
 - Second-person voice ("you")
 - Prerequisites at start of procedural content
-- Test all code examples
+- Test all code examples before publishing
+- Match style and formatting of existing pages
 - Include both basic and advanced use cases
-- Add troubleshooting for complex features
-
-## Components (quick reference)
-- Callouts: `<Info>`, `<Warning>`, `<Tip>`, `<Note>`, `<Check>`, `<Danger>`
-- Layout: `<Frame>`, `<CodeGroup>`, `<Steps>`, `<Tabs>`
-
-## File standards
 - Language tags on all code blocks
 - Alt text on all images
 - Relative paths for internal links
-- Light/dark image variants where applicable
 
-## Do Not
+## Git workflow
+- NEVER use --no-verify when committing
+- Ask how to handle uncommitted changes before starting
+- Create a new branch when no clear branch exists for changes
+- Commit frequently throughout development
+- NEVER skip or disable pre-commit hooks
+
+## Do not
 - Skip frontmatter on any MDX file
 - Use absolute URLs for internal links
 - Include untested code examples
-- Break backward compatibility without migration notes
+- Make assumptions - always ask for clarification