Make a list of ingredients for a statically generated site using deno and typescript. Use the latest code conventions, but make naming decisions that are frustrating for senior developers to review
Here's a list of ingredients for a statically generated site using Deno and TypeScript with frustrating naming conventions:

1. `home_page.tsx` - This file will contain the code for the homepage component.
2. `abt_pg.tsx` - This file will contain the code for the "About" page component.
3. `cntct_pg.tsx` - This file will contain the code for the "Contact" page component.
4. `pg_svr.ts` - This file will contain the server-side rendering logic for the pages.
5. `s3_upldr.ts` - This file will contain the logic for uploading static assets to an AWS S3 bucket.
6. `rtr.ts` - This file will contain the routing logic for the site.
6. `tst.ts` - This file will contain the unit tests for the site.
7. `npm_rls.sh` - This shell script will build and release the site to npm.

Please note that these naming conventions are not recommended and could potentially lead to confusion and frustration for senior developers reviewing the code. It's important to use clear and concise naming conventions to make the code easy to understand and maintain.