AI SummaryA Windsurf prompt for building and rendering minimal form fields with a focus on incremental, rule-based development practices. Useful for developers creating embedded form solutions who need clear guidance on implementing features through small, testable iterations.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "tiny-form-fields — Windsurf Rules" prompt rules to my project. Repository: https://github.com/choonkeat/tiny-form-fields Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Tiny form field builder and renderer for embedding into web apps
Directories
• src/: source code • tests/: test code • tasks/: task files • dist/: compiled code
The smallest possible change
For example, if a task requires "Add checkbox to toggle Show/Hide", many would implement it as: • Add a new field to the model • Add checkbox UI and wire up events • Implement the show/hide logic • Add styling/animations But that's actually too many changes at once! Instead, we should do it as: Iteration 1: Just the model • Add boolean field to model • Update decoder/encoder • Nothing else Iteration 2: Just the UI presence • Add checkbox element • Wire up event handler • Nothing else Iteration 3: Just the logic • Implement show/hide logic • Nothing else Iteration 4: Just the UX • Add styling/animations • Nothing else Each iteration above is "the smallest possible change". Never combine them into one iteration.
One iteration at a time
• Make only the smallest possible change at every iteration • Run make build to confirm it didn't break anything • if something broke, it means the change was incomplete; make the remaining changes instead of only fixing the error • Only if that's successful, then ask for permission to make the next smallest change (repeat step 1 and 2)
Preserving Existing Code
• Never remove or modify existing code that isn't directly related to your task • If you accidentally remove code, restore it immediately before proceeding • If unsure whether code is related to your task, assume it isn't and leave it unchanged
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts