Turn the user's information into a business model canvas that clearly shows "for whom what value is created, how it is delivered, and how revenue and costs work." The main deliverable is a Chinese landscape PNG; HTML and structured JSON are also retained for easy modification, traceability, and redrawing.
Workflow Routing
| Input | Processing and Delivery |
|---|---|
| Project introduction, interviews, documents, scattered descriptions | Organize according to the contract below, run Tools/Render.ts, and deliver the canvas after verification |
| Existing canvas and supplementary materials | Update the specified model with new materials; retain unaffected information and regenerate |
| Multiple independent businesses/business models | One canvas per model; keep the multi-sided customers of the same platform in the same diagram and associate them with C1, C2 |
Content Contract
- Confirm the object and scope before starting. When only a company name is given and there is no business material at all, ask for a business description or supplement research with the user's authorization; if the information is enough to draw a draft, draw it directly, and write "to be supplemented" for missing items. When multiple possible objects would change the canvas, first ask one focused question.
- Read CanvasGuide.md to calibrate the definitions, relationships, and classic layout of the nine modules. Use the user's materials as the main body, and do not automatically fill in facts from industry common sense.
- Mark each point as
given(provided by materials),inferred(inferred), orunknown(to be supplemented). "Provided by materials" does not equal external verification.givenAssociate source numbers,inferredattach the basis; plans explicitly stated by the user should still be written as "proposed/planned" and must not be changed into something currently happening. - Prefer 2–4 specific points per cell. Preserve distinguishing information such as who the customer is, what is bought, who pays, and the pricing unit. Write as "object + action/result" as much as possible; for revenue, keep price and period, and for costs, keep driving factors. When there is no material support, do not invent amounts, scale, partners, or conclusions.
- Place the nine cells in the same frame. Maintain the classic spatial relationships, with costs and revenue at the bottom; do not draw an equal-width 3×3 nine-grid, and do not arbitrarily switch to Lean Canvas. Color serves zoning and customer correspondence, and inferences must also use text labels, not be distinguished by color alone.
Generation and Acceptance
Prepare the input JSON in a unique temporary directory; for the structure see Tools/Render.help.md, for a complete fictional example see Example.json, and for layout reference see Example.png. Record the real directory of this skill as SKILL_DIR, and run from any working directory:
bun "$SKILL_DIR/Tools/Render.ts" --input "$WORK_DIR/model.json" --output "$WORK_DIR/model.html"
| User Intent | Parameter or Behavior |
|---|---|
| Default card drawing | Default width 1600 CSS px; final export PNG |
| Specified width | --width 1200 to --width 2400; readability still needs to be checked |
| Save to the specified location | After acceptance, put the final PNG, HTML, and JSON in that directory |
Open the HTML with a real browser on this machine, wait for fonts to be ready, and check the order of the nine cells, all text, and overflow. When the current environment has Interceptor, follow its isolation and screenshot contract; in other environments, use available real browser tools.window.businessModelAudit() Provide block count, missing items, inferences, and geometric overflow checks. Export the entire #canvas as PNG; 2x pixel density is recommended. If screenshot capability is unavailable, keep the HTML and clearly state that the PNG is incomplete; an HTML link must not be passed off as an image.
Open the final PNG to view the whole image, then zoom in on dense areas to check. If the text is too dense, first trim repetitive wording or increase the canvas height; keep key conditions, and do not crop, hide overflowing content, or shrink text to force it in. If the renderer rejects entries that are too long or too numerous, clean up the input and rerun; do not bypass validation.
Finally, display the PNG directly in the conversation and provide file links for the HTML and JSON; briefly point out missing information that affects understanding. Keep all drafts and screenshots in a temporary directory; only accepted deliverables go into the delivery directory.
Gotchas
- Customer segments are whom you serve; the payer may differ from the user. Multisided platforms need to preserve the corresponding relationships across value, channels, and revenue.
- Channels describe customer acquisition, conversion, and delivery paths; customer relationships describe how interactions are established and maintained. Resources are things owned or callable, activities are things done repeatedly, and partners are external participants.
- Revenue streams are how you charge; financing is not revenue. Cost structure is the logic of expenditure; you cannot use it to infer profit or add together data whose period is not specified.
- Clear categorization does not mean the business model is viable. Contradictory materials, unvalidated demand, and missing payment logic should be documented; they must not be erased with a smooth summary.
- Keep the footer attribution to Business Model Canvas, Strategyzer.com, and CC BY-SA 3.0; this is a Chinese adapted layout, not the official original or a restatement of the full original book. The license applies to the canvas template; rights to the user's business materials are not changed by it.
Examples
- "ljg-business-model: We provide procurement services for small restaurants and charge based on transaction volume..." -> Use the available materials to draw one canvas; write to be supplemented for missing partners and costs.
- "Turn this two-sided platform interview into a Business Model Canvas" -> Mark users and payers separately, and trace their respective value and revenue paths.
- "This is yesterday's canvas; now change it to an annual subscription" -> Update the charging method, and check based on supplementary materials whether customer relationships and costs have also changed; mark changes without evidence as inferences.