From 1p-local-auth
This skill should be used when the user asks to "remove local auth setup", "teardown local OAuth", "remove dev auth", "clean up my local OAuth setup","undo local auth setup", "remove the dev:auth script", "delete the auth template", or wants to reverse a previous /setup-local-auth run. Cleanly removes all 1p-local-auth artifacts from the project without deleting the 1Password item.
How this skill is triggered — by the user, by Claude, or both
Slash command
/1p-local-auth:teardown-local-authThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reverse of `/setup-local-auth`. Removes local artifacts (template file, `dev:auth` script, `.gitignore` entry) from the project. Does **not** delete the 1Password item by default — credentials are preserved for potential re-setup.
Reverse of /setup-local-auth. Removes local artifacts (template file, dev:auth script, .gitignore entry) from the project. Does not delete the 1Password item by default — credentials are preserved for potential re-setup.
Before making changes, audit what the setup created:
ls .env.local.dev.tpl 2>/dev/null && echo "EXISTS: .env.local.dev.tpl" || echo "NOT FOUND: .env.local.dev.tpl"
grep '"dev:auth"' package.json && echo "EXISTS: dev:auth script" || echo "NOT FOUND: dev:auth script"
grep -F '!.env*.tpl' .gitignore 2>/dev/null && echo "EXISTS: .gitignore entry" || echo "NOT FOUND: .gitignore entry"
Also note the 1Password item name (from the template if it exists):
grep -oP 'op://[^/]+/[^/]+' .env.local.dev.tpl 2>/dev/null | head -1
# Example: op://App Dev/clarity-dev-auth
Present the teardown plan and confirm with user before proceeding.
.env.local.dev.tplrm .env.local.dev.tpl
Verify deletion:
ls .env.local.dev.tpl 2>/dev/null && echo "STILL EXISTS" || echo "Removed"
dev:auth Script from package.jsonRead package.json, find the dev:auth line, and remove it. Use the Edit tool — do not rewrite the entire file.
Ensure the JSON remains valid after removal (no trailing commas).
.gitignore Entry (Conditional)Check whether any other .tpl files remain in the project:
fd -e tpl
If .env.local.tpl or other template files still exist: do not remove the .gitignore entry — other templates still need it.
If no .tpl files remain: remove the !.env*.tpl line from .gitignore.
Do not automatically delete the {slug}-dev-auth item from 1Password.
Instead, provide the exact command for manual deletion if the user wants it:
The 1Password item was NOT deleted automatically.
To delete it manually:
op item delete clarity-dev-auth --vault "App Dev"
Recommendation: archive instead of delete — keeps credentials if you re-setup later:
1Password app → find "clarity-dev-auth" → Move to Archive
Ask: "Would you like me to delete the 1Password item now, or leave it?" Only delete if explicitly confirmed.
Teardown complete
Removed: .env.local.dev.tpl
Removed: dev:auth script from package.json
Skipped: .gitignore entry (.env.local.tpl still present)
Preserved: 1Password item "clarity-dev-auth" in App Dev
To delete the 1Password item:
op item delete clarity-dev-auth --vault "App Dev"
To re-run setup in future:
/setup-local-auth
If the user only wants to remove specific artifacts (e.g., keep the 1Password item and template but remove the dev:auth script), handle only the requested subset. Confirm which parts to remove before acting.
npx claudepluginhub aventerica89/jb-claude-plugins --plugin 1p-local-authRemoves files installed by /optimus:init and /optimus:permissions. Classifies files as unmodified, likely generated, or user-modified; asks before deleting; preserves tests and git-tracked files.
Cleanly deletes a Hypervibe project and all of its cloud infrastructure - Vercel, Neon, Cloudflare R2 (global + EU), Workers, DNS, db-backup, scheduled crons on the shared worker, Stripe webhook, Render services, OAuth clients, Upstash, etc. First, it displays a BIG warning and asks for a double confirmation (irreversible action). It then performs a COMPLETE inventory, also scanning environment variables to detect third-party services outside the hypervibe stack that might be connected (OpenAI, Mapbox, Sentry, etc.). At the end, it gives the user the paths (not the commands) of the folders to delete via Windows Explorer. Use when the user says "delete project X", "completely clean up X", "/delete-project X", "clean up project X", or wants to decommission a project.
Safely remove an entire feature and every dead reference it leaves behind — not just the folder you point at, but the sibling folders in other architecture layers, the imports/registries/routes/i18n keys that point to it, and any newly-orphaned code. Verifies the quality gate stays 100% green and writes a Markdown removal report. Use when deleting a feature, screen, module, or directory and you need it gone WITHOUT leaving dead files or dead code. Triggers on /feature-purge <path>, "remove this feature", "delete this folder safely", "apaga essa feature sem deixar código morto", "limpa essa screen e as camadas".