harnios-mcp: Skill for Claude Code

Purpose

frontend/.env.example documents every variable the Next.js app reads (S3/storage connection, OAuth owner credential, MCP bootstrap path, OS_NAME branding, etc.). Next.js loads config from any file starting with .env (.env, .env.local, .env.development, .env.development.local, .env.production.local, etc.) — there is no single fixed filename, and several such files can coexist for different purposes (e.g. one per environment/deployment). frontend/.gitignore covers all of them with a blanket .env* pattern (except .env.example itself, which is intentionally tracked as the template) — none of them are ever committed.

This skill exists so any one of these files can be created or updated without the user having to hand-copy and decode .env.example themselves.

Steps

1. Determine the target filename — never assume .env.local. List every frontend/.env* file that currently exists (excluding .env.example). Ask the user (AskUserQuestion) which file this run targets:

   • Each existing .env* file found, offered as an option ("update <name>")
   • "Create a new one" — if chosen, ask for the filename (must start with .env); tell the user which Next.js env file it corresponds to if the name implies a specific load order (.env.local loads everywhere; .env.development/.env.production are environment-specific; the .local variants are per-machine overrides not meant to be shared)
   • If exactly one .env* file already exists, you may skip this question and confirm your assumption in one line instead of formally asking (e.g. "I'll update the existing .env.local") — only ask when there's a real choice (multiple existing files, or none yet)

2. Read frontend/.env.example and parse it into an ordered list of variables. For each variable, capture:

   • Its KEY
   • The full comment block immediately above it (this is the human-readable description — use it verbatim when asking the user, don't paraphrase it away)
   • Its example value, and whether that value is a usable default as-is (e.g. S3_REGION=us-east-1, S3_FORCE_PATH_STYLE=true) or a placeholder that must be replaced for anything beyond the exact local-MinIO setup this repo ships with (e.g. S3_ENDPOINT, S3_ACCESS_KEY_ID/S3_SECRET_ACCESS_KEY when not using the bundled local MinIO, OAUTH_OWNER_PASSWORD which ships empty on purpose)