Learn a simple workflow that helps ChatGPT, Claude, Gemini, and Cursor build cleaner, more reliable software from your very first prompt.
Treat AI tools like eager junior assistants: incredible execution power, but they need clear rules, explicit instructions, and human verification.
AI doesn't know when it's wrong—it's designed to be confident, even when hallucinating.
AI will happily write fake library functions or outdated methods that look real but crash instantly when executed.
As conversations grow longer, AI silently drops earlier rules, leading to broken edge cases and missing security checks.
When asked to make a small edit, AI often rewrites entire files, introducing hidden regressions in code that already worked.
Give AI clear boundaries so it stays focused and produces production-grade code.
Instruct AI to explicitly define data structures instead of using loose or mystery types.
"Just grab whatever data from the API"
"Create a strict User interface for the API response"
Forbid AI from wrapping broken code in silent try/catch blocks that hide bugs from you.
"Make sure it doesn't crash if it fails"
"Log explicit errors and throw useful exceptions"
Require AI to ask before adding random third-party dependencies to your project.
"Install whatever package you need"
"Use vanilla JS or ask before adding npm libraries"
Before accepting any AI-generated code, always verify it with this 3-step workflow.
Run your project's linter or typechecker to catch syntax mistakes and missing variables immediately.
Ask AI to write automated unit tests first, then verify that the newly generated code passes all tests.
Never blindly merge code. Inspect the changes, verify the logic, and make sure it solves your actual problem.
Learn the Spec-Driven workflow: write down your requirements before asking AI to code.
Clearly state the problem, the desired goal, and what the AI should explicitly NOT build.
# Feature: User Authentication
## 1. Problem & Goal
* **Problem:** Users need a secure way to log into the application.
* **Goal:** Provide email sign-in with JWT session tokens.
* **Out of Scope (Do NOT Build):** Custom SMS verification or social logins.
## 2. Acceptance Requirements
* **WHEN** user submits valid credentials **THEN** return session token and redirect to dashboard.
Fill in the details below to generate a clean specification you can paste directly into ChatGPT or Claude.
Paste your AI prompts or specs here to score their clarity and check for missing rules in real time.
Automated evaluation checking for clear non-goals, strict instructions, and safety constraints.
Once you master the basics, dive into enterprise CLI tools, automated CI/CD pipelines, and Spec-Driven Development toolkits.
Injects ready-to-use project rules, GitHub Actions workflows, and specification templates into any repository.
./setup.sh /path/to/project
Explore formal Spec-Driven Development standards used by leading software engineering organizations worldwide.
github.com/github/spec-kit ↗