menuyukti-web
Next.js web app (apps/web): GraphQL data fetching, Clerk auth, next-intl, workflow/milestone UI including milestone data preview and milestone run settings, API routes and Zod schemas. Use when changi
SKILL.md.agents/skills/menuyukti-web/SKILL.md
GitHubMenuyukti: apps/web
Next.js user-facing app: chat, campaigns, CRUD. All product data goes through GraphQL (no direct DB). Auth: Clerk. Copy: next-intl (no hardcoded user-facing strings).
For monorepo boundaries, see menuyukti-repo-orientation. For UI and i18n rules, see .cursor/rules/web-conventions.mdc.
Companion skills
When implementing in apps/web, follow these skills in addition to this doc.
Feature work (default)
vercel-react-best-practices— React and Next.js performance patterns.next-best-practices— Next.js file conventions, RSC boundaries, data fetching.shadcn— UI components and styling with the project’s shadcn setup.
For Clerk (auth, middleware, Server Actions), use clerk-nextjs-patterns.
Refactors, performance, and composition
When improving an existing implementation (not only greenfield features), also read:
nextjs-performance— Use when tuning Core Web Vitals, bundle size, LCP/INP, images/fonts, or RSC data performance.next-cache-components— Use when adopting Cache Components, PPR,use cache,cacheLife,cacheTag, orupdateTag.vercel-composition-patterns— Use when refactoring boolean-prop sprawl, compound components, render props, or flexible public APIs.
Layout (high level)
| Concern | Typical locations |
|---|---|
| App Router | apps/web/app/ |
| Protected shell | apps/web/app/(protected)/ — /workflow, /analytics, /canvas, /content, /advisor, … |
| GraphQL client | apps/web/lib/graphql/client.ts, queries/, node-schemas/ |
| Workflow UI | apps/web/app/(protected)/workflow/ |
| Milestone presets (web) | apps/web/lib/milestones/preset-definitions.ts, node-schemas/milestone-presets.ts |
| API routes (BFF) | apps/web/app/api/ — e.g. /api/workflows/.../milestones/.../run |
Named product features and aliases (e.g. workflow import presets): see .agents/menuyukti-features.md.
Commands: AGENTS.md § Web.
Milestone data and run
Milestone run uses LangGraph preset subgraphs keyed by milestone.data.presetId (menuyukti-agents). Milestone data (structured JSON) lives on milestonedata child nodes; the run BFF calls POST .../run with location_id and workflow_id only.
Chat (workflow sidebar and /advisor) uses a separate ReAct graph with milestone read/write tools — see apps/agents/agents/core/chat/tools.py (get_milestone, overview, input patches).
Checklist: new milestone preset (agents + web)
- Agents preset — add
apps/agents/agents/core/milestone_run/<preset_id>/andregister_preset_runner(menuyukti-agents). - GraphQL / Zod — extend
MILESTONE_PRESET_IDSand milestone data schemas innode-schemas/milestone-presets.ts. - Web preset catalog — update
preset-definitions.ts(create fields, icons, empty data) and timeline UI (preset select, input tabs, preview components). - Eval — criterion helpers in
milestone_eval/<preset>_eval.pywhen needed. - GraphQL export/import — keep milestone
dataJSON compatible when workflows round-trip (menuyukti-graphql).
GraphQL from the web
- Use
graphqlQueryfromlib/graphql/client.tsin Server Components andapp/api/handlers. - Validate node
dataJSON with Zod viaparseNodeData/ schemas underlib/graphql/node-schemas/— avoid casting. - Keep server/client boundaries aligned with Next.js conventions (
next-best-practices).
Related
| Topic | Skill |
|---|---|
| Milestone run | menuyukti-agents |
| Backend schema | menuyukti-graphql |
| Monorepo map | menuyukti-repo-orientation |
Canonical docs
Progressive disclosure
Split long route or component maps into reference.md in this folder if this file grows.