michaellperry

New-Item -ItemType Directory -Path ".cursor\rules" -Force
Invoke-WebRequest -Uri "https://gist.githubusercontent.com/michaellperry/1bfa039958ca6ad05a88f5e53f84c561/raw" -OutFile ".cursor\rules\documentation-structure.mdc"
Invoke-WebRequest -Uri "https://gist.githubusercontent.com/michaellperry/b1a58708036a914028af9d427e66e1f5/raw" -OutFile ".cursor\rules\prd-review.mdc"
Invoke-WebRequest -Uri "https://gist.githubusercontent.com/michaellperry/5a41c62bb4e8ad31e336116a18e3aaae/raw" -OutFile ".cursor\rules\plan.mdc"
Invoke-WebRequest -Uri "https://gist.githubusercontent.com/michaellperry/6fca895eb7ef63faa5014f94709b36a6/raw" -OutFile ".cursor\rules\plan-review.mdc"
Invoke-WebRequest -Uri "https://gist.githubusercontent.com/michaellperry/be30a4eac4d5f2d949a05e0d5758e386/raw" -OutFile ".cursor\rules\implement.mdc"
Invoke-WebRequest -Uri "https://gist.githubusercontent.com/michaellperry/642d556fed4e54e73f7bbb4569cfe832/raw" -OutFile "fix_formatter.py"

michaellperry

---
alwaysApply: false
---
# PRD Review and Compliance Rule

## Purpose
This rule instructs models to critically review Product Requirements Documents (PRDs) against established documentation standards and codebase consistency. The model must identify issues and recommend changes to bring PRDs into compliance, close gaps, ensure consistency with existing code, simplify over-engineered designs, and improve implementation feasibility.

## Review Criteria

michaellperry

---
alwaysApply: false
---

# Plan Creation Rule

When asked to create a plan for a feature, system, or project, you MUST follow these requirements:

## Plan Structure Requirements

michaellperry

---
alwaysApply: false
---
# Plan Review and Feasibility Assessment Rule

## Purpose
This rule instructs models to critically review implementation plans against established documentation standards and codebase consistency. The model must identify issues, assess feasibility, and recommend changes to ensure plans are implementable, well-structured, and aligned with existing code.

## Review Criteria

michaellperry

mkdir -p .cursor/rules
curl -L https://gist.githubusercontent.com/michaellperry/1bfa039958ca6ad05a88f5e53f84c561/raw -o .cursor/rules/documentation-structure.mdc
curl -L https://gist.githubusercontent.com/michaellperry/b1a58708036a914028af9d427e66e1f5/raw -o .cursor/rules/prd-review.mdc
curl -L https://gist.githubusercontent.com/michaellperry/5a41c62bb4e8ad31e336116a18e3aaae/raw -o .cursor/rules/plan.mdc
curl -L https://gist.githubusercontent.com/michaellperry/6fca895eb7ef63faa5014f94709b36a6/raw -o .cursor/rules/plan-review.mdc
curl -L https://gist.githubusercontent.com/michaellperry/be30a4eac4d5f2d949a05e0d5758e386/raw -o .cursor/rules/implement.mdc
curl -L https://gist.githubusercontent.com/michaellperry/642d556fed4e54e73f7bbb4569cfe832/raw -o fix_formatter.py

michaellperry

#!/usr/bin/env python3
"""
Script to fix frontmatter placement issues in .mdc files within .cursor/rules directory.
Moves misplaced frontmatter from the bottom of files to the top where it belongs.
"""

import os
import re
import shutil
from pathlib import Path

michaellperry

---
alwaysApply: false
---
# Implementation Rule

## Requirements
Review the mentioned section of the plan against the current application as implemented. Identify any issues, inconsistencies, or points of confusion.

## Clarification Process
If the instructions are unclear:

michaellperry

---
description: "Documentation structure standards for organizing project documentation into logical sections including implementation plans, technical architecture, user guides, and setup documentation. Emphasizes critical plan file requirements with progress tracking, checklists, phased work breakdowns, and project management focus. Includes file naming conventions, markdown formatting standards, content organization guidelines, and version control practices for maintaining documentation quality."
alwaysApply: true
---
# Documentation Structure and Standards

## Overview
The `/docs` folder contains comprehensive documentation for the project, organized into logical sections for different types of documentation and audiences.

## Documentation Structure

michaellperry

cat package.json | jq -r '.dependencies | keys | map(select(startswith("gatsby")) | "\(.)@latest") | join(" ")' | xargs npm 
i

michaellperry

git config --global alias.a 'add -A'
git config --global alias.b 'branch'
git config --global alias.c 'checkout'
git config --global alias.cb 'checkout -b'
git config --global alias.d 'diff'
git config --global alias.f 'fetch'
git config --global alias.l 'log --pretty=oneline --abbrev-commit'
git config --global alias.r 'rebase --interactive HEAD~10'
git config --global alias.s '-p status'