SiSkill Explore Skills Free Skills Pricing Installation guide

Visual Rules Studio

Keep your brand consistent, even when the tools change.

Turn approved brand assets into one visual rulebook. Use it to prepare image prompts, editable cover/banner/card samples, web tokens and a Figma handoff—then detect drift when the rules change.

Visual Rules Studio

Available now · v1.0.0

USD 9.99 · Single purchase, or get access through Pro.

What would you like to make?

Turn my references into rules

My avatar, banner and covers look related, but I cannot describe the consistent parts.

An evidence-backed rulebook, uncertain choices labelled, plus representative samples.

Make a consistent content set

I have approved rules and need a cover, banner and information card for one topic.

Editable HTML samples, three image briefs, CSS/JSON tokens and a prepared Figma handoff.

Update without losing consistency

I changed the accent or typography and need to find stale output.

Field-level changes, failed source/artifact checks when relevant, and a concrete regeneration list.

SIGNAL / FIELD · a reusable visual rulebook

AI-generated design concept · not a runtime screenshot

SIGNAL / FIELD · a reusable visual rulebook
Compare the AI concept with separate actual browser screenshots. The package contains the working compiler and examples; no Figma file was modified in this example.

The input

Original fictional newsletter brand, navy/cobalt palette and approved cover, banner and card copy.

The work

Codex creates a concept board; the independent local compiler renders bilingual editable compositions and derives tokens, briefs and handoff from one rule file.

Browse all output examples
  • AI concept · one fictional brand across formats — Original SIGNAL / FIELD concept created with Codex image generation. Direction study, not a compiler or Figma screenshot.
  • Actual compiler output · English — Real browser screenshot after running the shipped helper. Three editable compositions share the same tokens. Format filtering works; Figma handoff remains a local specification.
  • Actual compiler output · Chinese — Real browser screenshot after running the shipped helper. Three editable compositions share the same tokens. Format filtering works; Figma handoff remains a local specification.

From your material to the finished files

  1. Extract and resolve

    The Agent inspects your material, records repeated traits and flags uncertain fonts or conflicting references. Approve material choices before treating them as brand rules.

  2. Compile the same source

    Run the included Node tool on visual-rules.md to create editable samples, token files, image briefs and a Figma handoff. No external service is contacted.

  3. Check the real destination

    Audit source and output hashes, then inspect browser/image results. Apply the Figma mapping separately and verify bound instances before reporting it synchronized.

Bring this task into your Agent

Prepare these materials

Provide approved visual assets, usage rights, the current brand guide if any, and the copy/formats for this job. Existing rules should be adapted to the supported structured block; arbitrary Markdown is not parsed automatically.

  1. Sign in to acquire the package.
  2. Extract the entire folder into your project: .agents/skills/visual-rules-studio/SKILL.md (Codex) or .claude/skills/visual-rules-studio/SKILL.md (Claude Code).
  3. Open a new chat in that project, attach your materials and replace the bracketed fields in the brief below. Ask the Agent to check package instructions and dependencies first.

Use $visual-rules-studio on my attached authorized brand assets. Identify recurring color roles, type hierarchy, spacing and imagery. Separate observed traits from proposed decisions; do not guess exact fonts. Write visual-rules.md using the supported schema and compile a new local sample folder. Use my [approved copy]. Do not upload assets or edit Figma yet.

Installation & troubleshooting guide

The first result can be revised

Change only the accent in the canonical file, bump the version and compare. Rebuild into a new directory and verify that tokens, prompts and Figma map agree.

What the package includes

  • One maintainable visual-rules.md: semantic colors, type, layout, imagery and evidence for design decisions.
  • A local compiler producing 11 files plus a manifest: editable three-format preview, CSS/JSON tokens, image prompts, Agent brief and Figma mapping.
  • Source-change reports, readable-color checks and file-tamper detection; manual visual and integration review guidance.

What you provide separately

  • Your Codex or Claude Code access; Node.js 22+ and a browser for the local compiler. No npm packages or online account required for that helper.
  • An available image tool for new bitmaps; Figma access and an editor or connector to apply the handoff.

Before you start

Does this automatically synchronize ChatGPT and Figma?

No. It generates consistent local files and detects their drift. ChatGPT must receive the current rule file; Figma needs an editor step and verification. The mapping is not a native import format.

How is this different from GPT Prompt Studio?

Prompt Studio develops individual image prompts. This product maintains shared brand rules across jobs, derives several outputs and checks revisions. It does not replace an image model.

Is the referenced article included or resold?

No. Inspired by Morry.AI’s article at https://x.com/Morry4AI/status/2112429478471414101, SiSkill independently authored the workflow, compiler, schema and fictional examples. No article text, original prompts or author assets are bundled.

AI concept is an illustration; the separate HTML screenshots are actual compiler output. Does not automatically extract exact fonts from pixels, generate images, edit Figma, import arbitrary Markdown, synchronize cloud tools or publish. Figma files require a separate editor step. Model/image/Figma costs are separate.

More to make

  • Waitlist Landing Page — Create a responsive prelaunch page with a product story, FAQ and clearly labeled local demo form. Includes editable source and desktop/mobile previews.
  • SaaS Landing Page — Create a full SaaS marketing prototype with positioning, features, workflow, billing-period controls, FAQ and an implementation handoff.
  • Editorial SaaS Design — For writing and knowledge products. Upright editorial serif, generous paper margins, deep green actions, asymmetric manuscript composition. Give your Agent a brief to create a visual system and editable responsive page, or apply the direction to an existing project.
  • Industrial Catalog Design — For hardware, furniture and industrial products. Ruled catalogue grid, square geometry, product-first imagery and compact model annotations. Give your Agent a brief to create a visual system and editable responsive page, or apply the direction to an existing project.