Agentic Development
How agents should work inside this core repo.
AGENTS.md is the shared source of truth for coding agents.
Claude, Gemini, Cursor, and Copilot instructions should point back to AGENTS.md.
Run pnpm varel impact "<task>" --json to get affected-provider hints before open-ended provider, env, domain, auth, billing, email, analytics, deploy, or agent-guidance work.
Run pnpm varel setup plan --json before provider setup work.
If docs/product-prd.md exists, read it before product or implementation work, update it when scope or implementation assumptions change, and confirm before doing work that conflicts with the PRD.
Use .agents/product-marketing.md, the Varel reference files, and docs/launch-quality.md for brand, landing copy, UI/UX, shadcn dashboard quality, SEO, AEO, schema, and content strategy.
When Hyperdrive is installed and the task touches a landing page, homepage, pricing page, conversion copy, brand, or visual direction, call varel_hyperdrive_landing_page_plan before implementation and treat its skill availability gate as blocking.
Before landing-page strategy, design, copy, or implementation continues, the active Codex, Claude Code, Cursor, or equivalent skills-capable coding agent must expose frontend-design, web-design-guidelines, vercel-react-best-practices, and vercel-composition-patterns; if the client is in Plan Mode or cannot install/verify skills, stop and ask the user to switch to an execution-capable mode or install the skills manually.
Before marketing or app UI work, fill .agents/product-marketing.md and define product-specific palette values, semantic color roles, typography, logo direction, imagery/icon style, landing copy direction, visual archetype, CTA, objections, social proof, conversion goal, brand token notes, and screenshot QA notes.
Keep agents aware of local sandbox, Vercel preview, and Vercel production env readiness.
Run pnpm varel doctor --json and pnpm agent:preflight before broad handoff.
Use Varel Hyperdrive MCP tools for task impact, landing-page plans, thread orchestration, access bootstrap, setup plans, next steps, provider handoffs, domain shortlist, domain plans, browser automation, Chrome integration, Computer Use checkpoints, and setup validation.
Core owns local checks, env ownership, integration starting points, and generic provider reminders; Hyperdrive owns broad-work orchestration guidance, access bootstrap, deeper provider sequencing, and external-system orchestration when installed.
Provider setup should include product-specific providers such as OpenAI, transcription, CRM, search, maps, or AI APIs when they are in scope, and every provider resource should be dedicated to this product.
For Sanity provider work, use Sanity MCP, Sanity CLI, and official global Sanity skills; do not vendor official Sanity skills into this repo.
Keep docs, env, billing, data boundaries, and tests aligned when product behavior changes.