RuleStack

Configs

Stacks

Compare

Diff

RuleStack

Configs

Stacks

Compare

Diff

Read API

RuleStack

Configs

Stacks

Compare

Diff

Read API

Diff/harritaito-harritaito-github-io-claude ↔ harritaito-harritaito-github-io-agents

Comparison

A · CLAUDE.md · harritaito/harritaito.github.ioB · AGENTS.md · harritaito/harritaito.github.io
What each file covers, counted
DimensionSharedOnly in AOnly in BOverlap
Sections411125%
Commands0040%
Section tags0150%

What each file covers

Sections

4 shared · 1 only in A · 11 only in B
  • − CLAUDE.md
  • + AGENTS.md
  • + Stack
  • + Design Context
  • + Working Rules
  • + Verification
  • + Repo Notes
  • + Commits
  • + Scope control
  • + Generated files
  • + Commit and diff hygiene
  • + Next.js / GitHub Pages
  •   1. Think Before Coding
  •   2. Simplicity First
  •   3. Surgical Changes
  •   4. Goal-Driven Execution

Commands

0 shared · 0 only in A · 4 only in B
  • + npm test
  • + npm run build
  • + git status —short
  • + git diff —stat

Section tags

0 shared · 1 only in A · 5 only in B
  • − agent-behaviour
  • + build
  • + test
  • + code-style
  • + git-pr
  • + do-not

Line diff

