docs: add Cursor Cloud dev environment setup notes - #25
Draft
ephraimduncan wants to merge 1 commit into
Draft
Conversation
Co-authored-by: Ephraim Duncan <ephraimduncan@users.noreply.github.com>
ephraimduncan
commented
Jul 11, 2026
| @@ -0,0 +1,59 @@ | |||
| # AGENTS.md | |||
|
|
|||
| ## Cursor Cloud specific instructions | |||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sets up and documents the development environment for the Weekday Calendar monorepo (Bun + Turborepo + Next.js 16 + PostgreSQL + Drizzle + Better Auth).
Adds an
AGENTS.mdwith a## Cursor Cloud specific instructionssection capturing the non-obvious caveats for running this project:.envis required and gitignored; which vars are needed and which can be placeholders.turbo linthas nolinttask; ESLint on this commit throws a circular-JSON error (eslint-config-next@16+FlatCompatincompatibility, pre-existing).The suggested startup update script is minimal:
bun install.Verification
Environment was set up and the app run end-to-end in development mode.
weekday_app_walkthrough.mp4
Landing page, login page, and protected-route redirect all working:
Landing page
Login page
/calendar redirects to /login
The Google OAuth sign-in action was exercised via the auth API, generating a real Google authorization URL and persisting the corresponding state to Postgres — proving the app → auth → DB pipeline works.
To show artifacts inline, enable in settings.