Instruction file imported from alesanchezr/full-stack-with-ai (.cursor/rules/all-events.mdc). Copyright stays with the author.

The following rules apply for all the events written under content/events folder

Name: all-events
Author: alesanchezr

Every events needs to have a front matter at the top of the markdown file with the event meta information like:
- starting_at: date and time (utc and in the future)
- ending_at: it has to be later than starting_at, date and time in utc format
- title: string with less than 150 characters
- excerpt: SEO friendly string description with less than 220 characters

About the Event title

The title must invite people to come to the event, they need to understand what they are getting from this event, what will they gain from it, for example:

Example 1: "Vibe Coding: build a tech product from zero to launch in 20min"
Example 2: "Bridging Innovation: Celebrating the Impact of the Miami_Israel Collective"

About the event description

The event description cannot be longer than 600 characters.

This rule provides guidelines for writing compelling, informative, and effective event descriptions.

General Structure

Start with a compelling headline that c dlearly states the event name
Include a concise summary paragraph (2-3 sentences) at the beginning
Use subheadings to break up content into logical sections
End with a clear call-to-action

Essential Information (Must Include)

Date and time (including timezone)
Location (physical address or virtual access details)
Price/cost information (including free if applicable)
Registration/RSVP requirements and deadlines
Target audience/who should attend
Host/organizer information
Duration of the event

Content Best Practices

Use active voice and present tense where possible
Front-load the most important information
Incorporate relevant keywords naturally for SEO
Use bullet points for easy scanning of key details
Keep paragraphs short (3-5 sentences maximum)
Avoid jargon unless appropriate for the target audience
Highlight unique selling points and benefits of attending
Address potential questions or objections

Tone and Style

Be enthusiastic but authentic
Convey a sense of urgency without being pushy
Match the tone to the event type (professional for business events, fun for social gatherings)
Use second-person ("you") to directly address the reader
Include sensory details to help readers imagine the experience

Formatting for Readability

Use bold for key information (dates, times, locations)
Italicize speaker quotes or testimonials
Include a relevant, high-quality featured image
Use numbered lists for sequential information (like agenda items)
Maintain consistent formatting throughout

For Virtual Events

Clearly indicate the event is online
Specify which platform will be used
Mention if recording will be available afterward
Include technical requirements
Explain how participants will interact

Mobile Optimization

Keep sentences and paragraphs concise for mobile reading
Ensure all CTAs are tap-friendly
Front-load critical information for mobile readers

Call-to-Action Guidelines

Make registration/RSVP buttons prominent
Use action verbs (Register, Join, Secure Your Spot)
Create a sense of scarcity when appropriate ("Limited seats available")
Include sharing options for social media

{ "ocm": "1", "id": "alesanchezr-full-stack-with-ai-all-events-rule", "kind": "skill", "name": "all-events", "description": "The title must invite people to come to the event, they need to understand what they are getting from this event, what will they gain from it, for example:", "publisher": "alesanchezr", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "The title must invite people to come to the event, they need to understand what they are getting from this event, what will they gain from it, for example:" ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/alesanchezr/full-stack-with-ai", "path": ".cursor/rules/all-events.mdc", "ref": "8faeb7470b3ad07698a9dd2f1ffbefc70819fb60", "url": "https://github.com/alesanchezr/full-stack-with-ai/blob/8faeb7470b3ad07698a9dd2f1ffbefc70819fb60/.cursor/rules/all-events.mdc", "key": "alesanchezr/full-stack-with-ai/.cursor/rules/all-events.mdc" }, "applies_to": "content/events/*.md" }, "instructions": "# The following rules apply for all the events written under content/events folder\n\n- Every events needs to have a front matter at the top of the markdown file with the event meta information like:\n - starting_at: date and time (utc and in the future)\n - ending_at: it has to be later than starting_at, date and time in utc format\n - title: string with less than 150 characters\n - excerpt: SEO friendly string description with less than 220 characters\n \n\n## About the Event title\n\nThe title must invite people to come to the event, they need to understand what they are getting from th", "cost": { "context_tokens": 822 } }

all-events

About