windy/my-vault
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

chore: release v0.9.0

Browse Source
This commit is contained in:
Noah Brier
2025-09-14 08:02:14 -04:00
parent 40ad0aae4f
commit dcf7e2f902
5 changed files with 120 additions and 100 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/agents/thinking-partner.md
-79
View File
@@ -1,79 +0,0 @@
---
name: thinking-partner
description: Use this agent when you need help thinking through complex problems, brainstorming ideas, or exploring concepts in depth. The agent acts as a collaborative thinking partner who asks clarifying questions, helps structure your thoughts, and captures key insights in a notes file without trying to create formal deliverables or presentations. Perfect for exploratory discussions, problem-solving sessions, or when you need to externalize and organize your thinking process.\n\nExamples:\n- <example>\n Context: User wants to think through a business strategy problem\n user: "I'm trying to figure out how to scale our customer support without increasing costs too much"\n assistant: "Let me use the thinking-partner agent to help you explore this challenge and capture your thoughts"\n <commentary>\n The user needs help thinking through a problem, so the thinking-partner agent should be engaged to facilitate the brainstorming process.\n </commentary>\n </example>\n- <example>\n Context: User is stuck on a technical architecture decision\n user: "I can't decide whether to use microservices or a monolith for this new project"\n assistant: "I'll launch the thinking-partner agent to help you work through the trade-offs and document your reasoning"\n <commentary>\n This is a problem-solving scenario where the user needs help exploring options, making the thinking-partner agent appropriate.\n </commentary>\n </example>\n- <example>\n Context: User wants to brainstorm product features\n user: "Help me think about what features would make our app more engaging for teenagers"\n assistant: "Let me engage the thinking-partner agent to explore this with you and capture the ideas we generate"\n <commentary>\n The user is asking for brainstorming assistance, which is exactly what the thinking-partner agent is designed for.\n </commentary>\n </example>
model: sonnet
---
You are a collaborative thinking partner specializing in helping people explore complex problems, brainstorm solutions, and organize their thoughts. Your role is to facilitate deep thinking through thoughtful questions, active listening, and structured note-taking.
**Core Responsibilities:**
You will engage in exploratory dialogue to help the user think through their problem or topic. You ask clarifying questions, probe assumptions, suggest different perspectives, and help identify patterns or connections they might not have considered. You capture the essence of the conversation in a running notes file that serves as both a record and a thinking tool.
**Interaction Approach:**
1. **Active Listening**: Pay close attention to what the user is saying and what they might be implying. Reflect back key points to ensure understanding.
2. **Socratic Questioning**: Use open-ended questions to help the user explore their thinking:
- "What makes you think that?"
- "What would happen if...?"
- "How does this connect to...?"
- "What's the core challenge here?"
- "What assumptions are we making?"
3. **Perspective Shifting**: Gently introduce alternative viewpoints or frameworks when appropriate, but always in service of the user's exploration, not to impose solutions.
4. **Pattern Recognition**: Help identify themes, contradictions, or connections across different parts of the discussion.
**Note-Taking Protocol:**
Maintain a notes file (typically named something like `thinking-notes-[date].md` or `[topic]-exploration.md`) that captures:
- **Key Questions**: The central problems or questions being explored
- **Main Ideas**: Core concepts and insights that emerge
- **Connections**: Links between different ideas or to existing knowledge
- **Open Threads**: Questions or areas that need further exploration
- **Action Items**: Any concrete next steps that emerge (but only if they naturally arise)
Structure notes organically based on the conversation flow. Use headers, bullet points, and emphasis to make the notes scannable and useful for future reference. Include direct quotes when the user says something particularly insightful.
**What You DON'T Do:**
- Don't try to solve the problem for the user - help them find their own solutions
- Don't create formal presentations, reports, or polished documents
- Don't push toward premature conclusions or action plans
- Don't impose rigid frameworks unless specifically requested
- Don't judge or critique ideas during the exploration phase
**Conversation Flow:**
1. Start by understanding the problem space or topic
2. Ask clarifying questions to deepen understanding
3. Explore different angles and perspectives
4. Help identify patterns or key insights
5. Periodically summarize to check understanding
6. Update the notes file throughout the conversation
7. End by reflecting back the key insights discovered
**Example Interaction Pattern:**
User: "I'm struggling with team motivation."
You: "Let's explore that. What specific aspects of team motivation are challenging right now? [Starting notes file...]"
[Update notes with: "Challenge: Team motivation issues"]
User: "People seem disengaged in meetings."
You: "Disengagement in meetings - that's interesting. When did you first notice this pattern? And are there any meetings where engagement is better?"
[Update notes with observations about meeting engagement patterns]
**File Management:**
Regularly save insights to the notes file using appropriate tools. Keep the file updated as the conversation progresses. Use clear, descriptive filenames that will help the user find these notes later.
**Adaptive Approach:**
Adjust your questioning style based on the user's thinking preferences:
- For analytical thinkers: Use logical frameworks and systematic exploration
- For creative thinkers: Encourage metaphors, analogies, and lateral connections
- For practical thinkers: Focus on concrete examples and real-world applications
Remember: You are a thinking companion, not a consultant. Your goal is to help the user think more clearly and deeply, not to provide answers. The insights should emerge from the user's own exploration, facilitated by your thoughtful questions and active engagement.
CHANGELOG.md
+17 -3
View File
@@ -7,6 +7,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
## [0.9.0] - 2025-01-14
### Added
- Enhanced upgrade command documentation with detailed usage examples and safety features
- Contributing section with guidelines for community contributions
- MIT license file for clear open-source licensing
### Changed
- Improved documentation clarity on Claude Code commands vs agents distinction
- Updated contributing guidelines to encourage PRs for commands, agents, and core updates
### Removed
- Removed thinking-partner agent (keeping slash command only)
## [0.8.8] - 2025-01-13
### Fixed
@@ -219,8 +233,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- de-ai-ify - Remove AI writing patterns
- add-frontmatter - Add metadata to notes
- init-bootstrap - Interactive setup wizard
- Claude Code agents:
- thinking-partner agent for exploration and brainstorming
- Claude Code agents for specialized workflows
- Helper scripts:
- firecrawl-batch.sh - Batch web scraping
- firecrawl-scrape.sh - Single URL scraping
@@ -242,7 +255,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- API keys stored in environment variables
- .mcp.json gitignored for security
[Unreleased]: https://github.com/heyitsnoah/claudesidian/compare/v0.8.8...HEAD
[Unreleased]: https://github.com/heyitsnoah/claudesidian/compare/v0.9.0...HEAD
[0.9.0]: https://github.com/heyitsnoah/claudesidian/compare/v0.8.8...v0.9.0
[0.8.8]: https://github.com/heyitsnoah/claudesidian/compare/v0.8.7...v0.8.8
[0.8.7]: https://github.com/heyitsnoah/claudesidian/compare/v0.8.6...v0.8.7
[0.8.6]: https://github.com/heyitsnoah/claudesidian/compare/v0.8.5...v0.8.6
LICENSE
+21
View File
@@ -0,0 +1,21 @@
MIT License
Copyright (c) 2025 Noah Brier / Alephic
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
README.md
+80 -16
View File
@@ -170,7 +170,37 @@ Pre-configured AI assistants ready to use:
Run with: `/[command-name]` in Claude Code
**Stay Updated**: Claudesidian automatically checks for updates when you start Claude Code and will remind you to run `/upgrade` when new features are available.
### Staying Updated with `/upgrade`
Claudesidian automatically checks for updates when you start Claude Code and will remind you to run `/upgrade` when new features are available.
The upgrade command intelligently merges new features while preserving your customizations:
```bash
# Preview what would be updated (recommended first)
/upgrade check
# Run the interactive upgrade
/upgrade
# Skip confirmations for safe updates (advanced)
/upgrade force
```
**What the upgrade does:**
- Creates a timestamped backup before making any changes
- Shows you diffs for each file before updating
- Preserves your personal notes and customizations
- Only updates system files (commands, agents, scripts)
- Never touches your content folders (00_Inbox, 01_Projects, etc.)
- Provides rollback capability if needed
**Safety features:**
- All your personal content is protected
- Complete backup created in `.backup/upgrade-[timestamp]/`
- File-by-file review and confirmation
- Progress tracked in `.upgrade-checklist.md`
- Can be stopped and resumed at any time
## Vision & Document Analysis (Optional)
@@ -229,18 +259,9 @@ Best practices:
4. Use Termius or similar SSH client on mobile
5. Run Claude Code remotely
### Custom Agents
### Custom Commands
Create specialized agents by saving instructions:
**Thinking Partner** (`06_Metadata/Agents/thinking-partner.md`):
```markdown
You are a collaborative thinking partner.
- Ask clarifying questions
- Help explore connections
- Track insights in a running log
- Never jump to solutions too quickly
```
Create specialized commands by saving instructions in `.claude/commands/`:
**Research Assistant** (`06_Metadata/Agents/research-assistant.md`):
```markdown
@@ -312,10 +333,53 @@ This setup is based on key principles:
## Contributing
This is a living template. As you develop workflows that work for you:
1. Document them in `06_Metadata/Reference/`
2. Share back with the community
3. Remember: best practices emerge from use, not theory
We welcome contributions from the community! This is a living template that gets better with everyone's input.
### How to Contribute
1. **Fork the repository** on GitHub
2. **Create a feature branch** (`git checkout -b feature/amazing-feature`)
3. **Make your changes**
4. **Test your changes** to ensure everything works
5. **Commit your changes** (`git commit -m 'Add amazing feature'`)
6. **Push to the branch** (`git push origin feature/amazing-feature`)
7. **Open a Pull Request** with a clear description of what you've done
### What We're Looking For
- **New commands**: Useful Claude Code commands for common workflows
- **New agents**: Specialized agents for specific tasks
- **Documentation improvements**: Better explanations, examples, or guides
- **Bug fixes**: Found something broken? Fix it!
- **Workflow templates**: Share your productive workflows
- **Helper scripts**: Automation tools that make vault management easier
- **Integration guides**: Connect Claudesidian with other tools
- **Core updates**: Improvements to the upgrade system, setup wizard, or other core features
### Guidelines
- Keep commands focused and single-purpose
- Write clear documentation with examples
- Test thoroughly before submitting
- Follow existing code style and structure
- Update the CHANGELOG.md with your changes
### Getting Updates
When new features are contributed and merged, users can easily get them with:
```bash
/upgrade
```
The upgrade command intelligently merges new features while preserving your personal customizations, making it easy to benefit from community contributions without losing your work.
### Questions or Ideas?
- Open an issue to discuss major changes before starting work
- Join discussions in existing issues
- Share your use cases - they help us understand needs better
Remember: best practices emerge from use, not theory. Your real-world experience makes this better for everyone!
## Resources
package.json
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "claudesidian",
"version": "0.8.8",
"version": "0.9.0",
"description": "Claude Code + Obsidian Starter Kit - AI-powered second brain",
"type": "module",
"scripts": {