docs: rewrite README for portfolio visibility - #12
Merged
Conversation
- Lead with what's compelling (no server/DB, Calendar as backend) - Add AI Assistant section covering tool-use, agentic loop, all 8 tools - Add architecture decisions section (why Calendar backend, why no DB, why browser-side API calls, why React/TS, why Fibonacci points) - Promote live demo link to top - Update features to reflect current state (3-status board, sorting, persistence, optimistic drag-and-drop) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes the "Polish Plan-IT README for portfolio visibility" work item.
🤖 Generated with Claude Code