feat: add Full-Stack AI Engineering Playbook rules#301
Conversation
Added enterprise-grade AI behavior rules and full-stack guidelines to the playbook, focusing on architectural standards, token optimization, and security practices.
- Added a new 'Project Initialization' section detailing distinct paths for brand new projects (Scenario A) and legacy/existing codebases (Scenario B). - Restructured the 'Daily Operating Workflow' to clearly separate feature development, debugging, and code review phases. - Highlighted token optimization strategies to minimize API costs and prevent context bloat. - Organized the 'System Index' with direct links to all playbook files for faster navigation inside the IDE. - Improved overall readability, visual hierarchy, and formatting.
📝 WalkthroughWalkthroughAdds a new Cursor rules file that documents enterprise-grade AI behavior guidelines, including core directives, frontend/backend architecture boundaries, and security practices. The playbook is registered in README.md with a link and description. ChangesFull-Stack AI Engineering Playbook
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@rules/fullstack-ai-engineering-playbook.mdc`:
- Line 3: The rule currently uses a non-recursive pattern "globs: *" which won't
match nested files; update the globs entry in
rules/fullstack-ai-engineering-playbook.mdc to use a recursive pattern like
"globs: **/*" so it matches files in subdirectories—locate the "globs" key in
that file and replace the "*" value with "**/*" to align with the other rules.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ce106d39-514e-4b96-8876-a23741a9a71a
📒 Files selected for processing (2)
README.mdrules/fullstack-ai-engineering-playbook.mdc
| @@ -0,0 +1,33 @@ | |||
| --- | |||
| description: Enterprise-grade AI behavior rules, token optimization, and full-stack guidelines. Extracts from the Cursor AI Engineering Playbook. | |||
| globs: * | |||
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Read-only verification: inspect glob conventions used by existing rules
fd -e mdc . rules | xargs rg -n '^globs:\s*'
echo "---- potential non-recursive catch-all patterns ----"
fd -e mdc . rules | xargs rg -n '^globs:\s*\*$'Repository: PatrickJS/awesome-cursorrules
Length of output: 19331
Fix globs to ensure the rule applies to nested files — rules/fullstack-ai-engineering-playbook.mdc uniquely uses globs: * while the repo’s other rules use recursive patterns like globs: **/*; update it to match nested paths.
Proposed fix
-globs: *
+globs: **/*📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| globs: * | |
| globs: **/* |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@rules/fullstack-ai-engineering-playbook.mdc` at line 3, The rule currently
uses a non-recursive pattern "globs: *" which won't match nested files; update
the globs entry in rules/fullstack-ai-engineering-playbook.mdc to use a
recursive pattern like "globs: **/*" so it matches files in
subdirectories—locate the "globs" key in that file and replace the "*" value
with "**/*" to align with the other rules.
1 participant
Summary
Added a comprehensive
fullstack-ai-engineering-playbook.mdcrule. This rule provides enterprise-grade AI behavior constraints, focusing on token optimization, strict clean architecture boundaries (Frontend/Backend), and anti-hallucination directives. It also updates the README to include this new rule under the "Build Tools and Development" section.Contribution Type
rules/*.mdcruleValue To Cursor Users
This rule helps developers prevent common LLM mistakes such as over-engineering, modifying out-of-scope files, and breaking architectural boundaries. By enforcing strict constraints and a "Do Not Guess" policy, it significantly reduces token waste and maintains a clean, scalable codebase for full-stack applications.
Added Or Changed Files
rules/fullstack-ai-engineering-playbook.mdcREADME.mdQuality Checklist
react-typescript.mdc.rules/*.mdcfiles include frontmatter with a non-empty description, relevant globs, andalwaysApply: falseunless the rule is universal.Notes For Maintainers
This rule is a condensed, highly practical extraction from a larger open-source AI engineering playbook I maintain. It has been formatted strictly according to your
.mdcguidelines and frontmatter requirements. Thank you for maintaining this awesome list!Summary by CodeRabbit