medic8d-dev/shit_in_a_vault
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

move inbox files to proper folders: research, configs, models, skills

Browse Source
This commit is contained in:
stateofshit
2026-08-15 20:55:56 +00:00
parent faf23926cb
commit 5ffaa23e8b
5 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
000-configs/Environment Map — Open WebUI Container.md
+84
View File
@@ -0,0 +1,84 @@
# Environment Map
Discovered: 2026-08-11
## Platform
| | |
| --- | --- |
| OS | Debian 13 (trixie) Linux, x86_64 |
| Shell | /bin/bash |
| User | unprivileged (no sudo) |
| Home | /home/user |
## Runtime
| Tool | Version |
| --- | --- |
| Python | 3.12.13 |
| Node.js | v22.23.0 |
| npm | 10.9.8 |
| pnpm | _not installed_ |
| Playwright | not globally available (check node_modules) |
| Vite | available locally |
## Auth
| Service | Status |
| --- | --- |
| GitHub (`gh`) | ✅ Logged in as `stateofshit` (SSH + token) |
| Git config | name: stateofshit · email: [thestateofshit@gmail.com](mailto:thestateofshit@gmail.com) |
| SSH keys | none found in ~/.ssh |
## Directory Structure
```
/home/user/
├── 00-incoming/ → raw downloads
├── 000-configs/ → tool docs, scripts, Google creds
│ ├── GH_CLI_INSTRUCTIONS.md
│ ├── PLAYWRIGHT_BROWSER_INSTRUCTIONS.md
│ └── VITE_PREVIEW_INSTRUCTIONS.md
├── 01-docs/ → documentation
├── 02-repos/ → local git clones
│ ├── shit_in_a_vault/ ← main Obsidian vault (private, synced)
│ ├── superpowers/
│ ├── webby/ ← public project
│ └── shit_flare/ ← public, Cloudflare
├── 03-projects/ → active workspaces
│ ├── ai-chat-agent/
│ ├── msg-extractor/
│ └── rag_project/
└── .env.cloudflare ← Cloudflare credentials file
```
## GitHub Repos (7 total)
| Remote | Private? | Notes |
| --- | --- | --- |
| stateofshit/shit_in_a_vault | private | Main vault |
| stateofshit/shit_flare | public | Cloudflare project |
| stateofshit/webby | public | Web project |
| stateofshit/bendover-api | private | API |
| stateofshit/code | private | General code |
| stateofshit/da_vault | private | Another Obsidian vault |
| stateofshit/state-shit-backup | private | System defaults backup |
## Key URLs
* Vite preview: [https://preview.boogerclub.com](https://preview.boogerclub.com)
* Vault remote: github.com/stateofshit/shit_in_a_vault
## Missing / Notable
* No pnpm installed — may need `npm i -g pnpm` or use `npx`
* No global Playwright binary — check per-project installs
* No SSH keys — GitHub uses token-based auth via `gh`
* No Docker access assumed (unprivileged container)
* Internal services available: `open-webui:8080`, `searxng:8080`
000-configs/Master Skills and Tools Documentation.md
+328
View File
@@ -0,0 +1,328 @@
```markdown
# Master Skills and Tools Documentation
This document provides a comprehensive overview of all available skills, tools, and directory structures accessible in this technical workspace.
## Overview
This workspace is a sophisticated technical environment with extensive capabilities for development, testing, documentation, and system administration. It combines AI-powered development tools with traditional command-line interfaces and version control systems.
## Knowledge Base Skills
### Available Skills
#### 1. **System Processing Skills**
- **brainstorming-11** (Superpowers Brainstorming SKill)
- Purpose: Structured brainstorming and planning methodology
- Use case: Initial project planning and concept development
- **subagent-driven-development-03** (Subagent-Driven Development)
- Purpose: Execute plans by dispatching fresh implementer subagents per task with review cycles
- Use case: Complex multi-step implementation projects requiring systematic execution
- **executing-plans-01** (Executing Plans)
- Purpose: Load plan, review critically, execute all tasks, report completion
- Use case: Planning and execution of structured tasks
#### 2. **Cloudflare Development Skills**
- **workers-best-practices** (Workers Best Practices)
- Purpose: Reviews and authors Cloudflare Workers code against production best practices
- Use case: Cloudflare Workers development and code review
- **durable-objects** (Durable Objects)
- Purpose: Create and review Cloudflare Durable Objects for stateful coordination
- Use case: Chat rooms, multiplayer games, booking systems, RPC methods
- **wrangler** (Wrangler)
- Purpose: Cloudflare Workers CLI for deploying, developing, and managing Workers
- Use case: Cloudflare Workers deployment and configuration
- **building-mcp-servers-on-cloudflare-21** (Building MCP Servers)
- Purpose: Building MCP servers on Cloudflare with updated SDK knowledge
- Use case: MCP server development with Cloudflare integration
- **building-ai-agent-on-cloudflare** (Building AI Agent)
- Purpose: Building AI agents on Cloudflare with updated SDK knowledge
- Use case: AI agent development using Cloudflare Agents SDK
#### 3. **Testing and Performance Skills**
- **playwright-best-practices** (Playwright Best Practices)
- Purpose: Browser testing and screenshot capabilities
- Use case: End-to-end testing and visual regression testing
- **web-perf** (Web Performance)
- Purpose: Analyzes web performance using Chrome DevTools
- Use case: Web performance auditing and optimization
#### 4. **Business and User Experience Skills**
- **solo-dev-fiverr** (Solo Dev Fiverr)
- Purpose: Power skill for solo Node/JS/TS dev selling modern dashboard and UI work
- Use case: Client deliverables, Fiverr gigs, premium UI development
- **marketing-psychology** (Marketing Psychology)
- Purpose: Apply psychological principles to marketing
- Use case: Consumer behavior, persuasion, decision-making optimization
- **ux-content-formatte-** (UX Content Formatter)
- Purpose: Formats text, reports, and dashboard data into scannable layouts
- Use case: Content formatting, report generation, data presentation
#### 5. **Legal and Reference Skills**
- **courtlistener-api** (Courtlistener API)
- Purpose: Legal case law database with PACER data and judge profiles
- Use case: Legal research and case law analysis
#### 6. **Process Skills**
- **dispatching-parallel-agents-04** (Dispatching Parallel Agents)
- Purpose: Delegate tasks to specialized agents with isolated context
- Use case: Parallel processing and specialized task execution
- **find-skills** (Find Skills)
- Purpose: Discover and install agent skills
- Use case: Skill discovery and capability expansion
## Available Tools
### File and Directory Operations
- **list_files**: Return structured listing of files and directories
- **read_file**: Read file contents with optional line ranges and image support
- **display_file**: Open files in viewer (for visual inspection)
- **write_file**: Write text content to files with automatic directory creation
- **replace_file_content**: Find and replace exact strings in files
- **view_file**: Get file content by ID with pagination support
- **list_processes**: List all tracked background processes
### Calendar and Scheduling
- **create_calendar_event**: Create calendar events, reminders, alarms
- **search_calendar_events**: Search calendar events by text and date range
- **update_calendar_event**: Update existing calendar events
- **delete_calendar_event**: Delete calendar events permanently
### Git and Version Control
- **run_command**: Run shell commands in background with output tracking
- **send_process_input**: Write text to process stdin
- **kill_process**: Terminate processes
- **get_process_status**: Get process output and status
- **list_processes**: List all tracked background processes
### Knowledge Base Management
- **list_knowledge**: List knowledge bases, files, and notes
- **query_knowledge_files**: Semantic/vector search across knowledge files
- **view_knowledge_file**: Get content from knowledge base files
- **search_knowledge_files**: Search files by filename across knowledge bases
- **grep_knowledge_files**: Exact text search across knowledge files
- **write_note**: Create new notes with markdown content
- **view_note**: Get full note content by ID
- **search_notes**: Search saved notes by title and content
- **replace_note_content**: Update existing notes
### Project Management
- **create_tasks**: Create visible task checklists for multi-step work
- **update_task**: Mark tasks as completed/in_progress/pending/cancelled
### Documentation Generation
- **writing-plans**: Create comprehensive implementation plans with task decomposition
### Automation and Scheduling
- **create_automation**: Create scheduled automations with iCalendar RRULE
- **list_automations**: List scheduled automations
- **update_automation**: Update existing automations
- **toggle_automation**: Pause/resume automations
- **delete_automation**: Delete automations and history
### Research and Search
- **search_web**: Search the public web for current information
- **deep_research**: Multi-round research using Open WebUI web search
- **fetch_url**: Extract main text content from web pages
- **consult_council**: Orchestrates 3-stage council meetings
### Context and Library Management
- **context7_resolve-library-id**: Resolve package names to Context7-compatible library IDs
- **context7_query-docs**: Query up-to-date documentation from Context7
### Task Delegation
- **delegate_task**: Delegate focused work to parallel sub-agents
- **run_sub_agent**: Delegate tasks to sub-agents for autonomous completion
- **run_parallel_sub_agents**: Run multiple independent sub-agent tasks concurrently
### Time and Utilities
- **get_current_timestamp**: Get current Unix timestamp
- **calculate_timestamp**: Calculate timestamps for date filtering
- **timer**: Set one-shot timers
## Directory Structure
### Root and Main Directories
#### `/home/user/000-configs/` - System Configuration
- **GH_CLI_INSTRUCTIONS.md**: GitHub CLI usage instructions
- **PLAYWRIGHT_BROWSER_INSTRUCTIONS.md**: Playwright browser testing instructions
- **VITE_PREVIEW_INSTRUCTIONS.md**: Vite development server preview instructions
- **docs/**: Documentation folder with internal reference materials
- **google/**: Directory for Google-related tools or configurations
#### `/home/user/02-repos/` - Code Repositories
- **shit_in_a_vault/**: Private Obsidian vault for note-taking and knowledge management
- Contains structured markdown documentation with YAML frontmatter
- Used for project documentation and knowledge retention
- **webby/**: Separate web development project repository
- **fuckgovda_vault/**: Previously deleted locally but exists remotely Obsidian vault
#### `/home/user/02-repos/shit_in_a_vault/` - Obsidian Vault Structure
**Vault Rules and Configuration:**
- **04-models/Vault-Rules.md**: Core vault editing rules and conventions
- **04-models/model-memory.md**: Historical context and memory
- **000-configs/tools/**: Tool documentation and instructions
- **01-logs/daily/**: Automated daily notes
- **02-notes/**: Short notes, scratch work, per-topic research
- **03-archive/**: Completed or superseded materials
- **04-models/**: Rules, memory, boot prompt, model identity
- **05-handoffs/**: Model-to-model transition materials
- **06-research/**: Long-form research with citations
- **07-tasks/**: Task tracking files with metadata
- **00-assets/**: Attachments and media files
#### `/home/user/02-repos/shit_in_a_vault/04-models/` - Model Configuration
- **Vault-Rules.md**: Essential editing rules for all vault files
- **model-memory.md**: Historical context and memory
- Additional model configuration files may exist
#### `/home/user/projects/` - Development Projects
- Local project workspace for development activities
- Temporary project directories
- Experimentation and prototyping areas
## Integration and Usage Patterns
### Knowledge Management Workflow
1. **Research Phase**: Use `search_web` or `deep_research` for external information
2. **Documentation**: Store findings in `02-notes/` or `06-research/` using Obsidian vault structure
3. **Reference**: Access knowledge via `query_knowledge_files` or `search_notes`
4. **Automation**: Schedule documentation updates using `create_automation`
### Development Workflow
1. **Planning**: Use `writing-plans` for comprehensive task breakdown
2. **Implementation**: Execute tasks via `executing-plans` or `subagent-driven-development`
3. **Testing**: Use `playwright-best-practices` for browser testing
4. **Version Control**: Track changes via Git commands and `run_command`
### System Administration
1. **Process Management**: Monitor and manage background processes with `list_processes`
2. **Calendar Integration**: Schedule tasks and reminders with `create_calendar_event`
3. **Documentation Maintenance**: Keep skills and tools updated using `write_file`
## Capabilities Summary
### Core Strengths
- **Comprehensive Documentation**: Extensive tool and skill coverage
- **Multi-modal Development**: Supports both AI-powered and traditional development
- **Automation Integration**: Full scheduling and automation capabilities
- **Knowledge Management**: Sophisticated Obsidian-based documentation system
- **Testing Infrastructure**: End-to-end testing with Playwright integration
- **Cloud Integration**: Full Cloudflare Workers and Durable Objects support
- **Parallel Processing**: Multiple agent capabilities for concurrent development
### Development Spectrum
- **Simple Scripts**: Direct command-line execution
- **Complex Projects**: Multi-agent, systematic development
- **Documentation**: Comprehensive automated documentation generation
- **Testing**: Full browser automation and performance analysis
- **Deployment**: Cloud deployment with Cloudflare integration
### Collaboration Features
- **Task Delegation**: Multiple agent coordination
- **Review Cycles**: Systematic review and approval processes
- **Documentation**: Comprehensive task and project tracking
- **Knowledge Sharing**: Repository-based knowledge management
## Technical Specifications
### Environment
- **Operating System**: Linux 7.0.0-1010-aws (Ubuntu 22.04 base)
- **Shell**: bash
- **Home Directory**: `/home/user`
- **Primary Development Areas**: `/home/user`, `/home/user/projects`, `/home/user/repos`
### Authentication and Access
- **SSH Key**: Available for secure connections
- **GitHub CLI**: v2.96.0 authenticated as `stateofshit`
- **Access Levels**: Multiple access tiers for different environments
### Available Technologies
- **Languages**: Node.js, Python 3.12.13, bash
- **Frameworks**: Vite, React (preview available at `https://preview.boogerclub.com`)
- **Testing**: Playwright browser automation
- **Deployment**: Cloudflare Workers integration
- **Documentation**: Obsidian vault with markdown and YAML support
### Preview and Testing
- **Development Server**: Vite development server with preview at `https://preview.boogerclub.com`
- **Browser Testing**: Playwright screenshot and full-page testing capabilities
- **Performance Analysis**: Chrome DevTools integration for web performance
## Usage Recommendations
### For Beginners
1. Start with simple tasks using `run_command` for basic operations
2. Explore documentation in `/home/user/000-configs/`
3. Use `list_files` to understand directory structure
4. Begin with `write_note` for simple note-taking
### For Intermediate Users
1. Explore `subagent-driven-development-03` for complex projects
2. Use `search_web` for external research
3. Implement automation with `create_automation`
4. Develop comprehensive documentation with `writing-plans`
### For Advanced Users
1. Utilize parallel processing with `run_parallel_sub_agents`
2. Implement sophisticated workflows with `delegate_task`
3. Create complex Cloudflare Workers with `wrangler`
4. Build advanced automation systems with `durable-objects`
## Contact and Support
For assistance with this system:
- Refer to specific tool documentation in `/home/user/000-configs/`
- Use `search_notes` to find relevant documentation
- Consult `context7_query-docs` for library-specific information
- Contact through GitHub repositories for code-specific issu
```
000-configs/skills/Superpowers Skill System Overview.md
+74
View File
@@ -0,0 +1,74 @@
# Superpowers Skill System Overview
## What is "using-superpowers (bootstrap)"?
The "using-superpowers (bootstrap)" is the foundational skill in the Superpowers methodology that governs how all other skills are used and accessed.
## Key Points:
1. **Foundation Skill**: It establishes the rules for skill invocation before ANY action
2. **Bootstrap Process**: Automatically injects skill context into every session
3. **Mandatory Rule**: Skills must be invoked before ANY response, including clarifying questions
4. **Automatic**: No manual initialization needed - happens automatically via the plugin
## How it works:
1. The superpowers plugin at `.opencode/plugins/superpowers.js` handles the bootstrap
2. It discovers and loads all skills from `/home/user/02-repos/superpowers/skills/`
3. It injects the using-superpowers bootstrap content into the first user message
4. It makes all superpowers skills discoverable without manual configuration
## Available Skills:
The system includes 10+ core skills:
* **brainstorming** - Socratic design refinement
* **writing-plans** - Detailed implementation plans
* **executing-plans** - Batch execution with checkpoints
* **subagent-driven-development** - Fast iteration with review
* **using-git-worktrees** - Parallel development branches
* **finishing-a-development-branch** - Merge/PR decision workflow
* And more...
## Philosophy:
* **Test-Driven Development** - Write tests first, always
* **Systematic over ad-hoc** - Process over guessing
* **Complexity reduction** - Simplicity as primary goal
* **Evidence over claims** - Verify before declaring success
## Workflow:
1. **brainstorming** - Activates before writing code
2. **using-git-worktrees** - Creates isolated workspace
3. **writing-plans** - Breaks work into tasks
4. **subagent-driven-development** or **executing-plans** - Executes with reviews
5. **finishing-a-development-branch** - Completes work
## How to use:
When starting any conversation, the using-superpowers skill should be invoked first to establish how to find and use skills, with the requirement that skill invocation happens before ANY response.