react-component-cleaner

作成者: langfuse

このスキルを使用して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.

langfuseのその他のスキル

clickhouse-best-practices
langfuse
ClickHouseのスキーマ、クエリ、または設定をレビューする際には必ず使用すること。推奨事項を提供する前に必ず確認すべき28のルールが含まれています。常に読んでください…
official
skill-creator
langfuse
効果的なスキルを作成するためのガイド。このスキルは、ユーザーがClaudeの機能を拡張する新しいスキルを作成(または既存のスキルを更新)したい場合に使用されるべきです。
official
vercel-react-best-practices
langfuse
Vercel EngineeringによるReactおよびNext.jsのパフォーマンス最適化ガイドライン。このスキルは、React/Next.jsのコードを記述、レビュー、またはリファクタリングする際に使用すべきものです。
official
add-model-price
langfuse
Use when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing tiers, tokenizer IDs, or matchPattern regexes…
official
analyze-cloud-costs
langfuse
Metabaseのコストマートを使用してLangfuse Cloudインフラストラクチャのコスト構造を分析します。クラウド支出、AWS対ClickHouseのコスト配分、コスト…について質問されたときに使用します。
official
backend-dev-guidelines
langfuse
Build or review Langfuse backend code. Use for tRPC routers, public REST APIs, BullMQ processors, services, middleware, Prisma or ClickHouse access,…
official
clickhouse-best-practices
langfuse
ClickHouseのスキーマ、クエリ、または設定をレビューする際に必ず使用すること。推奨事項を提供する前にチェックしなければならない28のルールが含まれています。常に読むこと…
official
code-review
langfuse
Review Langfuse code changes for correctness, regressions, and best practices.
official