Let's do a brainstorming session for **add your intent here**
We need to discuss all aspects (functionality, UI/UX, schema, technologies, etc.)
You ask me questions and show options with [ ]. Preselectt he recommended answer.
We can do multiple rounds, but only one round at a time.
In each round ask one or multiple questions.
Ask me one round of questions, I answer, then we repeat until it’s done.
Use visualization when useful.
The entire brainstorming must happen in specs/{nr}-{name}-brainstorming.md
Only ask questions there. I will add my answers there. Only append to the file; never change any existing questions or answers.
When all questions are answered, then write the full specs to specs/{nr}-{name}-specification.md
Don’t start implementation, as this is only about the brainstorming.
Do a GIT commit when specification is written.
Run this in the same conversation after you finished the brainstorming
This brainstorming went well. Build a skill “/spec” for other featurres,
/spec {description}
Create the skill in the project; not home dir
You need to have Playwright MCP installed
Find the specification of the first feature in specs/*
Implement the entire feature
Ensure the code is clean and follows best practices
Continuously keep track of the progress in specs/{nr}-{name}-progress.md
Commit after every relevant step.
Write a comprehensive testplan for a browser test in specs/{nr}-{name}-testplan.md
When done, you must verify the results non-scripted in the browser, using Playwright.
Fix all bugs. Only finish when all functions are verified.
Run this in the same conversation after you finished the development
Based on this development process and my initial prompt plus steering creates a /dev {name} skill command to build any upcoming specification.