You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: add Phase 1 issue tracking and enhance project guidelines
Enhanced project documentation to support organized development workflow with comprehensive issue tracking and best practices.
TODO.md Updates:
- Added GitHub issue references (#5-#12) to all Phase 1 tasks for direct progress tracking
- Created new R2 verification task as issue #12
- Grouped related tasks under appropriate issue numbers for better organization
CLAUDE.md Enhancements:
- Added project management section with GitHub project board workflow
- Documented issue management requirements and labeling standards
- Included development workflow for issue-based development
- Expanded best practices section with specific guidelines:
- Documentation-first approach with official CLI usage
- Code quality standards for edge runtime
- Security guidelines for zero-knowledge architecture
- Performance considerations for Cloudflare Workers
- Testing requirements for critical paths
This establishes a clear development process where team members can pick issues from the project board, track progress in TODO.md, and follow consistent practices throughout implementation.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Always check official documentation of frameworks, UI components, Cloudflare, CodeMirror before implementing changes. If they provide generator or command line, please follow the documentation instead of manually generate them.
106
+
### Documentation First
107
+
- Always check official documentation before implementing:
108
+
- Next.js 15: Use `create-next-app` and official guides
109
+
- shadcn/ui: Use `npx shadcn-ui@latest` CLI commands
110
+
- Cloudflare: Follow Workers and R2 official docs
111
+
- CodeMirror: Refer to v6 documentation
112
+
- Use official CLIs and generators instead of manual setup
113
+
114
+
### Code Quality
115
+
- Run `npm run lint` and `npm run typecheck` before committing
116
+
- Follow TypeScript strict mode practices
117
+
- Write edge-runtime compatible code only
118
+
- Keep components small and focused
119
+
- Use proper error boundaries
120
+
121
+
### Security
122
+
- Never commit secrets or API keys
123
+
- Always validate and sanitize user input
124
+
- Use environment variables for sensitive data
125
+
- Follow encryption best practices in `docs/SPEC.md`
0 commit comments