agentleFS
fabioc-alohafabioc-aloha/Alex_ACT_Edition/.github/skills/prompt-creator/SKILL.md

prompt-creator

Skill0 starsChanged 4 months agoMITView on GitHub

Create prompts that pass prompt-review's five gates by construction — intent capture, slash-command naming, single-workflow scope, draft as numbered steps, dogfood self-review. Use when authoring a new prompt, refactoring an existing one, or promoting a Mall prompt into the heir's brain.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If another prompt covers the same workflow, extend it.

    line 46
  2. Very specific:

    Before committing, run prompt-review's five gates.

    line 112
  3. Distinctive:

    No new prompts authored via this guide in 90 days (decorative — sunset)

    line 132

“Common” is measured: kept by at least 6 in 10 of the 5 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
<!-- intentional divergence from Supervisor: Edition strips Supervisor-only routing tables (curation-only vs. mirror split) and uses heir-portable phrasing ("into the heir's brain"). Same five gates. Audited 2026-05-31. -->

Prompt Creator

Author prompts that pass prompt-review's five gates by construction. The gates are the quality bar; invert them, and you build to standard the first time.

Mirrors skill-creator's seven-phase structure with prompt-specific guidance. If a phase here disagrees with skill-creator on the shared scaffold, skill-creator wins; this file owns only the per-type guidance.

When to Use

  • Authoring a new prompt in .github/prompts/
  • Refactoring an existing prompt (rename, scope tighten, step revision)
  • Promoting a Mall prompt into your heir's brain

When not to use

  • Authoring a skill (the procedure body) → use skill-creator. Prompts are entry-points; skills are bodies.
  • Authoring an instruction (always-on or pattern-applied rule) → use instruction-creator
  • Authoring an agent (delegated sub-process role) → use agent-creator

The Seven Phases

Each phase inverts one of the five gates. Author against the phase, pass the gate.

Phase 1 — Intent capture

Answer in writing before any drafting:

  1. What workflow does this kick off? One sentence. If it contains "and" / "+", you have two prompts — split.
  2. What slash-command does the user type? The filename (minus .prompt.md) becomes /<name>. Pick something a user would intuitively type. /review-instruction good; /v2-thing-do bad.
  3. What skill does this prompt invoke? Most prompts are thin wrappers that call a skill. If the answer is "no skill, the prompt carries the workflow", stop — author the skill first, then the prompt.

Phase 2 — Prior-art scan

Get-ChildItem .github/prompts/*.prompt.md
Select-String -Path .github/prompts/*.prompt.md -Pattern "<keyword>"

If another prompt covers the same workflow, extend it. If a Mall prompt covers it, adopt.

Phase 3 — Draft against Gate 1 (Spec)

Frontmatter template:

---
description: "<third-person, what + when to invoke, ≤1024 chars>"
lastReviewed: YYYY-MM-DD
---

Do NOT add mode: agent — per current Microsoft Learn prompt-files spec, this field is deprecated. Existing prompts may carry it during sweep transition; new prompts should not.

File location: .github/prompts/<kebab-name>.prompt.md (flat — no subfolders).

Slash-picker discoverability: the filename IS the user's typing surface. After you pick a name, mentally type /<name> and ask: would a user trying to find this workflow guess that string? If not, rename.

Phase 4 — Draft against Gate 2 (Quality)

CriterionHow you author for it
Imperative voiceVerbs in the imperative ("Run", "Read", "Apply", "Save").
Numbered stepsThe prompt's body is a numbered step list. Brief context paragraph allowed before the steps; nothing else.
Single workflow scopeOne goal. No "menus" of unrelated commands.
≤100 linesIf you need more, the workflow belongs in a skill the prompt invokes.
FalsifierPrompts <30 lines may inline a one-line falsifier; longer prompts need an explicit ## Would Revise If section.

Template structure:

---
description: "..."
lastReviewed: YYYY-MM-DD
---

# /<prompt-name>

<one-paragraph context: what skill this invokes, what the user gets>

Steps:

1. <imperative action>
2. <imperative action>
3. <imperative action>

<optional: conditions / branches / output format>

Phase 5 — Draft against Gate 3 (Scope)

TargetRoute
Generic developer workflow (status, save-note, banner)Heir baseline
Project-specific workflowThat project's local-only repo
External-surface commandNot an ACT prompt — author a Mall unit

Workflow vs body distinction: the prompt invokes the skill; the skill carries the procedure. If your prompt body has more than ~10 numbered steps, it's drifting into skill territory.

Phase 6 — Draft against Gate 4 (Safety)

Same checks as skill-creator Phase 6. Prompt-specific: if the workflow invokes destructive operations (force-push, drop, delete), the step list must include an explicit user-confirmation step before the destructive call.

Phase 7 — Dogfood self-audit

Before committing, run prompt-review's five gates. Verdict lives in the commit message.

Slash-picker test: imagine the prompt appears in a picker alongside your existing prompts. Is it discoverable by name? Does the description make its purpose obvious?

Anti-Patterns

Anti-patternCorrection
Authoring a prompt before its underlying skill existsAuthor the skill first; the prompt is the entry-point
Adding mode: agent to a new promptDeprecated per Microsoft Learn spec. Drop it.
Bundling unrelated commands into a "menu" promptOne workflow per prompt
Cryptic prompt nameFilename = typing surface. If a user can't guess /<name>, rename.
Letting the prompt body grow into a procedureIf you need more than ~10 steps, the workflow belongs in a skill
Referencing a retired skill in Steps:Gate 5 semantic failure. Check that step references resolve.

Falsifiability

This skill's design has failed if any of the following occur within 90 days:

  • ≥2 prompts authored using this guide fail prompt-review on first self-audit
  • No new prompts authored via this guide in 90 days (decorative — sunset)
  • Slash-picker discoverability check produces consistent miscalibration (cryptic names accepted, or obvious names rejected) ≥3 times in a quarter

Track as you would any falsified discipline (commit log, retraining notes, or curation ledger if your repo ships one) tagged [PROMPT-CREATOR-MISS].

Related

  • prompt-review — the five gates this skill inverts
  • skill-creator — sibling for skills; canonical seven-phase scaffold
  • instruction-creator — sibling for instructions
  • agent-creator — sibling for agents
  • act-pass — required for medium-stakes prompt authoring

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.