​

Documentation project instructions

​

About this project

• This is the TalkCut product documentation site built on Mintlify
• Pages are MDX files with YAML frontmatter
• Configuration lives in docs.json
• Run npx mintlify dev to preview locally
• Run npx mintlify broken-links to check links

​

Quick start

npm install          # Install Mintlify CLI
npx mintlify dev     # Preview at localhost:3000
npx mintlify broken-links  # Verify all links

​

Structure

.
├── docs.json              # Navigation, theme, and site config
├── introduction.mdx       # English pages (default language)
├── getting-started.mdx
├── core-concepts/         # Canvas, AI agent, vision engine, workspace memory
├── creating/              # Image/video generation, analysis
├── workspace/             # Projects, assets, skills, team, settings, pricing
├── zh/                    # Chinese translations (mirror English structure)
└── ja/                    # Japanese translations (mirror English structure)

​

Adding a new page

1. Create the English .mdx file with YAML frontmatter (title, description, icon)
2. Add the page path to the appropriate group in docs.json under the en language
3. Create the zh/ and ja/ translated versions
4. Add those paths to the zh and ja language sections in docs.json
5. Run npx mintlify broken-links to verify all cross-references

​

Terminology

​

Translation conventions

​

Style preferences

• Use active voice and second person (“you”)
• Keep sentences concise — one idea per sentence
• Use sentence case for headings
• Bold for UI elements: Click Settings
• Code formatting for file names, commands, paths, and code references
• No marketing language: avoid “powerful”, “seamless”, “robust”, “cutting-edge”
• No filler phrases: avoid “it’s important to note”, “in order to”
• No emojis in content
• Present credit costs as ranges per operation type, not per model
• Use user-friendly descriptions for AI capabilities, not internal model names

​

Content boundaries

• Document only: End-user features visible in the product UI
• Do not document: Internal architecture, API endpoints, database schemas, model IDs, code patterns
• Do not name: Specific AI model providers or model identifiers (e.g., don’t mention “kling”, “veo”, “gemini” — describe capabilities instead)
• Coming soon: NLE export (AAF/XML for DaVinci/Premiere/FCP) — mention only on pricing page with “coming soon” label
• No developer docs: This site is for end users/creators, not developers or API consumers

​

Mintlify components

• <Steps> / <Step title="..."> — Sequential workflows
• <Tabs> / <Tab title="..."> — Tabbed content (e.g., annual vs monthly pricing)
• <Tip> — Helpful advice
• <Note> — Important context
• <Warning> — Caution about credit costs or destructive actions
• <Accordion title="..."> — Collapsible FAQ items
• <Card title="..." icon="..." href="..."> — Navigation cards
• <Columns cols={N}> — Multi-column layout for cards

​

Syncing with the product

• Product codebase: ~/repo/github.com/talkcut/talkcut
• Sync docs by reading product codebase for user-facing features — never expose implementation details
• Check lib/ai/tools/ for current AI capabilities (tool names, parameters)
• Check lib/credits/constants.ts for current credit costs
• Check components/assets/ for asset management UI behavior