Skip to content

feat: Add Cursor mastery blog post and update post rules - #82

Closed
wghglory wants to merge 4 commits into
mainfrom
topic/derek/cursor-post
Closed

wghglory wants to merge 4 commits into
mainfrom
topic/derek/cursor-post

Conversation

@wghglory

@wghglory wghglory commented Jan 11, 2026 •

Copy link
Copy Markdown
Owner

Add Cursor Mastery Blog Post, Custom Commands, and Refactor Tables

Summary

This PR adds a comprehensive blog post about mastering Cursor AI, introduces two new custom Cursor commands (/pr and /notion-post), and refactors all existing blog posts to use standard markdown tables instead of a custom React Table component.

Changes

✨ New Features

  1. New Blog Post: "Mastering Cursor - From Chatbot to Pair Programmer"

    • Comprehensive 8-phase guide covering:
      • Philosophy and mindset shift
      • Core toolkit (Tab, Inline Edit, Modes)
      • Context mastery with @ symbols
      • Planning & design workflows
      • Project configuration (Rules)
      • Advanced workflows (TDD, Debug Mode, Custom Commands)
      • Team collaboration patterns
      • Quick recipes for common tasks
    • Properly formatted with frontmatter, topics, and cover metadata
    • Uses standard markdown tables throughout (aligned with updated rules)
  2. New Custom Command: /pr

    • Enables AI-powered pull request creation and code review
    • Automatically analyzes code changes, generates PR descriptions, and performs code reviews
    • Includes workflow documentation, error handling, and usage examples
    • Located in .cursor/commands/pr.md
  3. New Custom Command: /notion-post

    • Enables creating blog posts directly from Notion pages via MCP server
    • Includes workflow documentation, error handling, and usage examples
    • Located in .cursor/commands/notion-post.md

🔧 Updates

  1. Post Creation Rules Update (.cursor/rules/post.mdc)

    • Changed table generation guidance from React <Table> component syntax to standard markdown table syntax
    • Aligns with existing remark-gfm support in the codebase
    • Simplifies post creation process
  2. Refactored Existing Blog Posts

    • Replaced custom <Table> components with standard markdown tables in:
      • angular-component.mdx
      • angular-form.mdx
      • angular-pipe.mdx
      • angular-service.mdx
      • angular-structural-directive.mdx
    • All tables now use consistent markdown syntax
  3. Component Cleanup

    • Removed components/share/MdxComponents/Table.tsx (no longer needed)
    • Updated components/share/MdxComponents/index.tsx to remove Table import
    • Documentation updated in docs/markdown-tables-support.md to reflect markdown-only approach

Files Changed

New Files:

  • content/posts/mastering-cursor-from-chatbot-to-pair-programmer.mdx
  • .cursor/commands/pr.md
  • .cursor/commands/notion-post.md

Modified Files:

  • .cursor/rules/post.mdc
  • components/share/MdxComponents/index.tsx
  • content/posts/angular-component.mdx
  • content/posts/angular-form.mdx
  • content/posts/angular-pipe.mdx
  • content/posts/angular-service.mdx
  • content/posts/angular-structural-directive.mdx
  • docs/markdown-tables-support.md

Deleted Files:

  • components/share/MdxComponents/Table.tsx

Breaking Changes

None. This is a purely additive change with refactoring that maintains backward compatibility.

Testing Instructions

  1. Verify Blog Post Rendering:

    • Navigate to /posts/mastering-cursor-from-chatbot-to-pair-programmer
    • Check that all markdown tables render correctly
    • Verify frontmatter is properly parsed (title, topics, cover, etc.)
    • Ensure all links in References section work
  2. Verify Refactored Posts:

    • Check all Angular blog posts still render correctly
    • Verify all markdown tables display properly with existing styling
    • Confirm no broken table components remain
  3. Verify Rule Update:

    • Create a test post using the updated rule
    • Confirm that standard markdown tables are used instead of <Table> components
    • Verify tables render correctly with existing styling
  4. Verify Command Documentation:

    • Review .cursor/commands/pr.md and .cursor/commands/notion-post.md for clarity
    • Ensure workflow steps are accurate and complete

Code Review Notes

✅ Code Quality

  • All files follow project standards
  • Command documentation is consistent with updated rules
  • Blog posts use proper markdown table syntax
  • Topic validation passes (AI exists in TopicType)
  • Cover image uses proper Unsplash URL format
  • No linter errors detected
  • Component cleanup properly removes unused code

📝 Documentation

  • New commands are well-documented with usage examples
  • Post rules clearly specify markdown table syntax
  • Documentation updated to reflect markdown-only approach

Checklist

  • Blog post follows frontmatter structure
  • All tables use standard markdown syntax
  • Topics are valid (AI exists in TopicType)
  • Cover image URL is accessible
  • References section includes working links
  • Command documentation consistent with rule changes
  • Unused Table component removed
  • All refactored posts tested
  • No linter errors

@vercel

vercel Bot commented Jan 11, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
my-website Ready Ready Preview, Comment Jan 11, 2026 2:05pm

@netlify

netlify Bot commented Jan 11, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for derekw ready!

