Shep Kit:Fast Loop
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
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Shep Kit:Fast Loop when an AI agent needs a reusable SKILL.md workflow for this job: 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
When not to use it
Skip Shep Kit:Fast Loop when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/shep-kitfast-loop # Save SKILL.md to ~/.claude/skills/shep-kitfast-loop/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/shep-kitfast-loop/SKILL.md. For a shared project, commit the folder at .claude/skills/shep-kitfast-loop/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Shep Kit:Fast Loop skill for this task: Use Shep Kit:Fast Loop when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 62/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Fast Loop — Rapid Iteration Mode
Skip TDD, builds, and commits. Just edit code, let the dev server hot-reload, and iterate based on user feedback.
## What This Overrides
This skill **temporarily suspends** these CLAUDE.md mandates for the duration of the session:
- **TDD** — no tests required during fast-loop - **Spec-driven** — no spec required, user drives direction - **Storybook stories** — not required during iteration - **Commit format** — no commits until user says "done"
## Rules
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
## Flow
``` User describes change → Edit files → User checks dev server → Repeat ```
## Exit
When the user is satisfied, suggest:
```bash pnpm validate # lint + format + typecheck pnpm test:unit # catch regressions ```
Then offer `/shep-kit:commit-pr` or `/commit` to wrap up.
Intended uses
- Use Shep Kit:Fast Loop when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.