+106 added−1 removed65 unchanged38.0% identical
harritaito/harritaito.github.io · CLAUDE.md
@@ −1 @@
1# CLAUDE.md
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2 
3Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.
4 
harritaito/harritaito.github.io · AGENTS.md
@@ +1 @@
1# AGENTS.md
2 
3These instructions apply to the entire repository.
4 
5## Stack
6 
7- Use Node.js 20.9.0 or newer.
8- App is Next.js portfolio site with page routes under `pages/`.
9- Shared UI lives under `components/`.
10- Extracted design-system primitives live under `components/design-system/`.
11- Static assets live under `static/`.
12- Static export output lives under `out/`.
13 
14## Design Context
15 
16- Read `PRODUCT.md` before making UX, copy, or layout decisions.
17- Read `DESIGN.md` before changing colors, type, spacing, elevation, or component styling.
18- Reuse existing tokens and primitives from `components/design-system/` before adding new hard-coded values.
19- Keep portfolio feel aligned with current design direction: light paper background, Trirong + Rubik typography, selective project accent colors, soft shadows, restrained motion.
20 
21## Working Rules
22 
23- Prefer small, low-churn edits over broad rewrites.
24- When a visual pattern is repeated 3+ times, extract into `components/design-system/` or an existing shared component instead of duplicating it again.
25- Avoid modifying `package-lock.json` unless dependency work requires it.
26- If you change source UI code, do not hand-edit `out/`; regenerate via build.
27 
28## Verification
29 
30- After making code changes, run:
31 ```bash
32 npm test
33 npm run build
34 ```
35- Ensure both commands succeed before committing.
36- `npm run build` performs static export and refreshes `out/`, including `out/.nojekyll`.
37 
38## Repo Notes
39 
40- `npm run build` is cross-platform. Keep it that way; do not reintroduce Windows-only shell snippets.
41- Repository contains generated static HTML at root and under `out/`. Treat `pages/` and `components/` as source of truth.
42- Jest tests live under `components/__tests__/`.
43 
44## Commits
45 
46- Follow Conventional Commits for commit messages.
47
48 
49## Scope control
50 
51Before editing, inspect the repository state:
52 
53- Run `git status —short`
54- Run `git diff —stat`
55- If the diff is large, identify the largest changed files before editing.
56 
57## Generated files
58 
59Do not edit, stage, commit, or include generated output unless explicitly instructed.
60 
61Treat these paths as generated:
62 
63- `out/**`
64- `.next/**`
65- `dist/**`
66- `build/**`
67- `coverage/**`
68- `.turbo/**`
69- `.vercel/**`
70- `node_modules/**`
71- `*.map`
72- `*.min.js`
73- `*.min.css`
74- generated lockfile churn not directly related to the requested change
75 
76If a build command modifies generated files, leave them unstaged and report that they changed.
77 
78## Commit and diff hygiene
79 
80Keep changes small and source-focused.
81 
82Prefer changing:
83 
84- `src/**`
85- `app/**`
86- `pages/**`
87- `components/**`
88- `public/**` only when actual static assets intentionally change
89- config files only when required
90 
91Avoid mixing:
92 
93- source changes
94- formatting-only changes
95- dependency updates
96- generated build output
97- deployment artifacts
98 
99If deployment output is required, make it a separate deployment-only commit or branch, not part of the implementation diff.
100 
101## Next.js / GitHub Pages
102 
103For normal development tasks, do not commit `out/`.
104 
105`out/` is deployment output, not source code. If GitHub Pages deployment needs it, use a separate deploy workflow, deploy branch, or explicit deployment step.
106 
107 
108Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.
109 
@@ −1 +1 @@
1−# CLAUDE.md
1+# AGENTS.md
2+ 
3+These instructions apply to the entire repository.
4+ 
5+## Stack
6+ 
7+- Use Node.js 20.9.0 or newer.
8+- App is Next.js portfolio site with page routes under `pages/`.
9+- Shared UI lives under `components/`.
10+- Extracted design-system primitives live under `components/design-system/`.
11+- Static assets live under `static/`.
12+- Static export output lives under `out/`.
13+ 
14+## Design Context
15+ 
16+- Read `PRODUCT.md` before making UX, copy, or layout decisions.
17+- Read `DESIGN.md` before changing colors, type, spacing, elevation, or component styling.
18+- Reuse existing tokens and primitives from `components/design-system/` before adding new hard-coded values.
19+- Keep portfolio feel aligned with current design direction: light paper background, Trirong + Rubik typography, selective project accent colors, soft shadows, restrained motion.
20+ 
21+## Working Rules
22+ 
23+- Prefer small, low-churn edits over broad rewrites.
24+- When a visual pattern is repeated 3+ times, extract into `components/design-system/` or an existing shared component instead of duplicating it again.
25+- Avoid modifying `package-lock.json` unless dependency work requires it.
26+- If you change source UI code, do not hand-edit `out/`; regenerate via build.
27+ 
28+## Verification
29+ 
30+- After making code changes, run:
31+ ```bash
32+ npm test
33+ npm run build
34+ ```
35+- Ensure both commands succeed before committing.
36+- `npm run build` performs static export and refreshes `out/`, including `out/.nojekyll`.
37+ 
38+## Repo Notes
39+ 
40+- `npm run build` is cross-platform. Keep it that way; do not reintroduce Windows-only shell snippets.
41+- Repository contains generated static HTML at root and under `out/`. Treat `pages/` and `components/` as source of truth.
42+- Jest tests live under `components/__tests__/`.
43+ 
44+## Commits
45+ 
46+- Follow Conventional Commits for commit messages.
47+
48+ 
49+## Scope control
50+ 
51+Before editing, inspect the repository state:
52+ 
53+- Run `git status —short`
54+- Run `git diff —stat`
55+- If the diff is large, identify the largest changed files before editing.
56+ 
57+## Generated files
58+ 
59+Do not edit, stage, commit, or include generated output unless explicitly instructed.
60+ 
61+Treat these paths as generated:
62+ 
63+- `out/**`
64+- `.next/**`
65+- `dist/**`
66+- `build/**`
67+- `coverage/**`
68+- `.turbo/**`
69+- `.vercel/**`
70+- `node_modules/**`
71+- `*.map`
72+- `*.min.js`
73+- `*.min.css`
74+- generated lockfile churn not directly related to the requested change
75+ 
76+If a build command modifies generated files, leave them unstaged and report that they changed.
77+ 
78+## Commit and diff hygiene
79+ 
80+Keep changes small and source-focused.
81+ 
82+Prefer changing:
83+ 
84+- `src/**`
85+- `app/**`
86+- `pages/**`
87+- `components/**`
88+- `public/**` only when actual static assets intentionally change
89+- config files only when required
90+ 
91+Avoid mixing:
92+ 
93+- source changes
94+- formatting-only changes
95+- dependency updates
96+- generated build output
97+- deployment artifacts
98+ 
99+If deployment output is required, make it a separate deployment-only commit or branch, not part of the implementation diff.
100+ 
101+## Next.js / GitHub Pages
102+ 
103+For normal development tasks, do not commit `out/`.
104+ 
105+`out/` is deployment output, not source code. If GitHub Pages deployment needs it, use a separate deploy workflow, deploy branch, or explicit deployment step.
106+ 
2107  
3108 Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.
4109  
RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack