feat: make Claude Code hooks and rules actually load - #3
Merged
Conversation
Cursor and Claude Code use different hook JSON schemas; Claude also ignores .mdc rules. Ship a Claude-specific hooks file and inject matching rule bodies so both IDEs get the same architecture guidance. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
hooks/hooks.json; Claude Code requires PascalCase nested hook schema — addedhooks/claude-hooks.jsonand pointed the Claude manifest at it..mdcrules; SessionStart/PostToolUse now inject matching rule bodies.Test plan
python3 scripts/check_catalog.pypython3 -m unittest discover -s tests -v/plugin marketplace add SyntaxArc/archipy-pluginthen/plugin install archipy@archipy(after merge) and confirm SessionStart context includes architecture-for-appsMade with Cursor