inkeep
@inkeep Organization
Public Skills
product-surface-areas
by inkeep
Consolidated dependency graph of Inkeep customer-facing surface areas (UIs, CLIs, SDKs, APIs, protocols, config formats). Example use: as a prd-time (planning/brainstorming phase) or post-change checklist to understand the full scope of side-effects or what making one change to the product means for the rest. Use whenever you need to understand the "ripple" out effects of any change.
write-docs
by inkeep
"Write or update documentation for the Inkeep docs site (agents-docs package). Use when: creating new docs, modifying existing docs, introducing features that need documentation, touching MDX files in agents-docs/content/. Triggers on: docs, documentation, MDX, agents-docs, write docs, update docs, add page, new tutorial, API reference, integration guide."
adding-env-variables
by inkeep
"Guide for adding new environment variables to the codebase. Ensures env.ts schemas include descriptions and .env.example is kept in sync. Triggers on: add env variable, new environment variable, env.ts change, add config variable, INKEEP_, adding to .env."
manage-database-usage
by inkeep
"How to correctly access the Doltgres manage database with branch-scoped connections. Use when reading or writing manage data (agents, tools, projects, credentials, triggers, evaluators, etc.). Triggers on: manage database, withRef, c.get('db'), manageDbPool, branch checkout, doltgres, ref-scope, branchScopedDb, AgentsManageDatabaseClient."
find-similar
by inkeep
Find similar or analogous code patterns elsewhere in a codebase. Use when answering "Do we do something similar elsewhere?" or "What existing patterns match this?" Returns factual findings about similar code - locations, similarity type, and confidence.
accessibility-checklist
by inkeep
Accessibility review checklist for React/Next.js components built on Radix UI / shadcn/ui. Covers component library misuse, form accessibility, accessible names, keyboard interaction, focus management, and dynamic content. Loaded by pr-review-frontend.
next-best-practices
by inkeep
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
internal-surface-areas
by inkeep
Dependency graph of internal subsystems, infrastructure, and tooling (everything NOT customer-facing). Use during planning, PR review, or refactoring to understand the internal ripple effects of a change. Complements product-surface-areas (which covers customer-facing surfaces).
audience-impact
by inkeep
Who does this change affect and how does it reach them? Maps audiences (roles × deployment modes) to impact propagation — immediate, next-publish, next-deploy, or silent. Use when planning, implementing, or reviewing a change to understand blast radius by audience. Complements product-surface-areas and internal-surface-areas (which catalog what exists; this skill tells you who cares). Triggers: who is affected, blast radius, breaking change, audience, persona, impact analysis, changeset needed, docs needed.
web-design-guidelines
by inkeep
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
vercel-composition-patterns
by inkeep
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
api-logging-guidelines
by inkeep
"Best practices and guidelines for using logger in API routes. Defines appropriate logging levels, what to log, and when to avoid logging. Use when implementing or reviewing API route logging, debugging strategies, or optimizing log output."
data-model-changes
by inkeep
"Guide for making changes to the database schema, validation, types, and data access layer. Use when adding tables, columns, relations, or modifying the data model. Triggers on: add table, add column, modify schema, database change, data model, new entity, schema migration."
vercel-react-best-practices
by inkeep
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
next-cache-components
by inkeep
Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag
next-upgrade
by inkeep
Upgrade Next.js to the latest version following official migration guides and codemods
ship
by inkeep
"Orchestrate any code change from requirements to merge-ready PR — scope-calibrated from small fixes to full features. Composes /spec, /implement, /review, and /research with depth that scales to the task: lightweight spec and direct implementation for bug fixes and config changes, full rigor for features. Use for ALL implementation work regardless of perceived scope — the workflow adapts depth, never skips phases. Triggers: ship, ship it, feature development, implement end to end, spec to PR, implement this, fix this, let's implement, let's go with that, build this, make the change, full stack implementation, autonomous development."
browser
by inkeep
"Browser automation with Playwright — navigate pages, fill forms, take screenshots, test responsive design, validate UX, test login flows, check links, inspect network requests, inject JavaScript, monitor console errors, capture network traffic, record video, inspect browser state, run accessibility audits, measure performance, simulate network conditions, discover page structure, persist auth sessions, create annotated GIFs, handle dialogs, dismiss overlays, capture traces, generate PDFs, and download files. Headless by default for CI/Docker. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform browser-based testing. Triggers: playwright, browser test, browser automation, web test, screenshot, responsive test, test the page, automate browser, headless browser, UI test, console errors, console monitoring, network inspection, network capture, accessibility audit, a11y test, performance metrics, web vitals, video recording, browser state, localStorage, network simulation, offline testing, page structure, accessibility tree, authenticated testing, auth state, session reuse, annotated gif, dialog handling, overlay dismissal, cookie banner, tracing, trace viewer, pdf generation, file download, time manipulation, websocket interception."
gslides
by inkeep
Create branded Google Slides presentations using Figma brand assets and Google Slides MCP. Use when asked to create a deck, presentation, pitch, or slides. Supports customer decks, sales presentations, internal updates, and product overviews. Pulls brand tokens (colors, typography, layouts) from Figma and creates slides in Google Slides. Requires figma and google-slides MCP servers.
saas-session-recon
by inkeep
"Validate whether a SaaS platform's APIs can be accessed using browser session cookies — testing feasibility of a Chrome extension session proxy. Connects to user's authenticated Chrome, enumerates cookies, captures network traffic, tests official and internal APIs with cookie auth, checks Origin/CSRF requirements, and produces a structured findings document with a credential extraction recipe. One platform at a time. Triggers: session recon, cookie auth testing, extension proxy feasibility, SaaS API cookie test, session proxy validation."
nest-claude
by inkeep
"Spawn child Claude Code instances from a parent Claude Code session. Covers the env guard pattern, stdin redirection, parallel execution, monitoring, and result collection. Use when you need to run multiple independent Claude Code processes concurrently for tasks like parallel research, bulk code review, multi-repo operations, or any work that benefits from full isolated Claude Code sessions rather than lightweight Task-tool subagents. Triggers: spawn claude, nested claude, parallel claude, child process, subprocess claude, run N instances, concurrent agents, fan-out."
research
by inkeep
"Conduct technical research and produce formal reports by default. Can also deliver findings directly or update/extend an existing report. Reports default to <repo-root>/reports/ when in a git repo, or ~/reports/ otherwise. Use when investigating technologies, comparing systems, analyzing codebases, documenting architectures, gathering context for decisions, or when asked to refresh/update prior research."
debug
by inkeep
Systematic debugging for local development. Enforces root cause investigation — never implements fixes. 5-phase: Triage, Reproduce & Comprehend, Investigate, Classify, Report & Recommend. Classifies root causes as dev environment/config vs code bugs. Uses tools aggressively for observable verification — runs commands, queries state, checks actual output. Includes triage playbooks, hypothesis-test-refine cycles, tool patterns, agent metacognition (loop detection, strategy switching, confidence calibration), escalation heuristics. Presents root cause findings with recommended fix strategy and hands off to implementer. Two autonomy modes: Supervised (propose diagnostic mutations, wait for approval) and Delegated (iterate freely within approved action classes). Composable with /implement, /qa, /ship, /tdd, /explore. Triggers: debug, fix bug, root cause, why is this failing, investigate error, diagnose, troubleshoot, something broken, test failure, crash, regression, stack trace, error message, it worked before, flaky test, wrong output, not working, build failure, type error, exception, debugging.
implement
by inkeep
"Convert SPEC.md to spec.json, craft the implementation prompt, and execute the iteration loop via subprocess. Use when converting specs to spec.json, preparing implementation artifacts, running the iteration loop, or implementing features autonomously. Triggers: implement, spec.json, convert spec, implementation prompt, execute implementation, run implementation."