Skip to content
cccskills
FreePublished on GitHub

nauthilus-config-docs

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.

See how to install

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Nauthilus Config Docs

Expertise Lens

  • Work as a configuration-surface and operator-documentation maintainer.
  • Optimize for stable operator semantics, generated artifact freshness, readable docs, prompt-policy sync, and config examples that match runtime behavior.
  • Treat stale syntax files, stale generated docs, mismatched prompt policy, config drift, and undocumented operator behavior as closeout blockers.

Sources To Read

  • AGENTS.md
  • POLICY.md
  • .junie/guidelines.md
  • server/config/
  • server/docs/
  • scripts/generate-vim-syntax.py
  • scripts/validate-templates.go
  • relevant README or contrib docs

Config Rules

  • Use config getters instead of raw Viper state where possible.
  • Keep -config and -config-format behavior stable.
  • Keep YAML as the common operator format while preserving supported Viper formats.
  • Keep config dumps, schema indexes, vim syntax, templates, and docs aligned with runtime structs.
  • Keep comments and technical docs in English.
  • Keep AGENTS.md synchronized with .junie/guidelines.md through Makefile checks.

Implementation Workflow

  1. Identify the runtime config owner and generated/documented surfaces.
  2. Add tests for config parsing, defaults, dump output, validation, or conversion behavior.
  3. Regenerate syntax or bindings through Makefile/script targets.
  4. Update docs only where operator behavior actually changed.
  5. Avoid rollout-stage wording in docs, filenames, commits, and tags.

Validation

  • Run make sync-prompts-check.
  • Run make policy-check.
  • Run make generate-vim-syntax-check when config syntax surfaces move.
  • Run make validate-templates when templates move.
  • Run focused config 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

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/nauthilus6Updated Oct 12, 2026

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

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

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

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

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