Configure engineering skills

[salasebas]

Summary

• document GitHub Issues as the repository issue tracker
• define the default triage label vocabulary
• configure RustAuth as a single-context domain with root-level context and ADR documentation
• add wayfinding and domain-document consumption guidance to AGENTS.md

Why

The engineering skills need repository-specific conventions for issue operations, triage labels, and domain documentation before they can operate consistently in RustAuth.

Impact

Agents can now discover the tracker workflow and shared domain-document layout from versioned repository documentation. This change does not alter Rust code or runtime behavior.

Validation

• git diff --check
• reviewed the staged four-file documentation diff
• Cargo checks skipped because this is documentation-only

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
rustauth-docs-site	Ignored		Jul 23, 2026 5:42am

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8dd05a473c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Specify the GitHub repository for issue commands

When skills run in this checkout, git remote -v and the local Git configuration contain no remotes, so gh cannot infer a repository; the issue and PR commands documented above omit --repo and will stop before reading or creating anything. Specify salasebas/rustauth with --repo, or document a required GH_REPO fallback.

Useful? React with 👍 / 👎.