Skip to content
Back to skills

Chrome Currents

ASecurity

Generate coherent Chrome Currents editorial illustration sets with a reusable 3d visual system. Use when illustrating articles, blogs, newsletters, essays, or social posts that need premium abstract hard-surface 3d built from one engineered system of brushed aluminum and saturated cobalt ribbons whose bends, tension, and alignment express invisible forces.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 19, 2026
ai-agentsexpress

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned October 19, 2026

npx -y skills add hahayang888/zyncli-template --skill chrome-currents --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Chrome Currents?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Chrome Currents
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hahayang888-chrome-currents/badge)](https://www.skillsdirectory.com/skills/hahayang888-chrome-currents)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: chrome-currents
description: "Generate coherent Chrome Currents editorial illustration sets with a reusable 3d visual system. Use when illustrating articles, blogs, newsletters, essays, or social posts that need premium abstract hard-surface 3d built from one engineered system of brushed aluminum and saturated cobalt ribbons whose bends, tension, and alignment express invisible forces."
---

# Chrome Currents

Create a coherent set of article illustrations with the Chrome Currents visual system. Translate strategy, technology, and transformation into engineered cobalt and brushed-aluminum ribbons. Controlled reflections, structural tension, and one decisive bend create a premium abstract system without drifting into glossy product advertising.

Read [references/style-guide.md](references/style-guide.md) before planning or generating. Use the images in `assets/examples/` only for low-frequency visual calibration; never copy their composition, people, objects, or wording.

## Workflow

1. Read the full article or supplied passage.
2. Identify the core argument, contrasts, turning points, system relationships, and conclusion.
3. Select 1-9 cognitive anchors. Do not illustrate paragraphs at even intervals.
4. Write a shot plan before generating. Give each image one core idea, one structure, and a different primary composition.
5. Compile every shot with the visual DNA and negative constraints from the style guide.
6. Use the host agent's available image-generation tool. Generate one standalone 16:9 image per request.
7. Inspect every output against the QA checklist. Regenerate or make one targeted edit when a failure signal appears.
8. Deliver ordered files and preserve original generated files.

## Shot plan

For every proposed image, specify:

- Placement after the relevant passage
- Theme and core idea
- Purpose in the article
- Structure type
- Composition and reading direction
- Suggested elements
- Essential short labels, or none

Prioritize the core argument, contrasts, turning points, system relationships, cause and effect, and a memorable conclusion. Avoid decorative filler, repeated claims, and paragraphs already concrete without a visual.

## Generation rules

- Output one standalone 16:9 horizontal editorial image.
- Keep one core idea per image.
- Make the article-specific relationship visible without relying on a headline.
- Change both the main metaphor object and spatial arrangement between consecutive images.
- Preserve identity through material, palette, hierarchy, and composition grammar rather than repeating a scene.
- Use real supplied labels only. Never invent statistics, quotations, dates, brand marks, or interface copy.
- Respect every `must`, `never`, and negative constraint in the style guide.

## QA and iteration

Reject an output when it is generic, off-style, repetitive, text-heavy, anatomically broken, semantically wrong, or dependent on decoration instead of the article idea.

When revising:

- Generic: replace the stock scene with one article-specific physical relationship.
- Complex: remove secondary elements and preserve one focal idea.
- Repetitive: change both the object family and composition pattern.
- Off-style: return to the exact visual DNA in the style guide.
- Text-heavy: remove the headline and keep only essential supplied labels.

## Delivery

Name files in article order using `{order}-{topic-slug}.png`. Report where each image belongs in the article and preserve the original generated outputs.

Files in this skill

  • SKILL.md3.4 KB
  • agents/openai.yaml217 B
  • assets/examples/01.webp52.3 KB
  • assets/examples/02.webp39.1 KB
  • assets/examples/03.webp48.6 KB
  • references/style-guide.md3.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.