Use to set up a full customer-support agent for a web app — runs the whole build pipeline (knowledge base, read-only tools + access SQL, diagnostic runbooks, persona, config/secrets scaffolding) and reports everything needing review. Invoke when the user says "set up a support agent for ", "stand up the support kit"…
Use to integrate a built support kit into the operator's end-user app — generates the session bridge, chat serving layer, end-user entry point, escalation wiring, deploy glue, and an operator-run smoke checklist, following the operator's own hosting practice. Invoke when the user says "integrate the support agent"…
Use when authoring the diagnostic runbooks a customer-support agent follows at runtime — turning a product's failure surface, its harness, and its read-only tool catalog into symptom-to-resolution decision trees plus synthetic evaluation tickets, for mandatory human review. Triggers: "author the support runbooks"…
Use when generating the read-only data-access tools a customer-support agent uses to diagnose an end user's live state — reading a project's backend to propose a tool catalog plus the database access SQL (restricted read-only role, column grants, row-level security), for mandatory human review. Triggers: "discover…
Use when turning a codebase into a sanitized plain-language help-center knowledge base ("harness") for an AI support assistant — reading one or more project roots and producing navigable Markdown that describes user-facing behavior with no technical detail and no security mechanisms or secrets. Triggers: "build a…
Use when generating a project-specific customer-support assistant persona from the reference template — turning a harnessed product's knowledge base and tool catalog into a finished persona.md for the runtime support agent. Triggers: "generate the support persona", "make the assistant persona for ", part of setting up…
Use to integrate a built support kit into the operator's real end-user app — discovers the app's own serving, session, frontend, and deployment practice and generates, for that practice, the session bridge (verified user id → per-connection identity), the chat serving layer, the end-user entry point, real escalation…
Use to set up a full customer-support agent for a web app — orchestrates the whole build pipeline (knowledge base, read-only tools + access SQL, diagnostic runbooks, persona, config/secrets scaffolding) by running the four stage skills in order, with a human-review gate after each, and hands off the local database…
Use when authoring the diagnostic runbooks a customer-support agent follows at runtime — turning a product's failure surface, its harness, and its read-only tool catalog into symptom-to-resolution decision trees plus synthetic evaluation tickets, for mandatory human review. Triggers: "author the support runbooks"…
Use when generating the read-only data-access tools a customer-support agent uses to diagnose an end user's live state — reading a project's backend to propose a tool catalog plus the database access SQL (restricted read-only role, column grants, row-level security), for mandatory human review. Triggers: "discover…
Use when generating a project-specific customer-support assistant persona from the reference template — turning a harnessed product's knowledge base and tool catalog into a finished persona.md for the runtime support agent. Triggers: "generate the support persona", "make the assistant persona for ", part of setting up…
Use to integrate a built support kit into the operator's real end-user app — discovers the app's own serving, session, frontend, and deployment practice and generates, for that practice, the session bridge (verified user id → per-connection identity), the chat serving layer, the end-user entry point, real escalation…
Use to set up a full customer-support agent for a web app — orchestrates the whole build pipeline (knowledge base, read-only tools + access SQL, diagnostic runbooks, persona, config/secrets scaffolding) by running the four stage skills in order, with a human-review gate after each, and hands off the local database…
Use to set up a full customer-support agent for a web app — runs the whole build pipeline (knowledge base, read-only tools + access SQL, diagnostic runbooks, persona, config/secrets scaffolding) and reports everything needing review. Invoke when the user says "set up a support agent for ", "stand up the support kit"…
Use to integrate a built support kit into the operator's end-user app — generates the session bridge, chat serving layer, end-user entry point, escalation wiring, deploy glue, and an operator-run smoke checklist, following the operator's own hosting practice. Invoke when the user says "integrate the support agent"…
Instructions for krishnanpandya007/support-technician-setup: This repository is a methodology bundle for building a read-only customer-support agent from a codebase. When asked to build or set up a support agent, follow the prompt files in .github/prompts/ (invoke with /) — for a full build, in this order.
Instructions for krishnanpandya007/support-technician-setup, covering support technician — agent instructions, build stages (skills), specialized agents, skill: authoring-support-runbooks and authoring support runbooks.
Instructions for krishnanpandya007/support-technician-setup, a project described as: An automated Support tehnician setup bundle for your web app, which won't only butter like ordinary chatbot, but diagnoses real data and metrics while keeping security measures bounded.