Loading...
Loading...
Found 21 Skills
Run the /check-flutter-duskmoon-design Claude command workflow in Codex.
Run a 5-dimension expert design review on any HTML artifact in the project — Philosophy / Visual hierarchy / Detail / Functionality / Innovation, each scored 0–10. Outputs a single self-contained HTML report with a radar chart, evidence-backed scores, and three lists: Keep / Fix / Quick-wins. Use when the brief asks for a "design review", "design critique", "5 维度评审", "design audit", or "what's wrong with my design".
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
Check whether a design is complete enough to move into implementation planning. Use when a design appears mostly done and needs a final readiness review for missing branches, weak assumptions, unresolved risks, failure handling, validation gaps, or non-functional omissions. Trigger before invoking writing-plans or when the user asks whether the current design is ready to implement. Do not use as a general design-document audit for external docs or as a replacement for initial design work.
Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design audit", or asks for a critique that should lead to a plan.
Audits a specific component, file, or CSS against the project's extracted design soul in .marrow.md and returns a list of violations with severity and fix instructions. Use this skill when the user wants to check if something matches the design soul, review a component for soul violations, or audit existing code before shipping. Triggers on: /marrow-check, or prompts like "check this against marrow", "does this match the design soul", "audit this component", "is this on-brand", "check this file", "review this for soul violations". Requires .marrow.md to exist. If not found, instructs user to run /marrow first.
Diagnostic audit across all seven layers — identifies the bottleneck layer and recommends where to focus
Audit and improve the visual design, polish, and player experience of an existing game
Check the evidence, biases, alternative explanations, and reporting boundaries required for research conclusions before implementation or submission. Use when the user asks for “review my research design”, “act as a strict reviewer”, “challenge this conclusion”, or requests the rw-research-referee workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.