context7-version-aware-implementation
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/context7-version-aware-implementation && cp -r /tmp/context7-version-aware-implementation/examples/plugin-packages/context7/skills/context7-version-aware-implementation ~/.claude/skills/context7-version-aware-implementationSKILL.md
# Context7 Version-Aware Implementation 1. Inspect the project manifest and lockfile to establish the exact dependency version. 2. Retrieve documentation and migration guidance for that release line. 3. Compare the current code with the documented API before editing. 4. Implement the smallest compatible change and preserve established project patterns. 5. Run the owning package checks and report any behavior that still requires runtime verification. If the requested API is unavailable in the installed version, explain the supported alternative or propose an explicit dependency upgrade instead of silently mixing versions.
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.
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
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.