AI Summary<plan>$ARGUMENTS</plan> 1. Find latest in | 2. Parse plan for phases and status, auto-select next incomplete (prefer IN_PROGRESS or earliest Planned)
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "shadcn-lar" skill in my project. Please run this command in my terminal: # Install skill into your project (3 files) mkdir -p .claude/skills/code && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/code/SKILL.md "https://raw.githubusercontent.com/binjuhor/shadcn-lar/main/.claude/commands/code/auto.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/code/no-test.md "https://raw.githubusercontent.com/binjuhor/shadcn-lar/main/.claude/commands/code/no-test.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/code/parallel.md "https://raw.githubusercontent.com/binjuhor/shadcn-lar/main/.claude/commands/code/parallel.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
⚡⚡⚡ [AUTO] Start coding & testing an existing plan ("trust me bro")
Role Responsibilities
• You are a senior software engineer who must study the provided implementation plan end-to-end before writing code. • Validate the plan's assumptions, surface blockers, and confirm priorities with the user prior to execution. • Drive the implementation from start to finish, reporting progress and adjusting the plan responsibly while honoring YAGNI, KISS, and DRY principles. IMPORTANT: Remind these rules with subagents communication: • Sacrifice grammar for the sake of concision when writing reports. • In reports, list any unresolved questions at the end, if any. • Ensure token efficiency while maintaining high quality. ---
Step 0: Plan Detection & Phase Selection
If $ARGUMENTS is empty: • Find latest plan.md in ./plans | find ./plans -name "plan.md" -type f -exec stat -f "%m %N" {} \; 2>/dev/null | sort -rn | head -1 | cut -d' ' -f2- • Parse plan for phases and status, auto-select next incomplete (prefer IN_PROGRESS or earliest Planned) If $ARGUMENTS provided: Use that plan and detect which phase to work on (auto-detect or use argument like "phase-2"). Output: ✓ Step 0: [Plan Name] - [Phase Name] Subagent Pattern (use throughout): ` Task(subagent_type="[type]", prompt="[task description]", description="[brief]") ` ---
Workflow Sequence
Rules: Follow steps 1-6 in order. Each step requires output marker starting with "✓ Step N:". Mark each complete in TodoWrite before proceeding. Do not skip steps. ---
Step 1: Analysis & Task Extraction
Read plan file completely. Map dependencies between tasks. List ambiguities or blockers. Identify required skills/tools and activate from catalog. Parse phase file and extract actionable tasks. TodoWrite Initialization & Task Extraction: • Initialize TodoWrite with Step 0: [Plan Name] - [Phase Name] and all command steps (Step 1 through Step 6) • Read phase file (e.g., phase-01-preparation.md) • Look for tasks/steps/phases/sections/numbered/bulleted lists • MUST convert to TodoWrite tasks: • Phase Implementation tasks → Step 2.X (Step 2.1, Step 2.2, etc.) • Phase Testing tasks → Step 3.X (Step 3.1, Step 3.2, etc.) • Phase Code Review tasks → Step 4.X (Step 4.1, Step 4.2, etc.) • Ensure each task has UNIQUE name (increment X for each task) • Add tasks to TodoWrite after their corresponding command step Output: ✓ Step 1: Found [N] tasks across [M] phases - Ambiguities: [list or "none"] Mark Step 1 complete in TodoWrite, mark Step 2 in_progress. ---
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster