react-component-cleaner

Используйте этот навык для очистки компонента React. Применяйте его только по указанию пользователя.

npx skills add https://github.com/langfuse/langfuse --skill react-component-cleaner

The goal of this skill is to clean up a React component. The changes are meant to be non-breaking and auditable, therefore the instructions below should be followed carefully.

Avoid making any additional edits besides the ones instructed in this skill. If you are unsure about any of the instructions or need to do a one-off edit, ask the user for confirmation. You are allowed to invoke formatting and linting commands. If there are formatting / linting issues, do not make manual edits to reformat code, always use the fix variants of the commands.

Before starting to do any changes, audit the component you were instructed to fix by reading the react-component-guidelines skill. Do not audit the callsites of the component, these will be looked at later in the skill.

This skill references a sweepy cli tool. This can be found under https://github.com/bezbac/sweepy. Unless already available, install version v0.1.0, pinned to commit e58b55c0fb94364c12798ed16e632a5931b4eaa1: https://github.com/bezbac/sweepy/tree/e58b55c0fb94364c12798ed16e632a5931b4eaa1. Follow only that pinned commit's instructions to install it. Do this in a safe manner and comply with other security guidelines of the repository. If you are unsure about any of the instructions, ask the user for confirmation.

Now, you are ready to start cleaning up the component. Copy the contents of the component cleanup todolist verbatim into a TODO file (Use cp no manual edit) and follow the instructions in order, adding ✅ to the items you have completed. Do not commit the todo file, it is only for your reference.


Notes:

  • When moving classes into a variant, the variant must own the complete set of classes for every CSS property it changes.

    • Remove those property classes from the component's base classes.
    • Ensure exactly one variant branch supplies each property. Do not rely on cn, tailwind-merge, CSS order, or specificity to resolve conflicting classes. Prefer an exhaustive lookup table or cva variants.
  • The sweepy cli by default assumes an interactive mode, but it can be run in a non-interactive mode by passing the --yes flag. This will automatically accept all changes and is useful for automation.

  • The sweepy cli has a --dry-run flag that can be used to preview the changes that will be made without actually making them.

Больше skills от langfuse

frontend-browser-review
langfuse
Используйте этот навык, когда изменение влияет на то, что пользователи видят или делают в браузере.
frontend-large-feature-architecture
langfuse
Используйте при создании, изменении или рефакторинге крупных функций фронтенда Langfuse, виртуализированных списков, больших таблиц, компонентов-контроллеров, локальных функций…
skill-developer
langfuse
Создание и управление навыками Claude Code в соответствии с лучшими практиками Anthropic. Используйте при создании новых навыков, изменении skill-rules.json, понимании триггеров…
langfuse-prompt-migration
langfuse
Мигрировать жестко закодированные промпты в Langfuse для контроля версий и итераций без развертывания. Используйте, когда пользователь хочет вынести промпты наружу, перенести промпты в Langfuse,…
incident-alert-tickets
langfuse
Read and, after human approval, update the Linear `incident-alert` knowledge base. Use before and after investigating a named Datadog monitor,…
refactor-react-effects
langfuse
Рефакторинг избыточного использования React useEffect в коде фронтенда Langfuse. Используйте при добавлении, ревью или удалении эффектов; инициализации форм или локального состояния UI из…
sentry-instrumentation
langfuse
Decide whether and how errors report to Sentry. Use when touching capture or error-handling paths in `web/**`, triaging Sentry noise, or changing Sentry…
posthog-instrumentation
langfuse
Product analytics with posthog. Use when adding a meaningful user action or feature in `web/**`, touching PostHog capture code, or answering product-usage…