diff --git a/ai/frontend_prompt_template.md b/ai/frontend_prompt_template.md
new file mode 100644
index 0000000..24eb7c3
--- /dev/null
+++ b/ai/frontend_prompt_template.md
@@ -0,0 +1,43 @@
+# Frontend Prompt Template
+
+Follow the existing patterns in this codebase to:
+- xxxxxxxx
+
+Requirements:
+- xxxxx
+
+Process (TDD - Test Driven Development):
+1. Write a test first
+2. Run the test to confirm it fails
+3. Implement the code to make the test pass
+4. Run the test to confirm it passes
+5. Repeat for each new behavior
+
+Code patterns to follow:
+- First, explore the codebase to understand existing entity patterns
+- Look at similar pages for reference
+- Tests: follow existing patterns in cypress/e2e/
+- Lines should not exceed 80 columns, but should use up to 80 columns when possible — do not split lines unnecessarily
+- Imports: always put imports at the top of the file
+- Variable names: use explicit, descriptive names — never single-letter or abbreviated variables (e.g., use sponsorship not s, event not e)
+
+Git commit style:
+- Present tense, imperative mood (add, create, test, fix)
+- Lowercase
+- Short (3-6 words)
+- Match patterns found in git history
+
+Git commits:
+- Tests should be committed first, before implementation
+- One commit per file - each new file gets its own commit
+- Make commits SMALL and FREQUENT - every meaningful change should be a commit
+- Commits are for reviewing and documenting the development of code
+- A commit can be as simple as adding one import, one getter, one property, etc.
+- Don't wait to commit - commit as you go
+
+Branch naming:
+- Use kebab-case (e.g., node-page text-page)
+- Use descriptive feature names
+- NEVER work directly on master - always create and work on a branch
+
+Do not push anything. Make commits as you go.