'simplify' 검색 결과

Diagnose failed pandoc PDF conversions by checking installed tools, capturing error logs, and trying alternative PDF engines. The workflow helps identify missing fonts or packages and suggests ways to simplify documents when conversion still fails.

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

• Investigating unknown errors during PDF conversion
• Finding missing fonts or LaTeX packages
• Choosing a PDF engine for a document

Recover from failed code execution by simplifying code, switching to shell commands, or handing complex tasks to shell_agent. Explicit working directories and output checks help keep generated files in the expected location.

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

• Recovering from sandbox execution failures
• Keeping generated files in the intended folder
• Checking output files after code execution

Build product pages that reveal interfaces and explanations as visitors scroll. Uses GSAP ScrollTrigger to coordinate pinned scenes, gradual reveals, and section transitions while keeping the product story and interface readable.

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

• Explain a product workflow through scrolling
• Reveal interface features in stages
• Connect product sections with coordinated transitions

Clean up code comments without changing executable code. The skill removes obvious explanations, decorative headings, and vague notes while preserving concise comments about intent, constraints, security, edge cases, and other information the code does not show.

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

• Removing comments that merely repeat the code
• Simplifying decorative headings and lengthy notes
• Preserving explanations of design decisions and constraints

Review the exact final set of changes for a LoopX goal, checking reuse, simplification, concrete risks, and project validations. Record and verify a quality receipt, a review record tied to those specific changes.

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

• Reviewing final changes before delivery or merge
• Checking reuse and opportunities to simplify code
• Recording validation results and concrete quality risks

Create simple, cute square character images using rounded shapes, two character colors, and a solid background. The skill can use product context to propose three design directions and generate six separate candidates for comparison.

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

• Create a product mascot
• Compare three character design directions
• Simplify an animal or object into a recognizable character

Tone down interfaces that feel visually overwhelming by refining colors, typography, spacing, decoration, and motion. Preserve important emphasis and recognizable character while creating a calmer layout that remains readable and easy to use.

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

• Softening overly vivid colors
• Reducing competing bold text and large elements
• Simplifying excessive decoration and animation

Review mock configurations in .NET tests by tracing the production code each test exercises. Identify unused, unreachable, duplicated, or replaceable setups, explain concrete fixes, and distinguish them from appropriate mocks for databases, HTTP clients, and other external services.

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

• Finding unused or unreachable mock setups
• Consolidating duplicated mock configurations
• Reviewing ILogger and IOptions replacements

Design modules that expose simple interfaces while hiding substantial behavior. Use shared terms and principles to assess interface complexity, decide where behavior can be swapped, and organize code so callers and tests use the same interface.

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

• Simplify a module interface
• Review module structure during refactoring
• Decide where behavior should be swappable

Review a coding session to identify improvements to the agent’s working environment. Get prioritized suggestions for finding files, strengthening automated checks, clarifying guidance, reducing costly tool calls, and accessing missing information.

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

• Reviewing why a coding agent struggled
• Finding gaps in automated checks
• Simplifying agent instructions

Use SymPy in Python to solve equations, simplify formulas, calculate derivatives and integrals, and work with matrices. Keep exact results such as fractions and square roots, then turn expressions into executable code or LaTeX.

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

• Solve equations and verify the solutions
• Calculate derivatives, integrals, and limits
• Find matrix eigenvalues and inverse matrices

Review LinkedIn campaign exports or pasted metrics to identify weak click rates, audience targeting issues, form friction, and inefficient spending. Receive a structured audit with B2B benchmark comparisons and prioritized recommendations.

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

• Investigating low LinkedIn ad click rates
• Reviewing audience targeting and lead quality
• Simplifying lead generation forms

Review system architecture, simplify boundaries, or compare interface designs from repository evidence

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

Deslop, simplify, or review low-value tests and prose only when explicitly requested for a branch or diff.

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

Guides a refactor, cleanup, or restructure with the right decomposition. Use when the user asks to refactor, simplify, extract, or modernize code.

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

Deterministic mathematical computation using SymPy. Use for ANY math operation requiring exact/verified results - basic arithmetic, algebra (simplify, expand, factor, solve equations), calculus (derivatives, integrals, limits, series), linear algebra (matrices, determinants, eigenvalues), trigonometry, number theory (primes, GCD/LCM, factorization), and statistics. Ensures mathematical accuracy by using symbolic computation rather than LLM estimation.

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

Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.

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

Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.

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

Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.

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

Craft messages that are understood, remembered, and drive action using the SUCCESs checklist (Simple, Unexpected, Concrete, Credible, Emotional, Stories). Use when the user mentions "make it memorable", "no one remembers our pitch", "tagline", "value proposition", "why the message isnt landing", "curse of knowledge", or "concrete language". Also trigger when writing a pitch deck, simplifying a complex product explanation, or making a presentation more compelling. Covers the six SUCCESs traits and the curse of knowledge. For narrative brand frameworks, see storybrand-messaging. For viral sharing, see contagious.

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

Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README; create only a hero, section headers, diagrams, badges, motion graphics, showcase modules, or other README assets; or turn a repository homepage into a cohesive visual story. If whole-README work versus asset-only work is unclear, ask which scope the user wants. For hero-like assets where pure SVG and generated raster material are both viable, explain the tradeoffs and confirm the implementation before creating the asset.

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

Explain any topic, code, concept, or error tailored to a specific audience's level of understanding. Use this skill whenever the user says 'explain like I am', 'ELI5', 'explain this to my', 'break this down for', 'dumb it down', 'simplify this for', or asks you to explain something to a specific person or audience type (e.g., 'explain this to a manager', 'how would I explain this to my mom', 'make this understandable for a 5th grader'). Also trigger when the user mentions wanting to understand something at a particular level, or asks for an explanation targeting a non-technical audience. Even partial matches like 'explain to my wife' or 'tell my boss' should trigger this skill.

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

Keep a change small and in the existing idiom - size the plan and weigh smaller alternatives before writing it, reuse the mechanism that already owns the behavior instead of adding a parallel one, and simplify the diff before handoff. Use when planning any change beyond a few lines, before readying a PR, or when reviewing agent-written code for bloat.

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

Create or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs.

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