Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By amoscicki
Subagent that researches technology documentation. Saves to .claude/knowledge/ or custom path. Intelligently updates existing files (preserves current, replaces outdated, adds missing)
npx claudepluginhub joshuarweaver/cascade-code-devops-misc-1 --plugin amoscicki-dotfilesUses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Import external documentation locally - bypass AI-blocking sites via Context7, WebFetch, or Playwright
Zero-config knowledge base MCP server โ search, manage, and embed documentation (SQLite default, PostgreSQL optional)
Document search with hybrid BM25/semantic retrieval, GraphRAG knowledge graphs, and pluggable providers for Claude Code. Index documentation and code, then search using keyword matching, semantic similarity, graph relationships, or comprehensive multi-mode fusion.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
AI-powered wiki generator for code repositories. Generates comprehensive, Mermaid-rich documentation with dark-mode VitePress sites, onboarding guides, deep research, and source citations. Inspired by OpenDeepWiki and deepwiki-open.
Claude + Obsidian knowledge companion. Sets up a persistent, compounding wiki vault (Karpathy's LLM Wiki pattern). v1.7 "Compound Vault" + v1.8 methodology modes close 5 of 5 priority gaps from the May 2026 compass artifact. Ships: substrate alignment with kepano/obsidian-skills, default Obsidian CLI transport, hybrid retrieval (contextual prefix + BM25 + cosine rerank per Anthropic's Sept 2024 research), per-file advisory locking for multi-writer safety, pre-commit verifier agent, AND methodology modes (LYT / PARA / Zettelkasten / Generic) for first-class organizational support no other Claude+Obsidian competitor offers. v1.7.x audit closure: every BLOCKER + HIGH + MEDIUM + LOW finding from the v1.7.0 audit is CLOSED or DEFERRED-with-rationale. Optional DragonScale Memory extension (log folds, deterministic addresses, semantic tiling lint, boundary-first autoresearch).
Google Tag Manager + Analytics Admin APIs CLI for Claude Code (shared OAuth2)
Semantic codebase search with pgvector embeddings. Multi-project support with persistent daemon. Use semantic search BEFORE grep/glob.
Manage project knowledge base. Use 'init' to setup, or provide a topic to research.
Payload CMS query/mutate CLI for Claude Code (persistent local API)
Multi-agent parallel task orchestration with wave-based execution, automatic auditing, and model escalation
Automated Windows 11 development environment setup using PowerShell scripts and configuration management.
Transform a factory-reset Windows 11 machine into a fully configured development workstation:
dotfiles/
โโโ .claude/commands/ # SpecKit slash commands for Claude Code
โโโ .specify/ # Spec-driven development templates
โโโ windows-install-scripts/ # PowerShell Windows automation scripts
โโโ powershell/ # PowerShell profile config (planned)
โโโ git/ # Git configuration (planned)
โโโ plugin.json # Claude Code plugin definition
โโโ .gitignore # Excludes secrets and working files
Current Status: Implementation complete! All scripts and configuration files are ready for use.
Prerequisites:
Installation Steps:
Clone the repository:
git clone https://github.com/amoscicki/dotfiles.git
cd dotfiles
Run the master installation script:
# Interactive installation (with confirmations)
.\windows-install-scripts\install.ps1
# Fully automated installation (no prompts)
.\windows-install-scripts\install.ps1 -Unattended
# Preview what would be installed (dry-run)
.\windows-install-scripts\install.ps1 -WhatIf
Complete manual post-installation steps:
# Update Git user configuration (REQUIRED)
git config --global user.name "Your Name"
git config --global user.email "your.email@example.com"
# Install Claude Code plugin (if Claude Code installed)
# In Claude Code, run:
/plugin install file://P:/dotfiles
# Or from GitHub:
/plugin install github.com/amoscicki/dotfiles
# Restart PowerShell to load profile with Oh My Posh
Verify installation:
choco --version
git --version
node --version
pnpm --version
gh --version
fzf --version
oh-my-posh --version
Time Estimate: ~30 minutes (excluding download times)
From GitHub:
/plugin install github.com/amoscicki/dotfiles
Local development:
/plugin install file://P:/dotfiles
Verify:
/plugin list
/speckit.constitution
This makes all SpecKit commands (/speckit.*) available globally in Claude Code.
git clone https://github.com/amoscicki/dotfiles.git dotfiles
cd dotfiles
Commands in .claude/commands/ are available when working in this directory.
This dotfiles repository follows the principles defined in .specify/memory/constitution.md:
Public by Default - All configuration files, scripts, and documentation are safe for public repositories. Sensitive data excluded via .gitignore or stored externally using secure credential management.
Automation First - Manual setup steps minimized through PowerShell scripts, Chocolatey package managers, and symlink automation. Installation achievable through a single master script execution.
Modular & Independent - Each tool's configuration is self-contained in its own directory. Configurations have no hidden dependencies on other configurations. Each module is installable independently via its own script.
Spec-Driven Development - All significant features follow SpecKit workflow: specification โ planning โ tasks โ implementation. Changes are documented in spec files before implementation.
Documentation as Code - Every script includes comments explaining its purpose and usage. Every configuration directory contains a README or inline comments describing the configuration's purpose. The main README is kept current with actual repository structure and capabilities.
Chocolatey Installation Fails:
logs/ directory for detailed error messages