YAO
31ce04c655
Merge the beta-ready Yao Meta Skill architecture, report, evidence gate, and release-boundary updates.\n\nRelease boundary: beta/public testing is allowed; formal world-class, fully reviewed, or superiority claims remain blocked until the pending evidence gates are accepted.
120 lines
4.5 KiB
JSON
120 lines
4.5 KiB
JSON
{
|
|
"skill_name": "yao-meta-skill",
|
|
"design_system": "metric editorial",
|
|
"primary_artifact": {
|
|
"key": "dashboard",
|
|
"label": "Dashboard or metrics page",
|
|
"direction": "Metric-first dashboard with stable dimensions, short labels, visible deltas, and narrative callouts only where they change interpretation.",
|
|
"matched_keywords": [
|
|
"metric",
|
|
"score",
|
|
"table",
|
|
"scorecard"
|
|
]
|
|
},
|
|
"artifact_families": [
|
|
{
|
|
"key": "dashboard",
|
|
"label": "Dashboard or metrics page",
|
|
"score": 4,
|
|
"matched_keywords": [
|
|
"metric",
|
|
"score",
|
|
"table",
|
|
"scorecard"
|
|
],
|
|
"direction": "Metric-first dashboard with stable dimensions, short labels, visible deltas, and narrative callouts only where they change interpretation."
|
|
},
|
|
{
|
|
"key": "review_viewer",
|
|
"label": "Review viewer",
|
|
"score": 3,
|
|
"matched_keywords": [
|
|
"review",
|
|
"viewer",
|
|
"audit"
|
|
],
|
|
"direction": "Side-by-side reviewer studio with explicit tradeoffs, evidence readiness, and fast paths for approving, blocking, or requesting one focused fix."
|
|
},
|
|
{
|
|
"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": "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": [
|
|
"metric board",
|
|
"ranked signals",
|
|
"comparison rows",
|
|
"interpretation",
|
|
"action queue",
|
|
"summary",
|
|
"variant comparison",
|
|
"evidence"
|
|
],
|
|
"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": [
|
|
"Avoid paragraph-heavy table cells.",
|
|
"Keep charts tied to one analytical question each.",
|
|
"Preserve stable color meaning across metrics and entities.",
|
|
"Make differences visible instead of hiding them in prose.",
|
|
"Separate author-facing recommendations from reviewer-only evidence.",
|
|
"Surface conflicts clearly and keep routine benchmark synthesis quiet.",
|
|
"Name the working directory and required inputs for commands.",
|
|
"Mark destructive, networked, or external side-effect operations."
|
|
],
|
|
"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."
|
|
} |