Minimal ceremony implementation for small tasks and quick fixes. Use when task is simple, greenfield, or clearly defined. 5-step process: Understand → Find → Fix → Verify → Commit. Invoked via /popkit:dev with orchestrator routing to simple tasks.
/plugin marketplace add jrc1883/popkit-claude/plugin install popkit@popkit-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Minimal ceremony implementation for small, well-defined tasks.
Orchestrator routes here when:
Explicitly invoked via:
/popkit:dev "add loading spinner"
/popkit:dev "fix timezone bug"
/popkit:dev --mode quick "complex task" # Force quick even if complex
Goal: Quick context gathering
1. Read the task description
2. Check for existing files mentioned (if any)
3. Identify: What needs to be built/fixed?
4. Note: No deep exploration, just surface-level context
Example:
Task: "Create bouncing balls animation"
Context:
- Files: index.html, balls.js (starter files)
- Need: Canvas animation with physics
- Scope: Single feature, clear requirements
Goal: Locate relevant code (if modifying existing code)
If modifying existing code:
1. Use Grep to find relevant functions/components
2. Use Read to examine key files
3. Identify: Where does the change go?
If greenfield:
1. Identify: What files need to be created?
2. Check: Any dependencies needed?
Example (existing code):
Task: "Fix timezone bug in user profiles"
Found:
- src/utils/formatDate.ts:45 - formatDate function
- src/components/UserProfile.tsx:23 - calls formatDate
Example (greenfield):
Task: "Create bouncing balls animation"
Files needed:
- balls.js (implement Ball class, physics, animation)
- index.html (already exists, may need updates)
Goal: Make the change
1. Write or Edit the files
2. Keep it simple and focused
3. Follow existing patterns (if modifying)
4. Add minimal comments (only where needed)
Guidelines:
Goal: Quick validation
1. Check: Does it compile/run? (if applicable)
2. Check: Does it meet requirements?
3. Run tests if they exist
4. Quick manual verification if needed
Example:
✓ JavaScript syntax valid (node --check)
✓ All 5 balls render
✓ Physics simulation works
✓ Animation is smooth
Goal: Offer to save work
Use AskUserQuestion tool with:
- question: "Quick mode complete. Commit these changes?"
- header: "Commit"
- options:
1. label: "Yes, commit"
description: "Create commit with descriptive message"
2. label: "No, keep working"
description: "Continue without committing"
- multiSelect: false
If user selects "Yes, commit":
git add [changed files]
git commit -m "feat: [concise description]
[Details if needed]
🤖 Generated with Claude Code via /popkit:dev quick
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>"
After commit (or if user skips):
Use AskUserQuestion tool with:
- question: "What would you like to do next?"
- header: "Next Action"
- options:
1. label: "Done for now"
description: "Exit and save session"
2. label: "Another quick task"
description: "Run /popkit:dev quick again"
3. label: "Review code"
description: "Invoke code-reviewer agent"
- multiSelect: false
When POPKIT_BENCHMARK_MODE environment variable is set:
Auto-approve prompts:
Skip GitHub operations:
Use benchmark responses:
POPKIT_BENCHMARK_RESPONSES file[QUICK MODE] Creating bouncing balls animation
Step 1: Understand
- Task: Canvas animation with 5 balls, physics, collisions
- Files: balls.js (implement), index.html (starter)
- Scope: Single feature, greenfield
Step 2: Find
- balls.js: Empty starter (// TODO comment)
- index.html: Canvas element ready
Step 3: Fix
Writing balls.js:
- Ball class with position, velocity, mass
- Gravity and damping physics
- Wall collision detection
- Ball-to-ball collision
- Animation loop with requestAnimationFrame
Step 4: Verify
✓ JavaScript syntax valid
✓ 5 balls created with random colors/sizes
✓ Physics simulation working
✓ Smooth 60fps animation
Step 5: Complete
Quick mode finished!
Files changed: balls.js, index.html
Lines added: 135
If task is too complex for quick mode:
⚠️ This task may be too complex for quick mode.
Detected complexity indicators:
- Multiple architectural decisions needed
- Requires exploration of large codebase
- Unclear requirements
Recommend:
/popkit:dev --mode full "[task]" # Use full 7-phase workflow
/popkit:dev brainstorm "[task]" # Clarify requirements first
If stuck or blocked:
⚠️ Quick mode blocked: [reason]
Options:
1. Switch to full mode for deeper analysis
2. Ask user for clarification
3. Report what's blocking and exit
/popkit:dev "create password strength meter"
[QUICK MODE] Creating password strength meter
Step 1: Understand
- Component: Password strength indicator
- Visual: Progress bar with color coding
- Logic: Check length, characters, common passwords
Step 2: Find
- Create: src/components/PasswordStrength.tsx
- Pattern: Follow existing component structure
Step 3: Fix
[Creates component with strength calculation logic]
Step 4: Verify
✓ TypeScript compiles
✓ Weak password → red
✓ Medium password → yellow
✓ Strong password → green
Commit? [Yes/No]
/popkit:dev "fix timezone bug in date display"
[QUICK MODE] Fixing timezone bug
Step 1: Understand
- Issue: Dates showing in UTC instead of user timezone
- Impact: User profile, post timestamps
Step 2: Find
Found: src/utils/formatDate.ts:45
- formatDate(date) - missing timezone parameter
Step 3: Fix
Updated formatDate to use user.timezone:
- formatDate(date, user.timezone)
- Update all call sites (3 files)
Step 4: Verify
✓ Displays correct timezone
✓ Existing tests pass
Commit? [Yes/No]
The orchestrator (agent-orchestrator.py) routes to quick mode when:
analysis = {
'intent': 'build',
'complexity': 'simple', # < 50 words
'domains': ['frontend'],
'suggested_agents': [] # No specific agents needed
}
# Routes to: pop-dev-quick skill
Quick mode is fast but maintains quality:
✓ Syntax validation (if applicable) ✓ Basic functionality testing ✓ Requirements check ✗ Deep code review (use full mode for this) ✗ Comprehensive test coverage (use full mode for this) ✗ Architecture validation (use full mode for this)
Quick mode: Get it done, get it working, get it committed.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.