PixelPilot: Instructions file for GitHub Copilot

UI/UX Routes Naming Conventions

Professional URL and route naming patterns. Consistent, RESTful, and maintainable.

---

OVERVIEW

This skill covers:

1. URL naming conventions (kebab-case)
2. RESTful route patterns
3. Named routes (no hardcoded paths)
4. Route grouping and prefixes
5. Framework-specific examples

---

URL CONVENTIONS

Use Kebab-Case

✅ Good:
/user-profile
/blog-posts
/privacy-policy
/account-settings

❌ Bad:
/userProfile       (camelCase)
/user_profile      (snake_case)
/UserProfile       (PascalCase)
/user.profile      (dot notation)

Use Nouns (Not Verbs)

✅ Good:
GET    /posts          (list posts)
POST   /posts          (create post)
GET    /posts/123      (view post)
PUT    /posts/123      (update post)
DELETE /posts/123      (delete post)

❌ Bad:
GET    /get-posts
POST   /create-post
GET    /show-post/123
POST   /update-post/123
POST   /delete-post/123

Use Plurals for Collections

✅ Good:
/posts
/users
/categories
/products

❌ Bad:
/post
/user
/category
/product

---

RESTFUL CONVENTIONS

Standard CRUD Routes

Method	URL	Action	Name
GET	/posts	index	posts.index
GET	/posts/create	create form	posts.create
POST	/posts	store	posts.store
GET	/posts/{id}	show	posts.show
GET	/posts/{id}/edit	edit form	posts.edit
PUT/PATCH	/posts/{id}	update	posts.update
DELETE	/posts/{id}	destroy	posts.destroy

Nested Resources

# Comments on a post
GET    /posts/123/comments         comments.index
POST   /posts/123/comments         comments.store
GET    /posts/123/comments/456     comments.show
PUT    /posts/123/comments/456     comments.update
DELETE /posts/123/comments/456     comments.destroy

Shallow Nesting (Recommended)

# Only nest where parent context is needed
GET    /posts/123/comments         (need post context)
POST   /posts/123/comments         (need post context)

# Don't nest when ID is unique
GET    /comments/456               (comment ID is unique)
PUT    /comments/456
DELETE /comments/456