Name Link
🔨 Latest commit ae35f3e
🔍 Latest deploy log https://app.netlify.com/projects/derekw/deploys/6963ae06b281530008924015
😎 Deploy Preview https://deploy-preview-82--derekw.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@wghglory wghglory left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review Summary

Overall, this PR is well-structured and follows project standards. The changes are consistent and the blog post is comprehensive.

✅ Strengths

  • Blog post follows proper frontmatter structure
  • All markdown tables use standard syntax (aligned with remark-gfm)
  • Command documentation is clear and comprehensive
  • Rule update simplifies post creation workflow
  • All files are consistent with project standards

📝 Review Comments

See inline comments for specific feedback on key areas.

Code quality looks excellent! The inconsistency in the /notion-post command has been fixed, and everything aligns with the updated rules. Ready for review/merge! 🚀

Comment thread .cursor/rules/post.mdc
- cover.subtitle: A short, catchy sub-header relevant to the post.

Table Generation using below syntax instead of markdown table:
Table Generation: Use standard markdown table syntax:

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Excellent update! Changing from React <Table> component syntax to standard markdown tables aligns perfectly with the existing remark-gfm support in the codebase. This simplifies the post creation process and makes it more accessible.


Cursor has distinct modes for different stages of development.

| Mode | Best Used For | Capabilities |

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Great use of standard markdown tables! All tables in the post (lines 60-65, 73-78, 243-248) correctly use markdown syntax, which will render properly with the existing remark-gfm configuration.


4. **Save Post**
- Save to `content/posts/{kebab-case-title}.mdx`
- Follow the structure defined in `.cursor/rules/post.mdc`

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Well-documented command! The workflow is clear and the error handling section is comprehensive. Good that it references .cursor/rules/post.mdc to ensure consistency with the updated table syntax rules.

A comprehensive guide on shifting from treating AI as a snippet generator to using it as a fully integrated Junior
Developer in Cursor.
cover:
banner: https://images.unsplash.com/photo-1677442136019-21780ecad995?w=1200&q=80

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Frontmatter is properly structured with all required fields. The "AI" topic is valid in TopicType, and the Unsplash cover image URL is well-formatted with proper query parameters.

@wghglory wghglory left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review Summary

This PR introduces excellent improvements to the codebase. Here's my review:

✅ Strengths

  1. New Custom Commands: Both /pr and /notion-post commands are well-documented with clear workflows, usage examples, and error handling.

  2. Clean Refactoring: The migration from React Table components to standard markdown tables is thorough and consistent across all Angular blog posts.

  3. Component Cleanup: The unused Table.tsx component and its import have been properly removed, keeping the codebase clean.

  4. Documentation Updates: The post rules and markdown tables documentation have been updated to reflect the new approach.

  5. New Blog Post: The "Mastering Cursor" post is comprehensive, well-structured, and follows all frontmatter requirements.

📝 Code Quality

  • ✅ No linter errors detected
  • ✅ All files follow project standards
  • ✅ Consistent markdown table formatting
  • ✅ Proper component cleanup
  • ✅ Documentation is clear and accurate

🎯 Recommendations

  1. Testing: Consider manually testing the new blog post rendering to ensure all markdown tables display correctly with existing styling.

  2. Verification: Verify that no other posts in the codebase still use the old <Table> component syntax.

Overall Assessment

This is a high-quality PR that improves code maintainability, adds valuable new commands, and introduces excellent content. The refactoring is clean and consistent. Ready to merge after manual testing verification.

Great work! 🚀

Comment thread .cursor/commands/pr.md
@@ -0,0 +1,129 @@
---

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent documentation! The /pr command is well-structured with clear workflow steps. The inclusion of code review standards and error handling makes this a comprehensive guide. The example at the end is particularly helpful for users.

@@ -4,7 +4,6 @@ import Bilibili from './Bilibili';
import CodeFrame from './CodeFrame';
import Pre from './Pre';
import Quote from './Quote';

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good cleanup! The Table import and export have been properly removed. This ensures no unused code remains in the codebase. The component removal is consistent with the migration to markdown tables.

],
]}
/>
| Name | Description |

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great refactoring! The markdown tables are well-formatted and maintain readability. The conversion from the React Table component to standard markdown syntax is clean and consistent. All table data has been preserved accurately.

@@ -0,0 +1,281 @@
---

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent blog post! The frontmatter is properly structured with all required fields. The content is comprehensive and well-organized into 8 phases. The markdown tables are correctly formatted, and the References section includes working links. The cover image URL uses proper Unsplash format with query parameters.

Comment thread .cursor/rules/post.mdc
- cover.subtitle: A short, catchy sub-header relevant to the post.

Table Generation using below syntax instead of markdown table:
Table Generation: Use standard markdown table syntax:

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect update! The rule now clearly specifies standard markdown table syntax instead of the React Table component. The example is clear and matches the format used throughout the refactored posts. This will help ensure consistency for future posts.

| Use Case | Simple object creation | Patches, deep updates, large forms |
```

## Styling

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good documentation update! The removal of the Custom Table Component section is appropriate since we're standardizing on markdown tables. The documentation now accurately reflects the markdown-only approach. The formatting improvements (added blank lines) enhance readability.

@wghglory wghglory closed this Jan 11, 2026

This branch was successfully deployed

1 active deployment
Preview — ae35f3ec Deployed Jan 11, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant