prose-setup
Clone or update the OpenProse repository to ensure AIWG prose tools hook into the latest version of the specification and examples
What this skill does
# Prose Setup Skill
You ensure the OpenProse repository is cloned and up-to-date so that all prose-integration skills have access to the latest specifications, examples, and guidance.
## Triggers
- "setup prose" / "install prose" / "install openprose"
- "update prose" / "update openprose"
- "clone prose repo"
- "ensure prose is available"
- "prose setup"
## Behavior
### Step 1: Check Current State
Check if OpenProse is already cloned:
```bash
# Check default location
ls /tmp/prose/skills/open-prose/prose.md 2>/dev/null
# Check configured location (from addon config proseRoot)
```
### Step 2: Clone or Update
**If not present** — clone from GitHub:
```bash
git clone https://github.com/openprose/prose.git /tmp/prose
```
**If already present** — pull latest:
```bash
cd /tmp/prose && git pull origin main
```
### Step 3: Verify Installation
After clone/update, verify key files exist:
| File | Purpose | Required |
|------|---------|----------|
| `skills/open-prose/prose.md` | Prose VM specification | Yes |
| `skills/open-prose/forme.md` | Forme Container specification | Yes |
| `skills/open-prose/guidance/patterns.md` | Design patterns | Yes |
| `skills/open-prose/guidance/antipatterns.md` | Antipatterns guide | Yes |
| `skills/open-prose/guidance/tenets.md` | Design tenets | Yes |
| `skills/open-prose/examples/` | Example programs (50+) | Yes |
### Step 4: Report Version
```bash
cd /tmp/prose && git log -1 --format="%H %ci %s"
```
### Step 5: Output Summary
```markdown
## OpenProse Setup Complete
**Location**: /tmp/prose
**Version**: {commit hash} ({date})
**Latest commit**: {subject}
### Verified Files
- [x] prose.md (Prose VM spec)
- [x] forme.md (Forme Container spec)
- [x] guidance/ (patterns, antipatterns, tenets)
- [x] examples/ ({count} examples)
### Available Skills
All prose-integration skills now have access to the latest OpenProse specification:
- `/prose-reader` — parse contracts
- `/prose-run` — execute programs
- `/prose-validate` — validate grammar
- `/forme-manifest` — generate wiring manifests
```
## Custom Install Location
If the user wants Prose installed somewhere other than `/tmp/prose`, they can configure it:
```yaml
# In aiwg.yml
addons:
prose-integration:
proseRoot: /path/to/prose/skills/open-prose
proseRepoPath: /path/to/prose
```
The clone target is `proseRepoPath` (repo root), and `proseRoot` is `{proseRepoPath}/skills/open-prose`.
## Auto-Setup
Other prose-integration skills should check for the Prose installation before operating. If not found, suggest running `/prose-setup` first:
```markdown
OpenProse not found at /tmp/prose/skills/open-prose/prose.md
Run `/prose-setup` to clone the latest OpenProse repository, or configure
a custom path in aiwg.yml under addons.prose-integration.proseRoot
```
## Model
This skill runs on **Haiku** — it's just git operations and file checks.
## References
- @$AIWG_ROOT/agentic/code/addons/prose-integration/README.md — prose-integration addon overview
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/research-before-decision.md — Verify installation state before cloning or pulling
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/human-authorization.md — Confirm custom install location with user when non-default path requested
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference for AIWG addon configuration
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.