slack-to-faq Cursor Rules — Cursor Rules | Neura Market
    Neura MarketNeura Market/Cursor
    ChatGPTChatGPTClaudeClaudeGeminiGeminiCursorCursorGrokGrokPerplexityPerplexityDeepSeekDeepSeek
    CoPilotCoPilotStable DiffusionStable DiffusionMidjourneyMidjourney
    View All Directories
    OverviewRulesPromptsMCPsAgentsBlogVideosGuidesCoursesCommunityExtensionsTrendingGenerate
    CursorRulesslack-to-faq Cursor Rules
    Back to Rules
    Frontend

    slack-to-faq Cursor Rules

    endpoint-data April 15, 2026
    0 copies 0 downloads

    This is the context and rules for all responses about our "Slack to FAQ" app. The app turns Slack messages into easy-to-search FAQs for teams. We're building v1 to start. Use this to guide all your answers. Always follow the rules exactly.

    Rule Content
    # Project Context and Rules for LLMs
    
    This is the context and rules for all responses about our "Slack to FAQ" app. The app turns Slack messages into easy-to-search FAQs for teams. We're building v1 to start. Use this to guide all your answers. Always follow the rules exactly.
    - Stick strictly to the rules and tools listed below.
    - Keep answers clear, simple, and focused on this project.
    - If unsure about something, ask a short question for clarity.
    
    ## Frontend
    The frontend is the part users see in their browser, like buttons and forms.
    
    **Rules**
    1. Style everything with Tailwind only.
    2. Use Tailwind Flex properties for layouts. Do not use Tailwind Grid system.
    3. Component naming follows CamelCase.
    4. At the top of every file, just below the imports, document with a comment following this example:
    ```text
    /**
    * [Name of file / function / component]
    * @author [if done by LLM, then name should be **LLM**]
    *
    * @description [very brief - 1 / 2 lines]
    *
    * @todo
    * - xxx
    * - [list of things remaining / to improve]
    */
    ```
    5. Above every code logic (or on the side), comment with: // [simple explanatory phrase]
    
    **Context**
    - Built with React fully type safe (.tsx) and Next.js App Router.
    - Handles user login via Clerk.
    - Priority: Keep the user interface simple and easy to use.
    
    ## Backend
    The backend handles data, storage, and connections to microservices behind the scenes.
    
    **Rules**
    1. Follow the same documentation and commenting convention established in the Frontend section of this guide.
    2. Build microservices with Flask for simple tasks or FastAPI for faster ones.
    3. Use Supabase for all database work and file storage.
    4. Handle user login only with Clerk.
    5. Process payments only with Stripe.
    
    **Context**
    - Overall app type: T3 stack (TypeScript, Tailwind, tRPC, Next.js).
    - Database: Supabase.
    - File storage: Supabase (like an S3 bucket).
    - User login: Clerk.
    - Payments: Stripe.
    - Connects to Slack for pulling messages.
    - Priority: Focus on secure handling of Slack data and user info.
    

    Tags

    nextjsreacttypescripttailwindcsssupabasefastapi

    Comments

    More Rules

    View all
    Web Development

    Next.js 15 + TypeScript Cursor Rules

    Comprehensive .cursorrules file for Next.js 15 App Router projects with TypeScript, enforcing server components by default, proper use of "use client" directive, and App Router conventions.

    C
    Community
    Backend Development

    Python FastAPI Best Practices Rules

    Cursor rules for Python FastAPI projects enforcing async patterns, Pydantic v2 models, dependency injection, and proper error handling.

    C
    Community
    Frontend Development

    React + TypeScript Component Rules

    Rules for consistent React component development with TypeScript interfaces, proper hook patterns, and component composition.

    C
    Community
    AI/ML

    Cursor Agent Mode Configuration

    Rules optimizing Cursor Agent mode behavior including multi-file editing context, session management, and autonomous task completion patterns.

    C
    Cursor Team
    Frontend Development

    Tailwind CSS + shadcn/ui Rules

    Cursor rules for projects using Tailwind CSS with shadcn/ui component library, enforcing consistent utility class usage and component patterns.

    C
    Community
    Backend Development

    Go Backend Service Rules

    Rules for Go backend services enforcing idiomatic Go patterns, proper error handling, and clean architecture conventions.

    C
    Community

    Stay up to date

    Get the latest Cursor prompts, rules, and resources delivered to your inbox weekly.

    Neura Market LogoNeura Market

    Discover the best AI prompts, plugins, and resources for Cursor and more.

    Content Types

    • Rules
    • Prompts
    • MCPs
    • Agents
    • Guides

    Platforms

    • ChatGPT Directory
    • Claude Directory
    • Gemini Directory
    • Cursor Directory
    • Grok Directory
    • Perplexity Directory
    • DeepSeek Directory
    • CoPilot Directory
    • Stable Diffusion Directory
    • Midjourney Directory
    • All Directories

    Resources

    • Blog
    • Documentation
    • Help Center
    • Marketplace

    Legal

    • Privacy Policy
    • Terms of Service

    © 2026 Neura Market. All rights reserved.

    |

    Not affiliated with any AI platform vendors.