'simplification' 검색 결과

Apply systematic problem-solving techniques for marketing challenges including campaign complexity (simplification cascades), creative blocks (collision-zone thinking), recurring campaign patterns (meta-pattern recognition), assumption constraints (inversion exercise), audience scale uncertainty (scale game), and dispatch when stuck. Techniques derived from proven problem-solving frameworks adapted for marketing execution.

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

Review changed Anabasis v2 code for reuse, simplification, efficiency and altitude, then apply the fixes. Quality only: it hunts no bugs, which /code-review does. Starts from what the repository already finds (the lint plugins, the whole-tree census, the not-slop ledger), measures before and after with reduce-complexity's scripts, and holds a pass to its budgets and to the rules no pass trades. Use as /simplify on your own diff before a commit, or when the operator asks whether code is simple enough, why something exists, to go one layer higher, or to remove something and find another way.

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

Evaluate and simplify Boolean expressions using truth tables, algebraic laws (De Morgan, distributive, absorption, idempotent, consensus), and Karnaugh maps for up to six variables. Use when you need to reduce a Boolean expression to its minimal sum-of-products or product-of-sums form, verify logical equivalence between two expressions, or prepare a minimized function for gate-level implementation.

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

Use when the user asks to simplify, clean, or refine code. Not for new abstractions or whole-codebase refactors.

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

定石外発想で実装をシンプルにする。現状の発展型ではなく、実装の裏にある暗黙の前提条件を1つずつ外し、よりシンプルな別解がないか検討する。 ユーザーが「定石外発想で」「前提を疑って」「もっとシンプルにできないか」と言った時に使用する。

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

Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"

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

Simplify working code while preserving behavior—remove dead paths, flatten nesting, clarify names, reduce duplication. Use after features work but code feels over-engineered.

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

Runs synapse-docs, /simplify, sync-plugin-skills, and github-pages-sync in parallel for synapse-a2a development workflows. Use when you need doc updates, code simplification, plugin skill sync, and site-docs sync at the same time.

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

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise. This skill should be used when code-quality checks pass but the code would benefit from structural cleanup — deduplication, branching simplification, naming improvements, or dead-code removal. Invoked as a subagent from /code-quality or directly via the Task tool.

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

Use when restructuring existing frontend code while preserving observable behavior, including responsibility extraction, module movement, conditional simplification, API cleanup, or data organization. Do not use for new feature behavior, behavior-changing bug fixes, dependency or framework migrations, or proven dead-code cleanup.

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

Transform reference photographs and visually dense images into sparse, recognizable, high-saturation flat-vector-style illustrations through semantic compression rather than literal tracing. Use when the user asks for photo-to-flat illustration, photo-to-vector-style redraw, 照片转扁平插画, 无渐变高饱和插画, iconification, visual simplification, composition-preserving abstraction, a consistent minimal illustration set, or revisions that remove gradients, glow, texture, blur, clutter, text, logos, numbers, or UI. Default to human-perceived semantic complexity 6 out of 10 or lower, fixed-HSB solid fills, crisp boundaries, and no gradients or light-halo effects.

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

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.

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

One-command PR gate that runs four passes over exactly the changed surface — code review (correctness then simplification), security (injection, authz, secrets, dependency diff), tests (run the suite and flag untested changed lines).

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

Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"

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

Creative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplification

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

Use when designing, auditing, or simplifying Record Types and Page Layouts. Triggers: 'record type', 'page layout', 'different picklist values', 'different fields per team', 'dynamic forms', 'business process', 'recordTypeVisibilities', 'layoutAssignments', 'record type deploy failed', 'businessProcess required', 'layout assignment matrix'. NOT for layout explosion across many profiles — use admin/record-type-strategy-at-scale. NOT for sharing rules — use admin/sharing-and-visibility. NOT for FLS — use admin/permission-sets-vs-profiles.

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

Run an explicitly requested, unusually strict dygo maintainability audit that seeks structural simplification, removes accidental complexity, and challenges weak abstractions without changing behavior.

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

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

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

Audit agent runtimes and their tests for lifecycle inference, capability overload, context pollution, correlated verification, prompt-only control, false success, dead compatibility paths, test-only seams, and complexity without contribution. Use for whole-repository agent audits, slop or dead-code triage, test contribution reviews, large refactors, tool/context simplification, and cleanup requests that need proof before deleting code or tests.

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

Use when stuck on approach, not debugging. Unstick via 7 techniques: simplification, collision-zone thinking, inversion, first principles, via negativa. For debugging use mk:sequential-thinking.

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

Post-implementation simplification pass. Reduces complexity without changing behavior. Use after Phase 3 (Build GREEN) and before Phase 4 (Review). Catches dead code, unnecessary abstractions, over-engineering, and redundant patterns. Triggers on "simplify", "clean up", "reduce complexity", "too complex". NOT for style/convention enforcement (see mk:clean-code); NOT for reviewing diffs or PRs (see mk:review).

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

Enforces KISS/DRY/YAGNI during authoring and ad-hoc reviews: concise, direct, no unneeded comments. NOT for post-hoc diff/PR review (mk:review); NOT for simplification passes (mk:simplify).

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

Multi-pass structural code review with adversarial analysis, scope-aware dispatch, adversarial persona passes, and forced-finding protocol. Supports input modes: branch diff (default), PR number (#123), commit hash, pending changes (--pending). Use when asked to "review this PR", "code review", "pre-landing review", "check my diff", or "review #123". Proactively suggest when the user is about to merge or land code changes. NOT for behavioral verification against a running build (see mk:evaluate); NOT for post-implementation simplification (see mk:simplify).

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

Use when stuck on approach (not debugging). Strategic unsticking via 7 non-default techniques: simplification cascades, collision-zone thinking, meta-pattern recognition, inversion, scale game, first principles, via negativa. Triggers on complexity spiraling, innovation block, recurring patterns across domains, forced-assumption solutions, scale uncertainty, told-it's-impossible, or bloated systems needing subtraction. For evidence-based root-cause debugging, use mk:sequential-thinking instead.

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