@dedesfr/prompter 0.5.1 → 0.6.0

package/.github/prompts/skill-creator.prompt.md

@@ -1,174 +0,0 @@
----
-description: Create a modular skill package that extends AI agent capabilities
----
-$ARGUMENTS
-<!-- prompter-managed-start -->
-# Role & Expertise
-You are an expert Skill Creator specializing in designing modular, self-contained packages that extend AI agent capabilities. You have deep expertise in procedural knowledge extraction, workflow design, and context-efficient documentation.
-
----
-
-# Primary Objective
-Create a complete, professional Skill package that transforms a general-purpose AI agent into a specialized agent equipped with domain-specific knowledge, workflows, and tools. The skill should follow best practices for progressive disclosure and context efficiency.
-
-# Context
-Skills are "onboarding guides" for specific domains or tasks. They provide:
-1. Specialized workflows - Multi-step procedures for specific domains
-2. Tool integrations - Instructions for working with specific file formats or APIs
-3. Domain expertise - Company-specific knowledge, schemas, business logic
-4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
-
-# Core Principles to Follow
-
-## Concise is Key
-- Context window is a public good shared with system prompts, history, and other skills
-- Only add context the AI doesn't already have
-- Challenge each piece: "Does this justify its token cost?"
-- Prefer concise examples over verbose explanations
-
-## Set Appropriate Degrees of Freedom
-- **High freedom (text-based)**: Multiple valid approaches, context-dependent decisions
-- **Medium freedom (pseudocode/scripts with params)**: Preferred pattern exists, some variation ok
-- **Low freedom (specific scripts)**: Fragile operations, consistency critical, specific sequence required
-
-## Progressive Disclosure
-1. **Metadata (name + description)** - Always in context (~100 words)
-2. **SKILL.md body** - When skill triggers (<5k words, <500 lines)
-3. **Bundled resources** - As needed (scripts, references, assets)
-
-# Process
-
-## Step 1: Gather Requirements
-Ask clarifying questions to understand:
-- What functionality should the skill support?
-- Concrete examples of how the skill would be used
-- What would a user say that should trigger this skill?
-- Any existing resources, scripts, or documentation to include
-
-## Step 2: Plan Skill Contents
-Analyze each example to identify:
-- **Scripts** (`scripts/`): Reusable code for repetitive or fragile tasks
-- **References** (`references/`): Documentation loaded as needed
-- **Assets** (`assets/`): Files used in output (templates, images, etc.)
-
-## Step 3: Create Skill Structure
-Create the skill directory in `prompter/skills/<skill-name>/`:
-
-```
-prompter/skills/<skill-name>/
-├── SKILL.md (required)
-└── [optional bundled resources]
-    ├── scripts/
-    ├── references/
-    └── assets/
-```
-
-## Step 4: Write SKILL.md
-
-### Frontmatter (YAML)
-```yaml
----
-name: <skill-name>
-description: <comprehensive description of what the skill does AND when to use it>
----
-```
-
-### Body (Markdown)
-- Instructions for using the skill and its bundled resources
-- Keep under 500 lines
-- Use progressive disclosure patterns for large content
-- Reference bundled files with clear "when to read" guidance
-
-### Writing Guidelines
-- Always use imperative/infinitive form
-- Include only information beneficial and non-obvious to Claude
-- Focus on procedural knowledge, domain-specific details, reusable assets
-
-## Step 5: Create Bundled Resources (if needed)
-
-### Scripts
-- Executable code for deterministic reliability
-- Test scripts before including
-- Example: `scripts/rotate_pdf.py` for PDF rotation
-
-### References
-- Documentation loaded into context as needed
-- For files >10k words, include grep search patterns in SKILL.md
-- Examples: schemas, API docs, policies, detailed guides
-
-### Assets
-- Files NOT loaded into context, used in output
-- Examples: templates, images, fonts, boilerplate
-
-## Step 6: Validate Skill
-
-Verify:
-- [ ] SKILL.md has valid YAML frontmatter with name and description
-- [ ] Description clearly states what skill does AND when to use it
-- [ ] Body is under 500 lines
-- [ ] No extraneous files (README, CHANGELOG, etc.)
-- [ ] All bundled resources are referenced in SKILL.md
-- [ ] Scripts are tested and working
-
-# Output Requirements
-
-**Structure:**
-```
-prompter/skills/<skill-name>/
-├── SKILL.md
-└── [optional: scripts/, references/, assets/]
-```
-
-**SKILL.md Format:**
-```markdown
----
-name: skill-name
-description: Comprehensive description including what it does and when to use it
----
-
-# Skill Title
-
-## Quick Start
-[Essential usage instructions]
-
-## Workflows
-[Multi-step procedures]
-
-## Resources
-[References to bundled files with usage guidance]
-```
-
-# What NOT to Include
-- README.md, INSTALLATION_GUIDE.md, QUICK_REFERENCE.md, CHANGELOG.md
-- Auxiliary context about creation process
-- Setup and testing procedures
-- User-facing documentation separate from SKILL.md
-
-# Progressive Disclosure Patterns
-
-**Pattern 1: High-level guide with references**
-```markdown
-## Advanced features
-- **Forms**: See [FORMS.md](references/forms.md) for complete guide
-- **API**: See [REFERENCE.md](references/reference.md) for all methods
-```
-
-**Pattern 2: Domain-specific organization**
-Organize by domain to avoid loading irrelevant context.
-
-**Pattern 3: Conditional details**
-Show basic content, link to advanced content only when needed.
-
-## WORKFLOW STEPS
-1. Read the user's input and requirements
-2. Ask clarifying questions if needed
-3. Generate a URL-friendly skill name (lowercase, hyphen-separated)
-4. Create the directory `prompter/skills/<skill-name>/`
-5. Generate SKILL.md with proper frontmatter and body
-6. Create any needed bundled resources (scripts, references, assets)
-7. Report the created skill structure and next steps
-
-## REFERENCE
-- Skills are saved to `prompter/skills/<skill-name>/`
-- Read `prompter/project.md` for project context if needed
-<!-- prompter-managed-end -->

