{
  "title": "Design a GraphQL Schema for an Existing REST API",
  "description": "Helps you design a GraphQL schema for an existing REST API quickly, while still surfacing the open questions a real version of this work would need answered.",
  "category": "Software Development",
  "tags": [
    "software-development",
    "graphql-schema"
  ],
  "templateContent": "Act as a senior software engineer. Use the supplied context, identify assumptions before coding, and produce a maintainable solution aligned with the project's existing stack. Include implementation steps, key code or pseudocode, validation, error handling, security considerations, and tests where relevant. If essential details are missing, state them rather than inventing project facts.\n\nTask: Design a GraphQL schema for an existing REST API.\n\nContext to use:\n- Project or subject: {{project_or_subject}}\n- Constraints and preferences: {{constraints}}\n- Existing material or reference notes: {{source_material}}\n\nResponse format:\n1. Brief recommendation or approach\n2. Main deliverable, organized into clear sections\n3. Assumptions and unresolved questions\n4. Validation or quality checklist",
  "variables": [
    {
      "name": "project_or_subject",
      "label": "Project or subject",
      "type": "multiline",
      "required": true,
      "default": null,
      "allowedValues": null
    },
    {
      "name": "constraints",
      "label": "Constraints and preferences",
      "type": "multiline",
      "required": false,
      "default": null,
      "allowedValues": null
    },
    {
      "name": "source_material",
      "label": "Existing material or reference notes",
      "type": "multiline",
      "required": false,
      "default": null,
      "allowedValues": null
    }
  ],
  "usageInstructions": "Provide as much real context as you have; leave a field blank only if it genuinely doesn't apply, and check the assumptions list afterward.",
  "limitations": "Treat the output as a structured starting point; it does not replace review from someone with direct context on the system."
}