'critique' 검색 결과

Processes eDNA metabarcoding from raw paired-end reads to species tables, navigating ASV (DADA2, UNOISE3) vs OTU (swarm v2) decision (Callahan 2017 vs Schloss multi-copy-16S critique), marker/primer choice (Leray COI, MiFish 12S, 515F/806R 16S, ITS2) with primer-specific bias, OBITools3 v3 command-name break (obi stats plural; .tar.gz taxonomy), tag-jumping with dual-indexing (Schnell 2015; NovaSeq 10x MiSeq), decontam as screening-not-classifier (Davis 2018), read-counts-not-abundance critique (Lamb 2019), site-occupancy modeling (Ficetola 2015), Naive-Bayes calibration limits (Bokulich 2018), and eDNA decay (Strickler 2015). Use when going from raw eDNA FASTQ to species tables, picking marker + denoising pipeline, deciding whether read counts represent abundance, applying occupancy modeling, configuring OBITools3 v3, or interpreting decontam output. Not for clinical 16S microbiome (see microbiome/amplicon-processing).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Rigorous multi-pass editor for law review articles, student notes, seminar papers and other legal scholarship. Runs six specialized passes — structure, substantive critique, Bluebook citations, grammar and clarity, fact-checking against sources, and a synthesizing memo — and delivers an editorial memo with issues prioritized as critical, substantial or minor and keyed to specific footnotes and paragraphs. Handles articles of any length, including 50,000-word pieces, by chunking on section boundaries. Reads .docx directly. Use when editing, critiquing, workshopping or pre-submission-reviewing academic legal writing. Triggers on "edit my article," "review this draft," "critique my note," "check my Bluebook citations," "is my argument sound," "read my law review piece," "workshop this paper," "pre-submission review." Chunking needs Python 3; fact-checking needs web search; both degrade gracefully without.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Direct, build and render premium cinematic motion design from code — launch films, product and feature videos, looping feature animations for landing pages and social, logo stings and reveals, UI walkthroughs, app demos, kinetic type, teasers, trailers, intros and promo clips. Use this whenever the user wants any video, animation, motion graphic or animated demo made with Remotion, HyperFrames, HTML/GSAP or React, or asks to storyboard, time, score, render, polish or critique one — even if they only say "make a video about X", "animate this feature" or "we need a launch clip". It supplies concept and copy discipline, type and colour taste that defers to a supplied brand, a beat-locked timeline that drives both picture and a code-made soundtrack, choreography and transition craft, real product UI in motion, film-grade finishing (true motion blur, no banding, BT.709, sync-checked mux) and a measured self-critique loop on contact sheets and renders.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Architecture quality critique dimensions for peer review. Load when invoking solution-architect-reviewer or performing self-review of architecture documents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Architecture quality critique dimensions for peer review. Load when performing architecture document reviews.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Critique dimensions and scoring for research document reviews

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Platform design review critique dimensions and severity levels. Load when reviewing CI/CD pipelines, infrastructure, deployment strategies, observability, or security designs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use Grok 4.5 as the required external design advisor when a task needs UI critique, UX critique, component-choice review, interaction-flow review, design imagery markdown, art direction, visual hierarchy judgment, design-system fit, color/type/layout suggestions, HTML mockups, SVG icons, handwritten SVG wordmarks, or file-based feedback on existing UI. Trigger on requests like "design a page", "generate design imagery", "give design advice", "optimize this UI", "improve UX", "optimize user flow", "review interaction", "check usability", "reduce friction", "choose the right component", "review this design", "create an icon", "suggest colors", "UI mockup", "visual direction", "lettering", "wordmark", "handwritten logo", or when another agent needs a second opinion on visual or interaction quality.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provider-independent governance workflow for verifying and correcting human- or model-generated video descriptions. Use for pre-caption critique and post-caption revision, aspect-by-aspect factual review, critique precision/recall/constructiveness, second-stage peer review, calibration, appeals, versioned triplets, provenance, and acceptance reporting; not for pixel/audio QA, accessibility captioning, model training, or creative shot direction.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Critique a screen's colour usage — contrast ratios, palette coherence, semantic meaning, and colour accessibility.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Critique a screen's composition — balance, whitespace, rhythm, and gestalt principles.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Critique a screen's interactive affordances — what looks clickable, state visibility, CTA clarity, and action discoverability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Critique a screen's brand consistency against mood.md, voice.md, and tokens.md.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Critique a screen's information density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Critique a screen's visual hierarchy — entry point, eye flow, weight distribution, and emphasis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Critique a screen's typography — scale usage, readability, consistency, and token compliance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Spec or critique custom illustrations — style, composition, and brand alignment. Use when asked to "spec an illustration", "critique this illustration", or "define an illustration style".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The creative process in art from idea to exhibition. Covers five phases of creative work (inspiration, incubation, exploration, execution, reflection), sketchbook practice, artist statements, critique methodology (formal and conceptual), portfolio development, and the studio as a working environment. Use when guiding students through project development, facilitating critique sessions, developing artist statements, curating portfolios, or understanding how professional artists structure their creative practice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before any CLI/TUI display code is written, modified, or audited — runs the 7-stage discipline (Context, Register, Shape brief, Implement, Critique, Audit, Polish) for Typer, Rich, Textual, and Questionary work, grounded in per-project PRODUCT.md and DESIGN.TUI.md/DESIGN.md. Triggers on output formatting, display design, interactive prompts, visual consistency, TUI layout, progress display, dashboard design, design audit, design polish, design critique, shape brief, register decision (brand-cli vs product-cli), and AI-slop checks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Skeptical analysis and critique of claims, plans, and code without taking anyone at face value. Use when the user says "don't trust me", wants adversarial review, red-teaming, assumption checking, or verification that generated or proposed code is actually correct. Triggers on skepticism, critique everything, verify claims, challenge assumptions, red team, devil's advocate, prove it, smell test.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.