236건 · 관련도순
Detects long-lived objects (caches, listeners, singletons) that capture an entire enclosing scope via closures/environment capture, keeping large arrays or buffers alive, and proposes copying only the needed fields.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects per-caller special-cases (bandaids) bolted onto shared infrastructure/common functions, and when two or more same-kind special-cases exist proposes generalizing the lower-level mechanism instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve clarity and reduce needless complexity after behavior is understood; preserve behavior and keep cleanup separate from correctness fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TOP PRIORITY skill — find and immediately fix or remove every piece of wrong, outdated, or redundant information in ToolUniverse docs. Wrong code, broken links, incorrect counts, and overlapping instructions must be fixed or removed — never left in place. Runs five phases: (D) static method scan, (C) live code execution, (A) automated validation, (B) ToolUniverse audit, (E) less-is-more simplification. Core philosophy: each concept appears exactly once; remove don't add; no emojis; single setup entry point. Use when reviewing docs, before releases, after API changes, or when asked to audit, fix, or simplify documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze a completed phase diff for high-confidence behavior-preserving simplifications and apply only explicitly approved proposals. Use after execution and before review to reduce duplication, dead code, needless complexity, or avoidable inefficiency.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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-cro. For lead capture forms (not account creation), see form-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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Streamline code by removing redundancy and aligning with repo style. Use when you need to consolidate logic, reduce indirection, clean up repeated patterns, or make code more concise.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill for internal Vue reactivity and state-model work in the nuxt-ui-tools repository. Covers lean reactivity, query-state integration, when to use computed vs watch vs shallowRef, VueUse usage, and how to simplify over-layered state models.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test Data Builder Pattern complete implementation guide. Used when using builder pattern to create maintainable test data or simplify complex object test preparation. Covers fluent interface, semantic methods, default value design, and Builder composition patterns. Keywords: test data builder, builder pattern test, test data builder, object mother, fluent interface, fluent interface, UserBuilder, ProductBuilder, .With(), .Build(), AUser(), test data preparation, complex object creation, semantic testing
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AutoFixture and NSubstitute Integration Guide - Implementing Auto-Mocking. Use when you need to automatically create mock objects and simplify testing of complex dependency injection. Covers AutoNSubstituteDataAttribute, Frozen mechanism, Greedy construction strategy. Includes customized handling for special dependencies like IMapper (AutoMapper/Mapster). Keywords: autofixture nsubstitute, auto mocking, AutoNSubstituteDataAttribute, auto-mocking, Frozen, AutoNSubstituteCustomization, AutoFixture.AutoNSubstitute, Greedy, fixture.Freeze, Received(), Returns(), IMapper, AutoMapper, Mapster, mapper testing
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete guide for AutoFixture and xUnit integration. Use when you need to use AutoData or InlineAutoData to simplify xUnit parameterized test data preparation. Covers custom Customization and test data attributes to improve test readability and maintainability. Keywords: AutoData, InlineAutoData, AutoFixture xUnit, [AutoData], [InlineAutoData], AutoDataAttribute, ICustomization, DataAttribute, parameterized test, Theory AutoData, MemberAutoData, test data attributes, fixture.Customize
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplify a bounded code area when the user explicitly requests behavior-preserving refactoring or a named complexity/readability problem is the accepted task; do not trigger automatically after implementation, during every review, for adjacent cleanup, or when behavior may change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.