Development preview · Evaluation pending
React app starter bundle
Plan a small interactive form, separate reusable state, and test what the user can do.
For an existing React project. Choose dependencies and routing to match the project; this is not an app scaffold.
Download the reference plan
Reference manifest only: selection notes, skill IDs, and public catalog links. No skill bodies, executable code, credentials, or host configuration are included. Downloading does not install or enable skills.
Markdown is a reading plan; JSON is a SkillDB reference manifest. Neither is a host-specific install package.
Why these skills fit together
Accessible Forms defines interaction requirements; Testing Library turns some of them into assertions. Custom Hooks covers state ownership. The two form-focused references are intentionally complementary, not two competing form frameworks.
1. State and reusable behavior
Custom Hooks
Use its composition and cleanup discussion to decide whether repeated stateful logic deserves a hook.
Review note: Some examples read window during initialization. Adapt and test them for server rendering; sample fetching code is not a production data layer.
React Patterns · Open catalog reference
2. Form interaction requirements
Accessible Forms
Covers labels, field grouping, error association, and focus after an invalid submission.
Review note: HTML examples need adaptation to React. Check the actual browser and assistive-technology behavior after implementation.
Accessibility · Open catalog reference
3. Behavioral regression tests
Testing Library
Covers queries by role or label, user events, and waiting for asynchronous results.
Review note: A passing role query does not prove screen-reader usability. Keep manual checks and use the test runner already chosen by the project.
Testing Services · Open catalog reference
Try a representative task
Build a settings form with async submission, field errors, and a recoverable network failure in a sample React project.
- Verify labels, keyboard submission, pending feedback, and retained input after failure.
- Test the successful submit and failed-request paths through user-visible behavior.
- If extracting a hook, test cleanup and isolate state between two consumers.
This evaluation has not been run. Compare the same task with and without these references using the same environment and checks, and record outcomes before claiming an improvement.