my-config

Use this skill when the user asks to analyze, create, or update an investment asset/company in Notion Assets / Investments. Produces professional-grade, evidence-backed asset research and then creates or updates the matching Notion asset page after confirmation.

Cartography, deep codebase map, repo map, onboarding map, or navigation index. Use for explicit codebase mapping/onboarding requests that need multiple cartography subagents and docs/indexes.

Comment code, explain functions, or add documentation comments. Use to make code understandable after implementation.

Commit, git commit message, or staged changes summary. Use by github agent only when the user explicitly requests a commit.

Medium article, long-form article, essay, or article from notes. Use when the user asks to create/write a Medium-style article using Content Vault evidence, positioning, and humanization rules.

LinkedIn post, social post, short content draft, or post from notes. Use when the user asks to write/create a LinkedIn/social post using the Content Vault voice, evidence, and anti-AI-writing rules.

Weekly content generation, content ideas from week, repurpose recent notes, or content calendar. Use when the user asks what to post from recent work or wants LinkedIn/article ideas from vault notes.

Create architecture docs, stack choices, Mermaid diagrams, cost/ops estimates, module maps, or system design files. Use when mapping full architecture or changing structure.

Create doc, documentation, repo docs, or vault docs. Use when writing concise project documentation inside the codebase and optionally ObsidianMemory.

Create index, routing index, repo index, or vault index. Use to make compact navigation maps from documentation and cartography.

Create-plan, PLAN file, TASK_CONTEXT.md, implementation plan, or planning template. Use by the plan agent to write PLAN-*.md, maintain TASK_CONTEXT.md, and invoke plan-contest.

Create-pr, pull request, or PR body. Use by github agent when the user explicitly requests a PR.

Create-project, new project vault setup, or project folder template. Use by the vault agent to create a project inside ObsidianMemory using Dev Vault, PM, and domain vault routing.

File search, code search, or exploration summary. Use to summarize focused repository/vault searches with exact paths and relevance.

Frontend-design, DESIGN.md, UI quality, design system, visual identity, contrast, hero/section layout, and component reuse. Use before and after frontend implementation.

Grill me, clarify idea, interview user, or stress-test vague requirements. Use when more information is needed before planning or building.

Implementation review, final diff review, or logic check. Use to compare code changes against the original goal, plan, and verification output.

Kanban-create, create task, or write ticket. Use by kanban/vault workflows to create structured task records in ObsidianMemory PM and optionally link Dev Vault project kanban.

Kanban-search, find task, ticket lookup, or board search. Use by kanban/start-session workflows to locate relevant ObsidianMemory PM tasks and Dev Vault project kanban items.

Memory-write, save learning, coding advice, decision, or reusable project knowledge. Use to write durable notes into the configured ObsidianMemory vaults.

Onboard-project, existing codebase onboarding, or create vault project from current repo. Use before cartography/indexing an existing repo into ObsidianMemory Dev Vault and PM.

Project sum-up, project summary, or status synthesis. Use to summarize a project from vault notes, docs, and implementation history.

Review code quality, logic, slop, oversized files, and simplification opportunities. Use after implementation before tests/final response.

Use this skill when the user asks to analyze an investment sector/theme, build a public-company universe, rank candidates, and optionally create/update multiple Notion Assets pages using the structured asset template.

Simplify recently modified code, preserve behavior, reduce nesting/duplication, improve naming, or refine React/server code. Use after review and before final verification.

Start-session, prepare existing project context, load vault notes, or check kanban before planning/building. Use by CTO when durable project context matters.

Test code, write tests, or validate implementation. Use when creating focused tests from the plan/spec rather than from implementation details.

Vault-search, Obsidian search, memory lookup, or project note lookup. Use to search the configured ObsidianMemory supervault and route to Dev, Research, Content, Investment, PM, or legacy vault context.

Wrap-up, implementation summary, or final handoff. Use after build/test/review to explain what changed and what remains.

AGENTS.md, agent harness, PROGRESS.md, DECISIONS.md, feature_list.json, or repo state files. Use when creating or updating a repository's agent-readable harness and vault progress mirror.