Add repository-scoped Copilot/Codex guidance docs aligned with Gitfolio branch/data constraints (#42)

Author: Copilot

.github/copilot-instructions.md

@@ -0,0 +1,36 @@
+# GitHub Copilot Instructions for Gitfolio
+
+## Project context
+- This repo is both a Vite + React + TypeScript portfolio app and an npm CLI (`gitforge`).
+- Keep the app deterministic and static: do not add runtime GitHub API calls in browser code.
+- Use functional React components with TypeScript and Tailwind CSS.
+
+## Branch and data rules
+- `main` is template code only: `data/*.json` must stay empty (`[]`).
+- `web` is deployment + personal data branch.
+- Never propose changes that put personal content into `main`.
+
+## Generated files
+- Do not hand-edit generated files:
+  - `src/generated/githubData.ts`
+  - `src/siteContent.json`
+- If content generation is needed, use existing generator workflows/scripts.
+
+## Config and secrets
+- Source-of-truth config is `gitforge.config.json` (git-ignored).
+- Only template config (`gitforge.config.example.json`) is tracked.
+- Never commit secrets (`.env`, tokens, client secrets, PATs).
+
+## Editing guidance
+- Make minimal, surgical changes tied to the request.
+- Reuse existing patterns and libraries before introducing new ones.
+- Avoid unrelated refactors.
+- Keep routing/template patterns consistent across pages.
+
+## Validation commands
+- Install: `pnpm install`
+- Lint: `pnpm lint`
+- Build: `pnpm build`
+
+## Documentation consistency
+- Keep `CLAUDE.md`, `README.md`, and workflow behavior in sync when changing architecture expectations.

CODEX.md

@@ -0,0 +1,43 @@
+# Codex Instructions for Gitfolio
+
+## Goal
+Contribute safely to Gitfolio with small, correct changes that preserve branch/data architecture and static-site behavior.
+
+## Understand first
+- Read `CLAUDE.md`, `README.md`, and relevant workflow files before structural changes.
+- Prefer minimal edits in existing patterns over broad rewrites.
+
+## Critical repository constraints
+- Two-branch model:
+  - `main`: template/dev branch, `data/*.json` must remain empty (`[]`).
+  - `web`: deployment branch with real personal data.
+- `sync-to-web.yml` preserves `web` data and dispatches deploy.
+- `deploy.yml` deploys from `web`.
+
+## Data and generation rules
+- Do not hand-edit generated outputs:
+  - `src/generated/githubData.ts`
+  - `src/siteContent.json`
+- Use existing generator script when needed: `scripts/generate-github-data.js`.
+
+## Security rules
+- Never commit secrets or local credentials:
+  - `.env`, PAT tokens, OAuth secrets, private keys
+  - `gitforge.config.json` when it contains private token values
+- Follow `SECURITY.md` guidance for safe commits.
+
+## Implementation style
+- React: functional components + TypeScript.
+- UI: Tailwind-first, clean and minimal style.
+- Keep browser behavior static/deterministic (no runtime GitHub API access in frontend).
+- Reuse existing utilities/components and avoid unnecessary dependencies.
+
+## Validation
+- Install dependencies: `pnpm install`
+- Lint: `pnpm lint`
+- Build: `pnpm build`
+- Report pre-existing failures separately from new issues introduced by your changes.
+
+## Scope discipline
+- Only change what the task requires.
+- If touching workflows or branching logic, ensure behavior still protects `web` data and `main` cleanliness.