senior-prompt-engineer

Refine existing SKILL.md prompts for triggers, role clarity, and output contracts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JuantoC/BlueStack-Test-Automation-Framework --skill senior-prompt-engineer-juantoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-prompt-engineer
Source: https://github.com/JuantoC/BlueStack-Test-Automation-Framework/tree/main/.claude/skills/senior-prompt-engineer
Command: npx skills add https://github.com/JuantoC/BlueStack-Test-Automation-Framework --skill senior-prompt-engineer-juantoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams sharpen and evolve existing prompts within the Bluestack QA workspace. It focuses on refining frontmatter triggers, clarifying the intended role and behavior, and tightening output contracts and validation blocks, all while respecting SSOT and wiki-first principles. It does not create new prompts from scratch; it enhances and aligns prompts to the project’s conventions.

Core Features & Use Cases

  • Evolves prompts of existing SKILL.md files: clarifies triggers, role, and required outputs.
  • Enforces promotion of safe, verifiable behavior: ensures presence of validation blocks and auditor-focused outputs.
  • Guides alignment with project conventions: references wiki-first workflow, JSdoc references, and SSOT rules; avoids embedding executable logic in Markdown.

Quick Start

Proporciona el SKILL.md existente y especifica los cambios deseados para optimizar desencadenadores, claridad de rol y los bloques de salida.

Frequently Asked Questions about senior-prompt-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refine SKILL.md frontmatter triggers and role clarity without altering TypeScript code?

Refine SKILL.md frontmatter triggers by evolving existing prompt instructions to clarify roles and output contracts, ensuring no underlying TypeScript behavior is modified. This aligns prompts with project conventions while keeping executable logic untouched.

What is the best way to add validation and auditor output blocks to an existing prompt?

Add validation and auditor output blocks by evolving the prompt's instruction set to enforce safe, verifiable behavior. This ensures required final validation blocks and auditor-focused outputs are present across the QA workspace.

Can I use this approach to create new prompts from scratch for my QA workspace?

No, you cannot create new prompts from scratch. This approach strictly evolves existing SKILL.md files by sharpening triggers, role clarity, and output contracts rather than generating new prompts.

How do I ensure my evolved prompts comply with SSOT rules and wiki-first guidance?

Ensure evolved prompts comply with SSOT rules and wiki-first guidance by verifying alignment with project conventions during refinement. This avoids embedding executable logic in Markdown and references JSdoc sources correctly.

Why should I avoid embedding executable logic in Markdown when updating prompt instructions?

Avoid embedding executable logic in Markdown to prevent introducing behavior not present in TypeScript sources. Markdown should only guide alignment and output contracts, ensuring the SSOT remains in the executable code.