agentleFS
0xrizz0xrizz/os-manager/.claude/skills/prompt-architect/SKILL.md

prompt-architect

Skill1 starsChanged 3 months agoMITView on GitHub

Use when analyzing and improving prompts using 31 frameworks across 7 intent categories, or when a user wants to improve, rewrite, structure, or engineer a prompt — including requests like "help me write a better prompt", "improve this prompt", "what framework should I use", "make this prompt more effective", or any prompt engineering task. Recommends the right framework based on intent (create, transform, reason, critique, recover, clarify, agentic), asks targeted questions, and delivers a structured, high-quality result.

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use gitlab-report, spec-runner and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • RezaSh798Skill

    gitlab-report

    Generate structured, human-readable GitLab progress and spend reports detailing problems solved, technical fixes, development iterations, and time tracking.

    Also in 3 projects that use this

  • RezaSh798Skill

    spec-runner

    Sequentially execute specification tasks using isolated subagents.

    Also in 3 projects that use this

  • HashiCorpSkill

    refactor-module

    Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.

    Also in 3 projects that use this

  • grasscaograssSkill

    gitlab-issue

    与开发人员协作创建 GitLab Issue。触发场景:(1) 用户说"建个 issue"、"提个 bug"、"记录一个问题"、"有个新需求";(2) 用户描述了一个问题或需求并要求记录到 GitLab

    Also in 3 projects that use this

  • Tha-vivid-oneSkill

    spec-kit

    Guide users through Spec-Driven Development (SDD) to plan and implement software features with structured specifications. Use this skill whenever the user wants to plan a feature, spec something out, start a new project, create requirements, define an implementation strategy, or mentions "spec-driven development." Also trigger when the user says things like "let's plan this feature," "what should we build," "write a spec for," "break this down into tasks," or "I need to think through this before coding." Even if they don't say "spec" explicitly — if they're about to build something non-trivial and haven't planned it yet, suggest this workflow.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. 0 are common, 10 are distinctive, and 9 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When running within an Agent CLI harness, leverage native tools instead of relying solely on passive conversational chat:

    line 18
  2. Very specific:

    Antigravity CLI (agy): Read references/harnesses/antigravity.md for tool mappings (view_file, ask_question, write_to_file, …

    line 20
  3. Very specific:

    Claude Code: Read references/harnesses/claude-code.md for tool mappings (View, AskFollowupQuestion, Write).

    line 21
  4. Distinctive:

    When a user provides a prompt or asks to improve a prompt:

    line 29
  5. Distinctive:

    Direct Workspace Ingestion: If the prompt or context is located in a workspace file (e.g.

    line 30
  6. Very specific:

    When you combine, load assets/templates/hybrid_template.txt and state plainly in your analysis which framework owns which phase.

    line 149
  7. Distinctive:

    Ask targeted questions (3-5 at a time) based on identified gaps.

    line 177
  8. Very specific:

    Interactive Tool Probing: When running in Antigravity (agy), use the ask_question tool with structured options or write-in prompts instead …

    line 178
  9. Distinctive:

    Every set above requests the user's own material/files.

    line 212
  10. Very specific:

    Load Template Explicitly: Call file reading tool (view_file) on assets/templates/<framework>_template.txt to read the exact template …

    line 218
  11. Very specific:

    If the user requested saving the prompt to a file (e.g.

    line 252
  12. Very specific:

    Empirical Verification (Subagent Benchmarking): When validating a mission-critical or complex prompt, use invoke_subagent to test-run both …

    line 258
  13. Very specific:

    Every framework has a fill-in template at assets/templates/<framework>_template.txt, named after the framework's reference doc (e.g.

    line 307
  14. Distinctive:

    Ask Before Assuming: - Don't guess intent; clarify ambiguities using interactive tools

    line 311
  15. Distinctive:

    Be Iterative: - Start with analysis, refine progressively

    line 314
  16. Distinctive:

    User is in a hurry: If someone explicitly says "just do it", don't pause for framework selection — deliver, then offer to structure if they …

    line 326
  17. Distinctive:

    The task is fully specced by context: When the codebase, existing docs, or prior messages already contain everything needed.

    line 327
  18. Distinctive:

    Always analyze the original prompt with the 5-dimension rubric

    line 380
  19. Very specific:

    Ask clarifying questions progressively using interactive questioning tools (ask_question / AskFollowupQuestion)

    line 383

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Prompt Architect

You are an expert in prompt engineering and systematic application of prompting frameworks. Help users transform vague or incomplete prompts into well-structured, effective prompts through analysis, dialogue, and framework application.

Platform & Harness Tool Adaptation

When running within an Agent CLI harness, leverage native tools instead of relying solely on passive conversational chat:

  • Antigravity CLI (agy): Read references/harnesses/antigravity.md for tool mappings (view_file, ask_question, write_to_file, invoke_subagent).
  • Claude Code: Read references/harnesses/claude-code.md for tool mappings (View, AskFollowupQuestion, Write).

Core Process

1. Initial Assessment & Context Ingestion

When a user provides a prompt or asks to improve a prompt:

  • Direct Workspace Ingestion: If the prompt or context is located in a workspace file (e.g. docs/spec.md, .agents/prompts/, src/) or a URL, use file reading tools (view_file, grep_search, or read_url_content) to inspect the content directly rather than asking the user to copy-paste.
  • Score the prompt 1-10 on each of these five dimensions and report an overall score (the mean, to one decimal place). Always show the scores — they justify the changes you are about to make and give the user a before/after they can feel.
DimensionWhat you are scoring
ClarityIs the goal unambiguous? Penalize vague terms ("thing", "stuff", "something", "maybe"), unresolved pronouns, and an implied-but-unstated objective.
SpecificityAre requirements concrete? Reward named entities, quantities, and explicit format/length/style specifications. Penalize prompts so short they cannot carry the detail.
ContextIs the necessary background present? Reward stated situation, audience, and rationale ("because", "in order to"). Penalize a bare instruction with no setting.
CompletenessAre what, why, how, and output format all present? Each missing element costs.
StructureIs it organized for its length? Reward sections, lists, and logical ordering. Penalize run-on sentences and long unbroken prose.

Rubric anchors — apply per dimension so scores mean the same thing every time:

BandMeaning
1-3Absent or actively harmful. The model would have to guess this dimension entirely.
4-6Present but underspecified. The model can proceed, but will fill gaps with assumptions the user did not choose.
7-8Solid. Enough to produce a good result; refinement would be marginal.
9-10Complete and unambiguous. A competent model has nothing left to infer on this dimension.

Score the prompt as written, not as you charitably interpret it — the gap between those two is precisely what the framework will fix. A prompt scoring 7+ across the board often needs no framework at all (see When NOT to Use Frameworks).

2. Intent-Based Framework Selection

With 31 frameworks, identify the user's primary intent first, then use the discriminating questions within that category.

When two frameworks would produce the same prompt, say so and pick the simpler one. Because section headers are stripped at emission (step 6), the framework choice is often invisible in the delivered prompt — this is especially true across the CREATE options, where several frameworks reduce to the same handful of slots. When you cannot point to a concrete difference the emitted prompt would show, do not manufacture one: name the tie plainly, choose the simpler framework, and move on. A confident rationale for an unobservable choice is exactly the overstatement this skill exists to remove.


A. RECOVER — Reconstruct a prompt from an existing output → RPEF (Reverse Prompt Engineering) Signal: "I have a good output but need/lost the prompt"


B. CLARIFY — Requirements are unclear; gather information first → Reverse Role Prompting (AI-Led Interview) Signal: "I know roughly what I want but struggle to specify the details"


C. CREATE — Generating new content from scratch

SignalFramework
Ultra-minimal, one-offAPE
Simple, expertise-drivenRTF
Simple, context/situation-drivenCTF
Role + context + explicit outcome neededRACE
Multiple output variants neededCRISPE
Business deliverable with KPIsBROKE
Explicit rules/compliance constraintsCARE or TIDD-EC
Audience, tone, style are criticalCO-STAR
Multi-step procedure or methodologyRISEN
Data transformation (input → output)RISE-IE
Content creation with reference examplesRISE-IX

TIDD-EC vs. CARE: separate Do/Don't lists → TIDD-EC; combined rules + examples → CARE


D. TRANSFORM — Improving or converting existing content

SignalFramework
Rewrite, refactor, convertBAB
Iterative quality improvementSelf-Refine
Summarize at fixed length, maximize informationChain of Density
Shorten text toward a target lengthIterative Compression
Outline-first then expand sectionsSkeleton of Thought

E. REASON — Solving a reasoning or calculation problem

SignalFramework
Numerical/calculation, zero-shotPlan-and-Solve (PS+)
Multi-hop with ordered dependenciesLeast-to-Most
Needs first-principles before answeringStep-Back
Multiple distinct approaches to compareTree of Thought
Verify reasoning didn't overlook conditionsRCoT
Linear step-by-step reasoningChain of Thought
Answer must be robust; sample many paths and majority-voteSelf-Consistency

F. CRITIQUE — Stress-testing, attacking, or verifying output

SignalFramework
General quality improvementSelf-Refine
Align to explicit principle/standardCAI Critique-Revise
Find the strongest opposing argumentDevil's Advocate
Identify failure modes before they happenPre-Mortem
Verify reasoning didn't miss conditionsRCoT
Draft may contain hallucinated facts; verify each claimChain-of-Verification

Self-Refine = any quality. CAI = compliance with an explicitly stated standard or requirement set (and aligning the artifact to it — e.g. auditing a plan against a brief's constraints). Devil's Advocate = opposing arguments. Pre-Mortem = failure analysis. RCoT = an answer or plan overlooked a condition implicit in the problem (units, edge cases, unstated dependencies). Chain-of-Verification = independent fact-checking of a draft's factual claims.


G. AGENTIC — Tool-use with iterative reasoning → ReAct (Reasoning + Acting) Signal: "Task requires tools; each result informs the next step"


Combining Frameworks

Most prompts need exactly one framework. Combine only when the task genuinely has two separable phases — one framework structures the request, a second governs how the output is checked or refined. If you cannot name the two phases, do not combine.

WhenCombinationWhy
High-stakes content that must survive reviewCO-STAR + Self-RefineCO-STAR fixes audience/tone/format; Self-Refine adds a critique-and-revise loop before delivery
Multi-step procedure executed with toolsRISEN + ReActRISEN specifies the steps and success criteria; ReAct governs the tool-use cycle within each step
Business deliverable with a hostile audienceBROKE + Devil's AdvocateBROKE sets objective and key results; Devil's Advocate stress-tests them before they reach a stakeholder

When you combine, load assets/templates/hybrid_template.txt and state plainly in your analysis which framework owns which phase. Never stack more than two — beyond that the frameworks' instructions start to overlap and contradict, and no single framework clearly owns any phase.

Composable Techniques

Some techniques are not frameworks you choose between — they are layers you add on top of whichever framework you picked. They answer "how should this prompt be built?", not "which shape is it?", so they never appear in the routing tables above.

  • Few-shot / in-context examples — showing 2–5 worked input→output examples inside the emitted prompt. This is the highest-leverage technique in prompting and applies to almost any framework, not just the two with a dedicated examples slot (CARE, RISE-IX). After you draft the framework prompt, decide whether examples earn their place; if they do, insert them before the final instruction, in the exact target output format, and end with the actual task. Load references/techniques/few-shot.md for when to use it, how many, ordering and recency effects, and the label-space rules — and for the rule that you never invent examples the user or their material did not supply.

3. Framework Quick Reference

One-line per framework (load references/frameworks/ for full detail):

Simple: APE | RTF | CTF Medium: RACE | CARE | BAB | BROKE | CRISPE Comprehensive: CO-STAR | RISEN | TIDD-EC Data: RISE-IE | RISE-IX Reasoning: Plan-and-Solve | Chain of Thought | Least-to-Most | Step-Back | Tree of Thought | RCoT | Self-Consistency Structure/Iteration: Skeleton of Thought | Chain of Density | Iterative Compression Critique/Quality: Self-Refine | CAI Critique-Revise | Devil's Advocate | Pre-Mortem | Chain-of-Verification Meta/Reverse: RPEF | Reverse Role Prompting Agentic: ReAct

Composable technique (layered onto any framework, not selected between): Few-shot / in-context examples

4. Clarification & Probing Questions

Ask targeted questions (3-5 at a time) based on identified gaps.

  • Interactive Tool Probing: When running in Antigravity (agy), use the ask_question tool with structured options or write-in prompts instead of plain unstructured chat text. In Claude Code, use AskFollowupQuestion.

For CO-STAR: Provide the material this is built from if any, the situation and constraints behind it, who the audience is and what you want them to do, the tone and style to write in, the output format and length? For RISEN: Provide the material the procedure runs on if any, the expertise and methodology to adopt, the steps in order, what must be true when it is done, what is out of scope or must not happen? For RISE-IE: Provide the actual data to be processed (not a description of it), its format and any quirks to expect, the expertise needed, the processing steps in order, what the output must look like? For RISE-IX: The expertise to embody, what to create and its core requirements, the workflow steps, provide 2-3 actual samples whose style and format the output should match? For TIDD-EC: Provide the material this task operates on (the message, document, or dataset itself, not a description of it), what kind of task this is and the background that shapes it, the exact steps in order, what must always be included and what must never happen (state each as a prohibition, not a topic), examples of a good result? For CTF: Provide the artifact this operates on if you have one, the situation and background around it, the exact task and deliverable, the output format? For RTF: Provide the material the task applies to if any, the expertise needed, the exact task and deliverable, the output format and length? For APE: Provide the material the action applies to if any, the one action to perform, why it is needed and who uses the result, what a good result looks like? For BAB: Provide the actual artifact being transformed, what is wrong with it now, what it should become, what rules govern the transformation? For RACE: Provide the material the task applies to if any, the role and expertise needed, the action to perform, the situational context and audience, what a successful output looks like? For CRISPE: The expertise and role to embody, provide the data or style sample it should work from, the background it needs, the exact task and deliverable, the tone and how many variants? For BROKE: Provide the supporting material or performance data if you have it, the current situation and why this task exists, the role to embody, the specific deliverable and the structure and length the response should have, the measurable business outcome it should move? For CARE: Provide the source document or draft this works from if any, your situation and why this task exists, the specific ask and deliverable, what must be included and what would make this output wrong or unusable, an example of what good looks like? For Tree of Thought: The decision or problem and its constraints, provide the evidence the branches must be judged against, the 2-5 distinct approaches to compare, the criteria that decide between them? For ReAct: Does the environment this runs in actually have callable tools — if not, stop and use Chain of Thought instead, which tools are available and how each is invoked, what end state counts as success, what limits apply and when to stop? For Skeleton of Thought: The topic or question to outline, provide the document, data, or notes the answer must be drawn from if you have any, who the answer is for and what scope it should cover, how far each point should be expanded (a few sentences, a paragraph, full detail)? For Step-Back: The specific question you want answered, provide the code, document, or design it is about if any, what higher-level principle or concept governs it? For Least-to-Most: The full problem in one statement, provide the material the subproblems must reason over, what is the simplest thing that must be answered first, what does the final answer depend on? For Plan-and-Solve: The problem with every number, unit, and constraint written out, provide the dataset or figures the calculation runs on if any, which values are given and which must be derived? For Chain of Thought: The problem with all its conditions stated, provide the code, data, or document to reason over if any, what the reasoning steps should be? For Self-Consistency: The problem with all its conditions stated, provide the data or figures it runs on if any, what the single final answer should look like so every sampled run ends in a comparable FINAL ANSWER: line, how many samples to run and majority-vote over (the paper uses 40; 5-10 is usually enough)? For Chain of Density: Provide the full document to summarize, the fixed word budget every summary must hit, how many densification passes (the paper uses 5)? For Iterative Compression: Provide the content to compress, where it should end up (word count, reading level, single paragraph), what should improve on each pass, how many passes and when to stop? For Self-Refine: Provide the actual draft to improve, which dimensions the critique should cover (clarity, completeness, tone), what would make this output wrong or unusable? For CAI Critique-Revise: Provide the actual output to be critiqued, the specific standard it must satisfy stated precisely enough to be checkable, what would make this output wrong or unusable? For Devil's Advocate: The position, plan, or decision to attack, provide the proposal or memo that sets it out if you have one, which dimensions the attack should cover? For Pre-Mortem: The project or decision being analyzed with its team, timeline, and goals, provide the plan or proposal document if you have one, how far in the future the imagined failure should be dated? For RCoT: The question with every condition and constraint written out, provide the document those conditions come from if any, any implicit requirement not yet written into the question (units, deadlines, exclusions, edge cases) that a correct answer must still satisfy? For Chain-of-Verification: Provide the draft answer to fact-check if you have one, or the factual question to answer carefully, which specific claims are most at risk of being wrong, what a correct final answer must not get wrong? For RPEF: Provide the actual output sample to reverse-engineer, provide the input that produced it or confirm it is output-only, which details are one-off specifics that should become [PLACEHOLDER] variables? For Reverse Role: What you want to achieve in one or two sentences, the domain of expertise to consult, questions one at a time or all at once, should it then do the task or synthesize a structured prompt for you to approve?

Every set above requests the user's own material/files. Three frameworks are deliberately exempt: ReAct (its material arrives as live tool output, not pasted text), Reverse Role (it elicits everything through the interview and its template has no material slot), and RISE-IX (its samples land in the EXAMPLES slot, which its own question already covers).

5. Apply Framework & Ingest Template

Using gathered information:

  1. Load Template Explicitly: Call file reading tool (view_file) on assets/templates/<framework>_template.txt to read the exact template structure into context.
  2. Map user's information to framework components.
  3. Fill missing elements with reasonable defaults — with two exceptions, below.
  4. Structure according to framework format.
  5. Decide whether worked examples would materially improve the output; if so, load references/techniques/few-shot.md and layer in few-shot examples. Reach for it especially on classification, extraction, strict-format, and style-matching tasks, and only when the user or their material supplies real examples.

Never default a fact about the user's world. Their business, metrics, history, policies, staff, customers, data, or constraints are things only they know. Where such a slot is unanswered, emit a visible [you fill this in: <what is needed>] placeholder and list every placeholder in your analysis section.

Never soften or drop a prohibition. If the user said something must not happen, it must survive into the emitted prompt as an explicit "Do not…" or "Never…" instruction. It cannot rely on a section header to carry the negation, because headers are stripped at emission (see step 6).

6. Present Improvements & File Persistence

Structure your output in this exact order:

A. Analysis section (comes first):

  • Framework selected and why
  • Changes made and reasoning
  • Framework components applied

B. Usage instructions (transition block, immediately before the prompt):

Your revised prompt is ready.

  • New chat: Copy the prompt below and paste it as your first message in a new conversation.
  • Same chat: Tell the assistant: "Use the revised prompt you just provided as a new instruction and execute it."

C. The revised prompt (comes last, in a fenced code block):

  • Present as a clean, flat-text block inside triple backticks.
  • No framework section headers (no "BEFORE:", "BRIDGE:", "CONTEXT:", etc.) — these are scaffolding, not part of the deliverable.
  • No indentation beyond what the prompt itself genuinely requires.
  • No markdown formatting inside the block unless the prompt explicitly needs it (e.g., it asks for tables).
  • The user must be able to copy the entire block contents and paste it verbatim with zero editing — except for [...] placeholders.
  • Nothing after the code block — the revised prompt must be the absolute last element in the chat response.

D. Direct File Persistence (Harness Action):

  • If the user requested saving the prompt to a file (e.g. .agents/prompts/name.txt, .agents/rules/name.md, or a project file), use write_to_file to write the clean prompt directly to disk.

7. Iterate & Verify

  • Confirm improvements align with intent.
  • Refine based on feedback.
  • Empirical Verification (Subagent Benchmarking): When validating a mission-critical or complex prompt, use invoke_subagent to test-run both the original prompt and revised prompt against a sample task to benchmark response quality and compliance.

Framework References

Detailed framework docs in references/frameworks/:

  • co-star.md - Context, Objective, Style, Tone, Audience, Response
  • risen.md - Role, Instructions, Steps, End goal, Narrowing
  • rise.md - Dual variant support: RISE-IE (Input-Expectation) & RISE-IX (Instructions-Examples)
  • tidd-ec.md - Task type, Instructions, Do, Don't, Examples, Context
  • ctf.md - Context, Task, Format
  • rtf.md - Role, Task, Format
  • ape.md - Action, Purpose, Expectation (ultra-minimal)
  • bab.md - Before, After, Bridge (transformation/rewrite tasks)
  • race.md - Role, Action, Context, Expectation (medium complexity)
  • crispe.md - Capacity+Role, Insight, Instructions, Personality, Experiment
  • broke.md - Background, Role, Objective, Key Results, Evolve
  • care.md - Context, Ask, Rules, Examples (constraint-driven)
  • tree-of-thought.md - Branching exploration of multiple solution paths
  • react.md - Reasoning + Acting (agentic tool-use cycles)
  • skeleton-of-thought.md - Skeleton-first then expand (parallel generation)
  • step-back.md - Abstract to principles first, then answer (Google DeepMind)
  • least-to-most.md - Decompose into ordered subproblems, solve sequentially
  • plan-and-solve.md - Zero-shot: plan + extract variables + calculate (PS+)
  • chain-of-thought.md - Step-by-step reasoning techniques
  • chain-of-density.md - Entity densification at fixed length, for summarization (Adams et al.)
  • iterative-compression.md - Progressive shortening toward a target length
  • self-refine.md - Generate → Feedback → Refine loop (NeurIPS 2023)
  • cai-critique-revise.md - Principle-based critique + revision (Anthropic)
  • devils-advocate.md - Strongest opposing argument generation (ACM IUI 2024)
  • pre-mortem.md - Assume failure, identify causes + warning signs (Gary Klein)
  • rcot.md - Reverse Chain-of-Thought: verify by reconstructing the question
  • rpef.md - Reverse Prompt Engineering: recover prompt from output (EMNLP 2025)
  • reverse-role.md - AI-Led Interview: AI asks you questions first (FATA)
  • self-consistency.md - Sample N reasoning paths, majority-vote externally (Wang et al., ICLR 2023)
  • chain-of-verification.md - Draft, plan checks, verify independently, revise (Dhuliawala et al., Findings of ACL 2024)

Load these when applying specific frameworks for detailed component guidance, selection criteria, and examples.

Composable techniques (layered onto a framework, not selected from the routing tables) live in references/techniques/:

  • few-shot.md - In-context examples: when to add them, how many, ordering, label-space rules

Harness tool adaptations live in references/harnesses/:

  • antigravity.md - Antigravity CLI (agy) tool mappings
  • claude-code.md - Claude Code tool mappings

Templates

Every framework has a fill-in template at assets/templates/<framework>_template.txt, named after the framework's reference doc (e.g. co-star.md → co-star_template.txt). RISE has two: rise-ie_template.txt and rise-ix_template.txt. One extra template, hybrid_template.txt, is for combined-framework prompts (see Combining Frameworks).

Key Principles

  1. Ask Before Assuming - Don't guess intent; clarify ambiguities using interactive tools
  2. Explain Reasoning - Why this framework? Why these changes?
  3. Show Your Work - Display analysis, show framework mapping
  4. Be Iterative - Start with analysis, refine progressively
  5. Respect User Choices - Adapt if user prefers different framework
  6. Leverage Harness Tools - Ingest files, read templates via file viewer, probe interactively, persist directly to disk

When NOT to Use Frameworks

Frameworks add structure — but structure has overhead. Skip them when:

  • The prompt is already complete: Clear goal, full context, defined format → just execute it.
  • Purely factual lookups: "What is the capital of France?" — no framework needed.
  • Conversational exchanges: Back-and-forth dialogue doesn't need a structured template.
  • Very short one-off tasks: "Translate this sentence to Spanish." APE would be overhead; just translate.
  • User is in a hurry: If someone explicitly says "just do it", don't pause for framework selection — deliver, then offer to structure if they want more.
  • The task is fully specced by context: When the codebase, existing docs, or prior messages already contain everything needed.

Rule of thumb: Apply a framework when there's a gap between what the user asked for and what they need. If there's no gap, there's no job for a framework.


Example Interaction

This example shows the full intent-based flow — detecting intent, using the discriminating table, selecting a framework, asking questions, and delivering a structured result.

User: "Rewrite this job posting in docs/job-post.md — it's too formal and isn't getting applicants."

Assistant:

  1. Reads docs/job-post.md via view_file.
  2. Assesses initial score (Clarity: 6, Specificity: 4, Context: 5, Completeness: 5, Structure: 5 → Overall: 5.0).
  3. Detects intent: TRANSFORM → BAB (Before, After, Bridge).
  4. Loads assets/templates/bab_template.txt via view_file.
  5. Clarifies requirements with structured questions via ask_question.

Analysis (BAB framework applied):

  1. Locked the current state so the AI understands the starting point
  2. Defined the target state in terms the AI can evaluate against
  3. Made transformation rules explicit and prioritized
  4. Protected non-negotiable elements (requirements) from being changed
  5. Gave a concrete length/tone constraint to prevent over-engineering

Your revised prompt is ready.

  • New chat: Copy the prompt below and paste it as your first message in a new conversation.
  • Same chat: Tell the assistant: "Use the revised prompt you just provided as a new instruction and execute it."
[Paste the current job posting here]

The job posting above suffers from corporate-speak, passive voice, overly formal tone, and generic language that doesn't reflect actual team culture.

The rewritten version should sound like it was written by engineers, for engineers. Early-career developers should read it and think "I want to work there." It should feel honest, direct, and human — not like legal boilerplate.

Follow these rules:
- Replace all passive constructions with active voice.
- Convert corporate jargon to plain English (e.g., "leverage" → "use").
- Add one specific, concrete detail about the team or culture per section.
- Keep all technical requirements and must-haves verbatim — do not change these.
- Target reading level: conversational, not academic.
- Length: same or shorter than the original. Cut fluff, don't add it.

Now rewrite the job posting above.

Usage Notes

  • Ingest source files directly using view_file or search codebase with grep_search
  • Always analyze the original prompt with the 5-dimension rubric
  • Recommend framework(s) with reasoning
  • Load framework template explicitly via view_file from assets/templates/
  • Ask clarifying questions progressively using interactive questioning tools (ask_question / AskFollowupQuestion)
  • Present improvements cleanly without scaffolding headers
  • Offer to save to file (write_to_file) or run subagent benchmark (invoke_subagent) when appropriate

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.