Skip to content
cccskills
FreePublished on GitHub

nauthilus-api-contracts

Use for Nauthilus OpenAPI, generated management or IdP clients, route contract tests, gRPC protobuf generation, HTTP route registration, management API authentication, public discovery API, `server/openapi`, `server/router`, `server/grpcapi`, `server/grpcclient`, and API-boundary client work.

The English summary is being prepared. Showing the original description.

croessner/nauthilus
See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Nauthilus API Contracts

Expertise Lens

  • Work as a contract-first API and protocol-boundary engineer.
  • Treat OpenAPI specs, generated bindings, gRPC protobufs, route registration, and supported client wrappers as public compatibility surfaces.
  • Optimize for reproducible generation, route-contract truth, explicit authentication, and separation between generated DTOs and protocol-realistic flows.

Sources To Read

  • AGENTS.md
  • POLICY.md
  • server/openapi/client/README.md
  • server/openapi/openapi.yaml
  • server/openapi/idp.yaml
  • server/openapi/oapi-management-bindings.yaml
  • server/router/
  • server/grpcapi/
  • server/grpcclient/

Contract Rules

  • Keep generated code committed and generated through central Makefile/script workflows.
  • Use make generate-openapi-bindings and make generate-openapi-bindings-check.
  • Use make generate-grpc-proto for gRPC bindings.
  • Keep route contract tests aligned with the actual Gin route registration.
  • Keep management API backchannel auth explicit.
  • Keep IdP discovery API public surfaces separate from browser login, MFA, OIDC token exchange, SAML SSO/SLO, CBOR auth, header auth, and NGINX auth_http flows.
  • Do not replace protocol-realistic client/test behavior with generated clients when the generator cannot model the protocol safely.

Implementation Workflow

  1. Identify whether the change is public API, generated client boundary, route registration, or internal handler behavior.
  2. Update specs before generated artifacts when the public contract changes.
  3. Regenerate through Makefile/script targets.
  4. Update route-contract tests for intentional route additions or exclusions.
  5. Keep supported client wrappers explicit in server/openapi/client.

Validation

  • Run make generate-openapi-bindings-check when OpenAPI or generated clients are in scope.
  • Run focused route/OpenAPI/client tests with GOEXPERIMENT=runtimesecret.
  • Run GOEXPERIMENT=runtimesecret make test and git diff --check.
  • Run make guardrails before commit or pull request.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

nauthilus-auth-identity

Free

Use for Nauthilus authentication and identity-provider work touching OIDC, OAuth2, SAML, MFA, TOTP, WebAuthn, recovery codes, LDAP-backed identity, browser login and consent flows, token/session/flow state, `private_key_jwt`, introspection, discovery metadata, endpoint-specific client authentication, and security-sensitive auth tests.

The English summary is being prepared. Showing the original description.

croessner/nauthilus6Updated Oct 12, 2026

nauthilus-config-docs

Free

Use for Nauthilus configuration loading, config schema and defaults, Viper-backed config formats, config dump behavior, vim syntax generation, template validation, prompt guideline sync, documentation under README/IDP/server docs, config converters, and generated documentation or syntax artifacts.

The English summary is being prepared. Showing the original description.

croessner/nauthilus6Updated Oct 12, 2026

nauthilus-lua-policy

Free

Use for Nauthilus Lua plugins, Lua callback tests, policy compiler and registry work, Lua environment and subject sources, Lua actions, hooks, backend scripts, policy facts, obligation targets, `server/lualib`, `server/lua-plugins.d`, `server/policy`, and JSON fixtures under `testdata/lua`.

The English summary is being prepared. Showing the original description.

croessner/nauthilus6Updated Oct 12, 2026

nauthilus-plugin-api

Free

Use for Nauthilus native Go plugin API design or implementation, `pluginapi/v1`, plugin loader, plugin registry, plugin runtime, reload integration, plugin config, extension-point parity with Lua, capability-based host services, lifecycle semantics, and the working draft under `server/docs/go_plugin_api_working_draft.md`.

The English summary is being prepared. Showing the original description.

croessner/nauthilus6Updated Oct 12, 2026

nauthilus-redis-runtime

Free

Use for Nauthilus Redis client, Redis Cluster/Sentinel/topology behavior, Redis-backed token/session/flow/cache/bruteforce state, Lua Redis scripts, `NOSCRIPT` recovery, script upload/retry behavior, redismock tests, local cache coordination, and fail-closed runtime state changes.

The English summary is being prepared. Showing the original description.

croessner/nauthilus6Updated Oct 12, 2026

nauthilus-release-closeout

Free

Use for Nauthilus validation, guardrails, dependency patch refreshes, vendoring, generated-output checks, `make release-guardrails`, govulncheck-sensitive publishing, structured commits, branch/tag choreography, website-doc side effects, and final clean-state reporting.

The English summary is being prepared. Showing the original description.

croessner/nauthilus6Updated Oct 12, 2026

See all skills by croessner

Report a problem with this skill