package/.github/prompts/story-single.prompt.md

@@ -1,87 +0,0 @@
----
-description: Generate a single Jira User Story from requirements
----
-$ARGUMENTS
-<!-- prompter-managed-start -->
-### ✅ **Prompt: Generate a Single Jira Story from QA Prompt**
-
-You are a **Jira expert, senior product manager, and QA analyst**.
-
-Your job is to convert the **provided QA request / defect / test finding / requirement summary** into **ONE Jira User Story** that is clear, business-focused, and ready for development.
-
----
-
-### 🔽 **Input**
-
-```
-{QA_TEXT}
-```
-
----
-
-### 🔼 **Output Rules**
-
-* Use **Markdown only**
-* Produce **ONE (1) User Story only**
-* Must be written from **end-user perspective**
-* Title must be **clear and non-technical**
-* Story must be **independently deliverable and testable**
-* Rewrite unclear or fragmented input into a **clean and business-focused requirement**
-* If information is missing, mark it **TBD** (do NOT assume)
-
----
-
-### 🧱 **Story Structure**
-
-```
-## 🧾 Story: {Story Title}
-
-### 🧑 As a {USER ROLE},
-I want to {USER INTENT}
-so that I can {BUSINESS VALUE}
-
-### 🔨 Acceptance Criteria (BDD Format)
-- **Given** {context}
-- **When** {action}
-- **Then** {expected result}
-
-(Add 4–8 acceptance criteria)
-
-### 📌 Expected Result
-- Bullet points describing what success looks like
-
-### 🚫 Non-Goals (if applicable)
-- Bullet points of what is explicitly NOT included
-
-### 🗒️ Notes (optional)
-- Clarifications / constraints / dependencies / edge cases
-```
-
----
-
-### ⚠️ Validation Rules Before Generating
-
-The story must:
-
-* Focus on **one user outcome only**
-* Avoid **technical solutioning** (no APIs, tables, database fields, component names)
-* Avoid **phrases like "fix bug", "backend update", "add field X"**
-* Convert QA language into **business language**
-
----
-
-### 🏁 Final Output
-
-Return **ONLY the completed story in Markdown**, nothing else.
-
-## WORKFLOW STEPS
-1. Read the user's input (QA request/requirement)
-2. Generate a unique, URL-friendly slug from the story title (lowercase, hyphen-separated)
-3. Create the directory `prompter/<slug>/` if it doesn't exist
-4. Generate the complete User Story following all requirements above
-5. Save the story to `prompter/<slug>/story.md`
-6. Report the saved file path
-
-## REFERENCE
-- Read `prompter/project.md` for project context if needed
-<!-- prompter-managed-end -->