keejkrej
- 13 skills
- 0 followers
- 4 hours ago last updated
- ▌ Dev · keejkrej bundleDevelopment workflows for the playwright-cli repository. Use when the user asks about rolling dependencies, releasing, or other repo maintenance tasks.
- ▌ Context7 Docs · keejkrejFetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service. Use whenever the user asks about a specific library — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot — because training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer. Do not rely on training data for API details, signatures, or configuration options — they are frequently out of date. Prefer this over web search for library documentation.
- ▌ Core · keejkrej bundleCore agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
- ▌ Coss · keejkrej bundleHelps implement coss UI components correctly. Use when building UIs with coss primitives (buttons, dialogs, selects, forms, menus, tabs, inputs, toasts, etc.), migrating from shadcn/Radix to coss/Base UI, composing trigger-based overlays, or troubleshooting coss component behavior. Covers imports, accessibility, Tailwind styling, and common pitfalls.
- ▌ QA · keejkrej bundleEstablish or harden a test cage for a codebase — the automated suite and conventions that lock behavior so change is safe. Use when surveying test health, introducing unit/acceptance/integration lanes, wiring coverage or mutation/CRAP gates, fixing a flaky or slow suite, or writing the project's testing policy. Not for shipping a feature (use Matt's wayfinder/implement/tdd flow), filing bugs from a QA session (triage), or one-off hard diagnosis (diagnosing-bugs).
- ▌ Solidjs · keejkrej bundleUse when writing, reviewing, debugging, or testing Solid applications and libraries that use `solid-js`, `@solidjs/router`, `@solidjs/start`, or `@solidjs/meta`; covers fine-grained reactivity, components and props, stores, resources, routing, server functions, SSR and hydration, metadata, and Solid component tests.
- ▌
- ▌ Gh Pr Description · keejkrej bundleDrafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.
- ▌
- ▌ Toolkit Guide · keejkrej bundleHow to triage an account and verify packaged skill resources with the toolkit CRM extension.
- ▌ Memory · keejkrejMaintain AGENTS.md (purpose, rules, tech stack) and docs/agent/ notes so context survives sessions. Use when starting work in a repo, syncing AGENTS.md from config and chat, recording decisions or preferences, resuming prior tasks, or when the user mentions agent memory, notes, or AGENTS.md.
- ▌ Tooling · keejkrej bundleDevelopment workflow, verification, and scaffolding. Lint/format/typecheck, CI, agent verification, Vite+ frontend toolchain, greenfield scaffolds, and npx command reference. Use after `techstack` decides the product-domain stack.
- ▌ Techstack · keejkrej bundleDefault product-domain stack guidance — frontend, backend, desktop, agent, scientific, static sites, and cross-surface contracts. Covers React, Effect Atom, TanStack Router, Effect Platform on Bun, Astro, coss-ui, Tailwind v4, Turborepo, Expo, NativeWind, React Native Reusables, FastAPI, Axum, Electron, CMake/Qt/VTK/ITK, and contracts (Effect Schema, OpenAPI, AsyncAPI). Use when choosing libraries, runtimes, architecture, refactoring stack, or comparing frameworks.