fix(nextjs): improve skill guidance for middleware composition#39
Merged
fix(nextjs): improve skill guidance for middleware composition#39
Conversation
The agent was choosing a server-side-only pattern instead of using AuthKitProvider. Strengthened Step 6 with CRITICAL marker, code example, and explicit "Do NOT skip" warning. Updated verification checklist with failure messaging.
Eval identified that nextjs/conflicting-middleware failed on first attempt because the skill lacked guidance for composing auth with existing middleware logic. Skill changes: - Add "Existing Middleware" section with authkit() composable pattern - Document handleAuthkitHeaders() for proper header routing - Show how to preserve custom logic (rate limiting, etc.) Grader changes: - Accept either authkitMiddleware OR authkit()+handleAuthkitHeaders - Both are valid SDK patterns for different use cases
This was referenced Feb 3, 2026
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
authkit()composable pattern when existing middleware is presentauthkitMiddlewareandauthkit()patternsWhy
Eval runs identified that
nextjs/conflicting-middlewarescenarios failed because:The SDK's
authkit()function +handleAuthkitHeaders()is designed for composition but wasn't documented in the skill.Notes
authkitMiddleware(simple) orauthkit()+handleAuthkitHeaders()(composition)