The feeling of vomiting when the use case is written-- the General Test case Library

I have been writing use cases for several days in a row. Looking back, apart from the business, they are basically additions, deletions, changes, paging control checks, required checks, format checks, maximum length checks, special character checks, and uniqueness checks. Since this is the case, why not set up a general test case library to store these general use cases? This eliminates the need for each view page of each project to verify what can be edited, and each list page to verify that the paging works.

Through writing use cases this time, there is another feeling: when you write use cases, you first write according to the requirements document, resulting in very few use cases spent on writing business-related use cases, which is very bad, and the use case coverage is very low. No, no, no.