context7-docs-research
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/context7-docs-research && cp -r /tmp/context7-docs-research/examples/plugin-packages/context7/skills/context7-docs-research ~/.claude/skills/context7-docs-researchSKILL.md
# Context7 Documentation Research 1. Identify the exact library, framework, product, and version from the request or current project. 2. Resolve the library identity before querying documentation. 3. Ask focused documentation questions and keep retrieved context bounded. 4. Prefer API references, migration guides, and official examples that match the installed version. 5. Explain the answer with relevant API names and version constraints; distinguish documentation from inference. Do not mix examples from incompatible major versions or claim undocumented behavior as guaranteed.
Search and summarize material from the Acme research service.
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.
Electron and Den, desktop plus cloud, two-sandbox e2e, cloud auth, marketplace, org policy, worker proxy, provider sync, desktop handoff. Validate Electron against a Daytona Den server with unified proof.