You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Project rules – Ralph loop, README, wiki, push when done, no extra MD, multi-agent
3
+
alwaysApply: true
4
+
---
5
+
6
+
# Project Rules
7
+
8
+
## Ralph Loop – Tasks Until Done
9
+
10
+
When working on a task:
11
+
12
+
1.**Loop until done** – Keep iterating on the task until it is fully complete. Do not stop with partial implementations or "good enough" states.
13
+
2.**Verify before claiming completion** – Before saying the task is done:
14
+
- Run the relevant verification (tests, build, lint).
15
+
- Read the output and confirm it actually passed.
16
+
- Only then treat the task as complete.
17
+
3.**No partial completion** – Deliver the full scope. If verification fails or something is missing, fix it and re-verify; do not leave failing tests or broken builds.
18
+
4.**Use a todo list** – For multi-step work, track items (e.g. with a todo list) and ensure every item is completed before finishing.
19
+
20
+
Do not claim completion without fresh verification evidence (e.g. test/build output showing success).
21
+
22
+
---
23
+
24
+
## README & Wiki Before Commit
25
+
26
+
Before committing changes:
27
+
28
+
1.**Look at the codebase** – Review what changed (new features, APIs, structure, scripts, or config) so docs stay in sync.
29
+
2.**Update README** – Add or edit README.md so it reflects current setup, usage, and behavior (e.g. new commands, env vars, or features). Keep it accurate and useful for someone cloning the repo.
30
+
3.**Update the GitHub Wiki** – Push corresponding updates to the repo's GitHub wiki (`https://github.com/davidagustin/davidagustin.github.io/wiki`). Use `gh api` or clone the wiki repo (`davidagustin.github.io.wiki.git`) to create/update pages. The wiki should mirror major README sections with additional detail (e.g. per-feature pages, architecture docs, how-to guides). At minimum, keep the wiki Home page in sync with the README overview.
31
+
32
+
Do this **before** staging and committing. If the change is trivial and doesn't affect setup or usage, a README/wiki update may be unnecessary.
33
+
34
+
---
35
+
36
+
## Push When Done
37
+
38
+
When you finish a task that changes files:
39
+
40
+
1.**Stage** the relevant files (`git add`).
41
+
2.**Commit** with a clear message describing the work.
42
+
3.**Push** to the remote (`git push`).
43
+
44
+
Do this as the final step before telling the user the task is complete. If the user says "don't push" or the repo has no remote, skip the push step.
45
+
46
+
---
47
+
48
+
## No Extra Markdown Files – Consolidate to README
49
+
50
+
-**Do not** create additional `.md` files (e.g. CONTRIBUTING.md, CHANGELOG.md, docs/*.md, task plans, assignment lists) unless they have **functional value** for the app.
51
+
-**Consolidate** all informational documentation into **README.md**.
52
+
-**Delete stale planning files** – Task breakdowns, generation plans, assignment lists, and other one-time planning documents must be deleted once completed. Do not leave them in the repo.
53
+
-**Audit on every commit** – Before committing, run `git ls-files '*.md'` and verify the only tracked markdown files are `README.md` and `.claude/rules/*.md`. If any other `.md` files exist, either delete them (if stale/informational) or consolidate their useful content into README.md.
54
+
-**Exception:** Create a separate markdown file only when the app or tooling **uses it at runtime** (e.g. a template, config schema doc consumed by code, or required by a tool). Purely informational content belongs in README.md.
55
+
56
+
---
57
+
58
+
## Multi-Agent Unique Tasks
59
+
60
+
When spawning or orchestrating multiple agents (e.g. parallel workers, swarm, autopilot, pipeline, or any multi-agent flow):
61
+
62
+
1.**Assign distinct work** – Each agent must have a clearly different responsibility. No two agents should be given the same task, file, or subtask.
63
+
2.**Partition by scope** – Split work by file, feature, layer, or step so there is no overlap (e.g. one agent on frontend, one on backend; or one per file/component).
64
+
3.**Avoid duplicate effort** – Before spawning, confirm the task list has no duplicate entries. If using a shared task list, use atomic claiming or similar so only one agent takes each item.
65
+
4.**Name or tag tasks** – When creating tasks for multiple agents, label them so it's obvious which agent does what (e.g. "Agent A: auth API", "Agent B: login UI").
66
+
67
+
If you are about to spawn N agents, ensure there are at least N unique tasks (or N non-overlapping scopes); never assign the same task to more than one agent.
Copy file name to clipboardExpand all lines: README.md
+17-10Lines changed: 17 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# David Agustin — Portfolio
2
2
3
-
Personal portfolio showcasing 22 full-stack projects built with React, Next.js, Angular, Vue, SvelteKit, Python, and AI/ML technologies. Deployed across 8+ cloud platforms.
3
+
Personal portfolio showcasing 25 full-stack projects built with React, Next.js, Angular, Vue, SvelteKit, Python, and AI/ML technologies. Deployed across 10+ cloud platforms.
0 commit comments