preview-mode
From the author
Show-before-commit previews — after completing work, present what changed as a live dev-server URL or a concise plain-language description so the user can confirm or request changes with confidence. Use when delivering visible changes (pages, components, styling) to a running project.
Install
npx skills add wasintoh/toh-framework --skill preview-mode -a claude-code
Installs to .claude/skills/preview-mode/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 81
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- previewtobihagemann/turboStand up the project's live app and hand it to the user to try a change firsthand, then act on their verdict once they reply. Use when the user asks to "preview the change", "let me try it", "spin up the app so I can test it", "set it up so I can poke at it", or before finalizing a UI/UX change that needs human eyes.Testing★ 416
- verification-before-completionmvschwarz/openrigUse when about to claim work is complete, fixed, or passing, or before committing or creating PRsOther★ 8.1K
- dev-serverGoldziher/ai-rulezStarts the web app dev server. Use when the user wants to preview UI changes locally.Design★ 163
- frontendOyadotAI/oya-browserUse when building or changing anything in the frontend: a page, a component, a layout, styling, copy on screen. Produces distinctive, production-grade UI that fits this project's existing design, covers every state, is accessible, and is checked in a browser before it is called done.Design★ 351
- plan-modeCodeAlive-AI/ai-driven-developmentUse this skill when the user asks to plan, design, scope, estimate, or implement a feature, bug fix, refactor, migration, integration, API change, UI change, or other project modification. Enforces a planning gate before editing code — investigate project context, analyze the task, surface ambiguities, contradictions, risks, dependencies, and blockers, ask focused questions, produce an evidence-based step-by-step plan, and implement only after explicit user approval. Not for trivial one-line edits, pure questions about the codebase, or changes the user has already reviewed and approved for direct implementation.Planning★ 165
- git-workspace-reviewathola/claude-night-marketVerifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct.Engineering★ 343
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in