Design Guidelines
Practical guides for the NepWalk Design team. Read these before starting work.
First time on this repo? After cloning
nepwalk-design, runbash scripts/install-hooks.shonce (works on Linux, macOS, WSL, and Windows via Git Bash). See Workflow → One-time setup for why.
Guides
| Guide | What it covers | Read when |
|---|---|---|
| Workflow | Step-by-step design workflow, prefix commands, execution order | Starting any design task |
| Stitch Prompts | How to write Stitch prompts that produce consistent results | Before running design: component or design: page |
| Component Naming | Atomic design hierarchy, React/Next.js naming conventions | Creating or naming new components |
| Accessibility | WCAG AA quick reference, colour contrast, touch targets | Reviewing any design output |
| Handoff to Frontend | What frontend needs from design, what to check before handoff | Before publishing any page spec |
| Review Process | Draft → review → approved stages, what each means, who approves | Before running design: publish |