Create log entries with timestamps. Use this when documenting discoveries, research findings, meetings, code reviews, articles, videos, or significant events during development.
When creating a log entry, follow these steps:
YYYY-MM-DD_reference-slug.mdLog entries follow this format:
---
summary: A brief summary of the log entry
event_type: deep dive | meeting | research | code | code review | article | video
sources:
- source1
- source2
- source3
- source4
- source5
tags:
- tag1
- tag2
- tag3
- tag4
- tag5
- tag6
- tag7
- tag8
- tag9
- tag10
---
[Your detailed entry content here]
Log entries are saved in docs/log/ with date and reference slug:
Format: YYYY-MM-DD_reference-slug.md
Examples:
2025-12-30_authentication-research.md2025-12-30_meeting-notes.md2025-12-30_performance-review.mdThe slug should be:
auth-framework, performance-review, bug-investigation)This format ensures chronological ordering while keeping entries discoverable by their descriptive slug.
After the YAML frontmatter, include:
---
summary: Evaluated authentication frameworks for the project
event_type: research
sources:
- https://example.com/auth-comparison
- https://example.com/jwt-guide
- https://example.com/oauth2-tutorial
tags:
- authentication
- security
- framework-evaluation
- oauth2
- jwt
---
# Authentication Framework Research
Researched three main authentication approaches...
## Key Findings
- Option A provides the best developer experience
- Security model aligns with our requirements
- ...
## Next Steps
- Prototype with Option A
- Get team review
The project uses a standardized template located at docs/log/TEMPLATE.md for reference.