Coding Skills and Projects for Real Code Changes

Find Skills and software for React performance, debugging, testing, code review, and behavior-preserving refactoring.

Work Inside an Existing Codebase

Start with the change you need to make: a failing behavior, a slow render, a risky diff, or an unclear type. React guidance, TDD instructions, coding agents, and static-analysis tools help at different stages. A Skill describes a method; a project supplies software or supporting resources. Match both to the repository’s language and test setup before changing code.

Skills supply instructions; projects supply software or supporting resources. Check each source for setup, runtime, access, and license requirements.

Choose by the Job

A Behavior Change Needs Tests

Start with TDD when the expected behavior can be stated and checked before implementation.

A Failure Has No Clear Cause

Use diagnosis or investigation guidance to rank evidence before editing the suspected code.

A Codebase Needs Improvement

Choose React-specific guidance for performance issues, or Safe Refactor when behavior must remain unchanged.

Explore Related Task Categories

Find instructions and software for the next stage of your work, from code changes and interface design to office tasks and media production.

Frequently Asked Questions

How should I choose between debugging, TDD, and refactoring guidance?
Start with the current uncertainty. Debugging investigates why behavior is wrong; TDD makes an expected behavior executable; refactoring improves structure while preserving behavior. A single task may move through all three, but they answer different questions.
What makes a useful bug report for a coding agent?
Provide the smallest reproducible example, expected and actual behavior, relevant errors, and the environment where the issue occurs. A failing test or concrete input is more actionable than a general statement that the code is broken.
Should every change begin with a new test?
A test is valuable when it can detect the behavior or regression at issue. Exploratory work may first need a clearer requirement; cosmetic changes may need visual checks. Avoid tests that merely repeat the implementation without checking a meaningful outcome.
How can I verify that a refactor preserved behavior?
Record the behavior that must remain stable, run relevant checks, and review the diff for accidental scope changes. Passing tests are useful evidence, but untested interfaces and error paths may still need targeted inspection.
When should I use React-specific performance guidance?
Use it when the problem involves React or Next.js concerns such as rendering, data fetching, state, or bundle size. Measure the actual application so a plausible optimization does not become an unverified change with no demonstrated benefit.
Can several coding Skills be combined in one task?
Yes, when their roles are clear. For example, reproduce a failure, isolate the cause, make a small change, and then inspect the diff. Resolve conflicting instructions and keep one acceptance criterion rather than layering unrelated checklists.
How do coding Skills differ from the listed software?
A Skill describes a method such as reviewing a diff or investigating a failure. A coding agent, compiler, or analysis tool supplies execution or analysis capabilities. Check language support and the existing test environment before combining them.

Keep Code Changes and Reviews Together

Bring the task, repository context, tests, and review decisions into one workspace.