get_conventions

read-only

Start here. Returns token, theme, alias, and naming conventions plus selection and customization guidance. Define a brand direction, compare candidates, install pristine source, then adapt it. Without both brief answers, returns status: "needs_brief" and discovery questions instead of this result. Answer from existing context, ask the user only for material gaps, and retry with the same brief on every call.

Arguments

NameTypeNotes
brief{ intent?: string; visualDirection?: string }Both answers are needed for catalogue data: what you are building, for whom, and the desired action; then the brand's tone, references, assets, and styles to avoid. Missing/blank answers return questions. Reuse across this task.

Direct HTTP request

These examples use the original JSON API. Connected MCP clients call this tool through tools/call; results arrive as JSON text in content. Invalid arguments return a tool error in MCP or HTTP 400 in this API.

Request
curl -X POST https://jabkit.joseadrianbuctuanon.dev/mcp \
  -H "Content-Type: application/json" \
  -d '{
      "tool": "get_conventions",
      "arguments": {
        "brief": {
          "intent": "Photography portfolio for art directors; show projects and invite enquiries.",
          "visualDirection": "Restrained editorial layout with supplied photography; avoid dashboard chrome."
        }
      }
    }'

Response 200

{
  "tailwind": "Tailwind CSS v4 with semantic --jk-* tokens",
  "theme": "Class-based .dark mode. …",
  "alias": "@/components/jabkit",
  "naming": "kebab-case folders with PascalCase-prefixed files",
  "selection": [ "Establish the brand's audience, …", … ],
  "customization": [ "Show get_install_plan, …", … ]
}

Errors

None specific to this tool. An unknown tool name returns 400.