wtf-p 0.1.0 → 0.3.0

package/{commands → vendors/claude/commands}/wtfp/help.md

@@ -1,6 +1,7 @@
 ---
 name: wtfp:help
 description: Show available WTF-P commands and usage guide
+allowed-tools: []
 ---
 
 <objective>
@@ -14,6 +15,7 @@ Output ONLY the reference content below. Do NOT add:
 - Any commentary beyond the reference
 </objective>
 
+<process>
 <reference>
 # WTF-P Command Reference
 
@@ -333,10 +335,36 @@ Claude adapts its role per section:
 /wtfp:respond-reviews  # Generate response doc
 ```
 
+## Contributing to WTF-P
+
+Found a bug or want a new feature? Use these commands:
+
+**`/wtfp:report-bug`**
+Report a bug via GitHub issue.
+- Guides you through describing the problem
+- Collects environment info automatically
+- Creates well-formatted issue with `gh` CLI
+
+**`/wtfp:request-feature`**
+Request a new feature via GitHub issue.
+- Helps articulate what you need and why
+- Checks for duplicate requests
+- Can lead into implementation if desired
+
+**`/wtfp:contribute`**
+Guide through contributing code via Pull Request.
+- Fork → Branch → Implement → Test → PR workflow
+- Works for new commands, bug fixes, docs
+- Follows project conventions automatically
+
 ## Getting Help
 
 - Read `.planning/PROJECT.md` for paper vision
 - Read `.planning/STATE.md` for current context
 - Check `.planning/ROADMAP.md` for section status
 - Run `/wtfp:progress` to check where you're at
+- Report bugs: `/wtfp:report-bug`
+- Request features: `/wtfp:request-feature`
+- GitHub: https://github.com/akougkas/wtf-p
 </reference>
+</process>

package/vendors/claude/commands/wtfp/report-bug.md

@@ -0,0 +1,131 @@
+---
+name: wtfp:report-bug
+description: Report a bug in WTF-P via GitHub issue
+allowed-tools:
+  - Bash
+  - Read
+  - AskUserQuestion
+---
+
+<objective>
+Help the user report a bug in WTF-P by creating a well-formatted GitHub issue.
+</objective>
+
+<context>
+@~/.claude/write-the-f-paper/references/github-contrib.md
+</context>
+
+<process>
+
+## Step 1: Verify GitHub CLI
+
+Check if `gh` is authenticated:
+
+```bash
+gh auth status 2>&1
+```
+
+If not authenticated, inform the user:
+> To create GitHub issues, you need to authenticate the GitHub CLI.
+> Run: `gh auth login`
+> Then try this command again.
+
+## Step 2: Gather Bug Information
+
+Use AskUserQuestion to collect bug details:
+
+**Question 1: Bug Category**
+- Header: "Bug Type"
+- Options:
+  - "Command fails" - A /wtfp:* command doesn't work as expected
+  - "Installation issue" - Problems with npx wtf-p install/uninstall
+  - "Workflow error" - Writing workflow produces wrong output
+  - "Documentation gap" - Docs are missing or incorrect
+
+**Question 2: Bug Description**
+- Header: "Description"
+- Options:
+  - "Let me describe it" - User provides description
+  - "Help me articulate" - Claude helps user describe the bug
+
+If user needs help articulating, ask follow-up questions:
+- What were you trying to do?
+- What happened instead?
+- What did you expect to happen?
+
+## Step 3: Gather Environment Info
+
+Automatically collect:
+```bash
+npx wtf-p --version 2>/dev/null || echo "Not installed via npx"
+node --version
+uname -s 2>/dev/null || echo "Unknown OS"
+```
+
+## Step 4: Collect Reproduction Steps
+
+Ask user:
+- What command or action triggered the bug?
+- Can you reproduce it consistently?
+- Any error messages? (ask to paste them)
+
+## Step 5: Draft the Issue
+
+Create a draft and show it to the user:
+
+```markdown
+## Bug Description
+[From user input]
+
+## Steps to Reproduce
+1. [Step 1]
+2. [Step 2]
+3. [What happened vs expected]
+
+## Environment
+- WTF-P version: [collected]
+- Node.js version: [collected]
+- OS: [collected]
+
+## Additional Context
+[Error messages, logs, screenshots mentioned]
+```
+
+## Step 6: Confirm and Create
+
+Ask user to confirm:
+- "Create this issue?" with options: Yes / Edit first / Cancel
+
+If confirmed, create the issue:
+
+```bash
+gh issue create \
+  --repo akougkas/wtf-p \
+  --title "bug: [SHORT_TITLE]" \
+  --body "$(cat <<'EOF'
+[FULL_BODY_HERE]
+EOF
+)" \
+  --label "bug"
+```
+
+## Step 7: Report Success
+
+Show the user:
+- Issue URL (from gh output)
+- Issue number
+- What happens next (maintainer will review)
+
+</process>
+
+<error-handling>
+
+**gh not installed**: Direct user to https://cli.github.com/
+
+**gh not authenticated**: Guide through `gh auth login`
+
+**Network error**: Save draft locally, retry later
+
+**Permission denied**: User may need to fork first for external contributors
+
+</error-handling>

package/vendors/claude/commands/wtfp/request-feature.md

@@ -0,0 +1,160 @@
+---
+name: wtfp:request-feature
+description: Request a new feature for WTF-P via GitHub issue
+allowed-tools:
+  - Bash
+  - Read
+  - AskUserQuestion
+---
+
+<objective>
+Help the user request a new feature for WTF-P by creating a well-formatted GitHub issue.
+</objective>
+
+<context>
+@~/.claude/write-the-f-paper/references/github-contrib.md
+</context>
+
+<process>
+
+## Step 1: Verify GitHub CLI
+
+Check if `gh` is authenticated:
+
+```bash
+gh auth status 2>&1
+```
+
+If not authenticated, inform the user:
+> To create GitHub issues, you need to authenticate the GitHub CLI.
+> Run: `gh auth login`
+> Then try this command again.
+
+## Step 2: Understand the Feature Request
+
+Use AskUserQuestion to understand what the user wants:
+
+**Question 1: Feature Category**
+- Header: "Category"
+- Options:
+  - "New command" - A new /wtfp:* slash command
+  - "Workflow enhancement" - Improve existing writing workflow
+  - "Installation/CLI" - Improve npx wtf-p experience
+  - "Template/Format" - New venue template or output format
+  - "Integration" - Connect with other tools (Zotero, Overleaf, etc.)
+
+**Question 2: Complexity**
+- Header: "Scope"
+- Options:
+  - "Small tweak" - Minor change to existing behavior
+  - "New capability" - Add something that doesn't exist
+  - "Major feature" - Significant new functionality
+
+## Step 3: Gather Feature Details
+
+Based on category, ask targeted questions:
+
+**For new command:**
+- What should `/wtfp:new-command` do?
+- When would you use it in your writing workflow?
+- What inputs does it need? What outputs?
+
+**For workflow enhancement:**
+- Which workflow needs improvement?
+- What's missing or frustrating?
+- How should it work differently?
+
+**For templates/formats:**
+- Which venue or format?
+- Do you have example requirements?
+
+## Step 4: Explore Use Case
+
+Ask user:
+- What problem does this solve for you?
+- How often would you use this?
+- Have you tried any workarounds?
+
+## Step 5: Check for Duplicates
+
+Search existing issues:
+```bash
+gh issue list --repo akougkas/wtf-p --search "[KEYWORDS]" --limit 5
+```
+
+If similar issues exist, show them to the user and ask:
+- "These similar issues exist. Should we add to one of these, or create a new issue?"
+
+## Step 6: Draft the Feature Request
+
+Create a draft:
+
+```markdown
+## Feature Description
+[Clear description of the feature]
+
+## Use Case
+[Why this is needed, what problem it solves]
+
+## Proposed Solution
+[How it should work, with examples]
+
+### Example Usage
+```
+/wtfp:new-command
+> [Expected interaction]
+```
+
+## Alternatives Considered
+[Other approaches, if discussed]
+
+## Additional Context
+[Related features, prior art, mockups]
+```
+
+## Step 7: Offer Implementation Path
+
+Ask user:
+- Header: "Next Step"
+- Options:
+  - "Create issue only" - Submit as feature request for maintainers
+  - "I'll implement it" - Create issue + guide through PR process
+  - "Help me implement" - Claude assists with implementation
+
+If user wants to implement, transition to `/wtfp:contribute` workflow.
+
+## Step 8: Create the Issue
+
+If confirmed:
+
+```bash
+gh issue create \
+  --repo akougkas/wtf-p \
+  --title "feat: [SHORT_TITLE]" \
+  --body "$(cat <<'EOF'
+[FULL_BODY_HERE]
+EOF
+)" \
+  --label "enhancement"
+```
+
+## Step 9: Report Success
+
+Show the user:
+- Issue URL
+- Issue number
+- Encourage voting/commenting to show interest
+- If they want to implement: next steps
+
+</process>
+
+<tips>
+
+**Good feature requests include:**
+- Specific use case (not just "it would be nice")
+- Example of how it would work
+- Explanation of why existing features don't solve this
+
+**Signal boost:** Encourage users to share the issue link with others who might want the feature. More reactions = higher priority.
+
+</tips>

package/vendors/claude/skills/wtfp/echarts/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: wtfp-echarts
+description: Generate publication-quality charts using Apache ECharts
+allowed-tools:
+  - Bash
+  - Read
+  - Write
+---
+
+# ECharts Generator Skill
+
+Use this skill to create charts from data for papers, posters, or slides.
+
+## Usage
+
+Generate an HTML file with ECharts configuration.
+
+### Example Template
+```html
+<!DOCTYPE html>
+<html>
+<head>
+    <meta charset="utf-8">
+    <script src="https://cdn.jsdelivr.net/npm/echarts@5.4.3/dist/echarts.min.js"></script>
+</head>
+<body>
+    <div id="main" style="width: 800px;height:600px;"></div>
+    <script type="text/javascript">
+        var myChart = echarts.init(document.getElementById('main'));
+        var option = {
+            title: { text: 'ECharts Example' },
+            tooltip: {},
+            xAxis: { data: ["A", "B", "C", "D"] },
+            yAxis: {},
+            series: [{ name: 'Sales', type: 'bar', data: [5, 20, 36, 10] }]
+        };
+        myChart.setOption(option);
+    </script>
+</body>
+</html>
+```
+
+## Strategy
+1.  Receive data and chart requirements.
+2.  Generate ECharts configuration object.
+3.  Inject into HTML template.
+4.  User can open HTML in browser to view/export.

package/vendors/claude/skills/wtfp/marp/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: wtfp-marp
+description: Compile Markdown+CSS to HTML posters or PDF slides using Marp CLI
+allowed-tools:
+  - Bash
+  - Read
+  - Write
+---
+
+# Marp Compiler Skill
+
+Use this skill to compile Markdown presentations or posters to HTML or PDF.
+
+## Commands
+
+### Compile to HTML (recommended for posters)
+```bash
+npx @marp-team/marp-cli input.md -o output.html
+```
+
+### Compile to PDF (recommended for slides)
+```bash
+npx @marp-team/marp-cli input.md -o output.pdf
+```
+
+### With custom theme
+```bash
+npx @marp-team/marp-cli input.md --theme theme.css -o output.pdf
+```
+
+## Marp Markdown Format
+
+Marp uses extended Markdown. Slides are separated by `---`.
+
+Example:
+```markdown
+---
+marp: true
+theme: default
+---
+
+# Slide 1
+Content
+
+---
+
+# Slide 2
+More content
+```