agentleFS
chuang44-tiffchuang44-tiff/optivibe-mcp/.claude/skills/design-review/SKILL.md

design-review

Skill19 starsChanged 22 days agoApache-2.0View on GitHub

Use when the user asks to review, assess, or check a lens design against a spec. Also use after optimization to evaluate results. Triggers on "how does this look", "check the design", "review", "evaluate".

167 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use team-level, team-audio and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 13 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 14 projects that use this

  • lilangMaxSkill

    asset-spec

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.

    Also in 11 projects that use this

  • lilangMaxSkill

    create-control-manifest

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).

    Also in 11 projects that use this

  • julianoczkowskiSkill

    brief-to-tasks

    Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".

    Also in 7 projects that use this

  • +4 more from lilangMax
  • +3 more from CoralGame

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 139 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After loading a design ("how does this look?")

    line 17
  2. Distinctive:

    After optimization ("did it improve?")

    line 18
  3. Distinctive:

    Before saving ("is this worth keeping?")

    line 19
  4. Distinctive:

    When the user asks to "review", "check", "assess", or "evaluate"

    line 20
  5. Very specific:

    NOT for: comparing multiple designs (use /design-compare)

    line 21
  6. Distinctive:

    If the user provided a spec (EFL, F-number, max spot size, MTF target, field angles, wavelength band), use those.

    line 27
  7. Distinctive:

    If the user gave a *partial* spec — first-order targets but no image-quality bands, say — do not silently invent the missing ones.

    line 31
  8. Distinctive:

    Run steps 1-2 first (fast prescription reads), then 3-5 (heavier analyses).

    line 47
  9. Very specific:

    Keep every section. If a section has nothing in it, say why rather than dropping it — an absent Manufacturability block reads as "clean" …

    line 90
  10. Distinctive:

    Keep suggestions brief. The user is an optical engineer — they need the data organized, not a lecture.

    line 99

“Common” is measured: kept by at least 6 in 10 of the 139 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design Review — Comprehensive Lens Assessment

Overview

One-command lens assessment. Pulls the relevant analysis metrics through the ZOS-API, compares them against the user's spec, and outputs a structured report. Manufacturability ratios are surfaced as prompted feedback to the user — the user brings the acceptance bands; this skill does not bake a verdict.

When to Use

  • After loading a design ("how does this look?")
  • After optimization ("did it improve?")
  • Before saving ("is this worth keeping?")
  • When the user asks to "review", "check", "assess", or "evaluate"
  • NOT for: comparing multiple designs (use /design-compare)

Workflow

Step 1: Gather spec targets

If the user provided a spec (EFL, F-number, max spot size, MTF target, field angles, wavelength band), use those. If not, ask: "What are your targets? (or I can just report current state)".

If the user gave a partial spec — first-order targets but no image-quality bands, say — do not silently invent the missing ones. Report the un-targeted metrics un-graded, and say in the report which columns have no target behind them.

Step 2: Run the analysis sequence

Pull these through the ZOS-API typed analyses, in order:

  1. System info — EFL, F-number, total track length, surface count, wavelengths, field set.
  2. Prescription — surface-by-surface radii, thicknesses, glasses.
  3. Spot — RMS and GEO spot size for ALL fields.
  4. MTF — MTF curves for ALL fields (report at two representative frequencies, e.g. 50 and 100 lp/mm).
  5. Wavefront — on-axis wavefront error (RMS waves) on a flat image plane.

Run steps 1-2 first (fast prescription reads), then 3-5 (heavier analyses).

get_mtf may return one more data series than you have fields — the extra one is the diffraction limit, not a field. Check the series count against the field count before you map them, and label the limit as the limit.

Step 3: Output report

## Design Review

### System Summary
| Parameter    | Value | Target | Status |
|--------------|-------|--------|--------|
| EFL          | ...   | ...    | PASS/FAIL |
| F-number     | ...   | ...    | PASS/FAIL |
| Total track  | ...   | ...    | — |
| Elements     | ...   | —      | — |

### Image Quality
| Field      | RMS Spot (um) | Target | MTF@50 | MTF@100 | Status |
|------------|---------------|--------|--------|---------|--------|
| On-axis    | ... | ... | ... | ... | PASS/FAIL |
| 0.7 field  | ... | ... | ... | ... | PASS/FAIL |
| Full field | ... | ... | ... | ... | PASS/FAIL |

### Wavefront
- On-axis RMS: ... waves (flat image plane)
- Diffraction limited: YES/NO

### Manufacturability (read-only ratios — bring your own bands)
- Min center / edge thickness and aspect ratios as raw numbers (from `check_clearance`).
- No baked verdict — these are prompts for the user's judgement.

### Verdict: [PASS / NEEDS WORK / FAIL]
[One sentence: what's good, what needs attention.]

The report ends with the verdict heading. It begins with the literal token ### Verdict: followed by exactly one of PASS, NEEDS WORK, or FAIL. Keep that marker exactly as written, so the verdict stays easy to find for the reader and in later sessions — do not substitute prose for it ("Bottom line", "Summary", "Overall"). Anything else you want to say goes above the line.

Keep every section. If a section has nothing in it, say why rather than dropping it — an absent Manufacturability block reads as "clean" when it means "not measured."

Step 4: Suggest next steps (only if NEEDS WORK or FAIL)

  • Spot too large: "Consider freeing more radii or adding an element."
  • MTF low at edge: "Field curvature may be the limiter — check the wavefront."
  • EFL off target: "Add an EFL operand to the merit function."

Keep suggestions brief. The user is an optical engineer — they need the data organized, not a lecture.

Key Rules

  • Evaluate the wavefront on a flat image plane unless the user explicitly asks for a best-focus refocus. If you also report a best-focus figure, label it as a refocus and keep the flat-plane number as the headline — a best-focus RMS can be 2× rosier, and quoting it unqualified overstates the design.
  • Surface ratios are prompts, not verdicts. The user owns the acceptance bands.
  • Report the worst field, always. A summary sentence about field performance must be supported by the corner row, not by the fields that flatter the design.
  • Ground any operand or glass you are unsure about with the reference tools (search_reference / lookup_operand) — do not guess a code.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.