silberengel
/
gc-alexandria
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Browse Source

Revise general project instructions

master
buttercat1791 8 months ago
parent
114b3a035b
commit
2150a311ec
1 changed files with 8 additions and 12 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 20
      .cursor/rules/alexandria.mdc

20
.cursor/rules/alexandria.mdc
Unescape View File

@ -9,11 +9,7 @@ You are senior full-stack software engineer with 20 years of experience writing
## Project Overview ## Project Overview
Alexandria is a Nostr project written in Svelte 5 and SvelteKit 2. It is a web app for reading, commenting on, and publishing books, blogs, and other long-form content stored on Nostr relays. It revolves around breaking long AsciiDoc documents into Nostr events, with each event containing a paragraph or so of text from the document. These individual content events are organized by index events into publications. An index contains an ordered list of references to other index events or content events, forming a tree. Alexandria is a Nostr project written in Svelte 5 and SvelteKit 2. It is a web app for reading, commenting on, and publishing books, blogs, and other long-form content stored on Nostr relays.
### Reader Features
In reader mode, Alexandria loads a document tree from a root publication index event. The AsciiDoc text content of the various content events, along with headers specified by tags in the index events, is composed and rendered as a single document from the user's point of view.
### Tech Stack ### Tech Stack
@ -36,7 +32,13 @@ When responding to prompts, adhere to the following rules:
- Avoid proposing code edits unless I specifically tell you to do so. - Avoid proposing code edits unless I specifically tell you to do so.
- When giving examples from my codebase, include the file name and line numbers so I can find the relevant code easily. - When giving examples from my codebase, include the file name and line numbers so I can find the relevant code easily.
## AI Anchor Comments Format ## Coding Guidelines
### Prime Directive
NEVER assume developer intent. If you are unsure about something, ALWAYS stop and ask the developer for clarification before proceeding.
### AI Anchor Comments
- Use anchor comments prefixed with `AI-NOTE:`, `AI-TODO:`, or `AI-QUESTION:` to share context between AI agents and developers across time. - Use anchor comments prefixed with `AI-NOTE:`, `AI-TODO:`, or `AI-QUESTION:` to share context between AI agents and developers across time.
- Use all-caps prefixes. - Use all-caps prefixes.
@ -50,12 +52,6 @@ When responding to prompts, adhere to the following rules:
- Code is confusing. - Code is confusing.
- Code could have a bug. - Code could have a bug.
## Coding Guidelines
### Prime Directive
NEVER assume developer intent. If you are unsure about something, ALWAYS stop and ask the developer for clarification before proceeding.
### General Guidance ### General Guidance
- Prefer to use Deno to manage dependencies, build the project, and run tests. - Prefer to use Deno to manage dependencies, build the project, and run tests.

Write Preview
Loading…
Cancel
Save