تشغيل أي مهارة في Manus بنقرة واحدة

polish

النجوم٢

التفرعات٠

آخر تحديث٤ يوليو ٢٠٢٦ في ٠٤:٠٦

Polish a NAMED visual dimension of an existing Teacher & School product page — spacing, type, radius, colour, shadow, or type/weight hierarchy (SLP-6). Use only when the ask names such a dimension — "polish the spacing", "tighten the type", "the colours look off", "the headings don't stand out from the body". NOT for a bare "polish / tidy / clean up the page (or screen)" with no visual dimension named — that general, dimensionless polish is critique's whole-page job, so route it to critique. NOT for a named structural or component change — that is design. Visual or page hierarchy — what draws the eye (emphasis, size, position, grouping) — is layout's; polish only touches type/weight hierarchy. Layout structure goes to layout, wording to copy, animation to motion.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

transformteamsg

transformteamsg/tfx-design-standard

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مصممو واجهات الويب والرقميةمهن الحاسوب والرياضيات·SOC 15-1255

SKILL.md

readonly

name

polish

description

Polish an existing surface

A focused pass on the polish dimension: the token, type, and colour craft that makes a screen read as cared-for rather than templated. You judge the visual surface only — structure, wording, motion, and flow are out of scope and get NOTED and routed.

Dimension controls (cite these; the catalog holds the rules — load them from ../../../standards/catalog.yaml, read each detail file that exists):

Tokens — TOK-1 (no raw colour), TOK-2 (spacing scale), TOK-3 (radius scale).
Type — TYP-1 (Plus Jakarta Sans / Inter only), TYP-2 (min sizes + line-height), TYP-3 (on-scale sizes), TYP-4 (no all-caps), TYP-5 (tabular figures).
Colour — COL-1 (product primary for primary actions), COL-2 (Radix functional scales).
Visual anti-slop — SLP-1 (no purple/glow), SLP-2 (no gradient text), SLP-3 (no side-tab card borders), SLP-6 (type hierarchy ≥ 1.25x), SLP-7 (spacing rhythm).

Reference: the polish bullets of ../design/implement-craft.md — tabular figures, concentric radius, layered shadows, type polish (text-wrap, font-smoothing), image edges. It refines these controls; it never replaces them.

Procedure: follow ../critique/pass.md with the subset above. Card/nested-card composition (SLP-4/5/11) is a layout matter — note and route it, do not fix it here.

المزيد من هذا المستودع

نفس المستودع

copy

transformteamsg/tfx-design-standard

Improve, write, or review the copy on a Teacher & School product surface — TFX voice & tone, naming, error-message anatomy, and anti-AI-writing rules (SLP-9), applied at generation time. Use for any copy-only edit — writing or reviewing user-facing text (page, form, notification, empty state, error state), tightening the wording on a page ("improve/polish the copy on the marks page"), or any longer prose (site content, marketing copy, documentation, decision records). Sufficient on its own for copy-only work; the design loop pulls it in at its implement phase. NOT for a whole-page review with no dimension named — that is critique; NOT for a named structural or visual change — that is design.

2026-07-102

design

transformteamsg/tfx-design-standard

Design or change a Teacher & School product UI — a new page, screen, form, flow, OR a modification to an existing one (adding a field, editing copy, restyling a component). Use whenever the user asks to design, create, build, add to, change, fix, or restyle any page, screen, form, component, or user flow — and whenever they ask to re-audit, re-check, or re-verify an existing page against the standards catalog (e.g. after the catalog gains new controls). Orchestrates the full loop — intent, diverge, plan (human gate), implement, verify — with the TFX-DS standards catalog enforced throughout. For copy-only edits the copy skill is sufficient; for questions about the catalog itself use standards; and to review, improve, or polish an existing page with no specific change named — or when the user just says they don't like it — use critique.

2026-07-082

flow

transformteamsg/tfx-design-standard

Improve the flow of an existing Teacher & School multi-step task or interaction — step traversal, async states, escapability, and draft safety. Use for a scoped ask that names this dimension — "improve this flow", "this multi-step form loses my draft", "smooth the journey between steps on <page>", "there's no way out of this wizard" — with no structural rebuild named. NOT for a whole-page review with no dimension named (that is critique); NOT for a named structural change or a brand-new flow (that is design). Layout goes to layout, wording to copy.

2026-07-082

critique

transformteamsg/tfx-design-standard

Critique an existing Teacher & School product page — capture it, grade it against the standards catalog and layout patterns, and return scored, ranked improvement suggestions without changing anything; then, on the user's approval, execute the accepted suggestions through the design loop's implement and verify phases. Use when the user asks to review, critique, audit, improve, polish, or judge an existing page, asks what's wrong with it, what's off, or what they should improve, or says they don't like it — WITHOUT naming a specific change. NOT for a named change ('add a field', 'change the button') or a new page; those go to design. NOT for grading the loop's own output; that is the evaluator agent. NOT for copy-only improvements — wording, microcopy, tone, or naming with no structural or visual change; those go to copy.

2026-07-082

layout

transformteamsg/tfx-design-standard

Tighten the layout of an existing Teacher & School product page — structure, visual hierarchy (what draws the eye — emphasis, size, position, grouping), density, alignment, and grouping. Use for a scoped ask that names this dimension — "tighten the layout", "fix the hierarchy", "the visual hierarchy is weak", "the density is off", "these cards should be a list". Bare "hierarchy" and "visual hierarchy" are layout's. NOT for a whole-page review with no dimension named (that is critique); NOT for a named structural change or a brand-new page (that is design). Visual styling — spacing tokens, type, colour — goes to polish (including type/weight hierarchy), wording to copy, motion to motion.

2026-07-082

start

transformteamsg/tfx-design-standard

Start here — orientation, a quick context check, and routing to the right TFX skill.

2026-07-042

name

polish

description

Polish an existing surface

Dimension controls (cite these; the catalog holds the rules — load them from ../../../standards/catalog.yaml, read each detail file that exists):

Tokens — TOK-1 (no raw colour), TOK-2 (spacing scale), TOK-3 (radius scale).
Type — TYP-1 (Plus Jakarta Sans / Inter only), TYP-2 (min sizes + line-height), TYP-3 (on-scale sizes), TYP-4 (no all-caps), TYP-5 (tabular figures).
Colour — COL-1 (product primary for primary actions), COL-2 (Radix functional scales).
Visual anti-slop — SLP-1 (no purple/glow), SLP-2 (no gradient text), SLP-3 (no side-tab card borders), SLP-6 (type hierarchy ≥ 1.25x), SLP-7 (spacing rhythm).

Procedure: follow ../critique/pass.md with the subset above. Card/nested-card composition (SLP-4/5/11) is a layout matter — note and route it, do not fix it here.