Best Practices

1. Provide context: Add markdown text around test links explaining what should be checked
2. Use headings: Organize related requirements under clear headings
3. Be specific: Describe expected behavior, edge cases, and constraints
4. Granular tests: Place [@test] links next to the requirements they verify. Create targeted test files for separate requirements.
5. Keep specs synchronized: Ensure specs stay up-to-date with implementation