GitHub Copilot Instructions for CodeBlue Project

Git Workflow Rules

❌ NEVER Do Automatically:

```
git add
```
- Don't stage changes without permission
```
git commit
```
- Don't commit without permission
```
git push
```
- Don't push to remote without permission
```
git checkout
```
- Don't switch branches without permission
```
git merge
```
- Don't merge branches without permission
```
git pull
```
- Don't pull changes without permission
```
git reset
```
- Don't reset history without permission

✅ ALWAYS Do:

Before making code changes:
- Explain what you plan to change
- Wait for explicit approval
- Show the impact (bundle size, breaking changes, etc.)
After making changes:
- Show the diff/summary of what changed
- Suggest a descriptive commit message
- Ask: "Would you like me to suggest the Git commands, or handle it yourself?"
- Let the user decide when to commit
For Git operations:
- Only suggest commands in code blocks
- Never execute Git commands without explicit permission
- Always explain what each command does

📝 Commit Message Format:

<type>: <short description>

- Bullet point 1
- Bullet point 2
- Impact/metrics if applicable

Types: feat, fix, refactor, docs, style, test, chore, perf

🔀 Branching Strategy:

main - Production-ready code
feature/ - New features (e.g.,
```
feature/swipe-gestures
```
)
refactor/ - Code refactoring (e.g.,
```
refactor/remove-theme-switcher
```
)
fix/ - Bug fixes (e.g.,
```
fix/navigation-bug
```
)
docs/ - Documentation only (e.g.,
```
docs/update-readme
```
)

🎯 Best Practices:

Create feature branches for experimental work
Keep commits atomic (one logical change per commit)
Write descriptive commit messages explaining WHY, not just WHAT
Show diffs before committing
Preserve user's work - never force operations

Code Quality Rules

Before Editing:

Read surrounding context (3-5 lines before/after)
Preserve existing code style
Don't break existing functionality
Check for errors after changes

After Editing:

Run build to verify (
```
npm run build
```
)
Check for TypeScript/lint errors
Test bundle size impact
Verify no broken imports

Project-Specific Notes

This is a React + Vite dating app:

Single-file component architecture (for now)
Tailwind CSS for styling
CSS variables with
```
--cb-*
```
prefix
NHS-inspired Classic Blue theme (single brand identity)
No theme switching UI (removed as of Nov 5, 2025)

Performance Targets:

Main bundle: Keep under 320 KB
Gzipped: Keep under 90 KB
Lazy load tabs
Use React.memo for expensive components

Documentation:

All major docs in
```
docs/
```
folder
Read first:
```
docs/PRODUCT_VISION.md
```
(concepts, principles) and
```
docs/ROADMAP.md
```
(MVP scope)
Update
```
docs/PROJECT_STATUS.md
```
after completing tasks
You may propose new docs when centralizing vision/roadmap clarifies direction; otherwise ask first

Last Updated: November 5, 2025
Created by: User request to prevent auto-commit issues

Git Workflow Rules

git add

- Don't stage changes without permission

git commit

- Don't commit without permission

git push

- Don't push to remote without permission

git checkout

- Don't switch branches without permission

git merge

- Don't merge branches without permission

git pull

- Don't pull changes without permission

git reset

- Don't reset history without permission

Before making code changes:

Explain what you plan to change
Wait for explicit approval
Show the impact (bundle size, breaking changes, etc.)

After making changes:

Show the diff/summary of what changed
Suggest a descriptive commit message
Ask: "Would you like me to suggest the Git commands, or handle it yourself?"
Let the user decide when to commit

For Git operations:

Only suggest commands in code blocks
Never execute Git commands without explicit permission
Always explain what each command does

<type>: <short description>

- Bullet point 1
- Bullet point 2
- Impact/metrics if applicable

Types: feat, fix, refactor, docs, style, test, chore, perf

main - Production-ready code

feature/ - New features (e.g.,

feature/swipe-gestures

)

refactor/ - Code refactoring (e.g.,

refactor/remove-theme-switcher

)

fix/ - Bug fixes (e.g.,

fix/navigation-bug

)

docs/ - Documentation only (e.g.,

docs/update-readme

)

Create feature branches for experimental work

Keep commits atomic (one logical change per commit)

Write descriptive commit messages explaining WHY, not just WHAT

Show diffs before committing

Preserve user's work - never force operations

Project-Specific Notes

Single-file component architecture (for now)

Tailwind CSS for styling

CSS variables with

--cb-*

prefix

NHS-inspired Classic Blue theme (single brand identity)

No theme switching UI (removed as of Nov 5, 2025)

Main bundle: Keep under 320 KB

Gzipped: Keep under 90 KB

Lazy load tabs

Use React.memo for expensive components

All major docs in

docs/

folder

Read first:

docs/PRODUCT_VISION.md

(concepts, principles) and

docs/ROADMAP.md

(MVP scope)

Update

docs/PROJECT_STATUS.md

after completing tasks

You may propose new docs when centralizing vision/roadmap clarifies direction; otherwise ask first

Last Updated: November 5, 2025
Created by: User request to prevent auto-commit issues

GitHub Copilot Instructions for CodeBlue Project

GitHub Copilot Instructions for CodeBlue Project

Git Workflow Rules

❌ NEVER Do Automatically:

✅ ALWAYS Do:

📝 Commit Message Format:

🔀 Branching Strategy:

🎯 Best Practices:

Code Quality Rules

Before Editing:

After Editing:

Project-Specific Notes

This is a React + Vite dating app:

Performance Targets:

Documentation:

Related Skills

Markdown Converter

Nano Banana Pro

1password

GitHub Copilot Instructions for CodeBlue Project

Git Workflow Rules

❌ NEVER Do Automatically:

✅ ALWAYS Do:

📝 Commit Message Format:

🔀 Branching Strategy:

🎯 Best Practices:

Code Quality Rules

Before Editing:

After Editing:

Project-Specific Notes

This is a React + Vite dating app:

Performance Targets:

Documentation: