Install
$ agentstack add skill-sametbrr-prompt-architect-prompt-architect ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Prompt Architect Skill
Transforms any user input — Turkish or English — into a domain-classified, pattern-aware, quality-reviewed expert prompt, and optionally executes it. Built on Anthropic's official Claude prompting practices (UI/chat-compatible only) and the user's CLAUDE.md global rules.
Reference Library (read these when needed)
When working through a request, consult the relevant reference file(s):
- [references/claude-prompting-patterns.md](references/claude-prompting-patterns.md) — 9 UI-compatible prompting patterns (role, XML structuring, positive guidance, in-context CoT, in-context few-shot, step ordering, output framing, long-context hierarchy, iterative refinement). API-only patterns are explicitly out of scope.
- [references/quality-gates.md](references/quality-gates.md) — 8 self-review gates with the insurance-claim case study showing bad → better → best progression.
- [references/domain-taxonomy.md](references/domain-taxonomy.md) — 25 domains with TR/EN signal keywords and conflict-resolution table.
- [references/mode-inference.md](references/mode-inference.md) — decision tree and precedence rules for
prompt_onlyvsprompt_and_execute. - [references/claude-md-rules.md](references/claude-md-rules.md) — how the 7 CLAUDE.md global rules apply both to the skill flow AND to the refined prompt itself.
Templates:
- [assets/templates/refined-prompt-xml.tmpl](assets/templates/refined-prompt-xml.tmpl) — XML scaffold (default for complex tasks).
- [assets/templates/refined-prompt-compact.tmpl](assets/templates/refined-prompt-compact.tmpl) — bullet scaffold (simple tasks, 500–1000 chars).
assets/templates/domain-*.tmpl— 6 domain packs (strategy, engineering, marketing, legal, finance, hr) with role phrasings, default steps, output formats.
Optional automation:
- [scripts/validateprompt.py](scripts/validateprompt.py) — runs the 8 quality gates against a draft. Useful for self-testing during development.
Workflow (6 stages)
Stage 1 — Analyze the Input
- Identify: primary objective, expected output, constraints, implied requirements.
- Compute a complexity score: simple / moderate / complex based on (a) input length, (b) number of distinct constraints, (c) presence of multi-step process signals, (d) need for reference data.
- Apply CLAUDE.md Rule #2 (Think Step by Step): never skip this stage.
- Belirsizlik kapısı: Only if input is completely unusable — single word, internally contradictory, or zero domain signal — ask one (and only one) clarifying question. Otherwise, infer.
Stage 2 — Classify the Domain
- Match input against [references/domain-taxonomy.md](references/domain-taxonomy.md) signal keywords (TR + EN).
- Pick the single dominant domain. Note a supporting domain only if it materially shapes the deliverable.
- Use the conflict-resolution cheat sheet for ambiguous cases.
Stage 3 — Select Patterns
- From [references/claude-prompting-patterns.md](references/claude-prompting-patterns.md), pick 3–6 patterns that this specific task warrants — not all 9.
- Defaults that almost always apply: #1 Role, #2 XML/Tag Structuring, #3 Positive Guidance, #8 Output Framing.
- Add conditionally: #4 CoT (multi-step analysis), #5 Few-shot (format/edge-case learning), #6 Step ordering (when order matters), #7 Long-context hierarchy (bulky data).
- Apply CLAUDE.md Rule #5 (Simplest Solution First): pick the minimum that makes the prompt complete.
Stage 4 — Draft the Refined Prompt
- Pick template by complexity:
- simple → [assets/templates/refined-prompt-compact.tmpl](assets/templates/refined-prompt-compact.tmpl) (500–1000 chars, bullet body, adherence footer)
- moderate or complex → [assets/templates/refined-prompt-xml.tmpl](assets/templates/refined-prompt-xml.tmpl) (1500–3000 chars, XML body with `
//////`) - Enrich with the matching
assets/templates/domain-*.tmplfor role phrasing, default steps, and output structure. - Prompt body is always in English, regardless of user's input language.
Stage 5 — Self-Review
- Apply CLAUDE.md Rule #4 (Self-Review): run the prompt mentally through the 8 gates in [references/quality-gates.md](references/quality-gates.md).
- For complex prompts, optionally invoke
python3 scripts/validate_prompt.py --stdinwith the drafted prompt to get an automated report. - If any gate fails, do one revision pass. If a gate still fails after revision, surface it honestly in the
Self-Review:line.
Stage 6 — Execute (only if mode is prompt_and_execute)
- Use the refined prompt as the internal instruction set; generate the deliverable.
- File output rule (Claude Code / local CLI context): If the deliverable is structured content (report, document, plan, code, schema, query, structured analysis) OR exceeds ~50 lines, save it to the current working directory as
-output.and only show a concise summary + the saved file path inline. Extensions: .mdfor strategy, plans, reports, prose, mixed content.ts/.py/.js/.cs/ etc. for code.sqlfor queries,.json/.yamlfor configs/schemas.txtonly as a last resort
For short, conversational, single-answer outputs (` block (6 bullets covering Rules #1, #7 / #2 / #3 / #4 / #5 / #6).
- Compact mode: single-line
Adherence:footer condensing the same six rules. - See [references/claude-md-rules.md](references/claude-md-rules.md) for the exact phrasings.
- Keep rationale concise and evidence-based.
- Keep assumptions minimal — but include them whenever genuinely uncertain (Rule #7).
- Supported input languages: Turkish and English only. If input is in another language, politely inform the user and ask them to resubmit in Turkish or English.
- Always respond in the same language the user used for surrounding text and section labels (Turkish input → Turkish section headers; English input → English section headers).
- The Refined English Prompt body is always written in English, regardless of input language.
- Apply CLAUDE.md Rule #3 (Give Only the Result): no preamble like "Here is your refined prompt..." — produce the structured output directly.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sametbrr
- Source: sametbrr/prompt-architect
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.