Prompt
Review this app for /security. Are public routes public, and are private routes or features protected? Are keys and tokens out of the code? Find the issues, then give me a plan for what to handle first, second, and third.
/security
v0.2 · Updated Sep 22, 2026
How do I know my app is secure and ready for active customers?
Security is a big topic. These are the simple things to check. This skill finds the issues and builds a plan for what to handle first, second, and third.
-
1. Public and private
Are public routes public, and are private routes or features protected?
-
2. Keys and tokens
Are you keeping keys and tokens out of the code?
Five things this rule looks for
- A route that should be public is locked, or a route that should be private is open.
- A feature only some people should use can be reached by anyone who knows the address.
- A key, token, or secret is sitting in the code, or in a file that gets committed.
- You can see the issues, and you do not yet have an order for first, second, and third.
- Active customers are close, and the private parts are still unprotected.
Here is how you get started. Copy this and drop it into your CLI.
npx skills add StephanSmith-me/builder-skills Or go to the repo to get more instructions.