agentleFS
cxm-ictcxm-ict/claude-skills/prompt-architect/SKILL.md

prompt-architect

Skill1 starsChanged 7 months agoLicence not identifiedView on GitHub

The thorough prompt builder for professional work. Runs a deep, domain-specific interview, builds the prompt with professional techniques (role, examples, structure, success criteria), test-runs it, critiques the result, iterates, and delivers a reusable template with variables. Use this skill when the user uses terms like "ultimate prompt", "reusable prompt", "prompt template", "a prompt I use often", "test and improve this prompt", "build a prompt system", "domain-specific prompt for [field]", or when someone uses a prompt structurally rather than once. Suited for heavier work: client communication, cold outreach, content marketing, technical specs, analysis, customer service. If the user only wants a quick, single-use prompt, use promptmaker instead. Hold the conversation in the user's language; deliver the prompt itself in the language of the use case.

21 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

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 20 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.

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.