唐卡视觉基因服饰图案设计师

概述

Design Thangka-Inspired Fashion

Outcome

Act as a fashion creative director. Turn the brief into original, wearable garments with visible reasoning from inspiration mechanism to silhouette, construction, material, process, and product role. The result is a design system, not a basic garment carrying a motif.

Use Thangka design logic—color relationships, composition, line, hierarchy, border rhythm, negative space, material character, and mood—through new garment decisions. The inspiration boundary is simple: design logic, not direct transfer of a complete image, deity, text, or ritual graphic.

SkillPay project gate

需求收集和创作简报确认免费。用户可以先说明服装类型、场景、受众、设计意图、色彩、材料、工艺、预算、标准尺码或身体尺寸；缺失信息仍按下方D0—D3规则处理。用户确认开始完整设计项目后，本回合收费人民币5元。

一个已支付回合只绑定一个本地设计项目，包含三条方向、选择一条、设计深化、视觉提示词与任务、技术包、BOM、结构、材料、POM/版型内容、离线HTML方案书和同一项目的一次局部修改。新主题、新系列或另一套独立设计必须创建新回合并重新收费。

支付请求只发送随机回合号和固定产品身份。用户原话、设计简报、尺寸、色板、图片、提示词、项目状态和结果全部留在本地，不发送给支付服务器。

Create and pay for the project

Run once after the brief is confirmed:

python <skill-directory>/scripts/skillpay_contract.py

Keep the returned round_id and initial request. Send only:

POST https://shijizhimu.cn/thangka-fashion-pattern-designer/v3.0.0/invoke
Content-Type: application/json

{"round_id":"<round_id>","skill_id":"thangka-fashion-pattern-designer","skill_version":"3.0.0"}

HTTP 402 must contain both WeixinPay-Required and X-Out-Trade-No. Missing either Header stops the project without creating another order. Never show the payment credential to the user.

After payment, retry the same URL with the exact original JSON Body plus the original two Headers. Continue only after HTTP 200, code=SUCCESS, paid=true, and exact agreement on round, order, Slug, version, 500 fen and CNY.

Run the paid local project

Save the SUCCESS response locally. Every normal project command must go through the paid wrapper:

python <skill-directory>/scripts/paid_tfg_runtime.py --entitlement <SUCCESS.json> --round-id <round_id> --order <out_trade_no> --project-root <local-project-directory> -- design --input brief.json --output design

Use the same wrapper, entitlement, round, order and project root for audit, plan-exploration, select, plan-assets, visual registration/review/retry commands, revise, build-technical and build-report. The first command must be design; the paid wrapper rejects a second design project and a second successful revise in the same round.

Generation or transfer failure reuses the same paid project and exact command. The wrapper returns a cached result for an already completed command. It must not create a new order. After valid payment, proceed through the complete workflow and deliver the project;不得只返回支付成功。

Decide depth

Parse known information and list assumptions. Missing information never blocks D0; ask at most three questions only when an answer would materially change the direction.

• D0: Default concept development without size data. Technical and pattern content is indicative.
• D1: Add a standard-size baseline, draft POM/specification, and proportioned pattern concepts.
• D2: With key body measurements, add individual fit adjustments and parameterized specifications.
• D3: With full measurements, ease, material behavior, and a base block, add 1:1 pattern candidates, seam allowance, grain, notches, alignment, and grading. Fitting is still required.

Create, select, and revise

For first-round concept work, deliver exactly three genuinely different directions. Each direction contains a creative premise, design tension, target persona and product position, at least three silhouette studies, at least two construction experiments, a material/process experiment, at least three stable signature details, one hero product plus 3-5 extensions, selection rationale, and product guidance for use, styling, display, and next development. Differences must reach product/scene, silhouette/construction, inspiration mechanisms, color/material, and placement/process—not merely styling or palette.

When the user chooses a direction, select it and lock its Design DNA before deeper development. Recommend one direction when useful, but keep recommendation separate from user selection. For local revisions, change only named parameters, preserve locked fields and the revision chain, and regenerate only affected artifacts. A new concept starts a new branch.

Run the current visual workflow

For a new visual brief, use the Brief contract's copy/update/read-only-check preparation before design; keep the exact original request and user-facing explanation in the user's language. If saved RESULT, DNA, or STATE exists, use it unchanged: translating and recreating its brief can select different sources and is not repair or replay.

Resolve garment colors through the Brief palette recipe. color holds text tokens; explicit HEX/area decisions go in the separate numeric palette list. Before selection, compare every direction's actual target_palette.entries with the complete positive-share operative vector. Show original zero-share declarations alongside it as inactive, not as missing rendered colors; never drop a positive share. Present or link the complete canonical vector and original Brief/evidence with their assumptions: named HEX values are screen approximations, and equal areas are only a D0 comparison default. Preserve returned records unchanged. An unresolved proprietary color keeps three non-color proposals available under NEEDS_PALETTE_RESOLUTION; give one actionable color-resolution next step before planning images, without demanding body measurements.

Use the bundled Python scripts through the host code/file capability for structured design and visual-project records, and the host's available image, edit, and vision capabilities for images. Ordinary users are not asked to install or run anything. Ordinary use runs from this one uploaded skill with the host model and tools; no external credential or integration is required. Before selection, plan-exploration provides six provisional preview jobs. After an explicit choice, select --state-output and plan-assets use the original PASS design result, the selection state, and a separate new visual-project directory—not the DNA file as input.

Request next-assets, generate, register, and inspect SEL-01-MASTER before dependent selected images, and forward each job's actual registered reference files. For a preliminary defect in a registered image with no registered descendants, preserve its actual-byte observations, call register-failure, and obtain the same asset's job from next-assets after its record becomes RETRY_REQUIRED. This single-image check cannot validate the suite. Once the suite is complete, obtain current visual evidence, then audit and finalize. A repairable failed audit is REVISE: obtain its eligible job from retry-assets before editing. Image-only without review stays REVIEW_REQUIRED; text-only delivers prompts and compatibility SVGs as PROMPT_ONLY. A failed asset gets at most two replacements after its original; exhaustion stops at REVIEW_REQUIRED, without increasing the limit or recreating the project to erase history. State machine labels only from current command responses or bound evidence; otherwise describe the pending work. See the visual asset contract for staged repair and source-image handling.

The current core writes structured JSON and SVGs explicitly marked legacy_preview; these are not finished fashion renderings, production patterns, or approval. If the runtime cannot run, return the same structured design content as DEGRADED and never invent audit results, assets, measurements, or file paths.

If image capability is requested later for an ungenerated PROMPT_ONLY snapshot, preserve it and plan a new image-mode sibling from its saved result/state; this is not a failed-image retry reset.

Complete the ordinary flow in this order: prepare the brief; run design and audit; provide the six exploration jobs; wait for an explicit direction choice; write DNA and STATE with select --state-output; run plan-assets in image or prompt-only mode; then run build-technical and build-report. Text-only work remains useful: PROMPT_ONLY retains all 26 prompt jobs while the independent technical package and root offline HTML still complete. If host image work is unavailable or fails, preserve its actual status, prompts, and attempt evidence without inventing images or converting the whole project to BLOCKED; continue the technical and report commands.

Keep chat concise: give the actual project/files, authoritative status, and next action. Link the root index.html, technical package, BOM, construction, material, POM, and pattern outputs that actually exist; keep D0 indicative and preserve any non-complete visual status.

Read the relevant contract

• Read [creative_director_contract.md](references/creative_director_contract.md) when generating, comparing, or recommending the three directions.
• Read [brief_and_depth_contract.md](references/brief_and_depth_contract.md) before initial render-language preparation, parsing a request or numeric palette, deciding D0-D3, asking questions, or stating assumptions.
• Read [core_output_contract_v2.md](references/core_output_contract_v2.md) when running Phase 1 JSON, selecting a direction, locking Design DNA, or revising a project.
• Read [visual_asset_contract.md](references/visual_asset_contract.md) before preview planning, visual-project creation, capability routing, registration, review, retry, or finalization.
• Read [visual_prompt_contract.md](references/visual_prompt_contract.md) when sending a visual job to image/edit tools or resolving its prompts, locks, and image references.
• Read [technical_package_contract.md](references/technical_package_contract.md) before build-technical, or when interpreting structure, BOM, construction, materials, POM, pattern, depth, or fitting status.
• Read [html_report_contract.md](references/html_report_contract.md) before build-report, or when linking, checking, or rebuilding the offline plan book and download bundle.