vault-management
This skill should be used when the user asks to "manage notes", "update vault", "add to obsidian", "document in vault", "search my notes", "find related notes", or when working with Obsidian vault files. Also triggers when discussing knowledge management, note organization, or when Claude Code auto-captures commits, tasks, or component creation.
What this skill does
# Obsidian Vault Management Manage the Obsidian vault as a developer knowledge base and automatic work journal. ## When to Use Activate this skill when: - User requests note operations (add, search, update, import, link, archive) - Working with project documentation that should be stored in the vault - Auto-capturing commits, tasks, or Claude Code components - User asks about their notes, documentation, or knowledge base - Organizing or finding information in the vault ## Vault Structure ``` ~/guerra_vault/ ├── projects/ # Project-specific documentation ├── technologies/ # Technology knowledge (Laravel, React, etc.) ├── claude-code/ # Claude Code components │ ├── agents/ │ ├── hooks/ │ ├── skills/ │ └── tools/ ├── ideas/ # Feature ideas and experiments ├── personal/ # Career and learning goals ├── todo/ # Tasks and checklists ├── references/ # Bookmarks, snippets, cheatsheets ├── journal/ # Auto-captured events │ ├── commits/ # Git commit documentation │ ├── tasks/ # Completed task summaries │ └── creations/ # Component creation logs └── _archive/ # Archived notes ``` ## Frontmatter Standard All notes MUST include this YAML frontmatter: ```yaml --- title: "Note Title" description: "Brief description of the content" tags: [tag1, tag2, category] related: [[path/to/related-note]] created: YYYY-MM-DD updated: YYYY-MM-DD --- ``` **Rules:** - `title`: Descriptive, matches the main heading - `description`: One sentence explaining the content - `tags`: Always include the category as a tag - `related`: Wiki-link format, add related notes when relevant - `created`: Set once when created - `updated`: Update whenever the note changes ## Available Commands | Command | Purpose | |---------|---------| | `/obsidian-vault:init` | Set up vault configuration and structure | | `/obsidian-vault:add <category> <title>` | Create a new note | | `/obsidian-vault:search <query>` | Find notes by title, content, or tags | | `/obsidian-vault:update <note>` | Edit note frontmatter or append content | | `/obsidian-vault:import <file>` | Import external files with frontmatter | | `/obsidian-vault:list [category]` | List notes, optionally by category | | `/obsidian-vault:tags [--stats]` | View tags and usage statistics | | `/obsidian-vault:link <note1> <note2>` | Create bidirectional related links | | `/obsidian-vault:archive <note>` | Move note to archive | ## Auto-Capture Behavior The plugin automatically captures: ### Git Commits - Creates `journal/commits/YYYY-MM-DD-<slug>.md` - Includes: commit message, date, project, branch, files changed - Placeholder sections for "What" and "Why" (fill in with context) ### Task Completions - Creates `journal/tasks/YYYY-MM-DD-<slug>.md` - Captures subagent summaries - Includes: summary, what was done, decisions made ### Claude Code Components - Creates `claude-code/<type>s/<name>.md` - Tracks: agents, hooks, skills, tools - Also logs to `journal/creations/` ## Best Practices ### Creating Notes 1. Choose the appropriate category 2. Use descriptive titles 3. Add relevant tags immediately 4. Link to related notes when obvious ### Updating Notes 1. Update the `updated` date (done automatically by scripts) 2. Add new related links as connections emerge 3. Keep descriptions current ### Searching 1. Start broad, narrow with `--title`, `--content`, or `--tag` 2. Use `--category` to focus on specific areas 3. Check related notes for additional context ### Organization 1. Use consistent naming within categories 2. Archive rather than delete 3. Maintain bidirectional links ## Integration with Workflows ### After Completing Features When finishing a feature or fix: 1. Ensure commit is captured 2. Add/update project documentation 3. Link new notes to project README ### When Learning Technologies 1. Create note in `technologies/` 2. Link to projects that use it 3. Add code snippets as needed ### For Ideas and Experiments 1. Start in `ideas/` 2. Move to `projects/` when starting implementation 3. Archive if abandoned ## Additional Resources ### Reference Files - **`references/frontmatter-spec.md`** - Detailed frontmatter specification ### Configuration - Config: `~/.claude/obsidian-vault.json` - Vault path: `~/guerra_vault`
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.