Your first galdr project
Galdr is installed. Now you need to tell it about your project — what it does, what it must never do, and what success looks like. This is what agents read at the start of every session.
Open PROJECT.md and define your mission
PROJECT.md is the single most important file in galdr. Every agent session starts by reading it. Open .galdr/PROJECT.md and replace the placeholder mission with yours.
PROJECT.md (example)# PROJECT.md — my-app ## Mission Build a developer tool that does X for developers who work with Y. ## Goals - G-01: Ship MVP by Q2 2026 - G-02: Onboard developers in under 10 minutes - G-03: Maintain < 100ms API response time ## Identity - Repo: github.com/yourname/my-app - Primary language: TypeScript - Framework: Next.js 15 App Router
Keep the mission short and honest. Agents use this to make decisions, not to impress anyone.
Add your first constraint
Constraints are hard rules agents must never violate. Open .galdr/CONSTRAINTS.md and add one that matters for your project.
CONSTRAINTS.md (example)## Active Constraints | ID | Constraint | Enforced by | |------|-----------|-------------| | C-001 | Never use SQLite — project requires Postgres for production use | All agents | | C-002 | All API routes must have rate limiting | All agents | | C-003 | No third-party analytics without explicit user consent | All agents |
Why constraints matter
Without CONSTRAINTS.md, agents will make reasonable-but-wrong decisions. An agent that doesn't know you've committed to Postgres will reach for SQLite when writing a quick prototype. The constraint prevents that.
Record your first decision
If you've already made architecture choices (framework, database, hosting), record them in DECISIONS.md now. Future agents and future you will thank you.
DECISIONS.md (example)## Decision Log | Date | ID | Decision | Rationale | Author | |------|----|----------|-----------|--------| | 2026-04-18 | D001 | Use Next.js 15 App Router | Best RSC support, strong auth ecosystem, Vercel deploy path | me | | 2026-04-18 | D002 | Postgres over SQLite | Production requirement — need concurrent writes and JSONB | me |
Check project status with @g-status
Open your AI tool and run:
@g-statusThis reads your PROJECT.md, TASKS.md, BUGS.md, and recent git log and produces a session summary: active phase, open tasks, open bugs, recent decisions, and a list of what to work on next.
With a fresh install, the output should show: Phase 0, 0 tasks, 0 bugs, and prompt you to create your first task.
Commit your .galdr/ folder
Galdr files belong in version control. Commit them now so your team (and future you) can use them.
git add .galdr/ .claude/ .cursor/
git commit -m "chore(galdr): initialize galdr project management"Team usage
Once committed, any team member who pulls the repo has galdr available. Their AI agents will load the same PROJECT.md, CONSTRAINTS.md, and DECISIONS.md you just wrote.
Project configured ✓
Your project has a mission, constraints, and decisions. The next tutorial shows you how to create and complete your first task through galdr's full quality gate cycle.