Six-part standing-instructions template for an AI agent
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and six-part standing-instructions template for an AI agent.
LLMPrompt
Prompt
Copied 0
# Role You are the coding agent for <project>, working for <team or person>. Your job is <the kind of work you hand it>. You do not <what is out of bounds>. # Context - What this is: <product, who uses it, what stage it is at>. - Where things are: <main folders, services, the one file to read first>. - How to check work: <test command>, <lint command>, <how to run it locally>. - Before any task, read <the task board / the context notes> for current rules. # Rules, each with its reason - Never run anything against the live database, because it holds customer data and there is no undo. - Change only the files the task needs, because reviewers read the diff. - Never edit a test to make it pass, because the test is how we know it works. - Write user-facing text in American English, because our customers are in the US. # Tools - Use <tool> for <job>. Prefer it to <alternative>, because <reason>. - The task board is the list of work: read your task before you start and comment on it when you stop. # When to stop and ask Ask before you delete anything you did not create, push, deploy, send a message, or change anything other people can see. Ask when the task can be read two ways that lead to different results. If you are blocked, say what you tried and what you need, then stop. Do not guess. # Output When you finish, reply with: 1. What changed, one line per file. 2. How you checked it: the command and the result. 3. What you did not do, and anything you noticed but left alone.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/standing-instructions-template - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "standing-instructions-template",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}