mikevalstar

okq CLI contract — commands, --json output, and exit codes for querying OKF bundles, Obsidian vaults, or any Markdown-with-frontmatter collection. Background reference, loaded whenever okq or OKF is in use.

Search and navigate an OKF bundle, Obsidian vault, or any Markdown-with-frontmatter collection with okq instead of grep. Use to find related docs, read a section, or see what links to what before starting work, or when the user mentions okq/OKF.

Find and fix OKF doc-bundle rot with okq — dead links, orphans, stale status. Use after renames or moves, before committing doc changes, or in CI.

Author or edit an OKF document (ADR, feature spec, runbook, wiki page). Use when writing docs in an OKF bundle — covers okq's templates, frontmatter, cross-links, and verifying the result.

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

Write or update lifecycle documentation in `docs/` that traces a feature's full journey through the codebase — from input to storage to scheduling to execution to UI. Use this skill whenever the user asks to "write a lifecycle doc", "document the lifecycle", "create a lifecycle reference", or "update the lifecycle docs" for any feature or system in the project. Only trigger on explicit lifecycle documentation requests, not general docs or requirements work.

Write and maintain concise, living product requirements in `docs/requirements/` for this project. Use this whenever the user asks to write requirements, scope a feature, plan implementation, break work into features or sub-features, document what is done or in progress, or update requirement docs after coding. Prefer this even when the user says "plan", "spec", "roadmap", "document this feature", or "update the docs" rather than explicitly saying "requirements."

Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.

Core caching with @gorgonjs/gorgon: Gorgon.get, Gorgon.put, Gorgon.clear (with wildcards), Gorgon.overwrite, expiry policies, cache key naming, concurrency deduplication, hooks, settings, custom storage providers via IGorgonCacheProvider, @gorgonjs/file-provider for disk persistence, and @gorgonjs/clearlink for distributed cache invalidation via WebSocket. Use when caching API calls, database queries, or any async operation in TypeScript/JavaScript.

React integration for @gorgonjs/gorgon via @gorgonjs/react: useGorgon hook with data/error/loading/refetch state, clearGorgon helper for cache invalidation from components, cache key management tied to component lifecycle, and DIY hook patterns. Use when building React components that need cached async data fetching.

How to use the @gorgonjs/gorgon caching library for async functions in TypeScript/JavaScript. Use this skill whenever the user wants to cache API calls, database queries, or any async operation; when they mention Gorgon, @gorgonjs, or ask about caching promises/async functions; when they need help with cache invalidation, expiry policies, custom storage providers, or React cache hooks; or when they're building a Node.js or browser app that would benefit from request deduplication or caching. Also trigger when the user is working in a project that already imports @gorgonjs/gorgon and needs guidance.