eve0415

Use when inside a cella dev container and you need to manage branches, dispatch tasks, run parallel agents, or interact with other containers. Also use when you see CELLA_DAEMON_ADDR in the environment or /cella/bin/cella exists.

Use when running a systematic test sweep of the cella worktree/task system from inside a container. Also use after modifying the daemon, agent CLI, or task manager, before releases, or after bug fixes.

Run the full CI verification suite locally (format, lint, test, snapshots). Use before committing or to check if changes pass CI.

Research devcontainer spec, official CLI, and VS Code extension behavior before making design decisions. Use this skill whenever implementing devcontainer commands, options, lifecycle hooks, or features — or when behavior is ambiguous, when fixing spec compliance issues, or when the user asks how something works in the original devcontainer tools. Also use before answering questions about how cella should behave when you're not certain of the correct behavior. Trigger on any devcontainer property name, lifecycle hook, feature resolution, Docker Compose integration, port forwarding, or environment variable handling question.

React useEffect best practices from official docs. Use when writing/reviewing useEffect, useState for derived values, data fetching, or state synchronization. Teaches when NOT to use Effect and better alternatives.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

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.

Use when you want to run the full verification suite — lint, type check, and unit tests

Use when writing, reviewing, or debugging code that touches TanStack Router, Start, Query, Table, or Virtual in apps/web. Enforces TanStack Intent as the source of truth for Router/Start API patterns and documents Graflare-specific query and mutation conventions not covered by individual rule files.

Build the project and run all tests to verify changes compile and pass.