FORMWEFT CLEAN ROOM · VISUAL OPERATIONS
Starting from requirements and asset rights, to layout, generation, quality inspection, platform adaptation, and archiving, each step has inputs, responsibilities, and acceptance criteria.
FIVE PRODUCTION STAGES
The SOP doesn't replace creative judgment, but lets creative teams spend time on effective decisions and leave reusable enterprise assets.
BRIEF
Fixed products, channels, sizes, audiences, core messages, brand guidelines, prohibited expressions, deadlines, and approvers; missing items don't enter formal production.
ASSET
Record source, authorization scope, expiration time, and modification restrictions for product images, people, fonts, music, trademarks, and generated content; isolate unknown assets first.
BUILD
Generate a small number of versions with clear assumptions using naming conventions, layout grids, color and font tokens, avoiding aimless bulk image generation and scattered files.
REVIEW
First check size, clarity, text, product authenticity, and platform rules, then have business owner confirm benefit points, price, claims, and landing page consistency.
ARCHIVE
Export per channel, record final files, source files, approval evidence, version numbers, publish dates, and experiment IDs, keeping rollback and reuse paths.
FIXED RELEASE
FORMWEFT clean-room original documentation-type Skill. MIT covers only the original documents in this package; the current fixed hash has completed structural validation and static review. Users remain responsible for input materials, platform rules, and final output.
You can download this reviewed version's resource package. If it includes SKILL.md, provide it and the related documentation to your AI tool; first read and check the materials and usage boundaries, and do not run anything automatically.
You can also select the text to copy directly; read it first before executing.
Rewritten independently based on the Feishu directory topic clean-room, without copying or redistributing the original package text. Conclusions apply only to the current fixed hash: the archive structure has been parsed, static rule result is eligible, with 6 files and no scripts, dependencies, or install hooks; online boundaries follow the statements in this resource, and files are output only to user-approved locations. Static review cannot replace runtime environment, input data, or later-version rechecks.
FORMWEFT94b1a40626712002695172afe048b6810b8d098a7e22f2d5476a360ef5ce4871
Tell us about your team, SKU count, channels, existing tools, approval chain, and delivery frequency, and we can further customize template libraries, prompt libraries, task workbenches, and quality dashboards.