openapi-directory-mcp CLAUDE.md

Claude Assistant Guidelines for openapi-directory-mcp

🚨 HARD RULES - WRITTEN IN STONE

GIT POLICY

NEVER PERFORM GIT OPERATIONS UNLESS EXPLICITLY TOLD TO DO SO BY THE USER

• DO NOT use git commit under any circumstances without explicit user instruction
• DO NOT use git add to stage changes unless explicitly told to do so
• DO NOT assume when commits should be made or how files should be grouped
• MAKE CHANGES TO FILES, but let the user handle all git operations
• ALWAYS wait for explicit git instruction: "stage these files", "commit this", etc.
• This rule applies to ALL situations: bug fixes, linting fixes, feature additions, documentation updates

Why No Auto-Staging:

• User may want to use changelists
• User may want strategic commit groupings
• User may want to review changes before staging
• User may have specific staging workflows
• Staging is part of the user's approval process

Git Operations Allowed Without Permission:

• git status - checking repository status (for information only)
• git diff - viewing changes (for information only)
• git log - viewing commit history (for information only)

Git Operations FORBIDDEN Without Explicit Permission:

• git add - NEVER stage files without explicit instruction
• git commit - NEVER without explicit instruction
• git push - NEVER without explicit instruction
• git merge - NEVER without explicit instruction
• git rebase - NEVER without explicit instruction

Correct Workflow:

1. User asks me to fix issues
2. I make the file changes
3. I report what was changed
4. User decides how to stage and commit

🤝 COLLABORATION PRINCIPLES

BE A THINKING PARTNER, NOT JUST AN EXECUTOR

Always Raise Concerns:

• If I notice edge cases the user might not have considered
• If a request might conflict with established patterns or architecture
• If there are potential rollback/deployment/maintenance implications
• If I see a better approach or alternative solution
• If the implementation might mask underlying issues