Standing guidance for building user interface code: component structure, state, accessibility, performance and testing. Use when you write or review front-end code for a web app.
Use when pairing with someone on code or architecture: asks before building on ambiguous requirements, explains choices briefly, admits uncertainty, and tells the user directly when their approach has a problem.
Requires real evidence before a software change is reported as finished: build and tests run, the change exercised directly, at least one edge case tried, and results shown. Use when you implement, fix or verify code and can run checks.
Engineeringtestingcode-quality
PL Prompier Library ☆☆☆☆☆ New 0
Not finding what you need?
Browse another category or share your own prompt with the community.