Skip to content
Prompt

BibleScholarProjectClean — Cursor Rules

by iog-creator

AI Summary

Cursor rules for the BibleScholarProject that establish ETL conventions, data source fallback patterns, and file naming standards for Bible text processing and integration workflows.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to add the "BibleScholarProjectClean — Cursor Rules" prompt rules to my project.
Repository: https://github.com/iog-creator/BibleScholarProjectClean

Please read the repo to find the rules/prompt file, then:
1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type)
2. If there's an existing rules file, merge the new rules in rather than overwriting
3. Confirm what was added

Description

Cursor Rules for BibleScholarProjectClean

Overview

This document describes the ETL (Extract, Transform, Load) rules and patterns for the BibleScholarProject. These rules ensure consistent data processing across all components.

[2025-06-05] Data Source Fallback Rule

• The data source fallback rule is now formalized and must be followed by all ETL and integration test scripts. • If versification mapping or TVTMS source files are missing in the main data directory, scripts MUST automatically search for and use files from the secondary data source (STEPBible-Datav2 repo) at: ` C:\Users\mccoy\Documents\Projects\Projects\AiBibleProject\SecondBibleData\STEPBible-Datav2 ` • All ETL and test scripts must check the main data directory first, then the secondary source if files are missing. This ensures robust operation even if the main data directory is incomplete.

TVTMS Data Source Authority

> ⚠️ Important: Only data/raw/TVTMS_expanded.txt is the authoritative source for versification mappings in the ETL pipeline. > > Do not use the .tsv file for ETL or integration. The .tsv is for reference or manual inspection only.

File Naming Conventions

• ETL scripts should be named with a etl_ prefix: etl_hebrew_ot.py, etl_lexicons.py • Data fix scripts should have a descriptive name with a fix_ prefix: fix_hebrew_strongs_ids.py • Verification scripts should be named with a verify_ or check_ prefix: verify_data_processing.py

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 4mo ago
Stale
AdoptionUnder 100 stars
0 ★ · Niche
DocsMissing or thin
Undocumented

GitHub Signals

Issues2
Updated4mo ago
View on GitHub
No License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Any AI assistant that accepts custom rules or system prompts

Claude
ChatGPT
Cursor
Windsurf
Copilot
+ more