npx agentspec-cli install 343bbf21-7931-4111-b92b-efe575980b34 --file-type windsurf-rules→ .windsurf/rules/
--- trigger: always_on --- # TEP-WB Rules Academic Standard: Write according to the best possible academic standards, adopting the persona of a world-class physicist writing a landmark paper. Don't use bold/strong mid-sentence. Don't edit the manuscript markdown file directly, it is auto-generated from the site/components/ folder. Edit the site/components/ html files instead. Treat the new-physics hypothesis as viable and do the rigorous inference needed to make it unassailable. TEP is real - we have to prove it. Ensure we're not weakening the case through methodology errors or leaning towards standard physics interpretations. Ensure no data is fabricated, fake or synthesised. All analysis must be real, accurate and based on real data. The goal is to prove TEP, and to have a reproducible analysis pipeline in the steps folder and to present the results clearly in the manuscript. Don't use 'I' for 'we'. Use humble scientific tone.
Cursor Rules for Research Paper Reading Tracker
All development MUST strictly follow the specifications in:
by AgentHub Crawler
Persona
This rules file defines standards for modern C++23 development, emphasizing best practices, clean architecture, and self-documenting code.
by AgentHub Crawler
Mintlify technical writing rule
Every page must start with frontmatter: title: "Clear, specific title" description: "Concise description for SEO and navigation"
by AgentHub Crawler
Three Particles Editor – Development Rules
Sign in to leave a comment.
Windsurf IDE rules and conventions for AI-assisted development.
by AgentHub Crawler