architecture-reviewer
Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean…
Use when the user wants rapid implementation iteration without tests, builds, or commits. Triggers include "fast loop", "fast iteration", "just code", "no tests", "iterate quickly", or when the user says they have a dev server running and want to check results manually. Part of
$ npx -y skills add shep-ai/shep --skill shep-kit-fast-loop --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/shep-kit-fast-loopContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user wants rapid implementation iteration without tests, builds, or commits. Triggers include "fast loop", "fast iteration", "just code", "no tests", "iterate quickly", or when the user says they have a dev server running and want to check results manually. Part of
name: shep-kit:fast-loop description: Use when the user wants rapid implementation iteration without tests, builds, or commits. Triggers include "fast loop", "fast iteration", "just code", "no tests", "iterate quickly", or when the user says they have a dev server running and want to check results manually. Part of the Shep autonomous SDLC platform — https://shep.bot metadata: version: '1.0.0' author: Shep AI (https://shep.bot) homepage: https://shep.bot repository: https://github.com/shep-ai/shep
Skip TDD, builds, and commits. Just edit code, let the dev server hot-reload, and iterate based on user feedback.
This skill **temporarily suspends** these CLAUDE.md mandates for the duration of the session:
1. **Edit code only** — no `pnpm test`, no `pnpm build`, no `git commit` 2. **Small, focused changes** — one thing at a time so the user can verify each step 3. **Trust the dev server** — assume hot-reload picks up changes (Next.js, Vite, etc.) 4. **Wait for user feedback** — after each change, pause and let the user check the result 5. **No over-engineering** — do exactly what the user asks, nothing more 6. **When user says "done"** — remind them to run `pnpm validate` and tests before committing
User describes change → Edit files → User checks dev server → Repeat
When the user is satisfied, suggest:
pnpm validate # lint + format + typecheck pnpm test:unit # catch regressions
Then offer `/shep-kit:commit-pr` or `/commit` to wrap up.
Ship features 10x faster. Built In Auto: Memory, K8S Agent & Security (SDD+SDLC) . 😇
Repo: shep-ai/shep
Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean…
Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions. Use when users ask to "cross-validate",…
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams…
React Flow (@xyflow/react) for workflow visualization with custom nodes and edges. Use when building graph visualizations, creating custom workflow nodes,…
Provides complete shadcn/ui component library patterns including installation, configuration, and implementation of accessible React components. Use when…
Use when ready to commit, push, and create a PR with CI verification. Triggers include "commit and pr", "push pr", "create pr", "ship it", or when…