deploy_template
ChatGPTPublish a saved template as the user's live portfolio at [subdomain].showcaseme.in. This replaces the portfolio that is currently live, so use it only after the template is saved and the user has confirmed both deploying and the subdomain. The subdomain is 3-63 lowercase letters, numbers or hyphens, with no leading or trailing hyphen, and must not be taken.
get_design_system
ChatGPTDesign rules for a Showcaseme portfolio website (personal website, resume or CV site, profile page) written from scratch, for any profession. Call it before writing a template with save_portfolio_template. Returns the next steps and the component-engine contract: authoring rules, data bindings and fields, the 12 sections and their allowed variants, a catalogue of every component, prop and allowed value, and an excerpt of a seeded template. detail "full" adds the raw JSON authoring schema and the whole example.
get_template
ChatGPTRead one of the user's saved templates as JSON (the same shape save_portfolio_template takes), with its updatedAt. Use it before a rewrite with update_portfolio_template, or to find node ids and paths for patch_portfolio_template when the template comes from an earlier chat. Find the templateIdentifier with list_templates. For a preview, use preview_template after the user confirms.
list_signature_templates
ChatGPTThe 15 Showcaseme signature designs to start from: identifier, name, a one-line style (palette, hero, projects and gallery layouts), light or dark, font pair. They suit any profession. Use it when the user's request is close to one of them, then call start_from_template with a brief; every part stays customisable.
list_templates
ChatGPTList the user's saved templates (identifier, name, profession, format, created). Use this when the user asks to see their existing templates, wants to change one from an earlier chat, or wants to choose a saved design to start from or deploy. The 15 Showcaseme signature designs are in list_signature_templates.
patch_portfolio_template
ChatGPTChange part of a saved template without resending it: the server applies the operations in order, validates the result and saves it (same templateIdentifier). All or nothing: if any operation or the result is invalid, nothing is saved and every error names its operation. If the template is deployed the live portfolio changes at once: confirm with the user first. Operations: - { "op": "setStyles", "value": { "tokens": { "primary": "#16a34a" }, "typography": { "heading": "syne" } } } merges into styles (null removes a key) - { "op": "setVariants", "value": { "projects": "deck" } } - { "op": "setSections", "order": ["gallery", "projects"], "hide": ["caseStudies"], "show": ["testimonials"] } - { "op": "setMeta", "templateName": "...", "description": "...", "tags": "a, b" } - { "op": "updateNode", "nodeId": "hero", "props": { "background": { "type": "gradient", "value": "..." } } } merges into that node's props (null removes a prop) - { "op": "replaceNode", "nodeId": "projects/1", "node": { "component": { "type": "list", "props": {...} }, "render": [...] } } - { "op": "insertNode", "parentId": "about", "index": 0, "node": {...} } (no index appends) - { "op": "removeNode", "nodeId": "contact/2" } - { "op": "moveNode", "nodeId": "skills", "parentId": "hero", "index": 1 } - { "op": "setSampleData", "value": { "headline": "...", "projects": [...] } } merges into the preview content nodeId and parentId: a props.id (the summary lists them per section, e.g. "hero", "projects", "skills"), "root", or an id followed by child indexes: "projects/1/0" is the first child of the second child of the projects section (read the structure with get_template when the template is from an earlier chat). Paths follow earlier operations in the same patch, so prefer ids. Root sections are reordered and hidden with setSections, never removed. Returns the summary, designSuggestions and the new updatedAt (pass it as baseUpdatedAt next time).
preview_template
ChatGPTShow a saved template as a live, scrollable preview inside the chat, plus a full-screen link (valid 24 hours, no sign-in needed). Call it ONLY after the user confirmed: first describe the design (style, palette, fonts, sections and their layouts, from the summary the save returned) and ask whether they want to see the preview. Call it again after later changes when the user wants to see them.
save_portfolio_template
ChatGPTSave a NEW portfolio website written from scratch on Showcaseme (call get_design_system first; to start from a signature design or one of the user's templates, start_from_template is faster). Never use this to change one that is already saved: if the user asks to change, fix, tweak or restyle a template (from this chat or an earlier one), use patch_portfolio_template (or get_template and update_portfolio_template for a rewrite). A save whose templateName matches one of the user's templates is refused and names the existing templateIdentifier. Saves a template written in the Showcaseme component-engine format (the same format as the site's hand-built templates). Steps: 1) Call get_design_system FIRST. It returns the rules, the portfolio data fields you can bind to, the per-section variants, a catalogue of every component and prop, and an excerpt of a seeded template. 2) Write the whole template: styles, variants and a layout container with exactly 12 sections (header first, footer last). Include every section; ones without data hide themselves. Also write sampleData: realistic preview content for a fictional "John Doe" in this person's profession (Showcaseme as every company, college and issuer), with layout { focus, omit } saying which sections lead and which this profession does not use, and socialLinks naming 2-4 platforms this profession uses (names only). Fill every collection you do not omit. 3) Save. The save validates everything: if anything is wrong nothing is saved and you get every error with its path; fix them all and save again. No separate validation call is needed. 4) It returns templateIdentifier (ai-...), a summary of the design and designSuggestions. Describe the design to the user and ask whether to show the preview; call preview_template only after they say yes. If the user pastes their own template JSON, save it AS GIVEN: only add what is missing (portfolioType, sampleData). Do not redesign it. If it fails validation, show the user the errors and ask before changing anything. Within one chat, after the first save, every further change goes to that templateIdentifier unless the user asks for a separate template.
start_from_template
ChatGPTCreate a NEW portfolio template quickly from a signature design (list_signature_templates) or one of the user's own templates (list_templates), customised with a brief, instead of writing every node. The base is never changed: the result is a new draft owned by the user. Use it when the request is close to a base; write from scratch (get_design_system, save_portfolio_template) when the user wants something different. Either way everything stays customisable afterwards with patch_portfolio_template. brief (all optional): - styles: merged into the base styles, e.g. { "mode": "light", "tokens": { "primary": "#0f766e", "background": "#fbfaf7", "text": "#1c1917" }, "typography": { "heading": "fraunces", "body": "inter" }, "motion": { "intensity": "expressive" } }. null removes a key. - variants: a layout per section, e.g. { "projects": "coverflow", "gallery": "mosaic" } (values from the variants table). - sections: { "order": ["gallery", "projects"], "hide": ["caseStudies"], "show": [...] } with root section ids. - sampleData: John Doe preview content for the profession, same shape as save_portfolio_template's sampleData. Recommended for a signature base: without it the preview uses the general sample. Returns templateIdentifier, summary (palette, fonts, sections and layouts, node ids) and designSuggestions, no JSON and no link. Then describe the design to the user and ask whether to show the preview; call preview_template only after they say yes.
update_portfolio_template
ChatGPTRewrite a saved template in place (same templateIdentifier). For targeted changes (colours, fonts, a layout, a few nodes, the sample content) patch_portfolio_template is much faster; use this for a redesign. Call get_template first, apply the change, keep everything else as it was, and send the WHOLE template back with baseUpdatedAt set to the updatedAt get_template returned (so a newer save is never overwritten). Validated exactly like save_portfolio_template; returns the summary and the new updatedAt. If the template is deployed, the live portfolio changes at once: confirm with the user before, and tell them after.
validate_template_quality
ChatGPTOptional: check a template without saving it, with the same input as save_portfolio_template. Not needed before a save (save_portfolio_template runs the same checks and saves nothing when something is wrong). Returns every contract error with its path (sections, variants, components, props, ids, nav links) and designSuggestions, with looksDefault=true when the design sits on the safest choices.