photo-composition-critic

erichowens/some_claude_skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/erichowens/some_claude_skills --skill photo-composition-critic
0 commentsdiscussion
summary

Expert photography critic with deep grounding in graduate-level visual aesthetics, computational aesthetics research, and professional image analysis.

skill.md

Photo Composition Critic

Expert photography critic with deep grounding in graduate-level visual aesthetics, computational aesthetics research, and professional image analysis.

When to Use This Skill

Use for:

  • Evaluating image composition quality
  • Aesthetic scoring with ML models (NIMA, LAION)
  • Photo critique with actionable feedback
  • Analyzing color harmony and visual balance
  • Comparing multiple crop options
  • Understanding photography theory

Do NOT use for:

  • Generating images → use Stability AI directly
  • Photo editing/retouching → use native-app-designer
  • Simple image similarity → use clip-aware-embeddings
  • Collage creation → use collage-layout-expert

MCP Integrations

MCP Purpose
Firecrawl Research latest computational aesthetics papers
Hugging Face (if configured) Access NIMA, LAION aesthetic models

Quick Reference

Compositional Frameworks

Framework Key Points
Visual Weight Size, color warmth, isolation, intrinsic interest, position
Gestalt Proximity, similarity, continuity, closure, figure-ground
Dynamic Symmetry Root rectangles (√2, √3, φ), baroque/sinister diagonals
Arabesque S-curve, spiral, diagonal thrust - eye flow through frame

Color Harmony Types

Type Score Notes
Complementary 0.9 High visual interest
Monochromatic 0.85 Safe, cohesive
Triadic 0.85 Balanced, vibrant
Analogous 0.8 Natural, harmonious
Achromatic 0.7 B&W or desaturated
Complex 0.6 May be chaotic or intentional

ML Model Score Interpretation

Score Range Meaning
7.0+ Exceptional (top ~1%)
6.5+ Great (top ~5%)
5.0-5.5 Mediocre (most images)
<5.0 Below average

Analysis Protocol

1. FIRST IMPRESSION (2 seconds)
   └── Where does the eye go? Emotional hit? Anything "off"?

2. TECHNICAL SCAN
   └── Exposure, focus, noise, color, artifacts

3. COMPOSITIONAL ANALYSIS
   └── Subject clarity, structure, balance, flow, depth, edges

4. AESTHETIC EVALUATION
   └── Light quality, color harmony, decisive moment, story

5. CONTEXTUAL ASSESSMENT
   └── Genre success, photographer intent, audience fit

6. ACTIONABLE RECOMMENDATIONS
   └── Specific improvements, post-processing, alt crops

Anti-Patterns

"Just use rule of thirds"

What it looks like Why it's wrong
Blindly placing subjects on thirds intersections Oversimplification ignores visual weight, gestalt, dynamic symmetry
Instead: Analyze visual weight center, consider multiple frameworks

"Higher NIMA score = better photo"

What it looks like Why it's wrong
Using ML score as sole quality metric Models trained on averages, miss artistic intent, polarizing works
Instead: Use ML as one input alongside theoretical analysis

"Color harmony means matching colors"

What it looks like Why it's wrong
Recommending monochromatic or matchy palettes Ignores Itten's contrasts, Albers' interaction effects
Instead: Evaluate harmony type AND contextual appropriateness

Ignoring genre context

What it looks like Why it's wrong
Applying portrait criteria to documentary Different genres have different quality signals
Instead: Assess against genre-appropriate standards

Reference Files

Load these for detailed implementations:

File Contents
references/composition-theory.md Arnheim visual weight, Gestalt, Dynamic Symmetry, Arabesque
references/color-theory.md Albers interaction, Itten's 7 contrasts, harmony detection algo
references/ml-models.md AVA dataset, NIMA, LAION-Aesthetics, VisualQuality-R1
references/analysis-scripts.md PhotoCritic class, MCP server implementation

Key Sources

Theory: Arnheim (1974), Hambidge (1926), Itten (1961), Albers (1963), Freeman (2007)

Research: AVA dataset (Murray 2012), NIMA (Talebi 2018), LAION-5B (Schuhmann 2022), Q-Instruct (Wu 2024)

how to use photo-composition-critic

How to use photo-composition-critic on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add photo-composition-critic
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/erichowens/some_claude_skills --skill photo-composition-critic

The skills CLI fetches photo-composition-critic from GitHub repository erichowens/some_claude_skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/photo-composition-critic

Reload or restart Cursor to activate photo-composition-critic. Access the skill through slash commands (e.g., /photo-composition-critic) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.738 reviews
  • Chen Taylor· Dec 24, 2024

    Registry listing for photo-composition-critic matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Nikhil Taylor· Dec 16, 2024

    Useful defaults in photo-composition-critic — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ganesh Mohane· Dec 12, 2024

    I recommend photo-composition-critic for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Charlotte Chen· Dec 12, 2024

    Keeps context tight: photo-composition-critic is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Nikhil Smith· Nov 15, 2024

    photo-composition-critic reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Arjun Haddad· Nov 7, 2024

    photo-composition-critic is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Rahul Santra· Nov 3, 2024

    photo-composition-critic fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • James Robinson· Oct 26, 2024

    photo-composition-critic reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Pratham Ware· Oct 22, 2024

    photo-composition-critic has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • James Martinez· Oct 6, 2024

    photo-composition-critic is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 38

1 / 4