Loading...
Loading...
Found 27 Skills
Use when capturing screenshots of local projects, documenting web app UI, taking screenshots of localhost dev servers, or generating images for READMEs and docs. Use when asked to "screenshot my app", "capture the UI", "take a screenshot of localhost", "generate screenshots for docs", "batch screenshot my pages", or "set up shot-scraper".
Navigates C3 architecture docs and explores corresponding code to answer architecture questions. Use when the user asks: - "where is X", "how does X work", "explain X", "show me the architecture" - "find component", "what handles X", "diagram of X", "visualize X" - "describe X", "list components", "trace X", "flow of X" - References C3 IDs (c3-0, c3-1, adr-*) <example> Context: Project with .c3/ directory user: "explain what c3-101 does and how it connects to other components" assistant: "Using c3-query to navigate the architecture docs." </example> <example> Context: Project with .c3/ directory user: "show me a diagram of the C3 architecture" assistant: "Using c3-query to generate an architecture overview." </example> DO NOT use for changes (route to c3-change). DO NOT use for pattern artifact management — listing, creating, updating refs (route to c3-ref). Requires .c3/ to exist.
Create and manage Obsidian notes for projects, companies, technical challenges, brag documents, daily logs, AI conversations, and quick captures using the Obsidian CLI. Use when documenting projects, tracking job applications, recording interview challenges, maintaining brag documents, creating daily notes, or saving AI conversations. Triggers on "create project", "new project note", "document company", "job application", "technical challenge", "brag document", "daily note", "today's log", "obsidian note", "save conversation", "chat summary", "session summary", "save this", "capture this", "quick note".