Reasoning ledger and context engine for Claude Code. Thoughtbox allows Claude to learn within and across runs + sessions, reducing the need to spend human brainpower and energy on the same concepts over and over.
git clone https://github.com/Kastalien-Research/thoughtbox.gitReasoning ledger and context engine for Claude Code. Thoughtbox allows Claude to learn within and across runs + sessions, reducing the need to spend human brainpower and energy on the same concepts over and over.
[{"step":"Initialize Thoughtbox at the start of your project. Use the prompt template to set [PROJECT_NAME], [INITIAL_CONTEXT], and [TASK]. This creates a persistent reasoning ledger for the project.","action":"Copy the prompt template into your Claude Code session and replace placeholders with your project details. Example: 'Initialize a Thoughtbox session for Acme Corp Website Redesign with the following context: Client wants a modern, accessible landing page...'","tip":"Include as much initial context as possible (e.g., goals, constraints, prior work) to reduce redundant explanations in future sessions."},{"step":"Reference Thoughtbox during task execution. When working on [TASK], ask Claude to check Thoughtbox for prior insights, decisions, or open questions related to the task.","action":"Use a command like: 'Check Thoughtbox for insights related to [SPECIFIC_TASK]. Are there prior decisions or constraints I should consider?'","tip":"Use specific keywords (e.g., 'accessibility,' 'budget') to retrieve relevant prior context quickly."},{"step":"Update Thoughtbox after completing tasks. Document key takeaways, resolved questions, and new open questions to maintain the ledger’s accuracy and relevance.","action":"After completing a task, run: 'Update Thoughtbox with the following: [SUMMARY_OF_TASK_OUTPUT], [RESOLVED_QUESTIONS], [NEW_OPEN_QUESTIONS].'","tip":"Use bullet points or structured formats (e.g., 'Key Insights:', 'Open Questions:') to make updates easy to scan later."},{"step":"Review Thoughtbox before critical meetings or handoffs. Use it to ensure continuity and avoid rehashing prior discussions.","action":"Before a meeting, run: 'Summarize the key insights and open questions from Thoughtbox for [MEETING_TOPIC].'","tip":"Highlight unresolved questions to prioritize them in the meeting agenda."},{"step":"Leverage cross-session learning. Thoughtbox persists across sessions, so use it to build institutional knowledge over time.","action":"At the end of a project, archive Thoughtbox with a summary of lessons learned for future reference. Example: 'Archive Thoughtbox for Acme Corp Website Redesign with key takeaways: prioritized accessibility first, saved 20% on costs by reusing design system.'","tip":"Include metrics (e.g., time saved, cost avoided) to demonstrate the value of Thoughtbox."}]
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/Kastalien-Research/thoughtboxCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Initialize a Thoughtbox session for [PROJECT_NAME] with the following context: [INITIAL_CONTEXT]. Use Thoughtbox to track reasoning, decisions, and learnings across this and future sessions. When working on [TASK], reference prior insights from Thoughtbox to avoid redundant explanations or rework. After completing [TASK], update Thoughtbox with key takeaways, open questions, and next steps for future reference.
```thoughtbox Project: Acme Corp Website Redesign Context: Client wants a modern, accessible, and high-converting landing page. Previous iterations focused on visual appeal but lacked clear CTAs and accessibility compliance. Budget is $15k, timeline is 6 weeks. Key Insights: - Client’s 2023 analytics showed 40% bounce rate on mobile due to slow load times (target: <2s). - Competitor analysis revealed 3 key UX patterns: sticky headers, micro-interactions, and minimalist forms. - Accessibility audit flagged color contrast issues in 70% of existing components (WCAG 2.1 AA required). Open Questions: - Should we prioritize A/B testing for CTAs or accessibility fixes first? - Can we reuse the existing design system to reduce costs? Next Steps: 1. Draft wireframes focusing on mobile-first design and sticky CTAs. 2. Run accessibility scan on wireframes before high-fidelity mockups. 3. Schedule stakeholder review to align on priorities. ``` **Task Output:** Designed 3 mobile-first wireframes with sticky CTAs, achieving 95% color contrast compliance. Open questions resolved: Client chose to prioritize accessibility fixes first due to legal risks. Updated Thoughtbox with revised next steps: finalize wireframes by EOD and share with dev team for feasibility review.
AI assistant built for thoughtful, nuanced conversation
Accelerate NP-complete problem solving
Cloud ETL platform for non-technical data integration
Get more done every day with Microsoft Teams – powered by AI
Customer feedback management made simple
Enterprise workflow automation and service management platform
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan