Initial project scaffold and agent docs.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
vader
2026-05-23 11:16:12 +01:00
commit b820b69ce6
8 changed files with 254 additions and 0 deletions
+31
View File
@@ -0,0 +1,31 @@
# Copy into a new Cursor chat (fill brackets, delete this line)
## Session
- Type: [learning | implementation | debug]
- Phase: [e.g. Phase 4 — Context discipline]
- Project: financeOne (`/home/duarte/development/financeOne`)
## Stack
- Next.js, React, TypeScript, Tailwind (planned — see README)
- Verify: `npm run lint && npm test` (when scaffold exists)
## How I want replies
- Concise and direct; no fluff or long summaries unless I ask.
- Ask me anything unclear (scope, constraints, tradeoffs) before big changes.
## My profile
- Senior dev/architect; learning Cursor.
- Minimal diffs; match existing patterns; short tradeoff notes when choices matter.
- Do not commit/push unless I ask; no secrets in chat.
## Goal (this chat)
[One sentence — what “done” looks like]
## Already decided
- Repo prepared: README, AGENTS.md, `.cursor/rules/`, `.gitignore`, `.env.example`
## Attachments
@README.md @AGENTS.md @.cursor/rules/
---
[Phase title and your questions below]
+20
View File
@@ -0,0 +1,20 @@
---
description: Core FinanceOne project standards for all work
alwaysApply: true
---
# FinanceOne — core
## Responses
- Concise, direct, plain language. No filler or fancy phrasing.
- Ask 13 specific questions when scope, constraints, or approach is unclear — do not guess on large changes.
## Code
- Minimal, focused diffs; match existing style and layout.
- Read `AGENTS.md` and `README.md` before multi-file edits.
- No commit, push, or git config changes unless the user explicitly asks.
- No secrets in repo; `.env.local` locally; names in `.env.example` only.
- Money: integer minor units or a decimal library — not JS `number` for currency math.
- Prefer `@` references over whole-repo search when the task names files or areas.
+13
View File
@@ -0,0 +1,13 @@
---
description: TypeScript conventions for FinanceOne
globs: **/*.{ts,tsx}
alwaysApply: false
---
# TypeScript
- Prefer explicit return types on exported functions and API handlers.
- Avoid `any`; use `unknown` and narrow, or small domain types.
- Use `import type` for type-only imports.
- Colocate types with features; shared types in a dedicated `types` module when reused.
- Handle errors explicitly; do not swallow failures without logging or user-visible feedback.
+13
View File
@@ -0,0 +1,13 @@
---
description: React and Next.js UI patterns for FinanceOne
globs: **/*.{tsx,css}
alwaysApply: false
---
# Web UI
- Next.js App Router: default to Server Components; add `"use client"` only for interactivity.
- Accessible markup: labels on inputs, semantic headings, keyboard-friendly controls.
- Tailwind: reuse spacing and color patterns from nearby components; avoid one-off magic values when a token exists.
- Forms: validate on client for UX and on server for security; show clear error messages.
- Loading and empty states for lists (accounts, transactions).