| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 0 | 6 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 2 | 2 | 20% |
What each file covers
Sections
0 shared · 0 only in A · 6 only in B- + SneakInMarket Project Overview
- + Project Description
- + Tech Stack
- + Key Architecture Patterns
- + File Organization
- + Development Guidelines
Commands
neither file has anySection tags
1 shared · 2 only in A · 2 only in B- − security
- − do-not
- + architecture
- + types
- code-style
Line diff
KAMAL20201/SneakerMarketplace · AGENTS.md
@@ −1 @@
1Codex Workspace Rules (AGENTS.md)
2
3Purpose
4- This file defines project-specific rules and preferences that Codex reads before answering any chat in this workspace.
5- Keep it concise and concrete. Place non-obvious, high-impact rules first.
6
7Cursor Rules
8- Also read and honor all rules in `.cursor/rules/*.mdc` for this project.
9- If any guidance conflicts, `.cursor/rules` takes precedence for this repo.
10
11Behavior Rules
12- Always: Ask 1–2 clarifying questions when scope or intent is ambiguous.
13- Always: Explain planned terminal actions briefly before running commands.
14- Always: Keep answers concise by default; expand only when asked.
15- Ask First: Before running destructive commands (rm/reset) or installing packages.
16- Ask First: Before changing config, adding dependencies, or altering build settings.
17- Never: Expose secrets or print full .env contents in answers or logs.
18
19Style and Tone
20- Tone: Friendly, direct, and efficient. Avoid filler.
21- Responses: Use short sections and bullet lists when they improve scanability.
22- File References: Use clickable paths like `src/file.ts:42` (single line only).
23
24Task Execution
25- Scope: Make minimal, surgical changes focused on the user’s request.
26- Tests: If tests exist, run targeted tests for modified code first.
27- Validation: Prefer small, verifiable steps; summarize progress between steps.
28- Plans: Use the plan tool for multi-step or ambiguous work only.
29
30Code and Project
31- Stack: Vite + React + TypeScript (see `package.json`).
32- Formatting: Match existing style; do not add formatters unless requested.
33- Types: Prefer explicit types in new/changed code; avoid one-letter names.
34- Security: Treat environment variables and credentials as sensitive.
35
36Shell and Approvals
37- Approval Mode: Default to asking before actions needing elevated permissions or network.
38- Sandboxing: Assume workspace-write, network restricted; call out when escalation is needed.
39- Commands: Prefer `rg` for search; read files in <=250-line chunks.
40
41Response Defaults
42- Brevity: Target 3–8 lines unless detail is necessary.
43- Structure: Use short headers sparingly; avoid over-fragmentation.
44- Monospace: Wrap commands, paths, env vars, and identifiers in backticks.
45
46When In Doubt
47- Clarify requirements, propose a minimal plan, and confirm before large changes.
48
49Project-Specific Rules (Customize Below)
50- Backend: Supabase is the source of truth (DB/Auth/Storage/Edge Functions). Do not add custom servers. Use Edge Functions for server logic.
51- Supabase Calls: Avoid redundant fetches. Cache shared data in React Context; expose typed hooks and explicit invalidate/refresh methods.
52- Pagination: For any list/multi-item fetch, implement pagination; show fewer items first and add page controls at the bottom.
53- Dependencies: Install latest stable versions. If unsure about API/usage, ask for a docs link and confirmation before adding. Request approval before changing build/config deps.
54- TypeScript: Use strict typing in all new code. Do not change existing TypeScript config; ensure new code compiles under current strictness. Never use `any`.
55- Mobile UI: Design mobile-first (320px+). Use Tailwind responsive prefixes (`sm:`, `md:`, `lg:`, `xl:`). Ensure touch targets ≥44px and test across screen sizes.
56- UI Patterns: Follow shadcn/ui and Radix-based components in `src/components/ui/`; keep props minimal and typed.
57- Secrets: Never echo or log values from `process.env.*`.
58
59Notes
60- Adjust or expand sections above to reflect your preferences.
61- This file is intended to be read as high-priority context at session start.
62
KAMAL20201/SneakerMarketplace · .cursor/rules/project-overview.mdc
@@ +1 @@
1# SneakInMarket Project Overview
2
3## Project Description
4
5SneakInMarket is a React-based marketplace application for sneakers, clothing, accessories, electronics, gaming, and collectibles. Built with TypeScript, Vite, Tailwind CSS, and Supabase.
6
7## Tech Stack
8
9- **Frontend**: React 19, TypeScript 5.8, Vite 7
10- **Styling**: Tailwind CSS 4.1, Radix UI components
11- **State Management**: React Context API
12- **Backend**: Supabase (Auth, Database, Storage)
13- **Payment**: Razorpay integration
14- **Forms**: React Hook Form with Zod validation
15- **Routing**: React Router 7
16
17## Key Architecture Patterns
18
19- **Component Structure**: UI components in `src/components/ui/`, page components in `src/pages/`
20- **Context Pattern**: Auth, Cart, Payment, and Seller form contexts
21- **Custom Hooks**: Reusable hooks in `src/hooks/`
22- **Service Layer**: Business logic in `src/lib/` with dedicated service files
23- **Type Safety**: Strict TypeScript with comprehensive type definitions
24- **Path Aliases**: `@/*` maps to `src/*` for clean imports
25
26## File Organization
27
28- `src/constants/enums.ts` - Centralized enums for routes, categories, brands, sizes
29- `src/types/` - TypeScript type definitions
30- `src/contexts/` - React context providers
31- `src/lib/` - Utility functions and services
32- `src/components/ui/` - Reusable UI components (shadcn/ui style)
33- `src/pages/` - Page-level components
34
35## Development Guidelines
36
37- Always use TypeScript with strict mode
38- Follow mobile-first responsive design
39- Minimize useEffect usage
40- Use enums from constants for consistent values
41- Implement pagination for list APIs
42- Use latest package versions
43- Follow existing code patterns and conventions
44 description:
45 globs:
46 alwaysApply: false
47
48---
49
@@ −1 +1 @@
1−Codex Workspace Rules (AGENTS.md)
1+# SneakInMarket Project Overview
22
3−Purpose
4−- This file defines project-specific rules and preferences that Codex reads before answering any chat in this workspace.
5−- Keep it concise and concrete. Place non-obvious, high-impact rules first.
3+## Project Description
64
7−Cursor Rules
8−- Also read and honor all rules in `.cursor/rules/*.mdc` for this project.
9−- If any guidance conflicts, `.cursor/rules` takes precedence for this repo.
5+SneakInMarket is a React-based marketplace application for sneakers, clothing, accessories, electronics, gaming, and collectibles. Built with TypeScript, Vite, Tailwind CSS, and Supabase.
106
11−Behavior Rules
12−- Always: Ask 1–2 clarifying questions when scope or intent is ambiguous.
13−- Always: Explain planned terminal actions briefly before running commands.
14−- Always: Keep answers concise by default; expand only when asked.
15−- Ask First: Before running destructive commands (rm/reset) or installing packages.
16−- Ask First: Before changing config, adding dependencies, or altering build settings.
17−- Never: Expose secrets or print full .env contents in answers or logs.
7+## Tech Stack
188
19−Style and Tone
20−- Tone: Friendly, direct, and efficient. Avoid filler.
21−- Responses: Use short sections and bullet lists when they improve scanability.
22−- File References: Use clickable paths like `src/file.ts:42` (single line only).
9+- **Frontend**: React 19, TypeScript 5.8, Vite 7
10+- **Styling**: Tailwind CSS 4.1, Radix UI components
11+- **State Management**: React Context API
12+- **Backend**: Supabase (Auth, Database, Storage)
13+- **Payment**: Razorpay integration
14+- **Forms**: React Hook Form with Zod validation
15+- **Routing**: React Router 7
2316
24−Task Execution
25−- Scope: Make minimal, surgical changes focused on the user’s request.
26−- Tests: If tests exist, run targeted tests for modified code first.
27−- Validation: Prefer small, verifiable steps; summarize progress between steps.
28−- Plans: Use the plan tool for multi-step or ambiguous work only.
17+## Key Architecture Patterns
2918
30−Code and Project
31−- Stack: Vite + React + TypeScript (see `package.json`).
32−- Formatting: Match existing style; do not add formatters unless requested.
33−- Types: Prefer explicit types in new/changed code; avoid one-letter names.
34−- Security: Treat environment variables and credentials as sensitive.
19+- **Component Structure**: UI components in `src/components/ui/`, page components in `src/pages/`
20+- **Context Pattern**: Auth, Cart, Payment, and Seller form contexts
21+- **Custom Hooks**: Reusable hooks in `src/hooks/`
22+- **Service Layer**: Business logic in `src/lib/` with dedicated service files
23+- **Type Safety**: Strict TypeScript with comprehensive type definitions
24+- **Path Aliases**: `@/*` maps to `src/*` for clean imports
3525
36−Shell and Approvals
37−- Approval Mode: Default to asking before actions needing elevated permissions or network.
38−- Sandboxing: Assume workspace-write, network restricted; call out when escalation is needed.
39−- Commands: Prefer `rg` for search; read files in <=250-line chunks.
26+## File Organization
4027
41−Response Defaults
42−- Brevity: Target 3–8 lines unless detail is necessary.
43−- Structure: Use short headers sparingly; avoid over-fragmentation.
44−- Monospace: Wrap commands, paths, env vars, and identifiers in backticks.
28+- `src/constants/enums.ts` - Centralized enums for routes, categories, brands, sizes
29+- `src/types/` - TypeScript type definitions
30+- `src/contexts/` - React context providers
31+- `src/lib/` - Utility functions and services
32+- `src/components/ui/` - Reusable UI components (shadcn/ui style)
33+- `src/pages/` - Page-level components
4534
46−When In Doubt
47−- Clarify requirements, propose a minimal plan, and confirm before large changes.
35+## Development Guidelines
4836
49−Project-Specific Rules (Customize Below)
50−- Backend: Supabase is the source of truth (DB/Auth/Storage/Edge Functions). Do not add custom servers. Use Edge Functions for server logic.
51−- Supabase Calls: Avoid redundant fetches. Cache shared data in React Context; expose typed hooks and explicit invalidate/refresh methods.
52−- Pagination: For any list/multi-item fetch, implement pagination; show fewer items first and add page controls at the bottom.
53−- Dependencies: Install latest stable versions. If unsure about API/usage, ask for a docs link and confirmation before adding. Request approval before changing build/config deps.
54−- TypeScript: Use strict typing in all new code. Do not change existing TypeScript config; ensure new code compiles under current strictness. Never use `any`.
55−- Mobile UI: Design mobile-first (320px+). Use Tailwind responsive prefixes (`sm:`, `md:`, `lg:`, `xl:`). Ensure touch targets ≥44px and test across screen sizes.
56−- UI Patterns: Follow shadcn/ui and Radix-based components in `src/components/ui/`; keep props minimal and typed.
57−- Secrets: Never echo or log values from `process.env.*`.
37+- Always use TypeScript with strict mode
38+- Follow mobile-first responsive design
39+- Minimize useEffect usage
40+- Use enums from constants for consistent values
41+- Implement pagination for list APIs
42+- Use latest package versions
43+- Follow existing code patterns and conventions
44+ description:
45+ globs:
46+ alwaysApply: false
5847
59−Notes
60−- Adjust or expand sections above to reflect your preferences.
61−- This file is intended to be read as high-priority context at session start.
48+---
6249
