yao-meta-skill/reports/artifact-design-profile.json

{
  "skill_name": "yao-meta-skill",
  "design_system": "metric editorial",
  "primary_artifact": {
    "key": "code_or_cli",
    "label": "Code, CLI, or implementation guide",
    "direction": "Execution-focused technical artifact with environment assumptions, copyable commands, expected outputs, and side effects made explicit.",
    "matched_keywords": [
      "code",
      "script",
      "command"
    ]
  },
  "artifact_families": [
    {
      "key": "code_or_cli",
      "label": "Code, CLI, or implementation guide",
      "score": 3,
      "matched_keywords": [
        "code",
        "script",
        "command"
      ],
      "direction": "Execution-focused technical artifact with environment assumptions, copyable commands, expected outputs, and side effects made explicit."
    },
    {
      "key": "report",
      "label": "Report or brief",
      "score": 2,
      "matched_keywords": [
        "report",
        "summary"
      ],
      "direction": "High-trust editorial report with a clear first-screen thesis, compact evidence blocks, and decisions separated from supporting detail."
    },
    {
      "key": "review_viewer",
      "label": "Review viewer",
      "score": 2,
      "matched_keywords": [
        "review",
        "viewer"
      ],
      "direction": "Side-by-side reviewer studio with explicit tradeoffs, evidence readiness, and fast paths for approving, blocking, or requesting one focused fix."
    },
    {
      "key": "dashboard",
      "label": "Dashboard or metrics page",
      "score": 1,
      "matched_keywords": [
        "table"
      ],
      "direction": "Metric-first dashboard with stable dimensions, short labels, visible deltas, and narrative callouts only where they change interpretation."
    },
    {
      "key": "visual_capture",
      "label": "Screenshot or visual evidence",
      "score": 1,
      "matched_keywords": [
        "screenshot"
      ],
      "direction": "Evidence-led visual artifact that records source, viewport, crop intent, and the exact region the reader should inspect."
    }
  ],
  "layout_patterns": [
    "prerequisites",
    "commands",
    "expected output",
    "failure handling",
    "rollback or cleanup",
    "thesis",
    "evidence blocks",
    "decision table"
  ],
  "design_tokens": {
    "type": [
      "Use a distinctive display face or serif for major claims when the artifact is editorial.",
      "Use a restrained sans for dense body text and technical details.",
      "Use mono only for metadata, paths, commands, labels, and evidence tags."
    ],
    "color": [
      "Choose colors from the artifact's domain, brand, or evidence mood.",
      "Do not default to Kami parchment, purple gradients, or generic SaaS blue unless the content justifies it.",
      "Keep accent color limited to decisions, active states, risk, or section anchors."
    ],
    "spacing": [
      "Prefer clear grid rhythm over floating decorative cards.",
      "Increase whitespace around decisions and shrink whitespace around supporting metadata.",
      "Split dense content instead of shrinking type or adding scroll traps."
    ],
    "components": [
      "Use cards for grouped evidence, tables for comparisons, callouts for decisions, and timelines for sequence.",
      "Avoid cards inside cards.",
      "Keep reviewer-only detail visible but visually quieter than user-facing guidance."
    ]
  },
  "quality_gates": [
    "Name the working directory and required inputs for commands.",
    "Mark destructive, networked, or external side-effect operations.",
    "Prefer the smallest runnable snippet over broad framework scaffolding.",
    "Keep the first screen useful without requiring the reader to parse every detail.",
    "Use tables only for comparisons; move explanations below the table.",
    "Keep source notes readable without flooding the body with markers.",
    "Make differences visible instead of hiding them in prose.",
    "Separate author-facing recommendations from reviewer-only evidence."
  ],
  "anti_patterns": [
    "Do not copy Kami's fixed parchment background as a default.",
    "Do not use generic purple gradients, glass cards, or stock SaaS hero sections unless the content calls for them.",
    "Do not let Markdown tables become the default shape for every comparison or explanation.",
    "Do not turn reviewer evidence into user-facing clutter.",
    "Do not invent screenshots, citations, charts, or UI states."
  ],
  "reviewer_note": "Use this profile to judge whether the generated artifacts feel designed for their job, not merely rendered."
}