docs: add CLAUDE.md agent guidelines for node-oauth2-jwt-bearer#249
Draft
jd3vi1 wants to merge 1 commit into
Draft
docs: add CLAUDE.md agent guidelines for node-oauth2-jwt-bearer#249jd3vi1 wants to merge 1 commit into
jd3vi1 wants to merge 1 commit into
Conversation
Add AI-agent guidelines generated by the generating-claude-md skill: a lean root CLAUDE.md (single source of truth) covering the monorepo, a thin AGENTS.md that imports it for non-Claude tools, and six references/*.md offload files.
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
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
Adds AI-agent guidelines for node-oauth2-jwt-bearer — a lean, guardrail-first
CLAUDE.mdplus a thinAGENTS.mdthat points to it, generated by thegenerating-claude-mdskill and validated against the repo. This is a monorepo, so per the skill's current single-root-file behavior it ships one rootCLAUDE.mdcovering the repo and its packages.CLAUDE.md(151 lines) — persona, working principles, project overview/structure, three-tier Boundaries, Security, and one-line anchors intoreferences/.AGENTS.md— imports@./CLAUDE.mdso non-Claude tools (Codex CLI, Gemini CLI) share the same guidance.references/*.md— full detail offloaded on demand:commands,testing,code-style,git-workflow,pitfalls,docs-update.What detection surfaced (node-oauth2-jwt-bearer specific)
oauth2-bearer→access-token-jwt→express-oauth2-jwt-bearer) plusexamples; onlyexpress-oauth2-jwt-bearer(v1.9.1) is published. Structure section and root scripts (test/lint/buildrun--workspaces) reflect this.Auth0-Clientheader. Per the skill's telemetry rules (shape 4), the telemetry boundary is intentionally omitted, and Security says so explicitly.jose, an enforced algorithm allowlist (nonerejected), and DPoP proof validation (dpop-verifier.ts) → documented in Security, not the persona.jest.config.js, all packages) → surfaced as an Always-Do boundary and a pitfall; lowering it is Ask-First.moduleNameMapper+ ts-jestpaths(resolve tosrc/, no build needed) → captured in testing + pitfalls.tsc; the published package bundles with Rollup (rollup.config.mjs) → noted in commands + pitfalls..eslintrc(@typescript-eslintrecommended) + Prettier (singleQuote,printWidth: 80); RFC 6750 typed error hierarchy (InvalidTokenError,InsufficientScopeError, ...) as the error convention.README.md/EXAMPLES.md/examples/;CHANGELOG.mdand generateddocs/(TypeDoc) intentionally not tracked.Validation
Filesystem validation pass: every cited path, every
package.jsonscript / CI job, and everyreferences/*.mdpointer (6/6) verified to exist in the repo — no invented tooling.Generated by the
generating-claude-mdskill.