Wiring to Cursor: Difference between revisions

From Knowledge Commons
Jump to navigation Jump to search
Created page with "This page contains notes about my efforts to connect Cursor to MediaWiki. === Reason Why This Is Necessary === Thus far, I have documented functional requirements in a wiki page and then copy/paste it to Cursor. As the project gets more complex, I realize that I need to create (or have AI create) documents that define the guiding principles, architectural decisions, and other details about the user experience. Those documents need to always be available to the AI to..."
 
No edit summary
Line 10: Line 10:


=== Requirements Pages ===
=== Requirements Pages ===
These wiki pages will be provided to Cursor to define various aspects of the project:
These wiki pages will be provide details on various aspects of the project:


* [[Wiki Page Types]]
* [[Wiki Page Types]]
* [[New User Onboarding]]
* [[New User Onboarding]]
=== Priority Tasks ===
I would like to complete these tasks first:
* Onboarding
** Users can choose between one of three environments
** Users can choose which page templates to install
* PARA Wiki accessible at https://para.goalstriving.org is viewable to anyone (does not require login) and can be edited by matt.shell7777@gmail.com or matt@mshell.net. 
* Community wiki
** Shows overall community stats and leaderboards
* Personal status page
** Shows current snapshot and historical info of tracked metrics
** Average edits per day, Qty pages w/o an Area or Topic,  New Captures per day, Average time to process new captures, etc.
* Page Schema with properties: type, status, area, topic
* Allow upload PDF
** Allow highlight text
*** Yellow: important
*** Blue: follow-up needed (mostly used on Idea notes and Study notes).
*** Red: needs attention (possible mistake, typo, etc.)
** Optionally disable the Summary box that opens after you click Save changes.
** Header Expansion to a New Page

Revision as of 09:33, 27 August 2026

This page contains notes about my efforts to connect Cursor to MediaWiki.

Reason Why This Is Necessary

Thus far, I have documented functional requirements in a wiki page and then copy/paste it to Cursor. As the project gets more complex, I realize that I need to create (or have AI create) documents that define the guiding principles, architectural decisions, and other details about the user experience. Those documents need to always be available to the AI to reference. These documents will be updated with every new feature added, describing how each feature is implemented, what its dependencies are, and how it interacts with other elements.

A major benefit of this is that it forces me to write comprehensive and detailed notes, because they will be read by the AI.

Mechanics

I create an API key in MediaWiki and provide that to Cursor, and then Cursor can read and edit every page.

Requirements Pages

These wiki pages will be provide details on various aspects of the project:

Priority Tasks

I would like to complete these tasks first:

  • Onboarding
    • Users can choose between one of three environments
    • Users can choose which page templates to install
  • PARA Wiki accessible at https://para.goalstriving.org is viewable to anyone (does not require login) and can be edited by matt.shell7777@gmail.com or matt@mshell.net.
  • Community wiki
    • Shows overall community stats and leaderboards
  • Personal status page
    • Shows current snapshot and historical info of tracked metrics
    • Average edits per day, Qty pages w/o an Area or Topic, New Captures per day, Average time to process new captures, etc.
  • Page Schema with properties: type, status, area, topic
  • Allow upload PDF
    • Allow highlight text
      • Yellow: important
      • Blue: follow-up needed (mostly used on Idea notes and Study notes).
      • Red: needs attention (possible mistake, typo, etc.)
    • Optionally disable the Summary box that opens after you click Save changes.
    • Header Expansion to a New Page