Stats
Actions
Tags
From design
Automatically process and add the most recent screenshot from src/images to the appropriate course materials. Analyzes the image content, determines the correct week and topic, moves the file, and adds properly sized markdown references. Invokable with /add-content-image or /add-image.
How this skill is triggered — by the user, by Claude, or both
Slash command
/design:add-content-imageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill automates the process of integrating new screenshots into course materials. It identifies the most recent image in `src/images/`, analyzes its content to determine relevance, moves it to the appropriate week folder, and adds properly formatted markdown references with optimized sizing.
This skill automates the process of integrating new screenshots into course materials. It identifies the most recent image in src/images/, analyzes its content to determine relevance, moves it to the appropriate week folder, and adds properly formatted markdown references with optimized sizing.
# Locate the newest image in src/images/
ls -lt src/images/ | head -2
Actions:
Read the image using the Read tool to visually understand:
Key Questions:
Course Structure:
Decision Process:
ai-code-review.md, cursor.md)Naming Convention:
{tool-name}-{feature-or-concept}.png
Examples:
coderabbit-review-example.png (CodeRabbit PR review)cursor-inline-editing.png (Cursor's inline edit feature)claude-code-planning-mode.png (Claude Code planning interface)github-copilot-suggestions.png (Copilot autocomplete)Guidelines:
# Move and rename image
mv "src/images/Screenshot YYYY-MM-DD at HH.MM.SS.png" \
content/week_X/images/{descriptive-name}.png
Ensure:
content/week_X/images/ directory existssrc/images/Default sizes based on content type:
Full-width examples (workflow diagrams, dashboards, comprehensive UIs):
No size specified = full content width
Large screenshots (tool interfaces, detailed examples):
<img src="images/filename.png" alt="Description" width="800">
800px width for detailed visibility while maintaining readability
Medium screenshots (specific features, code snippets with UI):
<img src="images/filename.png" alt="Description" width="600">
600px width for feature demonstrations
Small screenshots (UI elements, buttons, small dialogs):
<img src="images/filename.png" alt="Description" width="400">
400px width for focused UI elements
Sizing Guidelines:
Read the target markdown file and identify the optimal insertion point:
Insertion format:
For full-width or large images:
**Example: {Tool Name Feature}**:
*Caption explaining what the image shows and why it's relevant.*
For medium/small images:
**Example: {Tool Name Feature}**:
<img src="images/filename.png" alt="Descriptive Alt Text" width="600">
*Caption explaining what the image shows and why it's relevant.*
Caption Guidelines:
After adding the image reference:
npm run build
Verify:
Provide a summary to the user:
✓ Image added to Week X materials
**Image:** {descriptive-name}.png
**Location:** content/week_X/images/
**Added to:** content/week_X/{topic}.md (line XXX)
**Size:** {width}px (or full-width)
**Section:** "{Section Name}"
**Analysis:**
- **Depicts:** {what the screenshot shows}
- **Relevance:** {why it fits this topic}
You can view it at: output/week_X/{topic}.html
When analyzing the screenshot, systematically identify:
Tool Identification:
Feature/Concept:
Content Quality:
Educational Value:
1. Does this show a specific tool?
Yes → Which tool? → Find tool's dedicated section
No → Proceed to #2
2. Does this show a workflow or process?
Yes → Which week covers this process? → Find workflow section
No → Proceed to #3
3. Does this show a code review, testing, or quality concept?
Yes → Week 5 (AI Code Review, Team Collaboration, etc.)
No → Proceed to #4
4. Does this show agent/automation features?
Yes → Week 6 (Agent Skills, Workflows, etc.)
No → Proceed to #5
5. Does this show development environment setup?
Yes → Week 2 (Cursor, Claude Code, MCP)
No → Ask user for clarification
Consider these factors:
Information Density:
Readability Requirements:
Page Context:
Aspect Ratio:
Example: CodeRabbit PR review interface
Analysis:
ai-code-review.mdActions:
coderabbit-pr-review-interface.pngcontent/week_5/images/ai-code-review.mdExample: Cursor inline code editing
Analysis:
cursor.mdActions:
cursor-inline-editing.pngcontent/week_2/images/cursor.mdExample: Claude Code terminal output
Analysis:
claude-code.mdActions:
claude-code-terminal-output.pngcontent/week_2/images/If src/images/ is empty:
No images found in src/images/. Please add a screenshot to process.
If the image content is unclear or doesn't match course topics:
⚠️ Unable to automatically determine the best location for this image.
**Image analyzed:** {filename}
**Content observed:** {description of what was seen}
**Suggested action:** Please specify which week and topic this relates to:
- Week number (1-6)
- Topic/markdown file name
If sensitive information is visible:
❌ This screenshot contains potentially sensitive information:
- API keys, tokens, or credentials
- Personal information
- Internal URLs or infrastructure details
Please crop or redact the sensitive areas before adding to course materials.
The HTML builder automatically:
content/week_X/images/ to output/week_X/images/No additional configuration needed - just add markdown references and rebuild.
Supported formats:
Recommendations:
npx claudepluginhub amdmax/claude_marketplace --plugin designGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.