agentleFS
Sign inStart free
wordbrickswordbricks/onequery/.agents/skills/onequery-blog-images/SKILL.md

onequery-blog-images

Skill17 starsChanged 7 months agoApache-2.0View on GitHub

Generate or replace OneQuery blog thumbnail images and article diagram images for apps/landing. Use when Codex needs to create blog list thumbnails, social share thumbnails, in-article architecture diagrams, update blog imageSrc references, follow the OneQuery diagram design system, or use the bundled assets/diagram-design-system.png visual reference.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create OneQuery blog thumbnails and article diagrams that match the existing landing-site image system.

    line 13
  2. Very specific:

    Read references/onequery-blog-image-system.md before generating.

    line 18
  3. Very specific:

    Use the built-in image_gen flow from the imagegen skill for generation.

    line 19
  4. Distinctive:

    Update the consuming post:

    line 22
  5. Very specific:

    Do not leave project-referenced images only under $CODEX_HOME/generated_images.

    line 29
  6. Distinctive:

    Do not overwrite existing image assets unless the user asked to replace them.

    line 30
  7. Distinctive:

    Keep thumbnail diagrams simple and centered with at least 1/5 canvas width empty on every edge.

    line 31
  8. Distinctive:

    Avoid readable text in thumbnails.

    line 32
  9. Very specific:

    Use assets/diagram-design-system.png as the visual reference.

    line 34
  10. Very specific:

    Do not use the filled app icon or OneQuery wordmark inside generated diagrams.

    line 35
  11. Very specific:

    Keep paths under apps/landing/public/images/blog/.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

OneQuery Blog Images

Create OneQuery blog thumbnails and article diagrams that match the existing landing-site image system.

Core Workflow

  1. Inspect the target post under apps/landing/src/landing/blog/posts/ and the current image references.
  2. Read references/onequery-blog-image-system.md before generating.
  3. Use the built-in image_gen flow from the imagegen skill for generation.
  4. Inspect the generated image with view_image before copying it into the repo.
  5. Copy the selected generated image from $CODEX_HOME/generated_images/... into apps/landing/public/images/blog/.
  6. Update the consuming post:
    • Thumbnail/social image: set imageSrc to /images/blog/<file>.png.
    • Section diagram: add imageSrc, imageAlt, imagePlacement, images, or inlineImages on the relevant section.
  7. Validate references with rg, verify dimensions with file, and run bunx turbo typecheck --json --filter @onequery/landing after TypeScript changes.

Hard Rules

  • Do not leave project-referenced images only under $CODEX_HOME/generated_images.
  • Do not overwrite existing image assets unless the user asked to replace them.
  • Keep thumbnail diagrams simple and centered with at least 1/5 canvas width empty on every edge.
  • Avoid readable text in thumbnails. Use icons, arrows, dots, tiles, and abstract diagram components instead.
  • For article diagrams, allow short uppercase module labels only when they improve clarity.
  • Use assets/diagram-design-system.png as the visual reference. Do not use the old diagram-system-reference.png name.
  • Do not use the filled app icon or OneQuery wordmark inside generated diagrams. Use the simplified line seal icon style when OneQuery is a diagram node.

Naming

  • Thumbnail/social share image: <post-slug>-icon.png.
  • In-article diagram: <post-slug>-<diagram-topic>.png.
  • Keep paths under apps/landing/public/images/blog/.

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.

Check your setup, free