'simplify' 검색 결과

Find, rank, and safely remove accidental codebase complexity by proving real consumers, dynamic entrypoints, compatibility obligations, duplicate representations, speculative surfaces, and lifecycle ownership. Use when asked to simplify or clean up a repository, reclaim code entropy, reduce over-engineering or redundancy, find deletion candidates, collapse duplicate state/APIs, remove dead or added-then-abandoned code beyond static-tool output, or implement an evidence-backed simplification pass in any language or stack. Also trigger for 代码化简、熵回收、删代码、清理冗余、收敛抽象、去除过度设计. Do not use as a performance audit unless simplification is the stated goal.

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

Rewrite and check technical writing to follow Simplified Technical English (ASD-STE100). Use when asked to simplify docs, rewrite in STE / plain technical English, write clear procedures or warnings, or flag hard-to-read or ambiguous technical text for a global / non-native audience.

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

Reviews an existing codebase for structural friction, unclear ownership, leaky or shallow interfaces, excessive coupling, misplaced state, poor testability, and risky dependency direction, then prioritizes evidence-backed improvement candidates. Use for architecture audits, modularization, modernization, or recurring cross-cutting change pain. Not for designing one new interface, simplifying a local function, or fixing a reproduced bug.

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

Analyse a learning task for cognitive load problems and recommend specific design improvements. Use when tasks overwhelm students, instructions feel complex, or materials need simplifying.

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

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.

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

When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.

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

Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does not apply fixes.

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

Make AI coding-agent messages to humans clear and easy to follow. Use for every user-facing update, explanation, review, question, and handoff in this repository, or when the user asks to simplify or rewrite an agent message.

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

Make AI coding-agent messages to humans clear and easy to follow. Use for every user-facing message in this repository, or when the user asks to simplify or rewrite an agent message.

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

The pedagogy of feeding — how to talk about food with children, what the Division of Responsibility model says, age-appropriate autonomy in eating, how to handle picky eating without creating disordered eating, and how to teach nutrition concepts to learners at different levels without either moralizing or oversimplifying. Use when a question is about raising, teaching, or advising a child or learner on eating, or when planning curriculum or parent guidance.

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

Symbolic manipulation, equation solving, and algebraic structures for mathematical reasoning. Covers distributive law, factoring, completing the square, linear through polynomial equation solving, systems of equations (substitution, elimination, Gaussian elimination, matrix methods), algebraic structures (groups, rings, fields), modular arithmetic, polynomial theory, and inequalities. Use when solving equations, simplifying expressions, working with algebraic structures, or performing symbolic manipulation.

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

Rewrites code to its simplest possible form while preserving exact external behavior (KISS, YAGNI).

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

Simplify cluttered UI by removing unnecessary elements, choices, features, and structural complexity. Use when the problem is too many controls, options, features, or competing elements—not when the structure is sound and the real issue is only visual intensity or lack of personality.

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

Use after EZ_math_model coding has produced src/*.py and before packaging when code quality, reuse, vectorization, naming, or unnecessary complexity should be reviewed without changing behavior.

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

Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels

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

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 a concept needs making clear rather than practising: explain simply, why does this exist, draw it, or simplify for a beginner. Not for scaffolded practice: use drill.

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

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

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

Use when the user says deslop, debloat, tidy, simplify, clean a diff, cleanup codebase, or deslop branch diff, or remove dead code or config. Not for remote, credential, publish, deploy, or irreversible changes.

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

Clean up a diff for reuse, simplicity and efficiency, then apply the fixes.

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

Design or revise Interpreter UI for non-developers with an ultra-minimal, utilitarian style inspired by the OpenAI website and ChatGPT, not the developer platform. Use when simplifying settings, onboarding, chat, forms, empty states, or helper copy; when removing extra containers, labels, or visual noise; when replacing technical wording with plain language; when clarifying hierarchy and making the main user action obvious; when making every visible label and status understandable to an average HR admin or other non-technical user; when hiding implementation details such as logs, IDs, endpoints, paths, or protocol names; or when a screen must respect the app's existing CSS variables and light/dark theme behavior.

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

"Apply Cognitive Load Theory to optimize instructional design by managing intrinsic, extraneous, and germane load within working memory limits. Use this skill when the user needs to diagnose why learners are overwhelmed, redesign training or documentation for better comprehension, evaluate UI/UX information architecture for cognitive burden, or when they ask 'why is this tutorial confusing', 'how to simplify complex instructions', or 'what causes information overload'.".

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

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

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

Prevents overengineering when designing, implementing, refactoring, or reviewing software. Use when the user asks to implement a feature, add an abstraction, refactor code, review a design, simplify existing code, or make an architectural decision. Also triggers when the user asks if code is too complex, whether to abstract something, or how to structure something. Do not use for deployment, infrastructure configuration, or debugging runtime errors unrelated to code structure.

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