go-authcrunch: Skill for Codex

Coding Directives

Use openapi-generation to evaluate and update the YAML HTTP contract after handler, wire-model, validator or configuration changes.

Overview

Apply these directives when editing or reviewing go-authcrunch code. Prefer small, package-local changes that preserve AuthCrunch's existing runtime shape: top-level authcrunch.Config and Server wire package-owned configs, constructors, validators, providers, stores, portals, gatekeepers, registries, and crypto key stores.

Do not import or use reflect in non-test code. Use typed APIs, explicit type switches, and generic helpers where needed. Reflection-based test helpers belong in _test.go files and must not become production dependencies.

Go changes must meet the testing requirements. scripts-and-automation owns Make targets, generated assets, and dependency commands; release-and-versioning owns version invariants. The root routes select those workflows when their tasks are in scope.

APIs are unversioned. Do not add version segments or suffixes to routes, API filenames, operation/schema names, or protocol identifiers. Keep this contract consistent across implementation, clients, OpenAPI and skills.

Keep Skills Current

Treat relevant repo-local skill maintenance as part of completing every code change. After updating implementation and tests, review the owning skills and their linked references and update affected guidance in the same task, before reporting completion. Do not wait for a separate documentation request.

Use skill-authoring to synchronize the relevant skills with implemented behavior, configuration, ownership, and validation changes, including corrected paths or examples after a refactor.

Implementation workflows

• Use authentication-portal-documents to maintain encrypted document storage, chunk transfers, recipient key envelopes, immutable account ownership and the external Documents React integration.