framework_docs
The framework_docs tool returns the Manh framework docs to the agent by topic, from the spec process to file conventions, UI, backend and deploy, readable one section at a time.
These docs are short and written for agents. The page you are reading is the version for people.
framework_docs
- Parameters:
topic(required): one of the topics below.section: large topics return a numbered table of contents first. Pass section numbers ("2,5") or words from a title ("ProTable") to read only those parts;"all"reads the whole topic (topics over 60 KB still return the table of contents).
- Returns: Markdown.
- When the agent calls it:
processandframeworkat the start of a session,proonce before the first page; the others when needed.
| Topic | Contents |
|---|---|
process | Spec before code: PRD, roles, objects, permissions, data model, lifecycles, API, screens, build order |
framework | The app/ contract (authoritative): .tsx / .ts split, routing, handlers, middleware, cron, database |
frontend | Pages, layouts, useApiClient, antd-pro patterns |
backend | Hono handlers, Zod schema, Drizzle, files, email, AI, upstream, secrets |
pro | antd-pro like a senior: 12 short rules with before / after (ResourceList, tableRequest, submit, status tabs, errors shown by the frame), read before the UI phase |
pro-full | The full ProComponents playbook: app shell, lists, dashboards, forms, detail pages, sign-in |
website | A public website that reads as a real business |
directions | Design directions for a website (fonts that render Vietnamese, colours, spacing, photos); pick one before any public page |
photos | Checked stock photos by trade, each with what it shows |
content | Real content: brand brief, names, phone numbers, prices, photos |
telegram | The app’s own Telegram bot |
supabase | Data on the owner’s Supabase |
types | App types (stock and POS, CRM, approvals, training centre, repair, booking, QR ordering, AI documents): what real products do, with 5 acceptance tests each |
handover | Handing the app to your client without the platform’s name |
antd | antd v6 and pro-components rules, crash-fatal mistakes |
patterns | Catalog of antd-pro page patterns |
components | What antd, pro-components, x and charts can do |
codegen | Code rules that keep apps deployable |
examples | Page examples, one app/page.tsx each |
deploy | Deploy: check, UI and API go live together, schema, secrets, npm packages, limits, cron, logs, rollback |
Each topic is also an MCP resource, manh://docs/<topic>, for clients that read resources.
Next steps
- Agent tools: the order of calls in a session.
- app/ and the two runtimes: the people’s version of the
frameworktopic.
Last updated