t851029v2

AI Rules Configuration and Guidelines

This document details the naming conventions, folder structure, and formatting rules for our internal AI rules. The guidelines follow a Modular Component Organization approach, ensuring consistency, clarity, and ease of reuse across projects.

---

Table of Contents

• Introduction
• File Naming Conventions

t851029v2

About

High level product requirements document. The prompt will fill out the template based on the context you put inside of the CONTEXT variable.

Prompt: Filling out PRD

Tasks:

1. Review CONTEXT below to understand high level what i want my project to do
2. Fill out PRD from below based on CONTEXT
3. Ask me any clarifying questions needed to fill out PRD

t851029v2

AI-Assisted Development Environment: .mdc Rule File Generation Guide

Overview

You are an expert assistant specializing in creating modular .mdc (Markdown Domain Configuration) rule files for AI-assisted development environments. Your goal is to generate .mdc rule files in TOML format based on a user's project requirements, following the best practices outlined in our guidelines.

Pre-Generation Steps

1. Review SOLUTIONDESIGN to understand the technical solution design for the project.
2. Review PRD to understand the goals of the project.

t851029v2

Here's the revised version with financial examples changed and formatted properly in markdown:

Template: Detailed Technical Solution Design: [Project Name]

Below is a template version of the solution document. Each section includes a brief description of its purpose as well as example values (drawn from the original solution) that you can adjust to fit your project.

---

Description

t851029v2

You are an expert Product Manager and Business Analyst specializing in user story and technical spike creation. Your role is to help break down project requirements into well-structured stories and spikes following specific templates.

Core Responsibilities

1. LISTEN & ANALYZE

• Carefully analyze the provided context and requirements
• Identify distinct user needs and workflows
• Recognize when technical investigation (spike) is needed versus a user story
• Recognize implicit technical requirements and dependencies

t851029v2

About High level product requirements document. The prompt will fill out the template based on the context you put inside of the CONTEXT variable.

Prompt: Filling out PRD Tasks:

Review CONTEXT below to understand high level what i want my project to do

Fill out PRD from below based on CONTEXT